Knowing where you are isn’t the same as knowing what to change
Teams often find it helpful to have a way of describing where they are. Whether it’s through surveys, assessments, retrospectives, or research-backed models, being able to say “this roughly reflects our situation” can bring a sense of clarity and shared understanding. It gives teams language for the conditions they’re operating within, and often creates a moment of recognition.
What tends to be harder is knowing what that recognition should lead to. Once a team can describe the environment it’s in, the question shifts from understanding to action. What would actually make a difference here? Which changes are worth attempting, and which would simply make the current situation run a little more smoothly without really changing it? That’s the question I want to explore.
Recognition creates clarity — but not direction
One of the reasons I’ve been using the DORA team archetypes in recent writing is that they offer a way of talking about different team environments without reducing everything to simple ideas of “high” or “low” performance. But the archetypes themselves are not the point. They’re a lens; a way of naming conditions so that we can have a more useful conversation about what change might mean in each case.
Once a team can name the environment they’re in, the natural impulse is to start changing things. New practices are introduced, processes are tightened or relaxed, tooling is upgraded. Sometimes entire operating models are revisited. From the inside, all of this feels like progress. And yet months later a team can find itself operating in much the same way; the archetype hasn’t really shifted.
What I’ve noticed over time is that teams rarely get stuck for lack of ideas. They get stuck because most change efforts focus on improving within existing interaction patterns rather than changing those patterns.
When efficiency reinforces the wrong system
A team under constant reactive pressure may automate parts of their delivery pipeline, but still rely on escalation and heroics to keep systems running. A process-heavy team may add more structure and checkpoints, smoothing the experience of moving work through the system without questioning why so much coordination is needed in the first place. A team producing high-impact work at an unsustainable cadence may push harder to deliver faster, reinforcing risk rather than reducing it. In each case, the team becomes more efficient at operating within its current environment.
The changes that seem to matter most are rarely the most visible ones. They tend to show up in quieter shifts: who gets involved earlier in shaping work, where decisions are allowed to sit, how much responsibility a team carries end-to-end, and how often work crosses boundaries that exist largely for historical reasons. When those interactions stay the same, teams can adopt new practices indefinitely without moving very far. When they change, progress often follows even without a formal transformation programme.
This is also why copying the outward shape of “high-performing” teams so often disappoints. Practices, rituals, and tooling can be transplanted relatively easily. Interaction patterns are harder to see, and harder to change, especially when they’re reinforced by incentives, reporting lines, or unspoken assumptions about risk and control.
Orientation matters more than optimisation
For me, the question that seems to unlock helpful change is not “what should we adopt?” but “what are our current interactions actually optimised for?” This is where orientation starts to matter more than optimisation. Teams that do manage to create healthier, more sustainable environments tend to share one thing in common: they have a clear, shared understanding of who their work is for and which needs matter most right now. That understanding doesn’t prescribe solutions, but it acts as a constraint. It makes some interactions feel obviously wasteful, and others worth protecting. It helps teams judge whether a change is reducing friction for users or merely making internal life more comfortable.
Without that orientation, teams still change, but they optimise for what’s easiest to see from the inside. They remove friction for themselves while quietly creating it elsewhere; progress feels real, but it doesn’t accumulate.
When environments make meaningful change possible
Meaningful change becomes possible when we pay attention to the conditions an environment creates — and how those conditions shape everyday interactions. Many of the interactions that define a team’s experience exist to manage dependencies that have built up over time. Improving flow rarely comes from managing those dependencies better; it comes from removing them altogether.
That kind of change requires trust. Teams need the safety and autonomy to recognise the systemic issues they’re operating within and to take small, informed steps to address them. As those dependencies are removed, teams don’t move to a new environment so much as the environment itself begins to change around them.
Recognition is still valuable — it helps teams see where they are. But meaningful change tends to come from a different place: from shaping an environment that enables autonomy, supports mastery, and reconnects work to a clear sense of purpose. When teams use that environment to decide which dependencies to remove next, rather than which practices to adopt, progress starts to accumulate.
That’s the part of the conversation I find most interesting, and the one that seems to distinguish teams that adapt over time from those that simply get better at managing the same problems.
If these ideas reflect challenges you’re seeing in your own teams, I’m always happy to talk things through — just drop me a message.
