View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation Design Thinking |  Architecture Request for Comments |  Delivery RAID Log |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
Purposedifferent | For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service. | 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. | 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. | 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. |
Complexitydifferent | High | Medium | Low | Low |
Timedifferent | 1 Tag bis mehrere Wochen | 1-3 Wochen vom Draft bis zur Entscheidung | 30 min Setup, dann laufend | 45-90 min |
Participantsdifferent | 4-10 | 3-20 Reviewer | 1-3 maintaining, briefing for everyone | 2-8 |
Formatdifferent | Workshop | Async | Async | Workshop + async |
Outputdifferent | Problem Statement, Prototype, Test Learnings | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | RAID Log, Status Report Source | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | InnovationPrototypeResearch | ArchitectureDecisionAsyncGovernance | RiskTrackingStakeholdersGovernance | AssumptionsRiskDecisionDiscovery |