View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy Strategy Map |  Architecture Request for Comments |  Architecture Architecture Decision Record |  Architecture Architecture Inception Canvas |
|---|---|---|---|---|
Purposedifferent | A Strategy Map translates strategy into a few connected objectives across perspectives such as finance, customers, processes, and learning. This makes visible which capabilities and activities are meant to drive which results. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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. | 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 | Medium | Medium | Low | Low |
Timedifferent | 2-4 h workshop plus review | 1-3 Wochen vom Draft bis zur Entscheidung | 15-45 min | 1-2 h |
Participantsdifferent | 4-10 | 3-20 Reviewer | 1-3 | 3-8 |
Formatdifferent | Workshop | Async | Async | Workshop |
Outputdifferent | Strategy Map, Objective Set, Cause-Effect Hypotheses | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | ADR File, Decision Log, Rationale | Inception Canvas, Risks, Goal List, Open Questions |
Tagsno overlap | AlignmentExecutionGoalsCausality | ArchitectureDecisionAsyncGovernance | ArchitectureRationaleDocumentationGovernance | AlignmentArchitectureCanvas |