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
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
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.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.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
MediumLowMediumLow
Timedifferent
1-4 Wochen1-2 h45-60 min20-40 min initial, dann laufend
Participantsdifferent
5-203-102-83-15
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Diary Entries, Longitudinal Patterns, Experience TimelineArchitecture Canvas, Goals, Constraints, Quality AttributesAssumption map, Test backlog, Risk rankingROAM Board, Owner List
Tagsno overlap
UX researchTrackingBehavior
CanvasArchitectureAlignmentWorkshop
AssumptionsRiskExperimentsValidation
RiskAgileTrackingAlignment
Add more methods