View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery Shape Up |  Architecture Request for Comments |  Decision Making Assumption Surfacing |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | Shape Up helps clarify scope, sequence, and delivery flow. It makes work boundaries and decisions explicit and captures results as pitches, bet-table decisions, and hill charts. | 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. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 6 Wochen Cycle + 2 Wochen Cool-Down | 1-3 Wochen vom Draft bis zur Entscheidung | 45-90 min | 15-45 min |
Participantsdifferent | 2-4 pro Pitch | 3-20 Reviewer | 2-8 | 1-3 |
Formatdifferent | Workshop + async | Async | Workshop + async | Async |
Outputdifferent | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Assumption List, Critical Assumptions, Learning Plan | ADR File, Decision Log, Rationale |
Tagsno overlap | PlanningDeliveryAutonomy | ArchitectureDecisionAsyncGovernance | AssumptionsRiskDecisionDiscovery | ArchitectureRationaleDocumentationGovernance |