Architecture & Organization6 min
Architecture is an economic decision before a technical one
Every architecture choice locks in a recurring cost and a speed limit. Treating it as a purely technical matter is outsourcing a financial decision.
Architecture rarely reaches the executive committee. What reaches it is the cloud bill, the roadmap deadline and the incident. All three are consequences of architecture decisions made months or years earlier, by people who were never invited to decide economically.
What an architecture decision locks in
A service boundary defines how many teams can work in parallel. A data model defines cost per transaction. A coupling choice defines how long the next product change will take. These are long-term commitments with direct effect on cash and on schedule.
Conway is not a metaphor
System structure converges to the organization's communication structure. Redesigning architecture without touching team boundaries produces, at best, an elegant diagram that does not survive two quarters.
The reverse holds too: reorganizations that ignore system design create teams accountable for parts they cannot change on their own.
How to bring this to the committee
The conversation works when each option is presented with three numbers: estimated recurring cost, time to first delivery, and what the option prevents you from doing later. The third is usually missing — and the most expensive.
ÀFÒNJÁ's stance
We do not recommend architecture out of technological preference. We recommend the option the organization can sustain, afford and evolve with the team it actually has.
Living note: this text is the basis for our architecture diagnostics and will be extended with anonymized examples.