Portfolio & delivery governance · Field note

Who gets to decide

TL;DR

Evidence does not change work by itself. For choices that matter, name who builds the case, flags a legal, safety, or policy limit that blocks an option, decides, and changes the work.

What the paper develops

A review can show that a project is late, a risk has changed, or another team needs the same people. The meeting still ends with a request for more analysis when no one has the right to redirect, pause, or stop the work.

An org chart does not answer that question. It names jobs. A decision contract names who takes each step when a real choice arrives.

First, name the recommender. That person builds the case, options, evidence, and due date. Second, name any agree role. Use a veto only for a real legal, safety, or policy limit, and require an option or an escalation path.

Third, name the decider. One person can close most operating choices. A board or required group can decide when the rules demand it, but the contract must say how the group closes the vote. Fourth, name the performer who changes the funding, work, permission, or record.

Add the four jobs to the intake form, stage gate, decision record, and delivery tool. If an agree role rejects a plan, record the limit, an acceptable option, and where the case goes next. If the decider misses the due date, pause, escalate, or use a short, recorded extension.

An agent can prepare a recommendation or act inside an approved limit. Named people still set the limit, decide exceptions, and own recovery. A rule can stop an unsafe action without gaining the right to restart the work.

Use the full contract for choices that are hard to reverse, affect other teams, or create real exposure. Keep low-cost choices close to the work.

Pick five recent decisions. Trace who built the case, who could block it, who closed it, and who changed the work. Repair the missing role, rule, or workflow step before the next decision arrives.

What to do next

Pick five recent decisions. Name who built the case, could block an option for a stated reason, decided, and changed the work.

OWNEREVIDENCENEXT COMMITMENT

Inside the white paper

  • Four jobs that take a choice from evidence to action
  • How to put those jobs in the workflow
  • How agents act inside limits set by named people

Sources and notes

  1. Paul Rogers and Marcia Blenko, "Who Has the D?" Bain & Company, June 28, 2006 — Bain's RAPID framework separates recommending, agreeing, deciding, and performing.
  2. Gary L. Neilson, Karla L. Martin, and Elizabeth Powers, "The Secrets to Successful Strategy Execution," Harvard Business Review 86, no. 6 (June 2008): 60–70. No reader-facing link is included because the full article is subscription-only — a study of more than 125,000 employee profiles found decision rights and information flow were strong execution levers.
  3. Thomas A. Stewart, "Putting Strategy into Practice," strategy+business, April 19, 2010 — a readable account of the same execution research reports the importance of decision rights and information flow.
  4. Project Management Institute, Pulse of the Profession 2026: Driving Success in Complex Projects - From Navigating Tasks to Navigating Systems, May 2026 — PMI names unclear decision authority as a source of decision friction and rework.
  5. Robert G. Cooper and Scott J. Edgett, "Portfolio Management: Fundamental for New Product Success," Stage-Gate International — portfolio management includes choosing, ranking, stopping, and moving resources among projects.
  6. Alexander Sukharevsky, Alexis Krivkovich, Arne Gast, Arsen Storozhev, Dana Maor, Deepak Mahadevan, Lari Hämäläinen, and Sandra Durth, "The Agentic Organization: Contours of the Next Paradigm for the AI Era," McKinsey & Company, September 26, 2025 — McKinsey advises embedded governance with people holding final accountability for agent actions.
  7. David Mallon, Brad Kreit, and Natasha Buckley, "Rethinking Operating Models for Humans with Agents," Deloitte Insights, April 2, 2026 — Deloitte advises setting human sign-off, escalation paths, stop mechanisms, and exception handling up front.
  8. David Mallon, Julie Duda, Stefano Besana, and Maya Bodan, "AI and the Future of Human Decision-Making," Deloitte Insights, March 3, 2026 — Deloitte calls for clear owners, override privileges, and escalation paths in AI decision systems.
  9. Jeffrey P. Bezos, Amazon 2015 Letter to Shareholders, 2016 — Amazon distinguishes hard-to-reverse choices from choices that can be made and changed quickly.
  10. Kathleen M. Eisenhardt, "Making Fast Strategic Decisions in High-Velocity Environments," Academy of Management Journal 32, no. 3 (1989): 543–576 — an eight-firm study found fast teams sought consensus, then used a CEO-led choice when consensus did not come.