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 Flywheel.
Growth
Flywheel
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Purposedifferent
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.When a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time.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
MediumLowMediumLow
Timedifferent
60-120 min1-2 h1-3 h1-2 h
Participantsdifferent
3-83-105-303-8
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Flywheel Map, Friction Points, Growth Levers, Experiment BacklogArchitecture Canvas, Goals, Constraints, Quality AttributesConsensus Clusters, Theme Titles, Priority AreasInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
GrowthRetentionConversion
CanvasArchitectureAlignmentWorkshop
FacilitationConsensusWorkshopAlignment
AlignmentArchitectureCanvas
Add more methods