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 |  Architecture C4 Model |  Operations Scatter Diagram |  Operations 8D Problem Solving |
|---|---|---|---|---|
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. | 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. | When the question is whether two measures are related, the method makes patterns in the data picture visible. It separates felt correlations from relationships that actually show up in the data. | For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. |
Complexitydifferent | Low | Low | Low | High |
Timedifferent | 45-90 min | 1-4 h | 30-90 min | 1-6 Wochen |
Participantsdifferent | 3-10 | 1-5 | 1-4 | 4-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Delegation Board, Decision Boundaries, Role Agreements | Context Diagram, Container Diagram, Component Diagram | Scatter Plot, Korrelationsnotiz, Hypothesenliste | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan |
Tagsno overlap | AutonomyRolesTeam | ArchitectureCommunicationVisualization | Root causeQualityVisualization | QualityProblem solvingRoot cause |