methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of Team Cognitive Load Assessment with its method-specific working model.
Team Design
Team Cognitive Load Assessment
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
Purposedifferent
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.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions.When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture.
Complexitydifferent
MediumMediumLowLow
Timedifferent
60-90 min1-3 h30-120 min45-90 min
Participantsdifferent
3-123-102-64-12
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Cognitive Load Profile, Action ListProcess Map, Handoff List, Improvement BacklogObservation Notes, Improvement IdeasSailboat Board, Risks, Improvement Actions
Tagsno overlap
TeamComplexityImprovementDiagnosis
ProcessOperationsImprovement
LeanObservationProcessOperations
RetrospectiveTeamImprovement
Add more methods