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 |  Delivery Shape Up |  Architecture Architecture Decision Record |  Innovation Design Sprint |
|---|---|---|---|---|
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. | 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 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. |
Complexitydifferent | High | Medium | Low | High |
Timedifferent | 1 Tag bis mehrere Wochen | 6 Wochen Cycle + 2 Wochen Cool-Down | 15-45 min | 4-5 Tage |
Participantsdifferent | 4-10 | 2-4 pro Pitch | 1-3 | 5-8 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop |
Outputdifferent | Problem Statement, Prototype, Test Learnings | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | ADR File, Decision Log, Rationale | Prototype, Test Findings, Decision Rationale |
Tagsno overlap | InnovationPrototypeResearch | PlanningDeliveryAutonomy | ArchitectureRationaleDocumentationGovernance | Design sprintPrototypeValidationInnovation |