methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration for Team Charter.
Facilitation
Team Charter
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
A paper-based illustration representing Customer Journey Canvas with its core stages and visible working result.
UX Design
Customer Journey Canvas
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
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 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.When a journey needs to be understood across several phases, it arranges experience, touchpoints, and opportunities into one picture. It makes gaps and friction along the user path clear.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
MediumLowMediumLow
Timedifferent
2-4 h1-2 h1-3 h1-2 h
Participantsdifferent
3-123-83-103-10
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Team Charter, Working Norms, Role NotesInception Canvas, Risks, Goal List, Open QuestionsCustomer Journey Canvas, Pain Points, Experience OpportunitiesArchitecture Canvas, Goals, Constraints, Quality Attributes
Tagsno overlap
TeamAlignmentCollaboration
AlignmentArchitectureCanvas
JourneyCustomerService designCanvas
CanvasArchitectureAlignmentWorkshop
Add more methods