Index of every page on this site: llms.txt
All skills
deanpeters avatar

/decision-rights-matrix

@476ae12
Run it yourself

Define who decides, who is consulted, and who is told for key product decisions, with one accountable person each. Use when decisions stall, get reopened, or go to whoever pushes hardest.

Use this Skill: https://skilld.dev/gh/deanpeters/product-manager-skills/decision-rights-matrix

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

examplessample-industrial.md

≈576 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Decision Rights Matrix Example: Industrial

Context: Northfield Automation: product management, plant operations, regional sales, and service each run a P&L slice. The NFA-500 launch exposed that nobody knew who called go/no-go. Why this example exists: in a matrix organization with regional leaders, the veto question and escalation matter more than the RACI.


## Decisions that hurt
1. Launch go/no-go (twice, Gate 1 and Gate 2)
2. List price and partner margin
3. Customer-specific engineering commitments
4. Last-time-buy and end-of-sale for the NFA-200

## Matrix
| Decision | Driver | **Approver** | Consulted | Informed | Veto |
|---|---|---|---|---|---|
| Launch Gate 1 (order intake) | PM | **COO** | Plant, Sales, Service, Compliance | Partners | Compliance if certification gaps |
| Launch Gate 2 (first shipment) | PM | **COO** | same | same | Service if technicians not trained |
| List price and partner margin | PM | **Commercial director** | Regional sales, Finance | Partners | none |
| Special engineering commitment | Regional sales | **Engineering director** | PM, Plant | Service | none |
| NFA-200 end of sale | PM | **GM, Controls** | Finance, Service, Sales, Legal | Partners, customers | Legal if contracts bar it |

## Forums
| Forum | Decides | Does not | Cadence |
|---|---|---|---|
| Launch forum | Gate 1, Gate 2 | Price | At each gate; monthly in the quarter before |
| Commercial council | Price, partner margin | Engineering commitments | Monthly |

## Escalation
Disagreement between a regional head and the approver goes to the GM within 5 working days, with a
one-page brief covering revenue at stake, risk, and what each side wants.

## Notes
- **Service holds a veto at Gate 2.** The first draft gave "consult" and the last launch shipped
  with untrained technicians.
- **Gate 1 and Gate 2 have the same approver** (COO) on purpose: two deciders would have recreated
  the problem.

What to learn from this

  • Veto is stated with a reason and a gate. Service's veto applies only to untrained technicians.
  • Escalation has a number of days. A regional head disagreeing with an approver has a path that isn't going around.
  • The previous launch's failure turned "consulted" into a veto, with the evidence on the page.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts7d3 checks · Risk SAFE
  • Gen Agent Trust Hub7d

    This skill is a structured organizational tool for defining decision-making rights using RACI and DACI frameworks. It consists entirely of markdown templates and instructional content, with no executable code or security risks detected.

  • Socket7d

    No alerts

  • Snyk7d

    Risk: LOW · No issues

Signed by skilld at 476ae12. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated last week
argument-hint
[the decisions that stall, and who is involved]
type
component
theme
stakeholder-comms
Other metadata
intent
Make it explicit who decides what, using RACI for the work and DACI (or a similar single-approver model) for decisions, for the handful of product decisions that cause the most friction: pricing, roadmap, requirements, launch go/no-go, and end of life. Adds the forums where decisions are made, the escalation path, and a decision log. Right-sized so a small team gets a half-page and a matrix organization gets the full set.
best_for
[
  "Ending decision thrash on pricing, roadmap, or launch go/no-go",
  "Clarifying decision rights after a reorganization or when a new team joins",
  "Setting up decision forums and escalation paths that resolve conflicts in days",
  "Leading through a matrix organization without relying on goodwill"
]
scenarios
[
  "Sales keeps overriding our list prices with special deals. Who actually decides?",
  "Who should make the go/no-go call on our launch?",
  "Every roadmap decision gets reopened in the next meeting. How do we make them stick?",
  "Draft a RACI for our product decisions across product, engineering, sales, and support"
]
estimated_time
30-60 min

README badge

README badge for deanpeters/product-manager-skills/decision-rights-matrix