Technical Leadership
Direction and judgment for decisions that are expensive to get wrong.
- Architecture and approach review
- Build-versus-buy and technology choices
- Technical due diligence
- Mentoring and team practice
Some of the most valuable work is also the smallest: a few days of genuinely independent review before a year of effort goes in a direction that won’t hold.
Twenty-five years means having seen several complete cycles of a decision being made, playing out, and being lived with. That’s most of what you’re buying here — not an opinion, but a reasonably well-calibrated sense of which problems get worse on their own.
I have no stake in the answer being complicated. If the recommendation is “what you have is fine, leave it alone”, that’s what you’ll get.
What this looks like in practice
- Reviewing a proposed architecture or approach while it’s still cheap to change.
- Working through build-versus-buy and technology decisions with someone who isn’t selling either.
- Due diligence on software or systems your organisation is about to depend on, or acquire.
- Mentoring engineers and helping teams establish practices that survive staff turnover.
Usually a short, bounded engagement with a written outcome you can circulate — or an ongoing arrangement a day or two at a time.
Sound like what you need?
Tell me about the problem and I'll tell you honestly whether I can help.