About me
I started in frontline operations before moving into enablement. Working directly with customers, escalations, and global support systems changed the way I think about learning at work.
The pattern I kept seeing was always the same: teams overwhelmed with information, managers repeating the same answers, new training being created without fixing the underlying friction. Most problems weren't caused by a lack of training. They came from unclear workflows, fragmented knowledge, and systems that expected people to memorise too much at once.
Over time I became more interested in reducing friction than creating content. That perspective shaped how I approach enablement today: less as a training function, more as operational infrastructure.
Over the last five years I've worked across global operations supporting distributed teams and customers across 150+ countries. That environment forced me to think beyond traditional learning design.
Processes had to scale asynchronously for both internal teams and customers. Knowledge had to remain usable across regions, roles, and experience levels. Systems had to support consistency without creating unnecessary complexity.
Onboarding systems · Workflow-based learning · Knowledge architecture · Operational readiness · Async enablement ·
Onboarding systems · Workflow-based learning · Knowledge architecture · Operational readiness · Async enablement ·
My work becomes most valuable in environments where operational complexity is increasing faster than internal clarity
Globally distributed companies, fast-scaling teams, organisations launching frequently and struggling with inconsistent execution.
Those environments require more than training. They require systems that help people perform consistently without depending on constant intervention.
Outside of work I apply the same methodology to my own learning. Most recently designing a self-directed system to reach conversational French, which I tested with 3 weeks in Paris.