View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Software Architecture CanvasICE ScoringRequest for CommentsArchitecture Communication Canvas
| Criterion |  Architecture Software Architecture Canvas |  Product Strategy ICE Scoring |  Architecture Request for Comments |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | When ideas need sorting quickly, it condenses impact, confidence, and effort into one compact score. It connects customer value, product logic, and decision priorities. The result is captured as an ICE table and top-ideas list. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 1-2 h | 30-60 min | 1-3 Wochen vom Draft bis zur Entscheidung | 60-120 min |
Participantsdifferent | 3-10 | 2-8 | 3-20 Reviewer | 2-8 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Architecture Canvas, Goals, Constraints, Quality Attributes | ICE Table, Top Idea List | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | CanvasArchitectureAlignmentWorkshop | PrioritizationScoringGrowthDecision | ArchitectureDecisionAsyncGovernance | ArchitectureCommunicationStakeholdersCanvas |