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
ChatOps workspace showing the question, observations, and next decision.
DevOps
ChatOps
Paper illustration for Fake Door Test
Product Discovery
Fake Door Test
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Purposedifferent
For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together.When demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small.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.
Complexitydifferent
MediumMediumLow
Timedifferent
Ongoing1-5 Tage45-90 min
Participantsdifferent
2-20Nutzertraffic3-12
Formatdifferent
Workshop + asyncAsyncWorkshop
Outputdifferent
Chat Transcript, Action Log, AutomationsClick Data, Interest Signal, Learning DecisionForce Field Map, Change Levers, Risk Notes
Tagsno overlap
CollaborationEngineeringIncident
ValidationExperimentsDemandDiscovery
ChangeDecisionStrategy
Add more methods

Often compared together

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

Paper illustration of Experiment Canvas with a method-specific labelled workspace.
Product Discovery
Experiment Canvas
Paper illustration of a Learning Card with four fields for hypothesis, observation, insight, and action.
Product Discovery
Learning Card
Paper illustration of MVP Test Matrix with a method-specific labelled workspace.
Product Discovery
MVP Test Matrix
Paper illustration for OODA Loop.
Decision Making
OODA Loop