View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery RAID Log | ![]() Growth Funnel Analysis | ![]() Architecture arc42 | ![]() Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 30 min Setup, dann laufend | 1-3 h | 1-2 Tage | 15-45 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1-5 | 1-4 | 1-3 |
Formatdifferent | Async | Async | Workshop + async | Async |
Outputdifferent | RAID Log, Status Report Source | Funnel report, Drop-off analysis, Optimization hypotheses | Architecture Document, Context View, Runtime View, Deployment View | ADR File, Decision Log, Rationale |
Tagsno overlap | RiskTrackingStakeholdersGovernance | AnalyticsConversionGrowth | ArchitectureDocumentationCommunication | ArchitectureRationaleDocumentationGovernance |



