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 |  Architecture Quality Attribute Workshop |  UX Research Affinity Diagramming |  Architecture Risk Storming |
|---|---|---|---|---|
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. | 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. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 30-60 min | 2-4 h | 45–90 min | 60-90 min |
Participantsdifferent | 3-7 | 5-15 | 3-10 | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Quality Scenarios, Priority List, Architecture Concerns | Theme clusters, Insight statements, Opportunity areas | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | RequirementsArchitectureWorkshop | SynthesisQualitativeRoot cause | RiskArchitectureWorkshopValidation |