View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation 1-2-4-All |  Architecture Request for Comments |  Facilitation Stakeholder Salience Model |  Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | When many people in a group too rarely get to speak, 1-2-4-All distributes thinking time more fairly. The format builds participation step by step and makes quiet or still-unformed thoughts usable faster. | 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 stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 10-20 min | 1-3 Wochen vom Draft bis zur Entscheidung | 60-90 min | 1-2 h |
Participantsdifferent | 4-100+ | 3-20 Reviewer | 3-6 | 4-12 |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Idea List, Shared Insights, Emergent Themes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Salience Diagram, Strategy per Class | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | FacilitationInclusionIdeation | ArchitectureDecisionAsyncGovernance | StakeholdersFacilitationAlignmentGovernance | AlignmentStakeholdersStrategyFacilitation |