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 Failure Mode and Effects Analysis |
|---|---|---|---|
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. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. |
Complexitydifferent | Low | Low | High |
Timedifferent | 45-90 min | 1-4 h | 2-6 h |
Participantsdifferent | 3-10 | 1-5 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Delegation Board, Decision Boundaries, Role Agreements | Context Diagram, Container Diagram, Component Diagram | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | AutonomyRolesTeam | ArchitectureCommunicationVisualization | RiskQualityOperationsRoot cause |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
