Skip to content
Systems & decisions

Why digital maturity gets harder before it gets easier

Yopla3 min read

Joining things up gives you more capability. It also gives you more to coordinate. That’s where a lot of organisations get stuck.

Make room for the next step

Illustrative concept: Capability / Capacity / Progress. Not a measured result.

Digital maturity is how reliably an organisation can use technology, information and clear decisions to get work done and improve it. You can see it in whether people can do the job without having to work around the system or rely on whoever happens to know the answer.

At first, everything is a bit disjointed. Different teams have their own spreadsheets, systems and ways of getting things done. People fill the gaps. It works, in the sense that the work gets done. It’s just much harder if the person who knows how it works is off.

So you start connecting things. You put shared records in a CRM, link up a few tools and take repetitive jobs off people’s plates. It’s a genuine improvement. Then comes the “oh no” moment. You’ve made each team better at what it does, but some of the silos are deeper than they were before.

It’s easy to miss this if you only look at the technology. A system can pass data in seconds. A decision can still wait a week for one person. The more work you connect, the more often you hit the limit of what that person, or that team, can absorb.

What the systems can do togetherCoordination people have to do
handover pressure01234
Handover pressure
  1. 0
  2. 1
  3. 2
  4. 3
  5. 4
Figure 1. The coordination cost of connecting work. Illustrative, not measured data. The dashed line comes back down only if ownership, decisions and handovers change too. It isn’t a benefit you get just for reaching the next level.

What the five levels look like in practice

These are the levels we use in Yopla. They describe how consistently an organisation makes and carries through digital decisions. Different parts of the same organisation can be at different levels.

0Initial0–24 / 100

People make it work. Tools solve immediate problems. To finish a piece of work you often need to know who to ask. Start by making the job and its owner visible.

1Emerging25–49 / 100

Good practice exists in pockets. A team has a useful CRM or a working automation. Elsewhere, the same work happens another way. The challenge is spreading what works without turning the team that built it into a permanent helpdesk.

2Defined50–74 / 100

Teams know how the work fits together. They use shared records, know who owns each handover, and can deal with common exceptions. This is coordinated. A process diagram doesn’t count if people still have to go around it to get the job done.

3Managed75–99 / 100

Owners use evidence to improve the work. They see where cases get stuck, review adoption and risk, and change something as a result. The challenge is choosing measures that help people decide, not just collecting more numbers.

4Optimising100 / 100

Improvement is part of everyday work. Teams can test, learn and change direction without unpicking everything else. That doesn’t mean changing constantly. Sometimes the most mature decision is to leave a dependable process alone.

What the number can hide

Strategy may be ahead of people’s capacity to act on it. A team can be excellent at its own job and still struggle to hand work to the next one. A website can improve while the reports used to run the service still need a spreadsheet rescue. The gap between those things is often more useful than the headline score.

Look at six dimensions together: strategy and leadership, people and culture, processes and operations, technology and data, customer and stakeholder experience (growth), and sustainability. The app scores sustainability separately, even though it matters in every dimension.

The flat organisation that looks great on a screen

Digital systems like a simple picture. Everyone can see what’s happening, information flows across teams and decisions don’t climb three levels of management. It sounds brilliant. It can feel very different if it means everyone can now interrupt you, nobody knows who has the final say, or the expertise you’ve built gets treated as an unnecessary layer.

Don’t flatten the people. Flatten the route the work has to take. Keep the depth of expertise and make it clear who has authority, what everyone can see, when to ask for help and how to escalate an exception. Shared access isn’t shared accountability. And sharing insight means sharing some of the power that came with knowing things other people didn’t. You can’t solve that with a permissions screen.

Change the organisation is being asked to absorbRoom people have to absorb it
bandwidth bottleneckRoll-out startsOld and new work overlapMake room for the change
Bandwidth bottleneck
  1. Roll-out starts
  2. Old and new work overlap
  3. Make room for the change
Figure 2. A change can be right and still be too much. Illustrative, not a forecast. The gap closes when you stop asking teams to do both versions of the work, make time to learn and give someone authority to resolve exceptions.

When you free up time, you can keep it as breathing room or spend it going faster. If the ambition catches up, the next constraint shows up.

What to do when you hit the gap

  • Follow one real job across teams. Find the wait, the repeated entry or the decision only one person can make.
  • Name the decision owner and the record everyone can trust. Give people a way to flag exceptions and get help.
  • Take something off the team’s plate. Retire the duplicate step once the new way works, then check whether waiting or rework actually fell.

That’s also how you build digital sovereignty. It’s not another maturity level, and it doesn’t mean building everything yourself. It means having enough control of your data, decisions and systems to change how you work without being stuck with one supplier or relying on the one person who knows where everything lives.

Related reading: Digital maturity is an operating capability.

All insights