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 |  Facilitation Stakeholder Mapping |
|---|---|---|---|
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. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. |
Complexitysame | Low | Low | Low |
Timedifferent | 45-90 min | 30 min Setup, dann laufend | 60–90 min |
Participantsdifferent | 3-10 | 1-3 maintaining, briefing for everyone | 2-8 |
Formatdifferent | Workshop | Async | Workshop + async |
Outputdifferent | Context canvas, Open questions, Shared context notes | RAID Log, Status Report Source | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | ContextFramingRequirementsCanvas | RiskTrackingStakeholdersGovernance | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
