Digital maturity is an operating capability

Look at how the work happens

A new system can look like progress long before it changes anything.

An organisation can buy a customer relationship management system while the useful customer history stays in personal inboxes. It can publish a data strategy while teams spend meetings arguing about whose figures are right. It can launch a platform that people avoid because the old spreadsheet makes a difficult task easier.

These are useful clues. They tell you to look beyond the purchase and ask what the organisation needs to make it work.

Who owns the process? Can people get help? Is there time to learn? Does the new approach make sense when something goes wrong? The answers reveal more about digital maturity than a list of installed software.

Look across the organisation

Technology depends on the conditions around it. A clear process helps people use a system consistently. Reliable information helps leaders make decisions. Good training has more chance of working when people can practise and their managers support the change.

Start with practical questions across the organisation:

• Strategy and leadership: a clear direction, understood priorities and people able to make the necessary decisions

• People and culture: the skills, confidence, time and support to work in new ways and raise problems

• Processes and operations: clear responsibilities and a way of working that holds up beyond the person who first designed it

• Technology and data: dependable, secure tools and information that people can find, understand and trust

• Customer and stakeholder experience: whether the change makes things work better for the people using or receiving the service

Consider environmental responsibility throughout: how do technology choices, data practices and day-to-day operations affect the resources the organisation uses?

A strength in one area cannot repair every weakness elsewhere. Good software cannot decide who has authority to approve a request. A committed leader cannot personally support every user indefinitely.

Look for the connections, especially where one part of the organisation is carrying the cost of a decision made elsewhere.

Understand the five levels

The five levels below offer a way to describe how consistently these capabilities appear in practice. Use them as a shared language for discussing the current position and the next useful change.

The right level depends on the work, the risks and the organisation's ambitions. There is little value in pursuing the highest level everywhere simply to improve a score.

Initial means work is largely reactive. Tools and processes have accumulated to meet immediate needs. People often rely on their own knowledge and workarounds to keep things moving. Start by making the important work visible and identifying who needs to own it.

Emerging means useful practices are taking shape. One team or a committed leader may be making progress, while other parts of the organisation work differently. The question is how to make that progress repeatable without losing what makes it useful.

Defined means the intended way of working is clear. Responsibilities, processes and basic standards have been agreed. Check that people understand and use them; a document on its own is weak evidence.

Managed means the organisation uses evidence to run and improve the work. Owners review adoption, outcomes and risks, then act on what they find. Measures are useful because someone can make a decision with them.

Optimising means improvement is part of everyday management. The organisation learns from experience and changes its approach deliberately, including when priorities or circumstances change.

Describe the level the evidence supports. A promising plan for the next level belongs in the improvement work, not in the account of what is already happening.

Check the account against the evidence

Leaders, managers and the people doing the work may describe the same change differently. Each can see something the others miss.

A sponsor may know why a system was introduced. A team member may know why its approval process adds a day's delay. Anonymous feedback may reveal a concern that people do not feel able to raise in a meeting. Records and observed work can help establish how often the problem occurs.

Use those perspectives together. Ask people to show how a recent piece of work moved from start to finish. Compare the intended process with what actually happened, including the awkward exception.

When accounts disagree, investigate. A difference between the leadership view and daily experience may be the most useful finding in the assessment.

Keep the evidence and its limits visible. If a judgement rests on a small sample or one team's experience, say so. A precise-looking score should not hide an uncertain conclusion.

Choose a next step you can sustain

An earlier-stage organisation may get most value from a dependable standard tool, clearer ownership and time for people to learn. A business can use relatively little technology and still run a sound service.

More complex digital work brings a larger commitment. Developing proprietary software, connecting critical systems or introducing AI into an important decision process needs people who can manage the resulting service and its risks. The effort continues after launch.

Before investing, ask what the change requires from the organisation. Who will decide how it works? Who will maintain the information? How will problems be spotted and resolved? What else will the team need to stop or postpone to make room?

Sometimes the right answer is to invest. Sometimes it is to simplify the process, connect tools you already have or wait while an essential responsibility is settled.

Turn the assessment into a decision

A useful baseline should lead to a short, explainable set of priorities. For each one, record the problem, the evidence, the person responsible and what a better result would look like.

Choose a review point that gives the change time to show up in real work. Check whether people are using it, whether the task is easier or more dependable, and whether it has created a problem elsewhere.

The purpose of understanding digital maturity is to make these decisions better. Know how the organisation works now, decide what it needs to become capable of next, and make a change it can carry through.