View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Request for Comments |  Facilitation Problem Framing Workshop |  Facilitation Decision Jam |  Architecture Software Architecture Canvas |
|---|---|---|---|---|
Purposedifferent | 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 team works on symptoms but the real question stays fuzzy, a Problem Framing Workshop sharpens the view of the right problem. It separates observation, interpretation, and target picture from each other. | 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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 60-120 min | 60-90 min | 1-2 h |
Participantsdifferent | 3-20 Reviewer | 4-10 | 4-10 | 3-10 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions | Problem Cluster, Prioritized Challenge, Experiment | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | FacilitationAlignmentDiscovery | FacilitationDecisionProblem solvingWorkshop | CanvasArchitectureAlignmentWorkshop |