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 Strategy Lean Canvas |  Architecture C4 Model |  Facilitation Stakeholder Mapping |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | When an early product bet still has too many open points, it brings target group, problem, and assumptions into a single view. It condenses the idea so core risks become nameable. | 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 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 stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 45-90 min | 1-4 h | 60–90 min | 60-90 min |
Participantsdifferent | 1-6 | 1-5 | 2-8 | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Lean Canvas, Core Assumptions, Experiment Backlog | Context Diagram, Container Diagram, Component Diagram | Stakeholder Map, Engagement Plan, Risk Notes | Salience Diagram, Strategy per Class |
Tagsno overlap | StartupLeanAssumptionsBusiness model | ArchitectureCommunicationVisualization | StakeholdersAlignmentFacilitationChange | StakeholdersFacilitationAlignmentGovernance |