Mission
By the end of this chapter, you can map a stakeholder system by incentives, authority, dependence, trust, and informal influence, then choose an ethical engagement move.
- Measurable outcome: Map a stakeholder system by outcomes, incentives, authority, dependence, trust, and informal influence, then select ethical engagement moves that reduce program friction.
- Prerequisites: Chapters 4, 13, and 16; a program with at least five stakeholder groups.
- Work product: A stakeholder-system map and engagement experiment for Helios Support.
- Time: 75–95 minutes.
Before you read: Predict → Commit → Connect
Predict: The executive sponsor supports the program, yet adoption stalls. Which stakeholder without formal approval power could still determine the outcome?
Commit: Name one stakeholder whose behavior appears “resistant.” Write one plausible incentive or risk they may be protecting.
Connect: Recall a decision that changed only after an informal conversation. What information or trust was unavailable in the formal meeting?
See a system, not a contact list
Stakeholders are people or groups who affect, are affected by, or hold authority over a program. A directory of names and communication cadence is not a stakeholder strategy. Programs move through a system of formal authority, expertise, resource control, interdependence, credibility, social ties, and perceived consequences.
Map at least six dimensions:
- Outcomes: What condition does this stakeholder need?
- Incentives: What is rewarded, measured, protected, or feared?
- Formal power: What can this role approve, block, fund, or mandate?
- Informal influence: Whose judgment changes others' behavior?
- Dependence: What does the program need from them, and what do they need from it?
- Trust and history: What commitments, disappointments, or identities shape interpretation?
Treat each entry as a hypothesis to test through conversation and evidence. Do not diagnose a person's motives from a distance. Incentives are rarely singular, and stated objections may reflect legitimate domain risk.
The dotted edges are easy to miss in an organization chart. A respected support lead may have no launch approval but can determine whether agents trust the workflow, report failures, and adopt it.
Understand power without manipulating people
Power is the capacity to affect choices or access. It can come from formal authority, expertise, control of scarce resources, information, relationships, reputation, or the ability to absorb delay. Ethical influence makes relevant interests and consequences visible, uses truthful evidence, preserves meaningful choice, and respects decision rights.
Manipulation hides material information, exploits vulnerability, creates false urgency, or pressures people outside legitimate authority. It may produce short compliance and lasting distrust. A TPM should not “manage around” a control owner. Instead, clarify the actual concern, develop options, and route the choice to the authorized decision system.
Resistance is information. Ask:
- What outcome or obligation might be threatened?
- What cost is concentrated on this group while benefits go elsewhere?
- What prior commitment or failure affects credibility?
- What evidence would change the stakeholder's view?
- What can be tested reversibly?
This does not mean every objection controls the program. It means objections are interpreted before they are accepted, negotiated, or escalated.
Build trust through observable reliability
Trust is context-specific. A stakeholder may trust Engineering's competence and distrust its transparency about incidents. The TPM cannot demand trust; the program can behave in ways that make reliance more warranted:
- state uncertainty rather than overpromise;
- keep or renegotiate commitments before they fail;
- surface bad news with evidence and response;
- represent stakeholder concerns accurately, including when they are absent;
- distinguish consultation from approval;
- show how feedback changed the plan;
- close loops and explain decisions.
Use small, observable commitments to repair credibility. A grand alignment workshop cannot substitute for repeatedly delivering what was promised.
Recurring case: Helios Support
Helios leaders describe support agents as resistant to the AI assistant. The stakeholder map reveals a different system. Agents are measured on handle time but fear that correcting unsafe suggestions will add invisible work. Support experts worry their knowledge will be extracted without recognition. Privacy needs proof about data boundaries. Product receives the benefit target, while Operations absorbs incident and training costs.
An experienced operations lead, Maya, has little formal authority but strong credibility with agents and executives. The TPM does not recruit Maya to “sell” a predetermined launch. Instead, Maya helps define failure categories, agent-visible controls, and a small monitored pilot. The program adds correction effort and override behavior to the outcome evidence, funds training, and gives Support ownership of workflow acceptance.
The pilot may still be rejected if controls fail. The engagement works because it improves the decision and distribution of cost, not because it neutralizes dissent.
Decision rights: Who owns what?
- Sponsor: owns strategic sponsorship, resources, and material business trade-offs.
- Product and business owners: own user and business outcomes.
- Functional and control owners: own domain decisions and obligations within their authority.
- People managers: own performance expectations, staffing, and employment decisions; the TPM should not make covert promises on their behalf.
- Affected users or representatives: provide workflow evidence and may own operational acceptance when defined.
- TPM: maps the system, tests assumptions about interests, builds transparent engagement, and gets authorized decisions closed. The TPM does not manipulate informal influencers or misrepresent consultation as consent.
I do
I place the Helios outcome in the center and map who provides authority, expertise, labor, data, adoption, and operational support. I annotate known facts separately from hypotheses. “Agents dislike AI” is not a fact; “11 of 15 pilot agents abandoned the draft after a tool suggestion” is evidence that needs interpretation.
I interview stakeholders with the same core questions, compare differences, and identify one concentrated cost: correction work. I propose a bounded pilot that measures it and gives the correct owner a decision point.
We do
Together, repair this stakeholder strategy: “Send weekly updates to high-power/high-interest stakeholders and monthly updates to everyone else.”
We retain cadence only after adding substance. Privacy needs data-flow evidence before design freeze. Support agents need workflow prototypes and a protected feedback route. The sponsor needs scenario decisions. Engineering needs stable acceptance criteria. Maya can translate frontline evidence but should not be used as a proxy for all agents. Engagement now follows stakeholder contribution and decision need, not a two-by-two label.
You do
Map 8–12 stakeholders for a real program. For each, record outcome, formal rights, likely incentives, dependence, trust evidence, and informal ties. Label assumptions. Conduct or simulate two interviews that could disconfirm your map. Choose one source of friction and design a reversible engagement experiment with a decision owner and ethical guardrail.
Show the model answer
Model answer and 0–4 rubric
Friction: Support agents are slow to adopt Helios drafts. Evidence: abandonment and correction time are high in billing cases; interviews report fear that overrides count against handle-time targets. Stakeholder system: Product receives automation benefit; Operations absorbs correction and incident cost; managers control performance measures; Maya has informal credibility; Privacy and Security own control requirements. Experiment: Run a two-week billing pilot with human approval, correction-time measurement, explicit no-penalty feedback, daily control review, and a kill switch. Operations owns workflow acceptance; Security owns tool-control acceptance; Product owns outcome interpretation. Ethical guardrail: Explain the pilot's purpose and data use, preserve opt-out where organizational policy allows, report negative evidence, and do not use Maya to manufacture consent.
Rubric
- 0 (Missing): A broadcast list or labels based only on title.
- 1 (Emerging): Power and interest are noted, but incentives, dependence, trust, or hypotheses are absent.
- 2 (Functional): A useful map and engagement plan exist; informal influence or ethics are underdeveloped.
- 3 (Strong): Evidence tests stakeholder hypotheses, concentrated costs are addressed, and decision rights shape engagement.
- 4 (Decision-ready): Level 3 plus network updates over time, explicit ethical constraints, disconfirming evidence, and demonstrated improvement in decision or adoption quality.
Pause & Recall
Without looking, name the six dimensions of a stakeholder system. Explain the difference between influence and manipulation. Connect to Chapter 16: which stakeholder is a contributor, which is an approver, and which is informed for your next decision?
Production lens
Update the map after reorganizations, incidents, missed commitments, vendor changes, and new evidence. Avoid storing sensitive personal judgments in broadly shared artifacts; record work-relevant observations and testable needs. Watch for excluded groups, proxy representatives, benefit-cost asymmetry, and relationships concentrated in one individual. When a key connector leaves, rebuild the information path deliberately.
Workplace artifact: Stakeholder-system card
Stakeholder / role:
Outcome needed:
Formal authority:
Expertise or resources:
Program dependence / their dependence:
Observed incentives and constraints:
Trust evidence and history:
Informal ties:
Fact vs hypothesis:
Engagement or evidence need:
Decision role:
Ethical guardrail:
Next review:Chapter compression
Stakeholders form a changing system of authority, incentives, dependence, trust, and informal influence. Treat motives as hypotheses, surface concentrated costs, use reversible evidence, and influence through truth and reliable follow-through rather than hidden pressure.
Retrieval deck
- Q: Why is a stakeholder list insufficient? A: It omits relationships, dependence, incentives, trust, and informal influence that shape behavior.
- Q: What makes an incentive entry scientifically and ethically safer? A: Treat it as a hypothesis tested through observation and conversation, not a diagnosis.
- Q: How can a person have power without formal authority? A: Through expertise, credibility, relationships, information, resources, or others' dependence.
- Q: What distinguishes ethical influence from manipulation? A: Truthful evidence, visible interests, meaningful choice, and respected decision rights.
- Q: How is trust strengthened? A: Through repeated observable reliability, candor, accurate representation, and closed commitments.
Spaced review
- Now: Name the six stakeholder-system dimensions from memory.
- +1 day: Redraw the Helios network without notes.
- +3 days: Test one incentive or trust hypothesis through a conversation.
- +7 days: Update the map with disconfirming evidence and one ethical engagement move.
- +14 days: Verify that implementers received a major decision's rationale and evidence route.