View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture C4 Model |  Product Discovery Opportunity Interview |  Facilitation Stakeholder Mapping |  Facilitation Problem Framing Workshop |
|---|---|---|---|---|
Purposedifferent | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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 an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | When a team works on symptoms but the real question stays fuzzy, a Problem Framing Workshop sharpens the view of the right problem. It separates observation, interpretation, and target picture from each other. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 1-4 h | 30-60 min je Interview | 60–90 min | 60-120 min |
Participantsdifferent | 1-5 | 5-12 Interviews | 2-8 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Interview Notes, Opportunity Themes, Customer Quotes | Stakeholder Map, Engagement Plan, Risk Notes | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions |
Tagsno overlap | ArchitectureCommunicationVisualization | DiscoveryInterviewsOpportunityCustomer | StakeholdersAlignmentFacilitationChange | FacilitationAlignmentDiscovery |