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 of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Diary Study.
UX Research
Diary Study
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
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.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 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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
2-6 h30 min Setup, dann laufend1-4 Wochen1-2 h
Participantsdifferent
2-81-3 maintaining, briefing for everyone5-204-12
Formatdifferent
Workshop + asyncAsyncAsyncWorkshop
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsRAID Log, Status Report SourceDiary Entries, Longitudinal Patterns, Experience TimelineAlignment Map, Open Issues, Decision Questions
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
RiskTrackingStakeholdersGovernance
UX researchTrackingBehavior
AlignmentStakeholdersStrategyFacilitation
Add more methods