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.

Selected:Lean Canvasarc42Assumption MappingLASR (Lightweight Approach for Software Reviews)
Criterion
Paper illustration of a Lean Canvas with nine fields, notes, and one highlighted learning risk.
Product Strategy
Lean Canvas
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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)
Purposedifferent
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.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
45-90 min1-2 Tage45-60 min3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
1-61-42-81 or a small team; particularly suitable for 3–4 people
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Lean Canvas, Core Assumptions, Experiment BacklogArchitecture Document, Context View, Runtime View, Deployment ViewAssumption 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 checks
Tagsno overlap
StartupLeanAssumptionsBusiness model
ArchitectureDocumentationCommunication
AssumptionsRiskExperimentsValidation
ArchitectureQualityRiskAssessmentLean
Add more methods