The same problem keeps returning.
The team is capable. The effort is real. The strategy is not wrong.
The visible cause is almost never the real one.
The gap between what you believe is happening and what is actually
happening is where almost every execution problem lives.
It is also the last place most organizations look.
The real cause is structural.
Decisions that should close keep reopening.
Strong leaders escalate to you instead of deciding.
Execution slows despite real effort and capable people.
By the time issues become visible, they are already yours to solve.
None of this is a performance problem.
It is an architecture problem.
How decisions actually get made, who holds authority in practice,
how work moves through the system. That architecture is producing the friction.
Until it is named precisely, the symptoms return.
More process does not fix
a structural problem.
The instinct is to add more. More meetings. More communication.
New frameworks. Additional strategy work.
None of it resolves the friction because none of it addresses the cause.
Decision ownership stays informal. Authority stays assumed rather than explicit. Escalation happens by default rather than by design.
When the structural mechanism becomes visible, it can be changed.
Until then, the symptoms return.
What I do
I find the gap between what you believe is happening inside your organization and what is actually happening.
That gap is almost always the real cause of whatever friction, slowdown, or execution breakdown you are experiencing. I have worked across the full stack of how organizations operate. Technical, technological, operational, and strategic. From the ground up and from the top down.
That range is what makes the diagnosis precise and the solution buildable, not just nameable. The result is structural. Decision ownership becomes explicit.
Authority becomes unavoidable. The system moves without requiring constant correction from the top.
Sometimes what the diagnosis surfaces is deeper than the
operational layer. When that happens, it gets named too.
That is part of the work.
A founder brought me in for operational optimization.
His team had been building and iterating for nearly two years.
Four people. New positioning tested more than once. Brand work done twice.
I was there for process. I saw something else.
The team was no longer aligned to what the company was actually about.
Not in a cultural sense. In a foundational one.
What they were each building toward was a slightly different version of the same thing. The gap was invisible because no one had made the core concrete enough to test against. Two sessions with the founder. One on one. I named what I saw. He went quiet. He sat with it. Then he named it back to me, differently, from inside his own experience of the last two years.
He stopped the company.
Where this has been applied.
Scaling organizations from €1M to over €500M in revenue,
across Belgium, Europe, and internationally.
"picks up on what's really going on, not just what's being said"
— Niels Declercq
"methodological and structured way of working"
— Rudi Plettinx
How the work takes shape.
The engagement follows what the situation requires.
No fixed packages. Two forms depending on what the
diagnosis reveals.
Diagnostic Partnership
A focused engagement that identifies where and why the organization stalls. Produces a precise map of the structural gap and the changes that close it.
Time-boxed.
Advisory Retainer
Ongoing diagnostic thinking partnership. Multiple sessions per month plus direct access. The structural cause gets named before it fully surfaces. The goal is an organization that moves without founder escalation.
The form is determined by what the situation requires.
Not by what is easiest to propose.
Not ready yet.
If something on this page landed but the timing is not right,
the work continues on LinkedIn and in an occasional newsletter.
No volume. No selling. Observations when something is worth saying.
Or follow on LinkedIn