View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Team CharterService BlueprintingSoftware Architecture CanvasTeam Topologies Interaction Modes
| Criterion |  Facilitation Team Charter |  UX Design Service Blueprinting |  Architecture Software Architecture Canvas |  Team Design Team Topologies Interaction Modes |
|---|---|---|---|---|
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. | When a service experience is spread across several touchpoints, it brings frontstage and backstage together. It shows where user contact and internal responsibility must fit. | 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 | Medium | High | Low | Medium |
Timedifferent | 2-4 h | 0.5-2 Tage | 1-2 h | Half day |
Participantsdifferent | 3-12 | 6-12 | 3-10 | Team-Leads plus Architecture |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Team Charter, Working Norms, Role Notes | Service Blueprint, Fail Points, Ownership Map | Architecture Canvas, Goals, Constraints, Quality Attributes | Interaction Heat Map, Agreements per Pair |
Tagsno overlap | TeamAlignmentCollaboration | Service designOperationsJourneyBlueprint | CanvasArchitectureAlignmentWorkshop | TeamAlignmentCollaborationOrganization |