Your dashboards say everything is fine. Your operation says otherwise.
I help organizations understand why the outcomes they're getting don't always match the outcomes they planned for.
Through a focused, independent Execution Diagnostic, I examine what is happening in the operation, where it has diverged from intent, and what needs to change.
When should you call me?
- The strategy was approved months ago, but the operation still looks the same.Possible diagnostic question: What has changed in the operating conditions since the strategy was approved?
- The transformation launched, but the operation gradually returned to the way it worked before.
- Projects keep finishing on time, but the outcomes they promised never fully arrive.
- Your teams have built workarounds around the official process, and those workarounds have become how the work actually gets done.Possible diagnostic question: Which parts of the official workflow can teams no longer rely on?
- Leadership reports one picture. Operations lives another.Possible diagnostic question: Where do reports and operating evidence begin to tell different stories?
- An AI rollout is surfacing problems that turn out to have nothing to do with the AI.
If any of these feel familiar, the Execution Diagnostic helps establish what is actually driving the problem.
The Execution Diagnostic
One engagement. A clear answer.
The Execution Diagnostic is a fixed-scope engagement with one purpose: an independent, evidence-based view of how the operation is working in practice, compared with how it is represented in systems, reports, and dashboards, and what needs to change first.
It is designed for decisions. Boards, investment committees, and leadership teams use it when the next allocation of money, time, or trust depends on knowing what is actually true.
- Fixed scope. Fixed fee. Two weeks.
- Independent. I have no stake in any system, vendor, or prior decision.
- Evidence-based. Every finding is indexed to something you can inspect.
- A maximum of seven findings, focused on the issues with the greatest operational significance.
- A written executive report, including what I did not find.
- A ninety-minute readout with the people responsible for the next decision.
The work
How it works
Where it leads
Execution Diagnostic
Independent diagnosis of the gap between organizational intent and operational reality.
Structural Redesign
Redesign of the operating conditions creating the execution problem, including decision rights, ownership, measurement, workflows, governance, and operational readiness where relevant.
Transformation & Implementation Support
Support for translating the required changes into execution where the findings call for it.
Every engagement begins with the Diagnostic. What follows depends on what it finds.
Evidence
The evidence behind the method
This method was built on operating floors, not in frameworks. My background spans enterprise system implementations, multi-site rollouts, operational launches, and delivery under highly constrained operating conditions in high-volume environments.
That includes an enterprise POS transformation that increased transaction throughput by 50% across a 20-site rollout, and a delivery operation stood up under lockdown conditions that grew to a quarter of revenue.
Operating environments
Multi-site food and beverage. Infrastructure and construction. Frontline service operations. High-volume, operationally intensive businesses.
Speaking
PMI Global Summit Africa 2026, Cape Town: The Authority Illusion Effect, on decision integrity in AI-assisted project delivery.
See speaking →Published thinking
The Operational Logic channel: documented breakdowns of why execution fails under real operating conditions.
See evidenceWorldview
How I think
The gap between organizational intent and operational reality is often where execution starts to break down.
When execution breaks down, the first questions are often about what went wrong, why the process wasn't followed, or why adoption stalled.
I start somewhere different.
What conditions made this outcome predictable?
Organizations can unknowingly be running two organizations at once. The formal one, which lives in strategy documents, process maps, org charts, and dashboards. And the operational one, where work actually happens: the real decisions, the informal fixes, the dependencies nobody documented.
The formal organization
This is where intent meets execution.