01
Evidence before theory
Start with the system, constraints, incidents, data, and behaviour that actually exist. Do not begin with the diagram everyone wishes existed.
Clarity before ceremony.
Good architecture is a disciplined way of understanding trade-offs and making delivery safer. It is not a performance involving expensive diagrams and mysteriously absent implementation details.
02
Architecture stays hands-on
The person making structural decisions should remain close enough to implementation to feel when those decisions become expensive or absurd.
03
Uncertainty is documented
Open questions should remain visible until they are resolved. False certainty is wonderfully tidy and operationally dangerous.
04
Leave capability behind
A successful engagement should make the team more independent, not create a permanent dependency on the person who advised them.
“The measure of an engagement is what the team can do after it ends.”
Need a second pair of eyes?
I can review a decision, system, or direction without manufacturing a six-month transformation programme around it.