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 Team Charter |  Architecture Software Architecture Canvas |  Facilitation Expectation Mapping |
|---|---|---|---|
Purposedifferent | 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. | 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 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. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 2-4 h | 1-2 h | 45-90 min |
Participantsdifferent | 3-12 | 3-10 | 3-12 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Team Charter, Working Norms, Role Notes | Architecture Canvas, Goals, Constraints, Quality Attributes | Expectation Map, Alignment Notes, Agreements |
Tags1 shared | TeamAlignmentCollaboration | CanvasArchitectureAlignmentWorkshop | AlignmentStakeholdersTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
