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
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Paper illustration for Future Reality Tree.
Systems Thinking
Future Reality Tree
Purposedifferent
Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins.In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic.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.A Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation.
Complexitydifferent
MediumHighLowHigh
Timedifferent
1-3 hHalber Tag30-120 min2-4 h
Participantsdifferent
3-125-202-63-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
System Map, Dependencies, Leverage PointsSimulation Notes, Gaps List, Updated RunbooksObservation Notes, Improvement IdeasFuture Reality Tree, Negative Branches, Assumption List, Improved Injections
Tagsno overlap
Systems thinkingMappingBoundariesChange
ResilienceOperationsIncident
LeanObservationProcessOperations
Theory of ConstraintsSystems thinkingChange
Add more methods