View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordRAID LogArchitecture Inception CanvasStakeholder Salience Model
| Criterion | ![]() Architecture Architecture Decision Record | ![]() Delivery RAID Log | ![]() Architecture Architecture Inception Canvas | ![]() Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 15-45 min | 30 min Setup, dann laufend | 1-2 h | 60-90 min |
Participantsdifferent | 1-3 | 1-3 maintaining, briefing for everyone | 3-8 | 3-6 |
Formatdifferent | Async | Async | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | RAID Log, Status Report Source | Inception Canvas, Risks, Goal List, Open Questions | Salience Diagram, Strategy per Class |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | RiskTrackingStakeholdersGovernance | AlignmentArchitectureCanvas | StakeholdersFacilitationAlignmentGovernance |



