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
Paper illustration for Concierge MVP
Product Discovery
Concierge MVP
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
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.When an idea can first fail or grow through genuine hands-on support, it relies on manual work instead of automation. It shows whether user value holds up even under manual execution.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
Half day initial, dann laufend1-4 Wochen15-45 min1-2 h
Participantsdifferent
Ein Team plus Stakeholder3-10 Kunden1-33-8
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop
Outputdifferent
Team API DocumentConcierge Learnings, Service Blueprint, MVP RisksADR File, Decision Log, RationaleInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
TeamAlignmentCommunicationService
MVPValidationServiceDiscovery
ArchitectureRationaleDocumentationGovernance
AlignmentArchitectureCanvas
Add more methods