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 arc42 |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|---|
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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 h | 60-90 min | 1-2 Tage | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 1-5 | 4-12 | 1-4 | Designers, developers as users, and facilitation |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Funnel report, Drop-off analysis, Optimization hypotheses | Annotated Diagram, Prioritized Risk List, Action Backlog | Architecture Document, Context View, Runtime View, Deployment View | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | AnalyticsConversionGrowth | RiskArchitectureWorkshopValidation | ArchitectureDocumentationCommunication | ArchitectureEngineeringFeedbackValidationTasks |