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 Accountability Ladder
Operations
Accountability Ladder
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration for Risk Storming.
Architecture
Risk Storming
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.With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on.When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.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.
Complexitydifferent
MediumLowHighLow
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional20-45 min1-4 Wochen60-90 min
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people1-81-64-12
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop
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 checksOwnership Reflection, Action Commitment, Coaching NotesExperiment results, Decision log, Learning summaryAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
ResponsibilityLeadershipTeam
ExperimentsGrowthAnalyticsValidation
RiskArchitectureWorkshopValidation
Add more methods