I work with companies where fixing the obvious thing keeps not working.
Most teams already know what is wrong. The harder question is why it keeps coming back.
A common situation
We follow the process, we bought the tools, the team is not bad. And yet the same problems keep coming back. I am not sure anymore whether we are missing something structural or just not doing it right.
Who I Work With and What Changes
1 Does This Sound Familiar?
- We bought a tool. The team is not using it.
- IT and the business are speaking different languages.
- We have the processes, and yet the same mistakes keep repeating.
- People are exhausted from all the changes. Nothing sticks, so more changes get introduced. The cycle continues.
- Development ran for months. What we got was not what we needed.
- New tools start well. Then usage drops off.
- We invested months in development. The system exists, but is never used to its full potential.
- The best-in-class tool was implemented. The team complies, but we are not seeing the projected benefits.
2 What Changes
- The team uses what was built, not just in theory.
- IT and the business start from the same picture.
- Processes reflect how work actually happens, not how it was designed on paper.
- New tools land with context, not just training.
- Development starts from a clear brief, not a general idea.
- Changes stick because the structure supports them.
Who This Is For
Company Size
10–80 employees
Annual Revenue
€500K – €5M
Typical Pattern
Tools exist. Results do not follow.
What Changes
Problems that kept returning get a structural explanation, not just another fix
The team stops waiting for direction on things it can own
Goals that looked unrealistic start being planned for
The structure carries what the founder used to carry personally
What You Get
Most leadership teams already sense where the friction is. What is harder to see is what is generating it, and why the same issues keep returning despite fixes.
That clarity is what the diagnostic produces. Not a to-do list. A different way of reading the situation.
Some of what shifts happens in the conversation itself, before anything is built. Teams often find themselves planning for targets they had written off as unrealistic.
Once the cause is clear, the work is to build the structure that removes it: who decides what, how the team stays aligned without everything routing through the centre, what a realistic operating rhythm looks like.
The goal is a team that does not need the same conversation again.
Built with the team, not handed to them. Designed to hold without ongoing support.
Read More
Common Objections
Objection
Things are fine right now.
Response
Good. Hidden problems often go unnoticed until they become urgent. While things are still working, that is the right time for a conversation.
Objection
We already have someone for this.
Response
Good. Do they have the systems that make that possible, or is everything held together by personal capacity?
Objection
You will tell us what we already know.
Response
Probably. That is normal. The question is not what you know. It is why it has not been fixed. By the end of the first conversation you will know whether I understand your situation.
Objection
We have had consultants before.
Response
Good. Why are you not working with them now? I work across the full chain, or only where needed. No reports that end up in a drawer.
From the work
A sample of what the work looks like in practice. Every situation is different.
Two decades across energy, financial services, manufacturing, and enterprise technology. Now working with the teams building what comes next.