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 |  Facilitation Stakeholder Mapping |  Architecture Software Architecture Canvas |
|---|---|---|---|
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. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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. |
Complexitysame | Low | Low | Low |
Timedifferent | 30-90 min | 60–90 min | 1-2 h |
Participantsdifferent | 3-20 | 2-8 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Prioritized Topics, Discussion Notes, Action Items | Stakeholder Map, Engagement Plan, Risk Notes | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | FacilitationAutonomyDialogue | StakeholdersAlignmentFacilitationChange | CanvasArchitectureAlignmentWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
