View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research Diary Study |  Delivery RAID Log |  Architecture Software Architecture Canvas |  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. | 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. | 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 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 | Medium | Low | Low | Low |
Timedifferent | 1-4 Wochen | 30 min Setup, dann laufend | 1-2 h | 20-40 min initial, dann laufend |
Participantsdifferent | 5-20 | 1-3 maintaining, briefing for everyone | 3-10 | 3-15 |
Formatdifferent | Async | Async | Workshop | Workshop + async |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | RAID Log, Status Report Source | Architecture Canvas, Goals, Constraints, Quality Attributes | ROAM Board, Owner List |
Tagsno overlap | UX researchTrackingBehavior | RiskTrackingStakeholdersGovernance | CanvasArchitectureAlignmentWorkshop | RiskAgileTrackingAlignment |