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 Kano Model |  Architecture Architecture Decision Record |  Architecture C4 Model |  Architecture Views and Beyond |
|---|---|---|---|---|
Purposedifferent | When features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-2 Tage | 15-45 min | 1-4 h | 1-3 Tage |
Participantsdifferent | 10-50 | 1-3 | 1-5 | 1-4 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | ADR File, Decision Log, Rationale | Context Diagram, Container Diagram, Component Diagram | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | SatisfactionPrioritizationCustomer | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationVisualization | DocumentationStakeholdersArchitecture |