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
Design Thinking as a learning loop: an observation notebook, a focused problem statement, different idea sketches, a cardboard prototype and user-test notes. Feedback leads to new understanding.
Innovation
Design Thinking
Paper illustration of Lean Startup with its method-specific working model.
Innovation
Lean Startup
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of Five-Minute VC Check with its method-specific working model.
Business Strategy
5-Minuten VC-Check
Purposedifferent
For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service.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.ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.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.
Complexitydifferent
HighMediumHighLow
Timedifferent
1 Tag bis mehrere WochenWochen bis Monate je LernzyklusSeveral meetings plus preparation and analysis; total effort depends on scope5-15 min
Participantsdifferent
4-102-8Evaluation team, architects, and relevant stakeholders1-5
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Problem Statement, Prototype, Test LearningsHypothesis list, MVPs, Learning reports, Pivot or persevere decisionPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsVC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation step
Tagsno overlap
InnovationPrototypeResearch
LeanStartupValidationMVP
ArchitectureQualityRiskTradeoffsStakeholders
StartupValidationCompetition
Add more methods