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 of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration for Concierge MVP
Product Discovery
Concierge MVP
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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.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.
Complexitydifferent
LowMediumLowMedium
Timedifferent
Half day initial, dann laufend45-60 min45-90 min1-4 Wochen
Participantsdifferent
Ein Team plus Stakeholder2-82-83-10 Kunden
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Team API DocumentAssumption map, Test backlog, Risk rankingAssumption List, Critical Assumptions, Learning PlanConcierge Learnings, Service Blueprint, MVP Risks
Tagsno overlap
TeamAlignmentCommunicationService
AssumptionsRiskExperimentsValidation
AssumptionsRiskDecisionDiscovery
MVPValidationServiceDiscovery
Add more methods