Reading misalignment between teams and systems
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
spot where the org chart and the architecture fight each other.
Planned topics
- Signals: one service changed by many teams, one team owning many unrelated services, constant cross-team tickets.
- Check ownership gaps: a system with no clear owner decays first.
- Compare change history to team boundaries; the data shows the real coupling.
- Fix with the smaller change: move a boundary, an owner, or an interface before restructuring.
Draft outline details
Demonstration
a heat map of Commerce 2030 pull requests per service, colored by how many distinct teams touched it in the last quarter, with the top five highlighted.
Check your understanding
What is better evidence of misalignment than opinions?
Show answer
Change history: which teams change which services, and how often they wait on each other.
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.