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 | ![]() Product Discovery Context Canvas | ![]() UX Research Contextual Inquiry | ![]() Agile ROAM Board |
|---|---|---|---|---|
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. | 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. | When work processes are known only from accounts and the real context stays hidden, Contextual Inquiry makes behavior at the workplace visible. Observation and follow-up questions together show how people actually work, get interrupted, and improvise. | When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 30 min Setup, dann laufend | 45-90 min | 1-3 Wochen | 20-40 min initial, dann laufend |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-10 | 4-12 Beobachtungen | 3-15 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Context canvas, Open questions, Shared context notes | Field Notes, Workflow Insights, Pain Points | ROAM Board, Owner List |
Tagsno overlap | RiskTrackingStakeholdersGovernance | ContextFramingRequirementsCanvas | UX researchObservationContext | RiskAgileTrackingAlignment |



