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.md

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

Decision Rights Matrix Example: SaaS

Context: Fieldlight. Sales keeps granting add-on discounts the product team set limits on; roadmap items get re-opened every Monday. 40 people across product, sales, CS, and finance. Why this example exists: "both" was the answer to every question, and splitting each decision was the whole job.


## Decisions that hurt
1. Add-on discount limits (sales overrides weekly)
2. What goes on next quarter's roadmap (reopened every Monday)
3. Customer-specific commitments (a promised feature for one deal)
4. Launch go/no-go for the Route Optimizer

## Matrix
| Decision | Driver | **Approver** | Consulted | Informed | Veto |
|---|---|---|---|---|---|
| Discount band for add-ons | PM (pricing) | **VP Product** | Finance, Sales VP | Reps, CS | Finance if margin below floor |
| Quarterly roadmap | PM | **VP Product** | Engineering, Sales, CS | Company | none |
| Deal-specific commitments | Account exec | **VP Sales** (within bands) / **VP Product** (outside) | PM, Engineering | CS | none |
| Launch go/no-go | PM | **VP Product** | Support, Sales, Legal, Engineering | Company | Legal if a must-pass fails |

*Note: "Deal-specific commitments" was "both" in the first draft; split by whether it is inside the agreed bands.*

## Forums
| Forum | Decides | Does not | Attends | Cadence |
|---|---|---|---|---|
| Pricing council | Discount bands, exceptions above band | List price | VP Product, VP Sales, Finance | Fortnightly, 30 min |
| Roadmap review | Quarter's roadmap | Individual deals | VP Product, Eng lead, Sales, CS | Monthly |

## Escalation
Pricing disputes go to the COO within 3 working days, with a one-page brief (deal size, margin impact).

## Decision log (first entries)
| Date | Decision | By | Evidence | Supersedes |
|---|---|---|---|---|
| Nov 4 | Add-on discount band 0-12%; above needs council | VP Product | Margin model, 11 deals | none |

All approvers confirmed individually before circulation. COO endorsed the escalation path.

What to learn from this

  • "Both" was split into inside-the-band and outside-the-band, which gave each side a real zone.
  • Finance's veto is stated with a reason (margin floor), so it can't become a general block.
  • The matrix was confirmed individually before it went to a group, so nobody learned of their role in a meeting.

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