View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Context Canvas |  Delivery RAID Log |  Decision Making Red Teaming |
|---|---|---|---|
Purposedifferent | When an environment of users, systems, and constraints is hard to grasp, it puts the context compactly on the table. It creates a clear reading of influence, boundary, and dependency. | 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 strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments. |
Complexitydifferent | Low | Low | High |
Timedifferent | 45-90 min | 30 min Setup, dann laufend | 1-4 h |
Participantsdifferent | 3-10 | 1-3 maintaining, briefing for everyone | 3-8 |
Formatdifferent | Workshop | Async | Workshop |
Outputdifferent | Context canvas, Open questions, Shared context notes | RAID Log, Status Report Source | Challenge Findings, Risk Register, Mitigation Plan |
Tagsno overlap | ContextFramingRequirementsCanvas | RiskTrackingStakeholdersGovernance | RiskDecisionSensemaking |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
