View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Example Mapping |  UX Research Affinity Diagramming |  Architecture Risk Storming |  Architecture Quality Attribute Workshop |
|---|---|---|---|---|
Purposedifferent | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | When research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. | 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. | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 30-60 min | 45–90 min | 60-90 min | 2-4 h |
Participantsdifferent | 3-7 | 3-10 | 4-12 | 5-15 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Theme clusters, Insight statements, Opportunity areas | Annotated Diagram, Prioritized Risk List, Action Backlog | Quality Scenarios, Priority List, Architecture Concerns |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | SynthesisQualitativeRoot cause | RiskArchitectureWorkshopValidation | RequirementsArchitectureWorkshop |