View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Architecture C4 Model | ![]() Architecture Architecture Decision Record | ![]() Innovation SCAMPER | ![]() Innovation Lotus Blossom |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | For an existing solution under pressure to change, the method deliberately opens space for systematic variants. It directs attention to rebuilding, combining, and repurposing rather than only new basic ideas. This produces concrete evolution paths for products, offerings, or workflows. | When a central question feels too large, the method breaks it into neighboring topic fields with their own depth of ideation. It holds structure and openness at the same time, so adjacent perspectives don't get lost. This grows an idea space out of a core problem. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 1-4 h | 15-45 min | 30-60 min | 45-90 min |
Participantsdifferent | 1-5 | 1-3 | 2-10 | 3-10 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | ADR File, Decision Log, Rationale | SCAMPER Idea List, Concept Shortlist, Variation Notes | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | ArchitectureCommunicationVisualization | ArchitectureRationaleDocumentationGovernance | BrainstormingIdeationCreativityReframingInnovation | BrainstormingIdeationCreativityDivergenceWorkshop |



