In 2023, I gave a talk at an Agile conference on evolution versus maturity in agile environments. The idea came from years of walking into organizations that had passed a maturity assessment, received a glowing report, and then stalled completely.
The pattern kept repeating. An organization runs a maturity assessment. It scores well. Leadership celebrates. The consultants leave. Two years later, the same organization wonders why nothing improves anymore. The problem sits in the word itself. Maturity implies a finish line. Agile environments have no finish line. Applying a maturity model to an agile environment is a category error. You are measuring a living system with a tool built for a static one. This article explains why that framing fails, what happens when organizations act on it, and what an evolution-based approach looks like in practice.Where the Maturity Frame Breaks
Maturity models come from a manufacturing mindset. They assume a defined end state, a set of levels, and a linear climb. Level one through level five. Reach the top, and you are done. That logic works for processes that stay fixed. It fails for environments built on adaptation. Agile environments exist because conditions change. Markets shift. Teams turn over. Priorities move. The whole point of working this way is to respond to change continuously. A model that says "you have arrived" contradicts the reason the environment exists. There is a second, quieter problem. Most maturity assessments measure evidence of practice rather than the reality of behaviour. If something is observed, documented, or verbally confirmed, it gets a check mark. I have watched organizations game this without even meaning to. They produce the documentation. They rehearse the ceremonies. They tell the assessor the right things. The boxes get checked. The gap between "we documented it" and "we actually live it" is where organizations rot. A binary check mark cannot see that gap. It records that a standup happens. It cannot record that nobody in the standup tells the truth.What Happens After the Trophy
Here is the sequence I have seen play out repeatedly. An organization invests in a transformation. It hires coaches, restructures teams, and runs the maturity assessment. The score comes back high. Leadership presents the result to the board as proof the investment paid off. Then the behaviour changes.- Improvement budgets shrink. The work is "done," so funding moves elsewhere.
- Coaching roles disappear. Mature organizations are supposedly no longer in need of them.
- Retrospectives go stale. The pressure to find problems fades because the report said there were none left.
- Leaders stop looking. The assessment gave them permission to look away.
Evolution as an Operating Philosophy
The frame I use instead is evolution. The difference goes deeper than vocabulary. These are two different operating philosophies. Maturity asks: how close are we to done? Evolution asks: what is constraining us right now? Under a maturity philosophy, assessment is an event. You run it once, get a score, and file the report. Under an evolution philosophy, assessment is a rhythm. You look at the system, find the current constraint, fix it, and look again. The next look reveals the next constraint. There is always a next constraint. This mirrors something I learned competing in jiu-jitsu. I never wore my medals around after a tournament. They went in the bag as soon as I stepped off the podium. The work itself held the value. The podium was a checkpoint on the way to the next problem to solve. Organizations that operate this way treat every improvement the same way. A quick acknowledgment, then attention moves to what comes next. The destination matters. You just pass through it rather than live there. 💡 The practical test: ask your leadership team what the organization's current biggest constraint is. If the answer is "we're in good shape," you are operating on a maturity philosophy, and stagnation is already underway.What an Evolution-Based Assessment Looks Like
After years of using assessments built on the maturity model, I built my own. It grew directly out of that 2023 talk and the gaps I kept finding in the available tools. I designed it around one requirement: it must reveal the living system and always produce the next step. The assessment examines eight pillars:- Leadership: how decisions get made, communicated, and reinforced to create clarity and accountability.
- Strategic Alignment: whether priorities are clear, competing work is controlled, and the organization moves in the same direction.
- Team Enablement: whether teams can execute without constant blockers and unnecessary interruptions.
- Value Creation: whether effort translates into outcomes customers notice and appreciate.
- Trust and Transparency: whether issues surface early for resolution or fester until they explode.
- Team Health and Growth: whether the pace of work is sustainable and continuous learning is embedded in the culture.
- Strategic Budgeting: whether funding supports priorities or quietly creates conflict with them.
- Delivery and Flow: whether work moves through the system with minimal delays, bottlenecks, and rework, so teams finish what they start.
The Pillar That Breaks First
People ask me which pillar is most consistently broken when I walk into an organization. The answer, without hesitation, is Leadership. The reason is structural. We have all been taught that the leader is the boss and that the title carries power. Plenty of people swear they will never operate that way. Then they get the role, and the system pulls them toward the behaviour it was built to reward. The power grabs. The prestige. The gravity of the title. I know this pull firsthand. I fell into that trap a few times myself. I caught it, felt terrible, apologized to my teams, and corrected course. Those apologies initially hurt my credibility. Over time, they built more of it than any title ever did, because they showed the team that a leader makes mistakes and learns from them. This is why an assessment that only checks documentation misses everything important. No document captures whether a leader owns their mistakes. Behaviour captures it. An evolution-based assessment looks there.Living Without a Finish Line
Even my own turning point follows this pattern. I chased a senior executive seat for years. When I got it, I sat in my office early one morning before anyone arrived and realized I was bored. The title delivered nothing. The teams I built along the way delivered everything. Organizations experience the same hollow arrival when they "achieve maturity." The score delivers nothing. The continuous work delivers everything. Here is what this looks like in practice for you:- Retire the language of maturity levels inside your organization. Words shape behaviour.
- Assess on a rhythm. Every assessment ends with one question answered: what is our current biggest constraint?
- Fund improvement permanently. Treat it like maintenance, because that is what it is.
- Measure behaviour and outcomes. Ignore anything that can be satisfied with a document.
- Celebrate progress briefly, then move to the next constraint. Let your teams celebrate as long as they need. Your job is to already be looking ahead.

