Operations & Process

Decision rights

Maps who actually decides what across the org map, scoring the clarity of each decision and naming gaps, overlaps and escalation traps.

  • Operations & Process
  • Traceable reasoning
  • Runs anywhere
Preview methodology

2–3 weeks ~40 minutes

For a full population, not a sample

No coding required

Input
Org map and role documentation
Output
A decision-rights map with owners per decision
Runs in
Skillsize · ChatGPT · Claude · Copilot
Export
SKILL.md · MCP
Time saved
~2–3 weeks per run

— USE CASES

What people use Decision rights for

Fixing decision bottlenecks

Find the decisions with no clear owner or three competing ones.

Post-restructure clarity

Re-establish decision rights after a structural change so teams know what they own.

Governance design

Define decision rights explicitly before a new operating model goes live.

What it works from

  • Org map and role documentation
  • Governance, delegation or authority documents
  • The decision set in scope

What you get back

  • A decision-rights map with owners per decision
  • Scored clarity, with gaps and overlaps named
  • An aggregated view of where accountability breaks down

— HOW IT BEHAVES

How Decision rights produces its result

The mechanics behind this specific template — what it reads, what it calculates, and where a human stays in the loop.

Scored against your criteria

Assessment happens against criteria you control and weight, so the same standard applies on every run.

Rolled up to the level you report at

Individual results aggregate into the population, function or portfolio view a decision-maker actually looks at.

Banded results

Results are placed into defined bands, so thresholds decide the outcome instead of individual interpretation.

Extraction to a fixed schema

Content is pulled into the same field structure every time, so records from different sources stay comparable.

Anchored to your org map

Analysis runs against your actual structure and reporting lines rather than an assumed org shape.

Live external research

Current external sources are researched during the run rather than recalled from training data, and the sources travel with the output.

Why this is expensive by hand

Slow decisions are usually an accountability problem, not a process problem. In practice it shows up as fixing decision bottlenecks: find the decisions with no clear owner or three competing ones. The value sits in the rigour, not the typing — yet the rigour is exactly what gets traded away when there is only 2–3 weeks of capacity for it.

How this Skill produces it

Here the same job runs as a Skill. Your material goes in; a decision-rights map with owners per decision comes out, alongside scored clarity, with gaps and overlaps named. The judgement is built in — how items are broken up, what standard they are held to, and where the run stops for a human review. In effect, 2–3 weeks of senior time compresses into ~40 minutes — and the output is comparable across clients, quarters and colleagues instead of shaped by whoever ran it.

Who it's for

  • Independent consultants codifying their own methodology
  • Strategy and transformation teams standardising delivery
  • Internal advisory functions under pressure to produce faster
  • Operators who need defensible output, not a one-off chat answer

Run it in Skillsize — or export it anywhere

Decision rights exports as a structured SKILL.md file and is MCP-ready, so the same method runs in ChatGPT, Claude, Copilot or your own AI products. Adapt it to your methodology, and the intelligence stays yours — not locked to one vendor.

ChatGPTClaudeCopilotAI Products (MCP)

More Operations & Process Skills

Browse the full library →