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:Risk Storming Request for Comments Architecture Inception Canvas Architecture Communication Canvas

Criterion	Architecture Risk Storming	Architecture Request for Comments	Architecture Architecture Inception Canvas	Architecture Architecture Communication Canvas
Purposedifferent	Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.	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 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.	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	Medium	Low	Medium
Timedifferent	60-90 min	1-3 Wochen vom Draft bis zur Entscheidung	1-2 h	60-120 min
Participantsdifferent	4-12	3-20 Reviewer	3-8	2-8
Formatdifferent	Workshop	Async	Workshop	Workshop + async
Outputdifferent	Annotated Diagram, Prioritized Risk List, Action Backlog	RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets	Inception Canvas, Risks, Goal List, Open Questions	Communication Canvas, Stakeholder Messages, Architecture Communication Plan
Tags1 shared	RiskArchitectureWorkshopValidation	ArchitectureDecisionAsyncGovernance	AlignmentArchitectureCanvas	ArchitectureCommunicationStakeholdersCanvas

Add more methods