Skip to content

Chapter 6 of 6

Decision Rights, Governance, and the Stakeholder Lifecycle

Decision rights are the backbone of governance, and RACI is the workhorse tool for clarifying them. RACI maps tasks or decisions to four roles: Responsible (does the work), Accountable (owns the outcome and sign-off), Consulted (gives input before the decision), and Informed (told after the decision). The typical rule is exactly one Accountable per task, because multiple Accountables create diffused responsibility and stalled approvals. A common mistake is marking everyone as Consulted, which signals a need for input that no one actually intends to honor and produces consultation fatigue. Useful variants of RACI exist for specific situations. ARACI adds an Approver role when an additional signature step sits between Consulted and final Accountable sign-off. RASCI adds a Supported role when one function is helping Responsible complete the work without owning it. DACI is a decision-rights variant for clarifying who initiates (Driver), who signs off (Approver), who shapes (Contributor), and who is told (Informed). RACI earns its place in stakeholder work because it makes the often-invisible decision rights explicit, so consultation and sign-off become predictable rather than political.

Logs and briefs give stakeholders a shared record to work against. A decision log is a timestamped record of each significant decision that includes the date, decision, decision-maker, context, options considered, rationale, dissent, follow-up actions, and links to evidence. It is especially valuable with stakeholders because it removes the recurring "we never agreed to that" debate. A RAID log tracks Risks, Assumptions, Issues, and Dependencies as a single ongoing list; the key distinction is that a risk is a future possibility that may happen, while an issue is something that has already happened and needs handling now. A stakeholder brief is a concise summary of goal, context, risks, dependencies, and asks for a specific audience. A "no-go" decision — an explicit, recorded choice not to pursue a path — is often more valuable than a list of greenlit ideas because it preserves focus. Heat maps make risk trade-offs visible at a glance, and stakeholder KPIs (response time to asks, attendance at reviews, satisfaction survey scores) measure how well the relationship itself is performing. Net Promoter Score can be repurposed as a pulse on the relationship, and short regular stakeholder satisfaction surveys rate clarity, responsiveness, and outcomes.

Stakeholder relationships also have a lifecycle that needs management. A key stakeholder interview is a structured 30- to 60-minute conversation using open-ended questions such as "What does success look like for you?" "What is the biggest risk you see?" "What would make this fail?" and "What is off the table for you?". A stakeholder persona captures a segment's goals, frustrations, decision triggers, and preferred channels as a reusable archetype. Segmentation by lifecycle stage groups stakeholders as unaware, aware, supportive, active, leading, or alumni. A "first 30 days" plan maps introductions, briefings, and quick wins for a new stakeholder; a stakeholder introduction email sets context, role, and engagement norms. When turnover hits, a stakeholder churn event takes knowledge and authority out of the organization, and the best preparation is to maintain the register, document decisions and rationale, and cultivate at least two contacts per critical role. A stakeholder handover is the structured transition in which an outgoing stakeholder briefs the incoming one on context, open issues, and commitments. When the work itself ends, a stakeholder offboarding formally closes the relationship by capturing lessons, expressing thanks, and leaving the door open for future collaboration. Throughout, the right time to escalate a problem is when the team has exhausted its authority, when the risk is becoming irreversible, or when the relationship is at risk of breaking down — a "code red" alert that flags a material problem and a "all clear" update that closes the loop together keep stakeholders neither surprised nor haunted by old issues. The final question every engagement should answer is "What is the next conversation, with whom, about what, by when?" — because stakeholder engagement without a next step decays fast.

All chapters
  1. 1Foundations of Stakeholder Management
  2. 2Mapping and Prioritizing Stakeholders
  3. 3Communication Practices
  4. 4Stakeholder Dynamics and Hard Cases
  5. 5Negotiation and Alignment
  6. 6Decision Rights, Governance, and the Stakeholder Lifecycle

Drill it

Reading is not remembering. These come from the Stakeholder Management deck:

Q

What is stakeholder management?

Stakeholder management is the practice of understanding, aligning, and communicating with people who influence or are affected by a project or decision.

Q

Why does stakeholder management matter?

Strong stakeholder management reduces surprises, improves alignment, and makes execution smoother.

Q

Who counts as a stakeholder?

Anyone with influence over the work, dependency on the outcome, or exposure to its impact can be a stakeholder.

Q

What is a stakeholder map?

A stakeholder map is a simple view of who matters, what they care about, and how much influence they have.