Part III — Cultivating Flow · Chapter 20 · First Public Draft
Equipping, Not Reviewing
Cultivating architecture as a competence rather than a place.
If architecture is a competence rather than a place, the question becomes what an architect actually does on a Tuesday.
The answer is less satisfying than reviewing and considerably more useful: you spend the week making other people’s decisions better rather than making them yourself.
What changes. Architecture stops being a place decisions are sent and becomes a competence that sits where decisions are made. That is a change in where people spend their week, not in what they are called.
Move from reviewing to equipping. Every review is a decision that had to travel. Count how many reviews a month exist only because the team was not trusted or not equipped, and convert one of them into a guardrail or a conversation.
Go where the architecture is actually decided. Anyone responsible for the organization’s ability to change has to be present where its most consequential architecture is created — in budget rounds, organization design, hiring and vendor selection, not only in the technical forums. Those rooms rarely think of themselves as architectural, which is exactly why the decisions made in them go unexamined.
Write down the decision and the reason, not the target state. The reason is what expires. Anyone who finds the record in three years needs to know what was true then, so they can tell whether it still is.
Test every proposal against one standard. Does this make the organization, and what it builds, easier to change. Not more consistent, not more compliant. Easier to change.
Governance asks was this decision approved. Architecture, done as a competence, asks are the people making these decisions equipped to make them well — and then does the slow work of making that true.