The problem is not technology, but the absence of decisions

In recent months, I’ve often found myself observing digital projects that are struggling.

They are not outdated projects, nor lacking resources. Quite the opposite.

The technology is modern. The tools are appropriate.

The people involved are often skilled and motivated.

And yet, something doesn’t hold.

What’s missing, in most cases, is not a technical solution.

What’s missing are clear decisions: what is part of the system and what isn’t, who has the final word, where one responsibility ends and another begins.

When these decisions are not made, the project keeps moving anyway.

But it moves through layering, silent compromises, accumulation.

This is how a debt is created — not only technical, but conceptual.

At that point, it’s tempting to look for another tool, a new framework, a supposedly “definitive” solution.

But very often the issue lies upstream: no one ever stopped to say this is the direction.

A system without decisions is not flexible.

It is simply unstable.

And sooner or later, it shows.