Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Selected:Request for Comments Architecture Communication Canvas Stakeholder Salience Model Architecture Inception Canvas

Criterion	Architecture Request for Comments	Architecture Architecture Communication Canvas	Facilitation Stakeholder Salience Model	Architecture Architecture Inception Canvas
Purposedifferent	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.	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.	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	Medium	Low
Timedifferent	1-3 Wochen vom Draft bis zur Entscheidung	60-120 min	60-90 min	1-2 h
Participantsdifferent	3-20 Reviewer	2-8	3-6	3-8
Formatdifferent	Async	Workshop + async	Workshop	Workshop
Outputdifferent	RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets	Communication Canvas, Stakeholder Messages, Architecture Communication Plan	Salience Diagram, Strategy per Class	Inception Canvas, Risks, Goal List, Open Questions
Tagsno overlap	ArchitectureDecisionAsyncGovernance	ArchitectureCommunicationStakeholdersCanvas	StakeholdersFacilitationAlignmentGovernance	AlignmentArchitectureCanvas

Add more methods