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 Five-Minute VC Check with its method-specific working model.
Business Strategy
5-Minuten VC-Check
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
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 Lean Startup with its method-specific working model.
Innovation
Lean Startup
Purposedifferent
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.Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable.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 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.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
5-15 min1-3 h3–4 h for initial assessment; preparation and deeper analysis additionalWochen bis Monate je Lernzyklus
Participantsdifferent
1-53-121 or a small team; particularly suitable for 3–4 people2-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
VC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation stepKnowledge Map, Critical Knowledge Areas, Transfer PlanLean 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 checksHypothesis list, MVPs, Learning reports, Pivot or persevere decision
Tagsno overlap
StartupValidationCompetition
KnowledgeMappingRisk
ArchitectureQualityRiskAssessmentLean
LeanStartupValidationMVP
Add more methods