Who Actually Has the Authority Here? Why Decision Rights Are the Hidden Engine of Project Success

Ask a project manager where budgets go off the rails, and you will hear the usual suspects: scope creep, resource shortages, technology failures. Rarely does anyone point to the moment — usually buried somewhere in week two — when a critical decision sat in an inbox for eleven days because nobody could agree on who was actually empowered to make it.

That ambiguity is not a minor inconvenience. It is one of the most expensive structural flaws in modern project governance, and it is almost entirely preventable.

The Real Cost of Decision Ambiguity

A 2023 PMI Pulse of the Profession report found that organizations waste an average of $97 million for every $1 billion spent on projects due to poor performance — and a significant share of that underperformance traces back to governance failures rather than technical ones. When decision authority is unclear, teams default to escalation. Escalation introduces delay. Delay compounds. By the time a project is formally flagged as troubled, the root cause — ambiguous ownership of key decisions — has been baked into the project's DNA for weeks.

Consider a mid-sized healthcare technology firm in the Midwest that launched a patient portal upgrade with a cross-functional team spanning IT, clinical operations, compliance, and marketing. The project had a RACI chart. It had a project charter. What it did not have was clarity on who could approve interface design changes that touched both clinical workflow and brand standards. When a dispute arose in week three, it traveled up two management chains simultaneously, generated four separate email threads, and consumed roughly 40 hours of senior leadership time before a decision was rendered. The delay pushed the first milestone by three weeks. That three-week slip cascaded through the entire schedule.

The problem was not the people. The problem was the architecture.

Why Most RACI Matrices Fail in Practice

The RACI model — Responsible, Accountable, Consulted, Informed — is nearly ubiquitous in U.S. project management practice. It is also nearly universally misapplied.

The most common failure mode is what might be called "RACI inflation": the tendency to assign Accountable status to multiple stakeholders simultaneously, or to list so many Consulted parties that the consultation process itself becomes a bottleneck. When three senior vice presidents are each listed as Accountable for a deliverable, none of them truly owns it. The designation becomes political decoration rather than operational guidance.

A second failure mode is temporal vagueness. A RACI matrix typically identifies who is accountable for a deliverable, but it rarely specifies the decision windows, escalation thresholds, or tie-breaking protocols that govern what happens when the accountable party is unavailable, conflicted, or simply slow to respond.

The result is a document that looks like governance but functions like bureaucratic cover.

Introducing the Decision Rights Charter

A Decision Rights Charter is not a replacement for the RACI matrix — it is its operational complement. Where a RACI defines roles relative to deliverables, a Decision Rights Charter defines authority relative to specific decision categories, establishing not just who decides, but under what conditions, within what timeframe, and through what escalation path.

An effective Decision Rights Charter addresses five core elements:

1. Decision Categories Group project decisions into logical domains: budget modifications, scope changes, resource reallocation, vendor selection, timeline adjustments, and compliance-related determinations. Each category may carry different authority thresholds.

2. Authority Tiers For each category, define the dollar or impact threshold that determines which level of the organization holds decision authority. A project manager may have unilateral authority over budget reallocations below $10,000, while anything above that threshold requires sponsor approval. Making these thresholds explicit eliminates the gray zones where delays breed.

3. Decision Windows Specify the maximum number of business days within which a decision must be rendered once formally submitted. This is not a soft suggestion — it is a governance commitment. Build in an automatic escalation trigger if the window lapses without resolution.

4. Tie-Breaking Protocols In cross-functional environments, conflicting priorities between departments are inevitable. The charter should name a designated tie-breaker for each decision category — typically the project sponsor or a standing governance committee — so that disputes do not orbit indefinitely.

5. Documentation Requirements Establish a lightweight but consistent record of how and why key decisions were made. This protects the project from revisionism, accelerates onboarding of new team members, and provides invaluable material for post-project reviews.

Putting It Into Practice at Kickoff

The Decision Rights Charter is most effective when introduced during the project kickoff process, not after the first conflict surfaces. Presenting it as a standard governance artifact — alongside the project charter, the communication plan, and the risk register — normalizes it as a professional expectation rather than a reaction to dysfunction.

During kickoff, walk stakeholders through each decision category and confirm alignment on authority tiers. Pay particular attention to decisions that cross departmental lines; these are the highest-risk zones for ambiguity. Where stakeholders express discomfort with the proposed authority assignments, treat that discomfort as signal. It is far better to surface a political tension in week one than to discover it when a $200,000 vendor contract is awaiting signature.

One practical technique: ask each named decision-maker to verbally confirm their understanding of their authority scope in the kickoff meeting. The act of public confirmation creates accountability that a signature on a document alone does not.

The Organizational Dividend

Organizations that implement structured decision rights frameworks consistently report measurable improvements in project velocity. A financial services firm in the Chicago area piloted a Decision Rights Charter across eight concurrent projects and documented a 47 percent reduction in approval cycle times over two quarters. More significantly, project teams reported higher confidence levels and lower escalation rates — indicators that the framework was reducing not just delays but the organizational anxiety that accompanies ambiguity.

That anxiety has a cost that rarely appears on a budget report. When team members are uncertain about who can say yes, they hedge. They over-document. They seek informal pre-approvals. They delay their own work while waiting for clarity that should have been established at the outset. This friction is invisible on a Gantt chart but very visible on a final project cost summary.

Smarter Governance Starts Before the Work Does

Project management excellence is often framed as a discipline of execution — of managing timelines, resources, and deliverables with precision. That framing, while valid, obscures a foundational truth: the conditions for success or failure are largely established in the governance decisions made before meaningful execution begins.

Clarifying who holds decision authority — specifically, explicitly, and with enforceable structure — is not administrative overhead. It is one of the highest-leverage investments a project leader can make. The teams that do this well do not just deliver on time and on budget more consistently. They build the kind of organizational trust that makes the next project easier to launch, easier to staff, and easier to lead.

The decision to get decision rights right is yours to make. Make it at kickoff.