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 a Lean Canvas with nine fields, notes, and one highlighted learning risk.
Product Strategy
Lean Canvas
Paper illustration for Risk Storming.
Architecture
Risk Storming
Paper illustration of Value Chain Analysis with its method-specific working model.
Business Strategy
Value Chain 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)
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.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list.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
MediumLowHighMedium
Timedifferent
45-90 min60-90 minHalf day3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
1-64-123-81 or a small team; particularly suitable for 3–4 people
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Lean Canvas, Core Assumptions, Experiment BacklogAnnotated Diagram, Prioritized Risk List, Action BacklogValue Chain Map, Lever ListLean 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
RiskArchitectureWorkshopValidation
StrategyBusiness modelDiagnosisAnalysis
ArchitectureQualityRiskAssessmentLean
Add more methods