View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking CATWOE Analysis |  Facilitation Delegation Poker |  Architecture arc42 |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | When decisions get stuck between leadership and team, Delegation Poker clarifies the desired scope of autonomy. It shows how much decision-making latitude a role should actually get in practice. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 45-90 min | 45-90 min | 1-2 Tage | 15-45 min |
Participantsdifferent | 3-8 | 3-10 | 1-4 | 1-3 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Async |
Outputdifferent | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Delegation Board, Decision Boundaries, Role Agreements | Architecture Document, Context View, Runtime View, Deployment View | ADR File, Decision Log, Rationale |
Tagsno overlap | Systems thinkingFramingStakeholders | AutonomyRolesTeam | ArchitectureDocumentationCommunication | ArchitectureRationaleDocumentationGovernance |