View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Futures Wheel |  UX Research Contextual Inquiry |  Agile Example Mapping |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
Purposedifferent | The Futures Wheel helps explore the consequences of a decision, a trend, or a strategic move in a structured way. It makes visible which first, second, and third-order effects could arise from an event. | 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 a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 60-120 min | 1-3 Wochen | 30-60 min | 20-40 min pro Story |
Participantsdifferent | 3-10 | 4-12 Beobachtungen | 3-7 | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Futures Wheel, Consequence Chains, Strategic Signals | Field Notes, Workflow Insights, Pain Points | Example Map, Acceptance Criteria, Open Questions | Acceptance Criteria, Story Update |
Tagsno overlap | ForesightSystems thinkingSignals | UX researchObservationContext | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsRefinementBehavior-Driven Development |