View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Growth Funnel Analysis |  Architecture Risk Storming |  Architecture Architecture Communication Canvas |  Architecture Software Architecture Canvas |
|---|---|---|---|---|
Purposedifferent | When many visitors or users drop off along the way, the reason behind the number often stays hidden. Funnel Analysis exposes these transitions and makes visible exactly where the path collapses. | 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 Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-3 h | 60-90 min | 60-120 min | 1-2 h |
Participantsdifferent | 1-5 | 4-12 | 2-8 | 3-10 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | Funnel report, Drop-off analysis, Optimization hypotheses | Annotated Diagram, Prioritized Risk List, Action Backlog | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | AnalyticsConversionGrowth | RiskArchitectureWorkshopValidation | ArchitectureCommunicationStakeholdersCanvas | CanvasArchitectureAlignmentWorkshop |