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 |  Architecture Views and Beyond |
|---|---|---|---|---|
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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. |
Complexitydifferent | High | Low | Low | Medium |
Timedifferent | 1 Tag bis mehrere Wochen | 15-45 min | 30 min Setup, dann laufend | 1-3 Tage |
Participantsdifferent | 4-10 | 1-3 | 1-3 maintaining, briefing for everyone | 1-4 |
Formatdifferent | Workshop | Async | Async | Workshop + async |
Outputdifferent | Problem Statement, Prototype, Test Learnings | ADR File, Decision Log, Rationale | RAID Log, Status Report Source | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | InnovationPrototypeResearch | ArchitectureRationaleDocumentationGovernance | RiskTrackingStakeholdersGovernance | DocumentationStakeholdersArchitecture |