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 Expectation Mapping |  Architecture Software Architecture Canvas |  Team Design Team Topologies Interaction Modes |
|---|---|---|---|
Purposedifferent | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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. | When several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 45-90 min | 1-2 h | Half day |
Participantsdifferent | 3-12 | 3-10 | Team-Leads plus Architecture |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Architecture Canvas, Goals, Constraints, Quality Attributes | Interaction Heat Map, Agreements per Pair |
Tags1 shared | AlignmentStakeholdersTeam | CanvasArchitectureAlignmentWorkshop | TeamAlignmentCollaborationOrganization |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
