From system architecture to organizational architecture
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
show that at 25 teams the architecture you manage is the system plus the teams that own it.
Planned topics
- Conway's law: systems tend to mirror the communication paths of the organization that builds them.
- Past a certain size, most delay comes from coordination between teams, not from code.
- Architecture decisions now include ownership, interfaces between teams, and who pays for shared parts.
- You steer by changing boundaries and incentives, not by reviewing every design.
Draft outline details
Demonstration
a diagram of Commerce 2030 with two layers: services (checkout, inventory, pricing, shipping) and the teams owning them, with arrows where a feature needs three teams to change together.
Check your understanding
Why does a feature that needs five teams to change often point to an architecture problem?
Show answer
Boundaries cut across the change; coordination cost is a design signal.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.