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 Usability Testing |  Delivery RAID Log |  Architecture Views and Beyond |  Architecture Risk Storming |
|---|---|---|---|---|
Purposedifferent | When a product is built but people get stuck on tasks, usability testing shows the friction at concrete points. Observed use instead of self-report makes visible where orientation, understanding, or interaction breaks down. | 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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-2 h je Session | 30 min Setup, dann laufend | 1-3 Tage | 60-90 min |
Participantsdifferent | Based on research question | 1-3 maintaining, briefing for everyone | 1-4 | 4-12 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Usability Issues, Severity List, Recommendations | RAID Log, Status Report Source | Architecture Views, Cross-view Notes, Rationale | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | ValidationUXPrototype | RiskTrackingStakeholdersGovernance | DocumentationStakeholdersArchitecture | RiskArchitectureWorkshopValidation |