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 Execution Loop |  Decision Making Assumption Surfacing |  Architecture arc42 |  Architecture Request for Comments |
|---|---|---|---|---|
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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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. |
Complexitydifferent | High | Low | Low | Medium |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 45-90 min | 1-2 Tage | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 5-12 | 2-8 | 1-4 | 3-20 Reviewer |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Assumption List, Critical Assumptions, Learning Plan | Architecture Document, Context View, Runtime View, Deployment View | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | ExecutionCadenceLearningGovernance | AssumptionsRiskDecisionDiscovery | ArchitectureDocumentationCommunication | ArchitectureDecisionAsyncGovernance |