Digitalisation does not begin with technology. It begins with a decision.

Imagine buying the most expensive running shoes in the world. The sole is a technical marvel, the material weighs almost nothing. You put them on, sprint off and feel fantastic.

And end up in entirely the wrong part of town.

Why? Because in your enthusiasm for the equipment, you never asked where the finish line actually is. You are not running better. You are just running faster in the wrong direction.

Most digitalisation projects do not fail because of the technology. They fail because of unresolved decisions that were already there beforehand.

What we actually see in projects

In most companies we work with, technology is not really the issue. The software works. The cloud is set up. The licences are paid.

But nobody quite knows who is allowed to make which decision. The departments talk past each other. The kanban board does not visualise progress, it visualises chaos. Tickets move from left to right, but no one knows why.

In companies, technology almost always acts as an amplifier of the existing decision culture. If roles are unclear, a new system will not make them clearer. If responsibility is diffuse, the ERP digitalises the diffusion. If leaders postpone decisions, automation accelerates the standstill.

The real bottleneck

It is tempting to look for the bottleneck in the technology. A better model. A faster platform. A smarter agent. The solution always seems to be just one software version away.

But the real bottleneck is not technological. It is human. It is an organisation's ability to make sound decisions in time.

Who decides whether the project continues or stops? Who clarifies whether the requirements are actually understood or merely documented? Who says out loud that the budget is being burned even though the goal has changed?

Software rarely answers these questions.

Whoever believes a better tool automatically produces better decisions is digitalising their own incompetence. Only faster.

Why good digitalisation begins with understanding

In our work, digitalisation does not begin with a specification document or a tool selection. It begins with a simple question: what actually needs to be understood, decided or changed?

That sounds trivial. In practice, it is not.

An example: a company wants to digitalise its project control. Management talks about efficiency, IT talks about interfaces, project leaders talk about overload. Three perspectives, three different problems, one shared budget.

If we answer the technology question first in such situations, we solve the wrong problem. The real work lies in making visible what is actually happening. Which decisions are outstanding? Where does energy drain away in approval loops? Which responsibilities are unclear?

Structure before digitalisation

Our experience from more than 40 mandates across 11 industries can be condensed into one sentence:

Do not digitalise first and understand afterwards. Understand and structure first, then digitalise with intent.

Goals, roles, processes, information flows and decision paths must be sufficiently understood and clarified before technology can meaningfully support, automate or scale anything.

A system can be technically implemented without having arrived organisationally. Implementation is provisioning. Adoption only shows up in real behaviour. Stabilisation means the new way of working also holds up under pressure.

What this means for leaders

Leaders who delegate digitalisation as an IT project miss the decisive point. Technology is rarely the problem. The problem is the decisions that are not made before and during the project.

Leadership in digitalisation means creating the conditions under which decisions can be made on time, transparently and soundly. It means asking good questions instead of just handing out answers. Explicitly making room for dissent. Admitting one's own mistakes.

Leadership is service to the mandate, to people and to responsibility. Not the administration of rollout plans.

The right order

If you are facing a digitalisation decision, do not first ask which tool is best. Ask yourself: do we actually understand what the problem is? Are responsibilities clear? Can the people involved openly say what they do not know?

If these questions are not answered, the best tool will change nothing. It will only show faster and more expensively what already did not work before.

Digital transformation is not an IT project. It is the result of excellent human decisions.

Which decision in your digitalisation initiative is actually still open?