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 for Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration for Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
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 roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie.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
LowMediumMediumHigh
Timedifferent
45-90 min1-3 h3–4 h for initial assessment; preparation and deeper analysis additional2-6 h
Participantsdifferent
3-122-81 or a small team; particularly suitable for 3–4 people3-10
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Expectation Map, Alignment Notes, AgreementsCause Tree, Evidence Notes, CountermeasuresLean 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
AlignmentStakeholdersTeam
Root causeTreeIncidentQuality
ArchitectureQualityRiskAssessmentLean
RiskQualityOperationsRoot cause
Add more methods