Decision rights
Who decides what on the team: one decision, one owner, consulted parties named — plus the supporting RACI matrix.
Decision rights
| Decision | Owner | Consulted |
|---|---|---|
| What outcome is valuable | Customer | Product manager, product designer |
| Build priority — what’s next | Product manager | Customer, trio, team |
| Technical approach | Tech lead | Engineers, enabling architects |
| UX and discovery method | Product designer | Product manager, users |
| Increment readiness | The product trio | Team |
| Commitment for the cycle | The team | Trio |
| Readiness exceptions | The trio — logged and visible | — |
| Team-specific decision | One owner | Consulted parties |
Exceptions
Decisions made off-table happen. Record every one in the exception log: who decided, what rule was excepted and why. Repeated exceptions against the same row mean the allocation is wrong, or the owner is being routed around. Both need fixing.
RACI matrix
The litmus test: if you can phrase it as who runs or produces X, it belongs in the RACI. If it’s who gets to choose X, it belongs in decision rights above.
| Outputs | Product Manager | Product Designer | Tech Lead | Architect | Product Engineer | Data / Business Analyst | DSO Engineer | Engineer / Quality Engineer | Customer |
|---|---|---|---|---|---|---|---|---|---|
| Strategic Event Storming | A | R | R | R | R | C | I | R | R |
| Tactical Event Storming | R | C | A | R | R | C | I | R | I |
| Target State Design | C | I | R | A | C | I | C | I | I |
| Business Analysis | A | C | R | I | I | R | I | C | C |
| Increment Planning | A | C | R | I | R | I | C | C | I |
| Demos, Retros, Standup | A | R | R | I | R | I | I | R | C |
R = Responsible, A = Accountable, C = Consulted, I = Informed
| |||||||||