Head of Digital Platforms
About
The person behind the work.
01About
Technologist by training. Translator by necessity.
A few paragraphs in your own voice: where you started, what pulled you from engineering into architecture and leadership, and what still pulls you back to building.
The through-line is translation: between business intent and technical design, between legacy systems and new ones, between teams who use different words for the same thing.
02How I think
A few working principles.
- 01
Boring technology, interesting outcomes.
Novelty is a budget. Spend it where it changes the result, not where it changes the CV.
- 02
Architecture is a set of decisions you can explain.
If the reasoning lives only in someone’s head, it is not architecture yet — it is a dependency.
- 03
Integration is where projects really fail.
Systems rarely fail alone. Draw the seams first, agree the contracts early, and test the joins hardest.
- 04
Ship the smallest true thing.
A small thing in production teaches more than a large thing in a slide deck.
- 05
Teams are the system.
Org charts become architecture diagrams eventually. Design both on purpose.
03Off the clock
There is a person behind the architecture diagrams.
The same curiosity, pointed elsewhere.
Music
What you play, listen to or make.
Football
Your team, and how you follow the game.
Experiments
Unusual applications, creative coding and things that probably should not work — but do.
Ideas
A notebook of product ideas that is longer than it should be.
Contact
Got a complicated thing?
A platform to rethink, a team to build, an integration nobody wants to own, or an idea that needs a first version. Tell me about it.