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 branching impact map with a Why goal at the root, actor circles, How behavior changes and What options.
Product Strategy
Impact Mapping
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Purposedifferent
When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures.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.LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail.In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.
Complexitydifferent
MediumLowMediumLow
Timedifferent
45-90 min45-90 min3–4 h for initial assessment; preparation and deeper analysis additional20–45 min
Participantsdifferent
3-83-121 or a small team; particularly suitable for 3–4 peopleSmall cross-functional group
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Impact Map, Outcome Hypotheses, Delivery OptionsForce Field Map, Change Levers, Risk NotesLean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checksRisk list, Mitigation plan, Assumption log
Tagsno overlap
OutcomesStrategyBehaviorPlanning
ChangeDecisionStrategy
ArchitectureQualityRiskAssessmentLean
RiskDecisionFailurePlanning
Add more methods