The problem isn't technology, it's the absence of decisions

Many digital projects struggle not because of a lack of resources or skills, but because no one has clearly decided what belongs in the system, who has the final say, and where one person's responsibility ends and another's begins. Without those decisions, the project keeps moving forward through layering and silent compromises — building up a debt that isn't technical, but conceptual.

Over the past few months I keep coming across digital projects that struggle to hold up.

They're not old projects, nor particularly short on resources. Quite the opposite. The technology is up to date. The tools are the right ones. The people involved are often skilled and motivated.

And yet something isn't working.

The debt that isn't technical

In most cases what's missing isn't a technical solution. What's missing are clear decisions: what's part of the system and what isn't, who makes the final call, where one person's responsibility ends and another's begins.

When those choices never get made, the project keeps moving forward anyway. But it does so through layering, through silent compromises, through accumulation. That's how a debt is born that isn't just technical, but conceptual.

Looking for the wrong tool

It's at these moments that people tend to look for a new tool, a different framework, a "definitive" solution. But often the problem sits further upstream: no one has stopped to say this is the direction.

A system without decisions isn't flexible. It's simply unstable.

And sooner or later it presents the bill.

Domande frequenti

Why can a digital project fail even with adequate budget, skills, and tools?

Because the most common cause isn't technical, it's decisional: no one has clearly established what belongs in the system and what doesn't, who has the final say on decisions, and where one person's responsibility ends and another's begins.

What happens to a project when the key decisions never get made?

The project keeps moving forward anyway, but through layering: silent compromises pile up instead of explicit choices. This builds a debt that isn't just technical, but conceptual — a set of unresolved ambiguities that stay inside the system.

Why does switching tools or frameworks often fail to solve the problem?

Because the problem is almost always further upstream than the tool itself: no one has stopped to clearly define the project's direction. A new tool doesn't fill a decision-making gap, at best it just moves it somewhere else.

What's the difference between a flexible system and an unstable one?

A flexible system comes from clear decisions that leave room for conscious adaptation. A system without decisions isn't flexible: it's simply unstable, because every unresolved ambiguity eventually presents the bill.

Tell me your problem