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 Strategy Map with its method-specific working model.
Business Strategy
Strategy Map
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)
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
A Strategy Map translates strategy into a few connected objectives across perspectives such as finance, customers, processes, and learning. This makes visible which capabilities and activities are meant to drive which results.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.For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
2-4 h workshop plus review3–4 h for initial assessment; preparation and deeper analysis additional45-90 min15-30 min
Participantsdifferent
4-101 or a small team; particularly suitable for 3–4 people2-52-6
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Strategy Map, Objective Set, Cause-Effect HypothesesLean 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 checksA3 Report, Action Plan, Root Cause AnalysisRoot cause notes, Countermeasures
Tagsno overlap
AlignmentExecutionGoalsCausality
ArchitectureQualityRiskAssessmentLean
LeanProblem solvingCoachingOperations
Root causeIncidentLeanProblem solving
Add more methods