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 a Polarity Map with two poles and four quadrants
Systems Thinking
Polarity Mapping
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Purposedifferent
Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely.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.
Complexitydifferent
MediumLowMedium
Timedifferent
1-2 h20-60 min1-3 h
Participantsdifferent
3-121-43-10
Formatdifferent
WorkshopAsyncWorkshop
Outputdifferent
Polarity Map, Warning Signs, Balance ActionsRunbook, Checklist, Escalation PathProcess Map, Handoff List, Improvement Backlog
Tagsno overlap
Systems thinkingTradeoffsLeadership
OperationsReliabilityDocumentation
ProcessOperationsImprovement
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for Theory of Constraints.
Operations
Theory of Constraints