Thought 01 · Digitalization

A maturity framework for digitalization

Across X all kinds of projects, it’s always critical to achieve as much clarity and common ground as possible with all stakeholders. Technical and business teams don’t always share the same language, and the messy reality of the day-to-day operations doesn’t help to create a clean picture.

After finding myself in this situation repeatedly, I gradually developed and refined this framework. It is deliberately simple, but I’ve found it useful for several purposes:

  • building a shared vocabulary with domain experts about the digital maturity of our processes, helping us improve our understanding of the current situation
  • identifying realistic next steps and setting clear expectations about what each one requires
  • making progress visible
Process maturityFrom visibility to autonomous action
01 / 04
01
Display

Just make it visible.

It won’t solve all your problems, but making data visible in the right place can make a huge difference. The hardest work here is breaking information silos and consolidating what’s relevant.

What it looks like

A screen showing stock levels in front of a machine. A dashboard that pulls from three systems that never talked to each other.

Watch out for

Data living in silos, requiring an analyst to extract, or only visible to someone who already knows where to look.

Select a stage to inspect it. Every stage earns the next one.

The way I see it, you can skip a stage, but not the work of understanding what happens there.

A good example: a company tried to implement autonomous forklifts on the shopfloor, directly from completely manually driven ones. The vendor had a sophisticated system that required a lot of structure and standards we were not even close to being able to provide. It never went anywhere. Eventually I led the development of a more pragmatic product that evolved as we learned. By the time I left, we reached the ‘Assist’ stage, where each forklift driver had a screen telling them when and where to pick up containers and where to deliver them. The product had become a critical part of the process and created strong foundations for future automation.

I’ve intentionally left AI out of the framework because it doesn’t affect its core. It changes what’s possible at each stage, or how fast you can move through them, but it doesn’t remove the lessons implicit in each stage.

With AI it can be even more tempting to jump directly to ‘Automate’, but more often than not, starting with a more manual approach can expose missing data, undocumented exceptions and the judgments people apply without necessarily being able to articulate them. That knowledge becomes the context necessary to make AI workflows reliable enough for production.

The framework isn’t intended as a rigid sequence for an entire company. A single process can contain tasks at very different stages. The useful question is not “How digitally mature are we?” but “What would the next useful level look like for this particular task?”

Next thoughtWhere AI fits in messy business processes