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 an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
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)
Paper illustration of a calibrated five-by-five risk matrix with response cards.
Decision Making
Risk Matrix
Purposedifferent
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.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.When a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List.
Complexitydifferent
LowLowMediumLow
Timedifferent
45-90 min45-90 min3–4 h for initial assessment; preparation and deeper analysis additional30-60 min
Participantsdifferent
2-83-121 or a small team; particularly suitable for 3–4 people3-10
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Assumption List, Critical Assumptions, Learning PlanForce 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 Matrix, Top Risk List
Tagsno overlap
AssumptionsRiskDecisionDiscovery
ChangeDecisionStrategy
ArchitectureQualityRiskAssessmentLean
RiskDecisionPrioritizationAssessment
Add more methods