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 of a Polarity Map with two poles and four quadrants
Systems Thinking
Polarity Mapping
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
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.Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely.When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all.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.
Complexitydifferent
MediumMediumLowHigh
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional1-2 h1-5 Tage1-4 Wochen
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people3-12Nutzertraffic1-6
Formatdifferent
Workshop + asyncWorkshopAsyncAsync
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 checksPolarity Map, Warning Signs, Balance ActionsInterest Metrics, Conversion Signal, Learning NoteExperiment results, Decision log, Learning summary
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
Systems thinkingTradeoffsLeadership
ValidationExperimentsDemandGrowth
ExperimentsGrowthAnalyticsValidation
Add more methods