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 board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
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.When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.
Complexitydifferent
MediumMediumLowLow
Timedifferent
1-4 Wochen2-6 h20-40 min initial, dann laufend30 min Setup, dann laufend
Participantsdifferent
5-202-83-151-3 maintaining, briefing for everyone
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Diary Entries, Longitudinal Patterns, Experience TimelineEvent Model, UI Flow, Commands, Read ModelsROAM Board, Owner ListRAID Log, Status Report Source
Tagsno overlap
UX researchTrackingBehavior
EventsBlueprintDomain-Driven DesignBehavior
RiskAgileTrackingAlignment
RiskTrackingStakeholdersGovernance
Add more methods