Handbook
This is where I document the frameworks, processes, and approaches I actually use in client engagements. It’s a living document — updated when I learn something new or when I discover that something I believed isn’t quite right.
Inspired by GitLab’s handbook philosophy: if you write down how you think about something, the thinking improves.
What’s in here
AI Strategy — How to assess where your company actually stands on AI readiness, frameworks for prioritising AI investments, and the build-vs-buy decision process I use with clients who are making their first serious AI bets.
Engineering — Principles and organisational patterns for high-performing engineering teams. Covers Harness Engineering methodology, how to structure feedback loops for AI-assisted development, and what good engineering culture looks like in practice.
Architecture — How to make and document architecture decisions that hold up over time. Includes the ADR process I use, patterns for modernising legacy systems without a big-bang rewrite, and principles for building systems that compound rather than accumulate debt.
Tech Strategy — The broader technology strategy layer: how to build and maintain a tech radar, when to invest vs. retire a technology, and how to communicate technical direction to non-technical stakeholders.
AI Strategy
Frameworks for AI maturity assessment, build vs buy decisions, and AI implementation roadmaps.
Engineering
Engineering principles, practices, and organizational patterns for high-performing technology teams.
Architecture
Architecture decision records, patterns, and principles for building systems that last.
Tech Strategy
Technology strategy frameworks including tech radar, build vs buy, and technology lifecycle management.