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 Jobs to Be Done |  Architecture arc42 |  Facilitation Stakeholder Mapping |
|---|---|---|---|
Purposedifferent | When switching motives and progress are unclear, it reconstructs the situation from real customer circumstances. It shows why a switch happens and what kind of progress is being sought. | 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. | 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. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 1-3 Wochen | 1-2 Tage | 60–90 min |
Participantsdifferent | 5-12 Interviews | 1-4 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Job Stories, Outcome Statements, Opportunity List | Architecture Document, Context View, Runtime View, Deployment View | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | CustomerOutcomesNeeds | ArchitectureDocumentationCommunication | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
