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
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 of Five-Minute VC Check with its method-specific working model.
Business Strategy
5-Minuten VC-Check
Paper illustration for Risk Storming.
Architecture
Risk Storming
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.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.The 5-Minute VC Check clarifies opportunities and strategic options at the earliest idea stage. It compares problem quality, customer willingness to pay, alternatives, differentiation, and market potential, and captures the result as a VC-check note, go/sharpen/park decision, and risk list.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.
Complexitydifferent
MediumMediumLowLow
Timedifferent
1-3 h Setup, laufend3–4 h for initial assessment; preparation and deeper analysis additional5-15 min60-90 min
Participantsdifferent
11 or a small team; particularly suitable for 3–4 people1-54-12
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
PARA Structure, Project Notes, Knowledge ArchiveLean 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 checksVC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation stepAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
KnowledgeProductivityOrganization
ArchitectureQualityRiskAssessmentLean
StartupValidationCompetition
RiskArchitectureWorkshopValidation
Add more methods