View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Change Analysis |  UX Research Usability Testing |  Architecture Risk Storming |
|---|---|---|---|
Purposedifferent | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | 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 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 | Medium | Low |
Timedifferent | 45-120 min | 1-2 h je Session | 60-90 min |
Participantsdifferent | 2-6 | Based on research question | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Usability Issues, Severity List, Recommendations | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | ChangeRoot causeTroubleshootingComparison | ValidationUXPrototype | RiskArchitectureWorkshopValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
