Technical strategy
Turn ambiguity into a clear direction, useful decisions, and a path teams can actually follow.
Technical leadership / Systems thinking / People first
Engineering leadership / Systems thinking / People first
I make complex
technical work
feel possible.
I help engineering teams build better systems, grow their craft, and turn ambitious ideas into work that lasts.
OBSERVATION / CLARITY EMERGING FROM COMPLEXITYGood work sits at the intersection of clear thinking, strong teams, and technology that serves a purpose.
01 / 05What I do
Useful structure for
hard problems.
The work is rarely just technical. It is about creating enough clarity for people to make good decisions together.
Platform evolution
Modernise critical systems without losing momentum or asking teams to absorb unnecessary risk.
Engineering enablement
Create the standards, tools, and coaching that make good work easier to repeat.
Selected work
Making an impact
through the details.
A selection of programmes, systems, and communities I've helped shape.
FIELD NOTE 01 / OLD STRUCTURE, NEW PATH0101 / FEATURED PROJECT
Platform modernisation
Situation A 15-year-old monolith was slowing every team down — 45-minute deploys, shared database schemas, and no clear ownership.
Approach I ran a 6-week discovery with 8 teams, mapped the bounded contexts, and wrote the target architecture RFC that got executive buy-in.
Outcome We split the first service out in month 3. Deploy time for that domain dropped from 45 minutes to 6. Two more teams followed the same pattern without me needing to lead — the playbook worked.
ArchitectureStrategyDelivery
Talk about a similar challenge 
SYSTEM / TOOLS THAT ENABLE PEOPLE0202 / FEATURED PROJECT
A developer experience system
Situation Engineers were solving the same problems repeatedly, with fragmented tooling and no shared definition of a healthy path to production.
Approach I brought teams together around a small set of standards, paved paths, and feedback loops — then paired the system with coaching rather than mandates.
Outcome The result was a calmer, more consistent developer journey that helped teams move faster without compromising quality.
DevExEnablementOpen source
Talk about a similar challenge 
SYSTEM / PEOPLE IN THE LOOP0303 / FEATURED PROJECT
A technical chapter playbook
Situation A growing engineering community needed stronger craft, better conversations, and a way to share ownership of its culture.
Approach I designed a repeatable operating model for a technical chapter: clear rituals, lightweight standards, and space for engineers to lead from where they are.
Outcome The playbook created a more connected engineering community and made leadership a practice shared across the chapter.
LeadershipCommunityCulture
Talk about a similar challenge Thinking
Notes on the work
behind the work.
Architecture is a conversation
Why the best architecture documents create alignment before they create code.
The operating system of a healthy team
The small rituals that help technical teams build trust and make better decisions.
Make the path easier to walk
Developer experience is less about shiny tools and more about removing needless friction.
FIELD NOTE 04 / LEADING WITH CURIOSITYA little context
Leading with
curiosity.
I lead technical chapters with a belief that the best engineering organisations are built deliberately — through trust, useful standards, and space for people to do their best thinking.
My work spans technical strategy, platform evolution, developer experience, and the everyday practice of helping engineers grow. I care about the bridge between the system on paper and the people who make it real.
01Make the complex clear.
02Build systems that help people thrive.
03Leave things better than you found them.
Career evolution
Learning in
public.
A career shaped by moving closer to the systems, teams, and decisions that create lasting impact.
Now
Technical chapter leadership
Growing people, platforms, and the conditions for better engineering.
Before
Platform and architecture
Making complex technology more coherent, reliable, and easier to change.
Always
Student of the craft
Writing, sharing, asking better questions, and staying curious.
Have a good question?
Let's make
something useful.
Whether you're thinking about technical leadership, improving how teams work, or just want to compare notes — I'd love to hear from you.