View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Delegation Poker |  Systems Thinking CATWOE Analysis |  Architecture C4 Model |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. | 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 | Low | Medium | Low | Low |
Timedifferent | 45-90 min | 45-90 min | 1-4 h | 1-2 Tage |
Participantsdifferent | 3-10 | 3-8 | 1-5 | 1-4 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Delegation Board, Decision Boundaries, Role Agreements | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Context Diagram, Container Diagram, Component Diagram | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | AutonomyRolesTeam | Systems thinkingFramingStakeholders | ArchitectureCommunicationVisualization | ArchitectureDocumentationCommunication |