Team Design Operating practice
Identifies a team’s intrinsic, extraneous, and germane cognitive load and derives relief actions.
The assessment collects concrete work situations, classifies load types, and considers frequency, severity, and recovery time. It diagnoses the team system, not individual performance.
Which load currently blocks sustainable flow, and what system change will reduce it?
Team Cognitive Load Assessment uses classify concrete load episodes as intrinsic, extraneous, or germane load. Assessments remain justified and context-bound.
Collect episodes
Collect concrete overload and flow situations from four weeks.
Classify load
Distinguish intrinsic, extraneous, and germane load with rationale.
Test boundary
Test load against team purpose, service boundary, and dependencies.
Design relief
Set a system action, owner, and success indicator.
Repeat after each relief action and when the team boundary changes.
For teams facing context switching, expanding domains, or recurring operational burden.
cognitive load map with traceable sources, assumptions, and domain decisions.
Owners, dates, and next review for cognitive load map.
Fictional worked example
classify concrete load episodes as intrinsic, extraneous, or germane load as a precise working structure with a fictional example.
| Subject | Episode | Load type | System cause | Relief |
|---|---|---|---|---|
| cognitive load mapWorked example | Release: six hours preparation, three approvals. | Conflicting runbooks: extraneous. | Deployment path lacks platform service. | Golden path; platform team; under two hours preparation. |
The example demonstrates the domain logic of Team Cognitive Load Assessment; worksheets remain blank.
Start with the core question: Which load currently blocks sustainable flow, and what system change will reduce it?
When a team juggles too many domains, systems, or handoffs, it measures mental overload as an organizational problem. It clarifies responsibility, interaction, and load between teams. The result is captured as a cognitive-load profile and action list.
The load is made visible through the structure of the work, not through personal resilience. This brings topic diversity, interfaces, and support pressure forward as the actual drivers. The conclusion aims at better scoping, less peripheral load, and clearer boundaries of responsibility.
The Cognitive Load Assessment from Team Topologies is based on Sweller's theory. Intrinsic load comes from the inherent complexity of the task, extraneous load from poor tools or processes, and germane load from building durable skills. The survey is often integrated into team health checks and shows whether measures such as a platform service or shifting responsibilities make sense.
Anonymize the survey when possible. Discuss results in a retrospective focused on structural causes.
The method guide walks execution through 4 phases, timing, 4 pitfalls, and clear stop criteria.
Open method guideYour perspective
Your feedback helps shape the next improvements to methodatlas.
Plan Team Cognitive Load Assessment around its domain steps and the concrete decision question.
To be confirmed
To be confirmed
Establish and review the practice Time: 75 minutes
Complete this worksheet on paper or in your own document during the work.
| Subject | Situation · trigger · effect | Intrinsic · extraneous · germane + rationale | Team boundary · tool · process · dependency | Action · owner · indicator |
|---|---|---|---|---|
| cognitive load map |
Enter only real input, sources, and decisions.
Team Topologies: Cognitive Load
Expected artifact: episode list
episode list · source · uncertainty · next decision
Entry:
...
Expected artifact: load map
load map · source · uncertainty · next decision
Entry:
...
Expected artifact: boundary diagnosis
boundary diagnosis · source · uncertainty · next decision
Entry:
...
Expected artifact: relief experiment
relief experiment · source · uncertainty · next decision
Entry:
...
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/team-cognitive-load-assessment/run-sheet
Fitting alternatives with decision guidance, followed by other related methods.
Instead of Team Cognitive Load Assessment, choose Team API when you want to clearly document a team's mode of collaboration.
Moves team boundaries, interfaces, and collaboration toward a concrete result through "prepare a template with the four structures", "place current teams as squads", and "derive actions".
Makes a team's winds, anchors, risks, and target picture visible and turns the review into prioritized improvements.
Sorts practices into Start, Stop, More, Less, and Keep, so routine changes get chosen more deliberately.
Sorts team feedback into start, stop, and continue so the retrospective produces clear next steps.
Sorts cases into the fitting domain and derives actions that match the degree of clarity or complexity.
