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 collections for projects, responsibilities, resources and archives.
Knowledge Modeling
PARA Method
Paper illustration for Risk Storming.
Architecture
Risk Storming
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
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)
Purposedifferent
The PARA Method organizes knowledge into Projects, Areas, Resources, and Archives. It creates order when digital notes, files, and tasks no longer cleanly fit current work.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.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.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.
Complexitydifferent
MediumLowLowMedium
Timedifferent
1-3 h Setup, laufend60-90 min15-30 min3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
14-122-61 or a small team; particularly suitable for 3–4 people
Formatdifferent
AsyncWorkshopWorkshopWorkshop + async
Outputdifferent
PARA Structure, Project Notes, Knowledge ArchiveAnnotated Diagram, Prioritized Risk List, Action BacklogRoot cause 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 checks
Tagsno overlap
KnowledgeProductivityOrganization
RiskArchitectureWorkshopValidation
Root causeIncidentLeanProblem solving
ArchitectureQualityRiskAssessmentLean
Add more methods