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 Working Backwards with its method-specific working model.
Product Discovery
Working Backwards
Paper illustration for Flywheel.
Growth
Flywheel
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Purposedifferent
When the target state and benefit need to be clear first, it thinks backward from the desired outcome into the product logic. It sharpens vision, objections, and value proposition before elaboration.Growth often breaks down where a reinforcing mechanism builds up too much friction. A Flywheel shows the cycle of value, repetition, and reinforcement meant to sustain growth.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.The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.
Complexitydifferent
MediumMediumLowLow
Timedifferent
4-8 h, mehrere Iterationen60-120 min1-2 h1-2 h
Participantsdifferent
2-63-83-103-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Future Press Release, FAQ, Vision StatementFlywheel Map, Friction Points, Growth Levers, Experiment BacklogArchitecture Canvas, Goals, Constraints, Quality AttributesInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
VisionNarrativeAlignment
GrowthRetentionConversion
CanvasArchitectureAlignmentWorkshop
AlignmentArchitectureCanvas
Add more methods