View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery RAID Log | ![]() Innovation Design Thinking | ![]() Architecture Architecture Communication Canvas |
|---|---|---|---|
Purposedifferent | 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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Low | High | Medium |
Timedifferent | 30 min Setup, dann laufend | 1 Tag bis mehrere Wochen | 60-120 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 4-10 | 2-8 |
Formatdifferent | Async | Workshop | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Problem Statement, Prototype, Test Learnings | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | RiskTrackingStakeholdersGovernance | InnovationPrototypeResearch | ArchitectureCommunicationStakeholdersCanvas |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






