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
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Purposedifferent
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.In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.
Complexitydifferent
LowLowLowMedium
Timedifferent
20-60 min45-90 min45-90 min45-60 min
Participantsdifferent
1-43-122-82-8
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathForce Field Map, Change Levers, Risk NotesAssumption List, Critical Assumptions, Learning PlanAssumption map, Test backlog, Risk ranking
Tagsno overlap
OperationsReliabilityDocumentation
ChangeDecisionStrategy
AssumptionsRiskDecisionDiscovery
AssumptionsRiskExperimentsValidation
Add more methods