Complete firstBounded subject
The scope and purpose of Team Cognitive Load Assessment are stated as a concrete question.
Without scope, cognitive load map becomes arbitrary.
Method guideTeam Design
Team Cognitive Load Assessment
A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.
ComplexityMedium
Time60-90 min
Participants3-12
FormatWorkshop + async
MaturityEmerging
01
Prerequisite
What needs to be finished first
Complete firstAccess to relevant perspectives
Examples from the last four weeks, interrupt and flow data, team boundaries and services and domain decision makers are available.
Without these perspectives, central claims in cognitive load map remain unsupported.
02
Preparation
What needs to be ready before start
Materials
Examples from the last four weeks, interrupt and flow data, team boundaries and services, shared workspace, source links, and decision log.
People / roles
Whole team · facilitator · platform or leadership role as needed
Pre-read
Collect Examples from the last four weeks, interrupt and flow data, team boundaries and services in advance and mark open assumptions.
Time needed
75 minutes
Setup
Prepare classify concrete load episodes as intrinsic, extraneous, or germane load visibly and calibrate assessment terms before starting.
03
Core question
The one question this method answers
Which load currently blocks sustainable flow, and what system change will reduce it?
04
Flow
Phases with goal, actions, output and pitfall
The assessment collects concrete work situations, classifies load types, and considers frequency, severity, and recovery time. It diagnoses the team system, not individual performance.
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. |
1. Episode
- cognitive load map
- Release: six hours preparation, three approvals.
2. Load type
- cognitive load map
- Conflicting runbooks: extraneous.
3. System cause
- cognitive load map
- Deployment path lacks platform service.
4. Relief
- cognitive load map
- Golden path; platform team; under two hours preparation.
The example demonstrates the domain logic of Team Cognitive Load Assessment; worksheets remain blank.
- 1
Collect episodes
Collect episodes
Goal
Produce episode list so the core question “Which load currently blocks sustainable flow, and what system change will reduce it?” can be answered with stronger support.
Inputs for this step
- Examples from the last four weeks
- interrupt and flow data
- team boundaries and services
Actions
- Collect concrete overload and flow situations from four weeks.
- Record source, rationale, and open uncertainty directly in episode list.
Output
episode list
episode list · source · uncertainty · next decision
Quality check
Does each entry include situation, trigger, and effect?
Pitfall
A sentiment score replaces concrete load episodes or every difficulty is called extraneous load. Return to observed situations, load type, system cause, and measurable relief.
Timing: 10–20 minutes
- 2
Classify load
Classify load
Goal
Produce load map so the core question “Which load currently blocks sustainable flow, and what system change will reduce it?” can be answered with stronger support.
Inputs for this step
- episode list
- interrupt and flow data
- team boundaries and services
Actions
- Distinguish intrinsic, extraneous, and germane load with rationale.
- Record source, rationale, and open uncertainty directly in load map.
Output
load map
load map · source · uncertainty · next decision
Quality check
Is classification based on cause rather than feeling?
Pitfall
A sentiment score replaces concrete load episodes or every difficulty is called extraneous load. Return to observed situations, load type, system cause, and measurable relief.
Timing: 10–20 minutes
- 3
Test boundary
Test boundary
Goal
Produce boundary diagnosis so the core question “Which load currently blocks sustainable flow, and what system change will reduce it?” can be answered with stronger support.
Inputs for this step
- load map
- interrupt and flow data
- team boundaries and services
Actions
- Test load against team purpose, service boundary, and dependencies.
- Record source, rationale, and open uncertainty directly in boundary diagnosis.
Output
boundary diagnosis
boundary diagnosis · source · uncertainty · next decision
Quality check
Does the load sit in the right team?
Pitfall
A sentiment score replaces concrete load episodes or every difficulty is called extraneous load. Return to observed situations, load type, system cause, and measurable relief.
Timing: 10–20 minutes
- 4
Design relief
Design relief
Goal
Produce relief experiment so the core question “Which load currently blocks sustainable flow, and what system change will reduce it?” can be answered with stronger support.
Inputs for this step
- boundary diagnosis
- interrupt and flow data
- team boundaries and services
Actions
- Set a system action, owner, and success indicator.
- Record source, rationale, and open uncertainty directly in relief experiment.
Output
relief experiment
relief experiment · source · uncertainty · next decision
Quality check
Does the indicator measure real flow improvement?
Pitfall
A sentiment score replaces concrete load episodes or every difficulty is called extraneous load. Return to observed situations, load type, system cause, and measurable relief.
Timing: 10–20 minutes
05
Artifact
What comes out at the end
Sketch: what the artifact looks like
Form
Versioned cognitive load map with date, sources, owners, and next review.
Versioning / ownership
Retain date, source, assumption state, and decision for every version of cognitive load map.
Tool alternatives
- cognitive load map as board or document
- Source and evidence register
- Decision and action log
team-cognitive-load-assessment-working-template.md
Plan Team Cognitive Load Assessment around its domain steps and the concrete decision question.
Team Cognitive Load Assessment: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Establish and review the practice Time: 75 minutes
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: Examples from the last four weeks, interrupt and flow data, team boundaries and services, shared workspace, source links, and decision log.
- Roles: Whole team · facilitator · platform or leadership role as needed
- Advance information: Collect Examples from the last four weeks, interrupt and flow data, team boundaries and services in advance and mark open assumptions.
- Overall time needed: 75 minutes
- Setup: Prepare classify concrete load episodes as intrinsic, extraneous, or germane load visibly and calibrate assessment terms before starting.
Prepare for the work steps
Collect episodes: Collect episodes
- Examples from the last four weeks
- interrupt and flow data
- team boundaries and services
Classify load: Classify load
- episode list
- interrupt and flow data
- team boundaries and services
Test boundary: Test boundary
- load map
- interrupt and flow data
- team boundaries and services
Design relief: Design relief
- boundary diagnosis
- interrupt and flow data
- team boundaries and services
cognitive load map
| Subject | Situation · trigger · effect | Intrinsic · extraneous · germane + rationale | Team boundary · tool · process · dependency | Action · owner · indicator |
|---|---|---|---|---|
| cognitive load map |
- cognitive load map: Worked example
Enter only real input, sources, and decisions.
Team Topologies: Cognitive Load
Collect episodes: Collect episodes
Expected artifact: episode list
episode list · source · uncertainty · next decision
Entry:
...
- Does each entry include situation, trigger, and effect?
Classify load: Classify load
Expected artifact: load map
load map · source · uncertainty · next decision
Entry:
...
- Is classification based on cause rather than feeling?
Test boundary: Test boundary
Expected artifact: boundary diagnosis
boundary diagnosis · source · uncertainty · next decision
Entry:
...
- Does the load sit in the right team?
Design relief: Design relief
Expected artifact: relief experiment
relief experiment · source · uncertainty · next decision
Entry:
...
- Does the indicator measure real flow improvement?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/team-cognitive-load-assessment/run-sheet
06
Example output
Concrete filled scenario, fictional example
Fictional example for orientation. Counts and timings describe this case and are not universal requirements.
team-cognitive-load-assessment-beispiel.md
Concrete filled scenario, fictional example
Episode: a release requires switching among product logic, IAM, and Jenkins. Intrinsic: product rules. Extraneous: three manual approvals and conflicting runbooks. Germane: learning the new deployment path. Action: platform team provides a golden path; success: release preparation drops from six hours to under two.
07
Pitfalls
Recognize symptoms and steer against them
Quick overview, the full text is in the matching phase in the flow
- Collect episodesA sentiment score replaces concrete load episodes or every difficulty is called extraneous load.View in phase
- Classify loadA sentiment score replaces concrete load episodes or every difficulty is called extraneous load.View in phase
- Test boundaryA sentiment score replaces concrete load episodes or every difficulty is called extraneous load.View in phase
- Design reliefA sentiment score replaces concrete load episodes or every difficulty is called extraneous load.View in phase
Trap
Collect episodes
Symptom
A sentiment score replaces concrete load episodes or every difficulty is called extraneous load.
What to do
Return to observed situations, load type, system cause, and measurable relief.
Trap
Classify load
Symptom
A sentiment score replaces concrete load episodes or every difficulty is called extraneous load.
What to do
Return to observed situations, load type, system cause, and measurable relief.
Trap
Test boundary
Symptom
A sentiment score replaces concrete load episodes or every difficulty is called extraneous load.
What to do
Return to observed situations, load type, system cause, and measurable relief.
Trap
Design relief
Symptom
A sentiment score replaces concrete load episodes or every difficulty is called extraneous load.
What to do
Return to observed situations, load type, system cause, and measurable relief.
08
Stop criteria
When to pause, resolve prerequisites, or choose another approach
cognitive load map answers the core question with traceable evidence or explicitly marked uncertainty.
Owners, next actions, and review dates are named for open points.
Finished the method guide?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.