Level 07 — Architecture Leadership
The path's final level, and the one that least resembles the previous ones.
The problem in this section
In the six previous levels, the difficulty is technical. Here it isn't.
A senior architect rarely fails for not knowing the correct answer. They fail because the correct answer required an investment nobody approved, because two teams disagreed and the disagreement was never resolved, because the decision was communicated in a way that left whoever controls the budget not understanding the risk, or because the proposed architecture went against the organizational structure and the organization won — as it always wins.
Conway's law is not a curiosity. It is the strongest constraint there is on an architecture, and the one that least appears in the diagrams.
Senior architecture is the intersection of:
Technology + Business + People + Organization + Economics + Risk + Strategy
What you will find here
Direction. Architecture vision, technical strategy and technical roadmaps. How to state a destination that guides decisions without prescribing every step.
Decision. Decision-making under uncertainty, negotiating trade-offs and what to do when there is not enough information and deferring also has a cost.
Influence. Stakeholder management, communication, presentations and technical influence. How an architect with no formal authority — which is the common case — makes a decision happen.
Organization. Conway's law, Team Topologies, organizational architecture, cross-team architecture and architecture ownership. Designing teams is designing architecture; ignoring that is designing against the current.
Sustaining. Governance, principles and standards, revisited from Level 06 from the point of view of whoever establishes them.
Economics and risk. Cost and risk management as first-order architectural responsibilities, not as someone else's concern.
Evolution. Evolutionary architecture, fitness functions and measuring architecture outcomes. How to know whether the architecture is improving, instead of arguing that it is.
Reading order
Start with Conway's law and Team Topologies. They are the concepts that most change how you read an organization, and they retroactively explain a good share of the strange architectures you have already encountered.
Then communication and negotiating trade-offs — the competencies with the highest practical return and the least trained among engineers.
Leave fitness functions and measurement for last. They are the instrument that turns the rest into a verifiable cycle instead of a recurring opinion.
By the end
You drive an architectural decision that crosses teams through to it actually being adopted. You present a proposal to whoever controls the budget in terms of risk and capacity, not technology.
You recognize when the desired architecture requires changing the organization, and you can propose that.
And you can measure whether the architecture is improving — which is the difference between architectural leadership and senior opinion.
The end of the path
The material ends here. What doesn't end is the practice: none of these competencies develops by reading. They develop by deciding, getting it wrong, recording why and revisiting — which is, once again, the cycle this path began with.