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 several people silently writing ideas and passing sheets around with arrows.
Innovation
Brainwriting
Paper illustration for Fault Tree Analysis.
Operations
Fault 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)
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
When loud voices or hierarchy distort the idea search, the method creates a quiet entry into joint development. It gives everyone thinking space and gathers contributions without social brakes, making diversity more visible and easier to build on.For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage.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 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
LowHighMediumLow
Timedifferent
15-30 min2-6 h3–4 h for initial assessment; preparation and deeper analysis additional15-30 min
Participantsdifferent
3-123-81 or a small team; particularly suitable for 3–4 people2-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Idea sheets, Expanded concepts, Prioritized listFault Tree, Critical Paths, Cause Hypotheses, Control ActionsLean 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 checksRoot cause notes, Countermeasures
Tagsno overlap
BrainstormingCollaborationInclusionIdeas
RiskRoot causeSafety
ArchitectureQualityRiskAssessmentLean
Root causeIncidentLeanProblem solving
Add more methods