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
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 for Evaporating Cloud.
Systems Thinking
Evaporating Cloud
Paper illustration for CATWOE Analysis.
Systems Thinking
CATWOE Analysis
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
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.The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict.CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.
Complexitysame
MediumMediumMediumMedium
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional60-120 min45-90 min45-60 min
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people2-83-82-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Lean 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 checksConflict Cloud, Assumption List, Breakthrough Ideas, Next ExperimentsCATWOE Canvas, Root Definition, Stakeholder Perspectives, ConstraintsAssumption map, Test backlog, Risk ranking
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
Theory of ConstraintsAssumptionsSystems thinking
Systems thinkingFramingStakeholders
AssumptionsRiskExperimentsValidation
Add more methods