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 Value Chain Analysis with its method-specific working model.
Business Strategy
Value Chain 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 of VRIO Framework with its method-specific working model.
Business Strategy
VRIO Framework
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.Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list.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 VRIO Framework rates resources and capabilities on whether they are Valuable, Rare, Inimitable, and Organized. It compares strengths, risks, market logic, and courses of action. The result is captured as a VRIO table and strategic actions.
Complexitydifferent
MediumHighMediumMedium
Timedifferent
1-3 h Setup, laufendHalf day3–4 h for initial assessment; preparation and deeper analysis additional90-180 min
Participantsdifferent
13-81 or a small team; particularly suitable for 3–4 people3-6
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
PARA Structure, Project Notes, Knowledge ArchiveValue Chain Map, Lever ListLean 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 checksVRIO Table, Strategic Actions
Tagsno overlap
KnowledgeProductivityOrganization
StrategyBusiness modelDiagnosisAnalysis
ArchitectureQualityRiskAssessmentLean
StrategyDiagnosisBusiness modelCapability
Add more methods