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
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration for Diary Study.
UX Research
Diary Study
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Purposedifferent
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 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.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.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.
Complexitydifferent
MediumMediumLowLow
Timedifferent
2-6 h1-4 Wochen30 min Setup, dann laufend20-40 min initial, dann laufend
Participantsdifferent
2-85-201-3 maintaining, briefing for everyone3-15
Formatdifferent
Workshop + asyncAsyncAsyncWorkshop + async
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsDiary Entries, Longitudinal Patterns, Experience TimelineRAID Log, Status Report SourceROAM Board, Owner List
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
UX researchTrackingBehavior
RiskTrackingStakeholdersGovernance
RiskAgileTrackingAlignment
Add more methods