View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() UX Design Service Blueprinting | ![]() Facilitation Team Charter | ![]() Architecture Architecture Inception Canvas | ![]() Architecture Software Architecture Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | 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 Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails. | 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. |
Complexitydifferent | High | Medium | Low | Low |
Timedifferent | 0.5-2 Tage | 2-4 h | 1-2 h | 1-2 h |
Participantsdifferent | 6-12 | 3-12 | 3-8 | 3-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Service Blueprint, Fail Points, Ownership Map | Team Charter, Working Norms, Role Notes | Inception Canvas, Risks, Goal List, Open Questions | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | Service designOperationsJourneyBlueprint | TeamAlignmentCollaboration | AlignmentArchitectureCanvas | CanvasArchitectureAlignmentWorkshop |



