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 HEART Framework |  Agile Example Mapping |  UX Research Contextual Inquiry |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | Helps clarify observations, needs, and patterns in concrete terms. It groups observations into patterns, questions, and decisions. The result is captured as a HEART-GSM table and dashboard. | 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 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 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 120 min initial, dann laufend | 30-60 min | 1-3 Wochen | 60-90 min pro Feature |
Participantsdifferent | 3-6 | 3-7 | 4-12 Beobachtungen | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | HEART-GSM Table, Dashboard | Example Map, Acceptance Criteria, Open Questions | Field Notes, Workflow Insights, Pain Points | Example Table, Acceptance Tests |
Tagsno overlap | MetricsUX researchMeasurementSatisfaction | Behavior-Driven DevelopmentRequirementsExamplesRefinement | UX researchObservationContext | AgileRequirementsExamplesBehavior-Driven Development |