Services / Operating partner
Operating partnerHow the work actually runs.
Four steps from diagnosis to handover, one case followed through, and three recent engagements.
From diagnosis to something that runs without me
Diagnose
See how work actually moves: decisions, handoffs, where the numbers break and who everything waits for.
Decide
One North Star, few priorities, named owners and clear decision rights. Written down, not implied.
Build
Short execution cycles. Processes, systems and AI put into the daily work, not into a slide.
Hand over
Owners, rhythm and guides in place, so the work keeps moving after I step back.
Twelve entities. Twelve charts of accounts.
- Before
“But they all need their own chart of accounts.”Twelve entities, each chart slightly different, each one defended.
The CFO said it as if it were obvious.
- Walk-through
Three charts, side by sideSame revenue lines, same cost categories, same operations. Different numbers, names and levels of detail.
Every difference traced back to a person’s preference years ago. Not regulation. Not tax.
- The cost
Eleven days to consolidate, every monthMapping, reconciling and explaining the differences by hand.
Nobody had asked whether the old reasons still applied.
- Rebuild
One shared structureEntity overlays only where they were actually needed.
Built once, owned centrally.
- After
Two days“The consolidation pack is readable for the first time in six years.”
The CFO, the first month after.
Eleven days became two. The system was never the constraint.
Recent engagements
Clients are not named. The work is.
- Fintech · Asset management
From zero to launch.
Building the processes, documentation and operating tooling a regulated business needs before its first client.
- Micromobility
Outsourcing assessment.
What to keep, what to hand over, and what the operating model has to look like either way.
- Trade union
AI adoption programme.
Individual capability and organisational deployment, run as two parallel tracks.
-
About operations · Process series · 2 of 3
The Intentional Process Environment.
Work should not depend on people remembering to do it. Tasks are created, assigned, carry their own guide, are checked off, and create the next task. That is how work moves.
-
About execution
The Framework Was Never the Problem.
Leadership teams diagnose slow execution and reach for a new goal framework. What actually decides speed is who can decide what, how much mandate a team has, and how short the cycles are.
-
About AI adoption
AI Capability Is Built, Not Installed.
Licences, a demo and a request to use it rarely change anything. People and organisations adopt AI on two different tracks, at two different speeds, and each needs something different.
A short conversation first.
Thirty minutes, no deck and no pitch. An honest read on what is actually in the way, and whether I am the right person to help move it.