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 a Lean Canvas with nine fields, notes, and one highlighted learning risk.
Product Strategy
Lean Canvas
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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)
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.When an early product bet still has too many open points, it brings target group, problem, and assumptions into a single view. It condenses the idea so core risks become nameable.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.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.
Complexitydifferent
LowMediumLowMedium
Timedifferent
45-90 min45-90 min15-45 min3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
2-81-61-31 or a small team; particularly suitable for 3–4 people
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Assumption List, Critical Assumptions, Learning PlanLean Canvas, Core Assumptions, Experiment BacklogADR File, Decision Log, RationaleLean 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 checks
Tagsno overlap
AssumptionsRiskDecisionDiscovery
StartupLeanAssumptionsBusiness model
ArchitectureRationaleDocumentationGovernance
ArchitectureQualityRiskAssessmentLean
Add more methods