No pre-built answers.
No generic frameworks.
Every engagement starts with understanding your specific situation. The solution is built around that, not applied to it.
Understand before proposing
I spend significant time at the start understanding your specific situation. Not the problem as it is described in a brief, but the actual operational reality — the history, the constraints, the people, and the pressures that shaped how things work today. Most consultants skip this. I do not.
Map what is actually happening
I document the current state honestly — how things actually work, not how the procedure says they should. This includes the workarounds, the informal fixes, the exceptions that have become the norm. The gap between the documented process and the real process is almost always where the problems live.
Design the solution with your team
I do not arrive with a pre-built answer. The solution is designed with your operational team, in your context, accounting for your specific constraints. This takes more time at the front. It produces significantly better adoption.
Implement with accountability
I stay involved through implementation — not as a reviewer, but as an active participant with accountability for the outcome. I manage vendors, resolve blockers, and maintain the governance discipline that most programmes lose under delivery pressure.
Own the go-live and what follows
Go-live is not the end of the engagement. The period immediately after is where most implementations succeed or fail in practice. I design the hypercare structure before launch and remain engaged until the organisation is genuinely stable.
Make the change last
The measure of success is not whether the system is live. It is whether the organisation is still running on it six months later — and whether the people who use it have genuinely adopted the new way of working.
Principles
- Simplicity over complexity. Always.
- People adopt what they understand and trust.
- No system works if the process around it is broken.
- Change is only real when it holds after I leave.
- The IT team and the business are both right. They need a translator.
Typical engagement
Engagements range from a focused four-week process review to a multi-year programme leadership role. I work remotely and on-site as the situation requires.
Discuss your situationOne thing I will always tell you.
If I am not the right person for your challenge, I will say so. I would rather have that conversation early than a difficult one six months into an engagement.