Team topologies and cognitive load
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
use team types and cognitive load to judge whether team boundaries are workable.
Planned topics
- Team Topologies describes four team types: stream-aligned, platform, enabling, and complicated-subsystem.
- Each team has a limit on the amount it can understand and operate: its cognitive load.
- Overloaded teams slow down, avoid ownership, and burn out.
- Check load by the number of domains, services, on-call burden, and technologies the team must master.
Draft outline details
Demonstration
a cognitive-load card per team: domains owned, services run, on-call incidents per month, technologies; flagged where above what the team can sustain.
Check your understanding
What is a sign of a team above its cognitive load?
Show answer
Slow change, unclear ownership, heavy on-call, and burnout.
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.