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)
Design Thinking as a learning loop: an observation notebook, a focused problem statement, different idea sketches, a cardboard prototype and user-test notes. Feedback leads to new understanding.
Innovation
Design Thinking
Paper illustration of Cost of Delay with its method-specific working model.
Delivery
Cost of Delay
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
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.For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service.Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.
Complexitydifferent
MediumHighHighLow
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional1 Tag bis mehrere Wochen90-180 min45-90 min
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people4-103-82-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
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 checksProblem Statement, Prototype, Test LearningsCoD Table, Prioritization SequenceAssumption List, Critical Assumptions, Learning Plan
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
InnovationPrototypeResearch
PrioritizationDeliveryEconomicsDecision
AssumptionsRiskDecisionDiscovery
Add more methods