View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Agile Specification by Example | ![]() Operations Gemba Walk | ![]() UX Research Contextual Inquiry |
|---|---|---|---|
Purposedifferent | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. | 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. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 60-90 min pro Feature | 30-120 min | 1-3 Wochen |
Participantsdifferent | 3-6 | 2-6 | 4-12 Beobachtungen |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Observation Notes, Improvement Ideas | Field Notes, Workflow Insights, Pain Points |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | LeanObservationProcessOperations | UX researchObservationContext |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






