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 Diary Study | ![]() Innovation Lotus Blossom | ![]() Agile Example Mapping | ![]() Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
Purposedifferent | When experiences build up over days or weeks and a single session cannot capture them, Diary Study records the course of everyday life. Recurring triggers, moods, and habits become visible this way, beyond the sharpness of memory. | When a central question feels too large, the method breaks it into neighboring topic fields with their own depth of ideation. It holds structure and openness at the same time, so adjacent perspectives don't get lost. This grows an idea space out of a core problem. | 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 | Low | Low | Low |
Timedifferent | 1-4 Wochen | 45-90 min | 30-60 min | 20-40 min pro Story |
Participantsdifferent | 5-20 | 3-10 | 3-7 | 3-6 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Lotus Diagram, Idea Themes, Shortlist | Example Map, Acceptance Criteria, Open Questions | Acceptance Criteria, Story Update |
Tagsno overlap | UX researchTrackingBehavior | BrainstormingIdeationCreativityDivergenceWorkshop | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsRefinementBehavior-Driven Development |



