View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Innovation Contradiction Analysis | ![]() Architecture arc42 | ![]() Innovation TRIZ | ![]() Architecture C4 Model |
|---|---|---|---|---|
Purposedifferent | When a system should improve while another measure suffers as a result, the method makes the underlying conflict precisely formulable. It separates the desired effect from its side effect. This makes solutions possible that address the contradiction deliberately instead of half-heartedly. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | For technical contradictions or trade-offs, the method looks for solutions that resolve opposing requirements at the same time. It translates limits into an explicit picture of conflict that becomes workable. This produces not just compromises but more elegant principles. | 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. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 60-120 min | 1-2 Tage | 1-4 h | 1-4 h |
Participantsdifferent | 2-8 | 1-4 | 2-8 | 1-5 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Contradiction Statement, Abstraction Notes, Solution Principles, Concept Ideas | Architecture Document, Context View, Runtime View, Deployment View | Contradiction Statement, Inventive Principles, Solution Concepts | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | ContradictionsInnovationProblem solving | ArchitectureDocumentationCommunication | InnovationProblem solvingContradictionsCreativity | ArchitectureCommunicationVisualization |



