View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Concierge MVP |  Team Design Team API |  Architecture Architecture Decision Record |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-4 Wochen | Half day initial, dann laufend | 15-45 min | 1-2 Tage |
Participantsdifferent | 3-10 Kunden | Ein Team plus Stakeholder | 1-3 | 1-4 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Concierge Learnings, Service Blueprint, MVP Risks | Team API Document | ADR File, Decision Log, Rationale | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | MVPValidationServiceDiscovery | TeamAlignmentCommunicationService | ArchitectureRationaleDocumentationGovernance | ArchitectureDocumentationCommunication |