What happens after the assessment (and the mistake most organisations make)

The results come back. The scores are on the table. And then, in almost every organisation I have worked with, the same thing happens.

Someone in the room looks at the lowest-scoring dimension and says: “Right. We need to fix this.”

It is a reasonable instinct. It is also, in most cases, the wrong call.

What the score is actually telling you

A digital maturity score is a map, not a verdict. The number tells you where you are. It does not automatically tell you where to go next.

The mistake is treating the gap as the instruction. If your Automation score is 28% and your Process score is 61%, the intuitive response is to invest in automation. You are behind. You need to catch up.

But a 28% Automation score on top of a 61% Process score usually means your processes are solid enough to support automation investment. That gap is actionable.

A 28% Automation score on top of a 31% Process score is a different problem entirely. Automating an unstandardised process does not close the gap. It locks the inconsistency in at scale. The bottleneck is the process, not the automation. Investing in automation first makes the underlying problem more expensive to fix later.

This distinction, between a gap that is ready to close and a gap that reveals a dependency, is one of the most important things the assessment tells you. And it is the one that gets missed most often.

The dimension that almost always surprises people

After more than 100 assessments across 13 sectors, the finding that catches organisations off guard most consistently is the People score.

Most leadership teams going into an assessment expect their technology and process gaps to be the story. The People dimension (digital literacy, change management capability, leadership alignment, training infrastructure) tends to be treated as a soft consideration, something to address alongside the main work.

In the majority of assessments I have delivered, the People dimension is not alongside the main work. It is the main work.

A manufacturing plant with strong OEE tracking, a well-configured MES, and a connected supply chain can still produce unreliable data if the people operating the system do not understand why consistency matters or what they are supposed to do when something does not fit the workflow. The system captures what the people enter. If the people are inconsistent, the data is inconsistent. A dashboard built on inconsistent data is not a digital factory. It is an expensive source of arguments.

What a useful next step actually looks like

The output of a digital maturity assessment should not be a three-year transformation roadmap. In my experience, three-year roadmaps produced immediately after an assessment are almost universally too ambitious, too sequential, and too focused on the technology layer.

A more useful output is a priority list: three things, sequenced by dependency, with a 90-day focus on the first one.

Three things because more than that diffuses accountability. Sequenced by dependency because starting with the wrong one sets everything else back. Ninety days because it is long enough to see results and short enough to course-correct if something is not working.

The assessment gives you the raw material for that list. The work is in the interpretation: which gaps are foundational and which are downstream, which wins will build internal credibility for the harder changes that follow, and which problems look urgent but are actually symptoms of something more basic.

What this looks like in practice

One assessment I delivered was for a mid-sized precision engineering firm that came in expecting their digital maturity gaps to be primarily in Automation. They had been deferring automation investment for years and felt behind their peers.

Their Automation score was below the sector average. But their Process score was lower, and their People score was lower still. The leadership team had been investing in individual tools without a shared understanding of what they were trying to achieve or why. Different departments were using different systems with no integration. The floor supervisors had not been involved in any of the technology decisions.

We agreed on three priorities. First: standardise the top five operational processes before touching any automation. Second: run a series of structured conversations with floor supervisors to surface the workarounds they had built into the existing system, because those workarounds were the real process documentation. Third: agree on a single data platform before adding any new tools.

Automation investment came six months later, after the foundation was in place. It landed well because the processes were clean and the people understood what the system was supposed to do.

The assessment is a starting point

A digital maturity score is not a report card. It is the beginning of a conversation about where to focus, in what order, and why.

That conversation is where the real value sits. The score tells you what is true. The interpretation tells you what to do with it. And the sequence you agree on, honest about dependencies, realistic about capacity, focused on the right 90 days rather than the perfect three years, is what determines whether the assessment becomes change or becomes a document that lives in a shared drive.

If you are curious what your organisation’s scores would tell you, and what the next step would actually look like, that is what the discovery call is for.