Why did you decide to become a mentor?
Honestly, it came from a pattern I kept seeing — talented practitioners who understood their domain well but were stuck because nobody had ever shown them how to think structurally about process work. They could execute tasks but couldn't diagnose systems. They knew the tools but not the methodology layer underneath. I'd had informal conversations with colleagues and peers over the years that seemed to unlock something for them — a different way of framing a problem, a diagnostic question they hadn't thought to ask — and I realised that was something worth doing deliberately. There's a gap between what organisations teach people about process work and what actually makes someone effective in this field. Mentoring is how I close that gap one practitioner at a time.
How did you get your career start?
I didn't set out to be a process excellence practitioner — I arrived at it by noticing what was missing everywhere I worked. Early in my career I kept seeing the same pattern: organisations investing heavily in technology or headcount to solve problems that were fundamentally structural. The process wasn't designed right, the framework wasn't fit for purpose, and no amount of new tools was going to change that. That observation became an obsession. I started going deeper into process management, process mining, lean methodologies — not as certifications to collect but as lenses to understand why organisations run the way they do. Over time that became a practice, and eventually a career built around designing better operational systems rather than just running them.
What do mentees usually come to you for?
Most come with a surface request — career advice, help with a specific transformation challenge, understanding process mapping tools. But the underlying thing is almost always the same: they're operating at the execution layer and want to move to the strategic layer, and they don't know what that transition actually requires.
They can run a process workshop or implement a process improvement model, but they can't yet architect the methodology behind it or influence how an organisation thinks about its operations. That's the shift I help with — from practitioner who executes to practitioner who designs.
The other common thread is people navigating the AI disruption in process work — not knowing whether to lean into it, how to use it without losing their own intellectual edge, or how to position themselves as the field changes.
What's been your favourite mentorship success story so far?
One that comes to mind immediately is a friend who came to me wanting to transition from project management in construction into process excellence. On paper it sounds straightforward — project managers understand workflows, timelines, dependencies. But the gap between managing projects and designing process systems is wider than most people realise, and she was hitting that wall.
We started by being honest about where she actually stood.
Her CV was framing her entirely around delivery — budgets, milestones, stakeholder coordination. All valuable, but none of it signalling process thinking. The first thing we did was reposition how she presented herself: identifying the moments in her project work where she had actually diagnosed operational problems, redesigned how work flowed, or built structures that outlasted the project itself. Those moments existed — she just hadn't recognised them as process excellence work.
Then we mapped the real gaps. Methodology knowledge, BPM fundamentals, process analysis tools — things her construction background hadn't required. Rather than overwhelming her with certifications, we built a focused curriculum: what to learn first, in what order, and why. Equally important was the honest conversation about affinity — does she actually find this work interesting when she goes deeper into it, or is she chasing a job title? That question matters more than any skills gap.
She pivoted successfully — which is no small thing in a market that's significantly harder than it was a few years ago. What made the difference wasn't a CV rewrite. It was clarity: knowing exactly what she was transitioning toward, why her background was an asset rather than a liability, and what she needed to close the gap with precision rather than guessing.
That's the kind of mentoring I find most meaningful — not cheerleading, but structured thinking that turns a vague ambition into a navigable path.
What are you getting out of being a mentor?
It sharpens my own thinking in ways that nothing else does. When you have to explain why a methodology works — not just that it works — you find the gaps in your own understanding fast. Mentoring forces precision. It also keeps me honest about what's actually useful versus what sounds good in theory.
The questions mentees ask are often the most interesting ones precisely because they haven't been conditioned yet to accept the standard answers. That friction is valuable. And frankly, building a network of practitioners who think rigorously about process work — across industries, geographies, career stages — is something I find genuinely energising.
