Two years is a common timeline for agile transformations. Consultants arrive, new processes are installed, teams are trained, retrospectives begin, metrics start tracking. The organisation adopts Scrum or Kanban or SAFe. Standups happen daily. Sprint reviews are scheduled. The mechanics are in place.
This is genuine progress. Getting to an agile process is a milestone worth celebrating. The team has learned new ways of working. Leadership has invested in change. The ceremonies are no longer foreign — they are routine.
But routine is where the real test begins. Because the transformation delivered the structure. What it may not have delivered is the culture that makes the structure work. And that is where three patterns tend to emerge: behavioral lag, when methods change but culture does not. Value lag, when methods change but the visibility of ROI disappears. And momentum lag, when the organisation celebrates the adoption of new practices and mistakes the beginning of the journey for the destination.
The question after two years is not “did we adopt agile?” The question is “have we built the capability to keep improving?”
Quick Wins vs. Deep Change
The early wins of an agile transformation are visible and immediate. Ceremonies provide structure. Metrics provide visibility. Teams that were previously working in isolation start coordinating. Blockers that used to fester for weeks surface in standups and get addressed. There is momentum, there is energy, and there is often a measurable productivity bump.
These wins matter. They build confidence. They justify the investment. But they are also surface-level. They address how the team organises its work. They do not necessarily address why the team works the way it does, or what happens when the initial energy fades and the new practices settle into routine.
Deep change is different. Deep change is when retrospectives stop being a ceremony the team attends and become a mechanism the team genuinely uses to improve. Deep change is when planning meetings shift from “what are we building?” to “what are we achieving, and why does it matter?” Deep change is when velocity is no longer treated as a target to hit but as a diagnostic tool to interpret.
That shift — from compliance with agile practices to embodiment of agile principles — does not happen in two years. It happens gradually, through repeated cycles of observation, adjustment, and learning. And it requires something the typical transformation does not provide: sustained support over time, not episodic intervention.
The DIY Trap
Most teams, by the end of a two-year transformation, know what is not working. Retrospectives are producing action items that go nowhere. Planning is still reactive. Velocity charts tell a story the team cannot quite interpret. The problems are visible. The frustration is real.
What the team cannot see is the pattern connecting those problems, because they are embedded in the system. When you are part of a system, certain things become invisible — not because you lack intelligence or commitment, but because perspective has limits. You see what you are conditioned to see. You work around what has become familiar. The pattern that might explain everything sits just outside your field of view.
This is why DIY approaches plateau. Teams try to fix what they can see. They adjust ceremonies, they refine processes, they experiment with new tools. Some of those adjustments help. Most do not, because the team is treating symptoms without addressing the underlying structure that produces them. And no amount of effort from inside the system will bring that structure into view.
What Actually Works
Lasting change requires a different model. Not big-bang consulting that installs new processes and leaves. Not episodic workshops that deliver frameworks and hope the team figures out the rest. What works is sustained, low-intensity support over time — the kind of support that helps teams build interpretive capability, not just adopt new practices.
Weekly conversations matter more than quarterly workshops. A coach who observes the team’s retrospective every two weeks, asks the questions the team has stopped asking, and helps them see the patterns they cannot see from inside — that presence compounds over time in ways that intensive intervention does not.
The goal is not to make the team dependent on external support. The goal is to build the team’s capability to see their own system clearly, so that they can continue improving long after the support ends. That takes time. It takes repetition. And it takes someone outside the system who can hold up a mirror without having a stake in what the reflection shows.
The Two Engines of Lasting Change
For change to stick beyond the initial transformation, two things need to function well. At the team level, retrospectives must operate as genuine improvement engines, not as theatre. At the organisational level, executive support and knowledge management must embed what the team learns, so that insights do not disappear when people move roles or leave the company.
When only one of these engines works, progress stalls. A team that runs excellent retrospectives but lacks organisational support will improve locally and then hit a ceiling when they encounter constraints they cannot change on their own. An organisation that provides executive backing but whose teams run ineffective retrospectives will see no improvement to support, because the teams are not generating the insights that would justify intervention.
Both engines need to run. Retrospectives give teams the mechanism to identify and address problems within their control. Executive support and knowledge management give the organisation the capacity to address systemic issues that no single team can solve. When both are functioning, improvement becomes self-reinforcing. When either is missing, momentum degrades over time.
Culture That Holds the Long View
The most insidious form of momentum lag is when organisations celebrate intermediate milestones and lose sight of the larger purpose. “We now do Scrum” becomes the achievement, rather than the starting point. The energy that drove the transformation dissipates. The practices remain, but the curiosity does not.
Lasting change requires a culture that treats current practices not as the answer, but as the current best guess — always open to revision in light of new experience. That is a different disposition than most organisations cultivate. It is not “we have arrived.” It is “we are always learning how to work better.”
That shift does not happen through exhortation. It happens through modelling. When leadership treats retrospectives as meaningful, teams take them seriously. When the organisation invests in embedding lessons learned rather than letting them evaporate, teams see that improvement is valued, not just claimed. The culture forms around what is rewarded and what is retained, not around what is proclaimed.
What “Lasting” Actually Means
Two years of transformation is the beginning, not the end. The processes are in place. The teams are trained. The metrics are tracked. That is the foundation. What comes next determines whether the foundation supports sustained improvement or whether it becomes another set of practices the organisation performs without understanding why.
Lasting change is not the absence of problems. It is the presence of capability — the ability to see what is not working, diagnose why, and adjust deliberately rather than reactively. That capability develops slowly. It requires more than training. It requires repeated cycles of observation, interpretation, and action, guided by someone who can see what the team cannot see from inside.
The timeline for that is not two years. It is as long as it takes for the team to internalise the interpretive frameworks they need to continue improving on their own. For some teams, that happens relatively quickly. For others, it takes longer. The variable is not intelligence or commitment. The variable is how deeply the old patterns are embedded, and how much support the organisation provides to replace them with new ones.
The two-year transformation delivered the structure. The question is whether the organisation is prepared to do the work that makes the structure meaningful. And that work, more often than not, takes longer than anyone expects.
If your agile transformation delivered new processes but not lasting improvement, the missing piece is often sustained support that builds capability over time. Let’s explore how embedding change that lasts beyond the initial transformation can work for your organisation. Book a free consultation to discuss where you are now, and what comes next.
Discover more from The Software Coach
Subscribe to get the latest posts sent to your email.
