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 JTBD interview notebook with a decision timeline, forces of change and a concise job hypothesis.
Product Discovery
Jobs to Be Done
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
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 Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Purposedifferent
When switching motives and progress are unclear, it reconstructs the situation from real customer circumstances. It shows why a switch happens and what kind of progress is being sought.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.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 process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.
Complexitydifferent
MediumLowMediumHigh
Timedifferent
1-3 Wochen30 min Setup, dann laufend3–4 h for initial assessment; preparation and deeper analysis additional2-6 h
Participantsdifferent
5-12 Interviews1-3 maintaining, briefing for everyone1 or a small team; particularly suitable for 3–4 people3-10
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop
Outputdifferent
Job Stories, Outcome Statements, Opportunity ListRAID Log, Status Report SourceLean 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 checksFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
CustomerOutcomesNeeds
RiskTrackingStakeholdersGovernance
ArchitectureQualityRiskAssessmentLean
RiskQualityOperationsRoot cause
Add more methods