Stop Grading Design on a Single Maturity Score

You hire a consultant, run the assessment, and get a number back. Level 3 of 5. It feels like progress. Then you try to do something with it and freeze. Level 3 in what? Your research is strong but your leadership has no seat at the table. Your delivery is fast but your standards are all over the place. One score buried all of that. That is the trap with maturity models. They take a messy, multi-part reality and squash it into a single ladder rung, which tells you where you sit and nothing about what to fix.

The better tool already exists. Rate the parts of your design org on their own, like a report card, and the fog clears. Here is how to think about it and what to do with your team.

The deep cut

• Grade the parts, not the whole. Peter Merholz rates twelve qualities on their own instead of one linear score.
• A single number hides where you are broken. An org can sit at many points on the maturity line at once, so the average lies.
• Score each quality, then fix the lowest one first. The report card points straight at the gap worth your Monday.

Why one score always lies

A maturity ladder assumes design grows in one straight line. Reach the next rung, level up, repeat. Real orgs do not work that way. Merholz found this while researching for his book: an org sits at multiple places along the maturity line at once, which makes a single number useless for diagnosis. You cannot fix an average.

Robert Powell sees the same thing inside a company as big as Shell, where maturity shows up in pockets, across regions, across projects. One meeting treats a Figma file as proof. The next asks why design is not on the board. A company-wide score would flatten both into a lie. The ladder feels tidy. Your org is not tidy.

What a report card actually measures

Swap the ladder for a set of qualities you grade one at a time. Merholz and Kristin Skinner lay out twelve qualities of effective design organizations, sorted into three buckets: Foundation, Output, and Management. Foundation is why the team exists, shared purpose and empowered leadership. Output is the work itself, quality and range. Management is the part leaders skip, running the team like a team.

That last bucket is where design usually bleeds. They warn against putting a design visionary in charge, because the skills that make someone a great creative director have almost nothing to do with running an org. A report card catches that. A single score wraps a strong portfolio around weak operations and calls it Level 4.

Tie every quality to the business, or skip it

Grading in a vacuum is its own trap. Erika Hall told Merholz that most maturity models are nonsense because they ignore the business model entirely. A polished process that serves an extractive business is just proficiency at candy-coating harm. Step zero is checking that the work actually helps the people it touches.

Powell makes the same point from the data side. He splits maturity into three levels by how a company uses data: data inspired, where the loudest voice still wins, data informed, where teams measure but stay siloed, and data driven, where one shared source settles the why before anyone designs. Notice these are not rungs to climb blindly. They describe how business, user, and technical needs line up. Grade that alignment, not your position on someone else's chart.

Fit the card to your context, not the chart

The report card only works if you build it for your org. Nezar Mansour makes this case for design systems: a maturity chart that shows a next level your team is not striving for breeds false pressure. A two-person team serving one product does not need Atlassian's system. Chasing the ladder's top rung would waste them.

Mansour offers three tests instead of a rung: iteration, alignment, and impact. Is the work an ongoing process, does it match company goals, and can you measure what it changed. Those are questions, not scores handed down from a template. Powell pushes the same discipline inward, asking which team is struggling and why, which is producing the best return. Point the assessment at your own operating model. If you cannot claim to improve your own process, you have not earned the word mature.

Three questions for your team

• Which single quality on our report card is lowest right now, and what is the one move that raises it this quarter? Do not average. Pick the weakest and act.
• Where does our design work sit against the business model, in Hall's sense: are we serving the people it touches, or just getting better at polishing the wrong thing?
• Are we chasing a maturity level nobody on the team actually needs? Name the rung we are striving for and prove it fits our size and goals, the way Mansour asks of a design system.