View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() UX Research Contextual Inquiry | ![]() Delivery Monte Carlo Forecasting | ![]() Operations Waste Analysis | ![]() Engineering Kanban |
|---|---|---|---|---|
Purposedifferent | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as Forecast Percentiles, Throughput Dataset, and Risk Communication. | For a process that keeps people busy but creates little value, the method exposes waste. It directs attention to unnecessary movement, waiting times, rework, and overdelivery. | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 1-3 Wochen | 30-90 min Setup, danach laufend | 45-120 min | Ongoing |
Participantsdifferent | 4-12 Beobachtungen | 1-8 | 2-8 | 2-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Forecast Percentiles, Throughput Dataset, Risk Communication | Waste Map, Prioritized Waste, Improvement Backlog | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | UX researchObservationContext | ForecastingFlowDelivery | WasteLeanProcess improvement | FlowVisual managementDelivery |



