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 Architecture Decision Record | ![]() Delivery RAID Log |
|---|---|---|---|
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 ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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 | High | Low | Low |
Timedifferent | 1 Tag bis mehrere Wochen | 15-45 min | 30 min Setup, dann laufend |
Participantsdifferent | 4-10 | 1-3 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop | Async | Async |
Outputdifferent | Problem Statement, Prototype, Test Learnings | ADR File, Decision Log, Rationale | RAID Log, Status Report Source |
Tagsno overlap | InnovationPrototypeResearch | ArchitectureRationaleDocumentationGovernance | RiskTrackingStakeholdersGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






