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 Architecture Decision Record | ![]() Innovation Design Sprint | ![]() Delivery RAID Log |
|---|---|---|---|
Purposedifferent | 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. | When the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess. | 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 | Low | High | Low |
Timedifferent | 15-45 min | 4-5 Tage | 30 min Setup, dann laufend |
Participantsdifferent | 1-3 | 5-8 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Async | Workshop | Async |
Outputdifferent | ADR File, Decision Log, Rationale | Prototype, Test Findings, Decision Rationale | RAID Log, Status Report Source |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Design sprintPrototypeValidationInnovation | RiskTrackingStakeholdersGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






