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 for Behavior Over Time Graph.
Systems Thinking
Behavior Over Time Graph
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
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 Riskiest Assumption Test with a method-specific labelled workspace.
Product Discovery
Riskiest Assumption Test
Purposedifferent
A Behavior Over Time Graph shows how a metric or observation develops over time. The method makes trends, breaks, and recurring patterns visible that get lost in snapshots.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.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 an idea hinges on one critical unknown, it prioritizes testing that exact piece of uncertainty first. It separates problem, assumption, solution, and evidence. The result is captured as a prioritized list of assumptions, a test plan, and a result report.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
20-45 min45-60 min3–4 h for initial assessment; preparation and deeper analysis additional1-2 Wochen pro Iteration
Participantsdifferent
1-102-81 or a small team; particularly suitable for 3–4 people2-6
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Behavior Over Time Graph, Trend Hypotheses, Key EventsAssumption map, Test backlog, Risk rankingLean 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 checksPrioritized Assumption List, Test Plan, Results Report
Tagsno overlap
Systems thinkingPatternsDynamics
AssumptionsRiskExperimentsValidation
ArchitectureQualityRiskAssessmentLean
ExperimentsValidationDiscoveryAssumptions
Add more methods