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 Opportunity Interview | ![]() Delivery Communication Plan | ![]() Architecture arc42 | ![]() Architecture Views and Beyond |
|---|---|---|---|---|
Purposedifferent | When opportunities are still hidden behind signals of need, it structures conversations around needs and obstacles. It looks for patterns that lead to new product opportunities. | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. | 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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 30-60 min je Interview | 45-90 min | 1-2 Tage | 1-3 Tage |
Participantsdifferent | 5-12 Interviews | 2-6 | 1-4 | 1-4 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Communication Plan, Channel Matrix, Message Cadence | Architecture Document, Context View, Runtime View, Deployment View | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | CommunicationStakeholdersDeliveryPlanning | ArchitectureDocumentationCommunication | DocumentationStakeholdersArchitecture |



