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 arc42 | ![]() Architecture Architecture Inception Canvas |
|---|---|---|---|---|
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. | 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. | 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 | Medium | Low | Low | Low |
Timedifferent | 1-4 Wochen | Half day initial, dann laufend | 1-2 Tage | 1-2 h |
Participantsdifferent | 3-10 Kunden | Ein Team plus Stakeholder | 1-4 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Concierge Learnings, Service Blueprint, MVP Risks | Team API Document | Architecture Document, Context View, Runtime View, Deployment View | Inception Canvas, Risks, Goal List, Open Questions |
Tagsno overlap | MVPValidationServiceDiscovery | TeamAlignmentCommunicationService | ArchitectureDocumentationCommunication | AlignmentArchitectureCanvas |



