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 Quality Attribute Workshop | ![]() Innovation Brainstorming | ![]() Innovation Reverse Brainstorming |
|---|---|---|---|---|
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. | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. | When a team faces an open question with many obvious directions, the method first creates breadth instead of premature commitment. It separates idea flow from evaluation and makes lines of thought visible, creating a pool for selection and further development. | For persistent errors or blockages, the method shifts the view to the opposite of the desired effect. It exposes the mechanics of failure and makes hidden causes easier to grasp. This makes improvement more concrete and the problem clearer. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 1-4 h | 2-4 h | 30-60 min | 30-60 min |
Participantsdifferent | 1-5 | 5-15 | 4-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Quality Scenarios, Priority List, Architecture Concerns | Idea pool, Theme clusters, Shortlist | Reverse Ideas, Risk Themes, Solution Ideas |
Tagsno overlap | ArchitectureCommunicationVisualization | RequirementsArchitectureWorkshop | BrainstormingIdeationCreativityWorkshopDivergence | BrainstormingIdeationCreativityRisk |



