How I think
about the work.
Twenty-five years at the seam between the boardroom and the codebase taught me a handful of principles I don't compromise on. They shape every engagement, from the first board conversation to the last pull request.
Six things I
believe about building.
Not slogans, operating defaults. This is how decisions actually get made when I'm in the room.
Business before backlog
I start from the product and the numbers, then build the engineering to match. Technology exists in service of the business and the P&L, never the other way around.
Read the essay →Read the thesis before the code
Architecture is a means, not an end. Before I judge a system I learn what the business is trying to become, then protect and compound the value of the asset.
Read the essay →Measure the system, not the people
Metrics that rank individuals get gamed. Point the measurement at flow, stability and friction, and you improve the machine everyone works inside.
Read the essay →Make delivery boring
Elite performance isn't heroics, it's a system that makes the safe path the easy path. Small batches, automation and predictability over drama.
Read the essay →Obsess over the operator
Customer experience wins the deal; operator experience decides whether you can afford to keep it. I design for the people who run the business, not only the people who buy it.
Read the essay →AI-native by default
Don't bolt AI onto an old operating model. Rebuild how products are built and how the organization runs so that AI is the default, not an add-on.
Read the essay →I think from a product and business point of view first, and everything derives down to technology and engineering in service of the business and the P&L.
Want this kind of
thinking in the room?
Whether it's a turnaround, an AI-native rebuild, or a full-time seat, let's talk about the work.