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 Empathy Mapping | ![]() Architecture Quality Attribute Workshop | ![]() Architecture Request for Comments | ![]() Facilitation Decision Jam |
|---|---|---|---|---|
Purposedifferent | When a lot is assumed about a target group but little is seen jointly, empathy mapping makes knowledge and gaps directly comparable. The picture also shows which assumptions hold up and where evidence is missing. | 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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 30–60 min | 2-4 h | 1-3 Wochen vom Draft bis zur Entscheidung | 60-90 min |
Participantsdifferent | 4-8 | 5-15 | 3-20 Reviewer | 4-10 |
Formatdifferent | Workshop | Workshop | Async | Workshop |
Outputdifferent | Empathy Map, Assumptions List, Research Gaps | Quality Scenarios, Priority List, Architecture Concerns | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Problem Cluster, Prioritized Challenge, Experiment |
Tagsno overlap | SynthesisQualitativeWorkshop | RequirementsArchitectureWorkshop | ArchitectureDecisionAsyncGovernance | FacilitationDecisionProblem solvingWorkshop |



