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 of Team API with its method-specific working model.
Team Design
Team API
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document.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 Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.
Complexitydifferent
LowLowMediumMedium
Timedifferent
Half day initial, dann laufend1-2 h60-120 min1-2 h
Participantsdifferent
Ein Team plus Stakeholder3-82-84-12
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Team API DocumentInception Canvas, Risks, Goal List, Open QuestionsCommunication Canvas, Stakeholder Messages, Architecture Communication PlanAlignment Map, Open Issues, Decision Questions
Tagsno overlap
TeamAlignmentCommunicationService
AlignmentArchitectureCanvas
ArchitectureCommunicationStakeholdersCanvas
AlignmentStakeholdersStrategyFacilitation
Add more methods