Something broke the day when going fast became more important than understanding. Agility was supposed to make it possible to better adapt to reality, but above all, it normalized rapid execution, sometimes at the expense of thinking. The rituals remained, the words too, but the space for thinking was gradually closed.
This phenomenon is not unique to SMEs. It is found in large companies as well as in ministries. Everywhere, the same dynamic is observed: a lot of action, little clarity. We advance, we deliver, we deploy, but without always knowing exactly where we are heading. Movement has become an end in itself, and it has too often been confused with progress.
Since the arrival of agility as the dominant model, each new technological wave has essentially replayed the same scenario. Automation, DevOps, security, governance, artificial intelligence: tools change, promises are renewed, but the root problem remains.
What is lacking is not one more tool, but a clear responsibility:
In their absence, solutions are implemented on processes that have never been formalized. Unclear decisions are automated. We secure systems that we partially understand. It is not a technological failure, but a problem of accountability and structure.
Today, automation has become faster and more accessible, sometimes at very low cost, especially in SMEs. It's a real opportunity, but it's also a brutal eye-opener.
Automating a poorly understood system does not create value. It just speeds up the inconsistencies that are already there.
Building something new on a fuzzy foundation is akin to accumulating debt, even when the technology is modern and attractive. The vocabulary is changing, the interfaces are improving, but the structural problems remain.
This position does not come from an official title or role. It comes from a transversal background, in contact with development, cloud, cloud, infrastructure, security, DevOps and governance. Touching these areas allows you to see how each discipline is trying to correct the system from its own angle.
Without the big picture, these well-intentioned efforts often end up contradicting each other. The value is not in the rapid execution of an isolated discipline, but in the ability to understand how the pieces fit together.
It is from this understanding that it becomes possible to:
It's not about rejecting new technologies or slowing down as a matter of principle. It's about understanding before implementing, clarifying before automating, and structuring before you want to scale. Tools have their place when they are part of a clear understanding of what we are trying to build.
Slowing down is not going backwards. It's creating the space needed to make conscious decisions. True agility starts there, long before sprints and tools: in clarity, structure and assumed responsibility.
Executing without understanding has never been a sustainable strategy.
