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
Visual Management workspace showing the question, observations, and next decision.
Operations
Visual Management
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Paper illustration for Theory of Constraints.
Operations
Theory of Constraints
Purposedifferent
With high tempo and many parallel topics, the method makes status, deviations, and priorities visible at a glance. It reduces search effort and prevents what matters from getting lost in daily work.For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.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.For a system that does not get faster despite effort, the method directs attention to the bottleneck. It concentrates improvement on the point that actually limits throughput.
Complexitydifferent
LowLowMediumHigh
Timedifferent
Ongoing20-60 min1-3 h2-4 h Analyse, laufend
Participantsdifferent
1-201-43-103-12
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop + async
Outputdifferent
Visual Board, Status Indicators, Exception CuesRunbook, Checklist, Escalation PathProcess Map, Handoff List, Improvement BacklogConstraint Map, Improvement Plan, Flow Metrics
Tags1 shared
SignalsOperationsVisual management
OperationsReliabilityDocumentation
ProcessOperationsImprovement
OperationsConstraintsFlowImprovement
Add more methods