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 for Concierge MVP
Product Discovery
Concierge MVP
Paper illustration for Risk Storming.
Architecture
Risk Storming
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Purposedifferent
When an idea can first fail or grow through genuine hands-on support, it relies on manual work instead of automation. It shows whether user value holds up even under manual execution.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.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.
Complexitydifferent
MediumLowLowMedium
Timedifferent
1-4 Wochen60-90 min1-2 h45-60 min
Participantsdifferent
3-10 Kunden4-123-102-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Concierge Learnings, Service Blueprint, MVP RisksAnnotated Diagram, Prioritized Risk List, Action BacklogArchitecture Canvas, Goals, Constraints, Quality AttributesAssumption map, Test backlog, Risk ranking
Tagsno overlap
MVPValidationServiceDiscovery
RiskArchitectureWorkshopValidation
CanvasArchitectureAlignmentWorkshop
AssumptionsRiskExperimentsValidation
Add more methods