View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:CATWOE AnalysisTheory of Constraints Thinking ProcessArchitecture Communication Canvasarc42
| Criterion | ![]() Systems Thinking CATWOE Analysis | ![]() Systems Thinking Theory of Constraints Thinking Process | ![]() Architecture Architecture Communication Canvas | ![]() Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way. | The Theory of Constraints Thinking Process exposes a system's bottleneck and the logic behind it. It suits situations where many symptoms trace back to the same limiting relationship. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. |
Complexitydifferent | Medium | High | Medium | Low |
Timedifferent | 45-90 min | 0.5-3 Tage | 60-120 min | 1-2 Tage |
Participantsdifferent | 3-8 | 4-10 | 2-8 | 1-4 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Current Reality Logic, Conflict Cloud, Future Reality Tree, Implementation Obstacles | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | Systems thinkingFramingStakeholders | Theory of ConstraintsConstraintsSystems thinkingCausality | ArchitectureCommunicationStakeholdersCanvas | ArchitectureDocumentationCommunication |



