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 Outcome-Driven Innovation |  Architecture C4 Model |  Architecture Software Architecture Canvas |  Architecture Architecture Inception Canvas |
|---|---|---|---|---|
Purposedifferent | Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs. | 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. | 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 Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails. |
Complexitydifferent | High | Low | Low | Low |
Timedifferent | Mehrere Wochen | 1-4 h | 1-2 h | 1-2 h |
Participantsdifferent | 2-6 researchers plus sample | 1-5 | 3-10 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Context Diagram, Container Diagram, Component Diagram | Architecture Canvas, Goals, Constraints, Quality Attributes | Inception Canvas, Risks, Goal List, Open Questions |
Tagsno overlap | OutcomesInnovationResearchQuantitative | ArchitectureCommunicationVisualization | CanvasArchitectureAlignmentWorkshop | AlignmentArchitectureCanvas |