View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Request for Comments |  Systems Thinking CATWOE Analysis |  Decision Making Assumption Surfacing |  Delivery RAID Log |
|---|---|---|---|---|
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. | CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way. | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 45-90 min | 45-90 min | 30 min Setup, dann laufend |
Participantsdifferent | 3-20 Reviewer | 3-8 | 2-8 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Async | Workshop + async | Workshop + async | Async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Assumption List, Critical Assumptions, Learning Plan | RAID Log, Status Report Source |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | Systems thinkingFramingStakeholders | AssumptionsRiskDecisionDiscovery | RiskTrackingStakeholdersGovernance |