Skip to content

deanpeters/Product-Manager-Skills / plugins/pm-drive/skills/decision-rights-matrix

decision-rights-matrix

Verified

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.

FileKindSize
SKILL.mdskill md12.2 KB
examples/sample-industrial.mdmarkdown2.2 KB
examples/sample.mdmarkdown2.3 KB
template.mdmarkdown1.2 KB

examples/sample-industrial.md

View on GitHub
# 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.

---

```markdown
## 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.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall