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 Architecture Decision Record |  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. | 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. | 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 | 15-45 min | 2-6 h |
Participantsdifferent | 3-10 | 1-3 | 3-10 |
Formatdifferent | Workshop | Async | Workshop |
Outputdifferent | Delegation Board, Decision Boundaries, Role Agreements | ADR File, Decision Log, Rationale | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | AutonomyRolesTeam | ArchitectureRationaleDocumentationGovernance | RiskQualityOperationsRoot cause |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
