View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Jobs to Be DoneConsensus WorkshopSoftware Architecture CanvasArchitecture Communication Canvas
| Criterion |  Product Discovery Jobs to Be Done |  Facilitation Consensus Workshop |  Architecture Software Architecture Canvas |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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. | When a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 Wochen | 1-3 h | 1-2 h | 60-120 min |
Participantsdifferent | 5-12 Interviews | 5-30 | 3-10 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Job Stories, Outcome Statements, Opportunity List | Consensus Clusters, Theme Titles, Priority Areas | Architecture Canvas, Goals, Constraints, Quality Attributes | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | CustomerOutcomesNeeds | FacilitationConsensusWorkshopAlignment | CanvasArchitectureAlignmentWorkshop | ArchitectureCommunicationStakeholdersCanvas |