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 of Lean Startup with its method-specific working model.
Innovation
Lean Startup
Paper illustration for Risk Storming.
Architecture
Risk Storming
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.For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight.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.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
MediumMediumLowMedium
Timedifferent
1-3 h Setup, laufendWochen bis Monate je Lernzyklus60-90 min3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
12-84-121 or a small team; particularly suitable for 3–4 people
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
PARA Structure, Project Notes, Knowledge ArchiveHypothesis list, MVPs, Learning reports, Pivot or persevere decisionAnnotated Diagram, Prioritized Risk List, Action BacklogLean 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
LeanStartupValidationMVP
RiskArchitectureWorkshopValidation
ArchitectureQualityRiskAssessmentLean
Add more methods