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 Lean Coffee |  Architecture arc42 |  Facilitation Stakeholder Salience Model |
|---|---|---|---|
Purposedifferent | When a group without a fixed agenda needs to get into useful conversations quickly, Lean Coffee structures the start around interests rather than a presentation. The group itself negotiates which topics get time first and which wait. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 30-90 min | 1-2 Tage | 60-90 min |
Participantsdifferent | 3-20 | 1-4 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Prioritized Topics, Discussion Notes, Action Items | Architecture Document, Context View, Runtime View, Deployment View | Salience Diagram, Strategy per Class |
Tagsno overlap | FacilitationAutonomyDialogue | ArchitectureDocumentationCommunication | StakeholdersFacilitationAlignmentGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
