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:Strategy Execution Loop Architecture Communication Canvas Request for Comments Architecture Inception Canvas

Criterion	Business Strategy Strategy Execution Loop	Architecture Architecture Communication Canvas	Architecture Request for Comments	Architecture Architecture Inception Canvas
Purposedifferent	The Strategy Execution Loop helps avoid treating strategy as a one-off document. It makes visible how strategic decisions are turned into objectives, initiatives, operational work, measurement, and learning.	The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.	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.
Complexitydifferent	High	Medium	Medium	Low
Timedifferent	Initial 3-6 h, then monthly or quarterly reviews	60-120 min	1-3 Wochen vom Draft bis zur Entscheidung	1-2 h
Participantsdifferent	5-12	2-8	3-20 Reviewer	3-8
Formatdifferent	Workshop + async	Workshop + async	Async	Workshop
Outputdifferent	Execution Loop, Review Cadence, Strategic Learning Log	Communication Canvas, Stakeholder Messages, Architecture Communication Plan	RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets	Inception Canvas, Risks, Goal List, Open Questions
Tagsno overlap	ExecutionCadenceLearningGovernance	ArchitectureCommunicationStakeholdersCanvas	ArchitectureDecisionAsyncGovernance	AlignmentArchitectureCanvas

Add more methods