methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration for Diary Study.
UX Research
Diary Study
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration for PDCA Cycle.
Operations
PDCA Cycle
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.Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic.For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode.
Complexitydifferent
MediumMediumLow
Timedifferent
1-4 Wochen2-6 h1 h bis mehrere Wochen
Participantsdifferent
5-202-81-8
Formatdifferent
AsyncWorkshop + asyncWorkshop + async
Outputdifferent
Diary Entries, Longitudinal Patterns, Experience TimelineEvent Model, UI Flow, Commands, Read ModelsPDCA Log, Experiment Plan, Learning Outcome, Standard Change
Tagsno overlap
UX researchTrackingBehavior
EventsBlueprintDomain-Driven DesignBehavior
Continuous improvementLeanExperiments
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

EventStorming on a long working surface: colored event cards form a business flow, friction points are marked, and a boundary separates different areas of responsibility.
Domain Modeling
EventStorming
Paper illustration for Kaizen Event.
Operations
Kaizen Event