View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Software Architecture CanvasTeam CharterExpectation MappingTeam Topologies Interaction Modes
| Criterion |  Architecture Software Architecture Canvas |  Facilitation Team Charter |  Facilitation Expectation Mapping |  Team Design Team Topologies Interaction Modes |
|---|---|---|---|---|
Purposedifferent | 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 a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. | 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. | 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 | Medium | Low | Medium |
Timedifferent | 1-2 h | 2-4 h | 45-90 min | Half day |
Participantsdifferent | 3-10 | 3-12 | 3-12 | Team-Leads plus Architecture |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Architecture Canvas, Goals, Constraints, Quality Attributes | Team Charter, Working Norms, Role Notes | Expectation Map, Alignment Notes, Agreements | Interaction Heat Map, Agreements per Pair |
Tags1 shared | CanvasArchitectureAlignmentWorkshop | TeamAlignmentCollaboration | AlignmentStakeholdersTeam | TeamAlignmentCollaborationOrganization |