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 | ![]() Operations A3 Problem Solving | ![]() UX Research Contextual Inquiry | ![]() Operations Kepner-Tregoe |
|---|---|---|---|---|
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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | 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. | For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. |
Complexitydifferent | Low | Medium | Medium | High |
Timedifferent | 45-90 min | 45-90 min | 1-3 Wochen | 2-8 h |
Participantsdifferent | 3-10 | 2-5 | 4-12 Beobachtungen | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Context canvas, Open questions, Shared context notes | A3 Report, Action Plan, Root Cause Analysis | Field Notes, Workflow Insights, Pain Points | Problem Analysis, Decision Analysis, Risk Plan |
Tagsno overlap | ContextFramingRequirementsCanvas | LeanProblem solvingCoachingOperations | UX researchObservationContext | Problem solvingRoot causeDecisionOperations |



