Working together
I start by finding out what's actually wrong. Everything else waits for that.
Most people who reach out already have a fix in mind. More staff. A new system. A restructure. Sometimes they're right. More often the fix is aimed at a symptom, and the real problem is one layer down, somewhere nobody has looked.
So I don't lead with a solution. I lead with a diagnosis. I find where the money is actually leaking, we agree what good looks like, and only then do we talk about what to change. You get clarity first. What you do with it is your decision, not something I've settled for you in advance.
How I work
I don't improvise. I run two frameworks: one to fix the operation, one to make the fix stick.
Most consulting lives or dies on whether the change outlasts the consultant. So I work two repeatable frameworks side by side. One fixes what the operation does. The other makes sure the people carry it on after I've gone.
01 / 02
The 3D approach: Discover, Design, Deliver.
How I take a business from "something is wrong" to "fixed, and proven in the numbers." Discover maps how the work really flows and finds where it leaks. Design rebuilds the workflow with control points, so the fix holds under pressure. Deliver puts a number on the result: money saved, risk reduced, service improved. Boardroom-ready, not shelfware.
Discover
Stages 1 to 3. Deep-dive diagnostics and workflow mapping find inefficiencies, handoff gaps and error-prone tasks. Outputs: Current State Report, Process Maps and Opportunity Tracker.
Design
Stages 4 and 5. Workflow redesign uses proven templates and automation triggers. Outputs: Future State Blueprint with control points and sequencing, plus an Implementation Roadmap aligning effort with impact.
Deliver
Stage 6. Outcomes are quantified. Outputs: Business Case and Executive Summary covering cost savings, risk reduction and service improvement.
02 / 02
AALAAM: the part everyone skips.
Fixing a process is half the job. Getting people to actually adopt it is the other half, and it is where most change quietly dies. AALAAM is how I handle that half: Alert, Aim, Learn, Apply, Achieve, Maintain. It builds on the established change-management models and adds two decades of watching what makes a change survive contact with a busy team. It runs from making the case for change, through equipping and empowering people, to embedding the new way so it holds long after the project ends.
- 01
Alert
Make the case for change and prepare people for it.
- 02
Aim
Set the vision and line up the people who will drive it.
- 03
Learn
Give everyone the knowledge and communication to come along.
- 04
Apply
Put the change into action, clear the blockers and win early.
- 05
Achieve
Consolidate the gains and keep improving.
- 06
Maintain
Embed it in the culture so it holds.
Who this is for
Established businesses that outgrew the way they're run.
This is for owners and operators who built something real, watched it grow, and now spend their days firefighting instead of running it. The business works. It has just started to strain against the habits and workarounds that got it here.
If your operation runs on memory and instinct rather than systems, and you can feel the cost of that without being able to point to it, this is the conversation to have. Line of work doesn't much matter. The pattern travels.
Two ways in
Talk to me, or see how the work gets delivered.
There are two doors here, depending on what you need.
Start with a conversation.
If you want to start a conversation, book a call with me directly. Thirty minutes, no pitch, just a straight read on whether I can help and how.
Book a conversationSee the full programme.
If you would rather see how a full programme runs, that is what my consulting practice, Operations Transformation HUB, is built for. It is where the structured, hands-on delivery lives.
See how OpsHub runs a programmeEither way, the first step is the same. A clear look at what is really going on, before anyone spends real money fixing the wrong thing.