From Scores to Roadmap: Turning a Maturity Assessment Into a Plan

The moment after a maturity assessment is where most of them fail. The results arrive, there is a short discussion, a few people nod at the radar chart, and then everyone returns to their day jobs. Six months later, the scores would be exactly the same.

The problem is rarely a lack of insight. It is the gap between knowing where you stand and knowing what to do on Monday. This article sets out a practical way to close that gap: from scores, to targets, to priorities, to a roadmap you can actually run.

Step 1: Read the results as a profile, not a number

The overall score is the least useful number in the report. An organisation scoring 2.0 overall might be consistently at level 2 everywhere, or strong in some areas and weak in others. Those are very different situations needing very different plans.

Look at three things instead:

1. The shape. Which areas are noticeably higher or lower than the rest? On a radar chart, look for the dents.
2. The lowest individual answers. A single question answered at level 1 can be a serious weakness hiding inside a respectable area average.
3. Dependencies. Some weaknesses hold others back. If nobody owns data quality, improving reporting will not stick.

Step 2: Set a target for each area

Not every area needs to reach the top level. Maturity costs time and money, and the right target depends on how much the capability matters to you.

A useful rule of thumb is to aim one level up in each area over the next year, and to accept that some areas can stay where they are. Then adjust:

• Raise the target for areas that are critical to your strategy or where weakness creates real risk.
• Hold the target for areas that are adequate for your size and situation.
• Never target two levels up in a year unless you have exceptional resources. Skipping a level usually means building advanced practices on weak foundations.

The assessments on this site let you set a target for each area in the results, and the report then highlights the gap between where you are and where you want to be.

Step 3: Turn gaps into specific changes

A gap such as "Performance Measurement & Review: level 1, target 2" is not yet actionable. To make it actionable, go back to the individual questions behind the score.

Each question describes concrete behaviour at each level. The difference between the level you chose and the next level up is, in effect, a description of the change you need to make. For example:

• Today: "Strategy is reviewed once a year during budget setting."
• Next level: "Progress against strategic priorities is reviewed quarterly, and priorities are adjusted when circumstances change."

That gap translates directly into a change: introduce a quarterly strategy review with a clear agenda and decision rights. The "Where to focus" section of each results report lists these today-versus-next pairs for the questions with the biggest gaps.

Step 4: Choose the few that matter most

You will now have more candidate changes than you can deliver. Choose ruthlessly. Score each candidate against three questions:

• Impact: how much would this improve outcomes, reduce risk or unblock other improvements?
• Effort: how much time, money and attention would it take?
• Readiness: is there an owner, and is now a sensible moment?

Pick three to five changes for the first six months. More than that and attention spreads too thin; the improvements become side projects that never finish.

Favour changes that are foundational (they make later improvements possible) and visible (people can see that something has changed, which builds momentum).

Step 5: Sequence the roadmap

Arrange the chosen changes over time. A simple structure works well:

• Now (next three months): quick, foundational changes. Assigning owners, agreeing definitions, introducing a regular review.
• Next (three to nine months): changes that build on the foundations. New processes, tools, training.
• Later (nine to eighteen months): changes that depend on earlier work, or that need budget you do not yet have.

Keep the roadmap to a single page. Its purpose is to communicate the plan and keep it visible, not to manage every task. Detailed planning belongs in whatever project or team tools you already use.

Step 6: Connect it to how the organisation already works

Improvement roadmaps fail when they live outside the normal rhythm of the business. Build the roadmap into existing mechanisms:

• Put the improvements into the relevant teams' objectives or plans, not a separate "maturity programme".
• Review progress in an existing leadership meeting, briefly, once a month or once a quarter.
• Tie any resource requests into the normal budget cycle.

If your organisation struggles with this kind of follow-through in general, it may be worth assessing that directly. The Strategic Planning & Alignment assessment looks at how well priorities are set, cascaded and turned into action.

Step 7: Reassess and adjust

Put a date in the diary to repeat the assessment, ideally with the same people, after six to twelve months. Compare the profiles. Expect some areas to have moved and others not, and be curious rather than defensive about why.

Then update the roadmap. Some changes will be done; some will need rethinking; new priorities will have emerged. A roadmap is a living plan, and the reassessment is what keeps it honest.

A worked example

Imagine a mid-sized services firm assesses its strategic planning and finds:

• Strategy Development & Vision: 2.25
• Strategic Communication & Cascade: 1.5
• Resource Allocation & Prioritisation: 1.75
• Performance Measurement & Review: 1.25

The average of 1.7 across these areas hides the real story. Leaders have a reasonable strategy, but few people know about it, budgets do not follow it, and nobody tracks whether it is working.

Targets: communication and performance tracking up one level each; resource alignment held for now. Priorities for the first six months:

1. Now: define five measures of strategic progress and review them quarterly at the leadership meeting.
2. Now: a one-page strategy summary, explained by each leader to their team.
3. Next: require new budget requests to show which strategic priority they support.

Three changes, all achievable, all directly linked to specific answers in the assessment.

Frequently asked questions

How long should an improvement roadmap cover?

Twelve to eighteen months is usually right. Shorter and you cannot show meaningful progress; longer and the plan becomes speculative.

Should every area have an improvement action?

No. It is fine, and often wise, to leave some areas alone for a year while you focus on the ones that matter most.

Who should own the roadmap?

A senior sponsor should own the roadmap as a whole, with a named owner for each individual improvement. Without a single sponsor, roadmaps tend to drift once the initial enthusiasm passes.