Influence Without Authority: The Governance Analyst's Toolkit
The short answer
Being right and being heeded are different skills
A correct recommendation is the entry price to getting a decision moved, not a guarantee of it. Governance work that only optimizes for defensible correctness, and never for whether the right person actually acts on it, has taught half a career's worth of the job.
What you will be able to do
- Apply a four-move toolkit (find the holder and their incentive, translate evidence into their metric, secure a trusted ally, time the ask to an open decision moment) to move any real governance decision you do not personally own.
- Identify the true decision holder for a live AI governance question in your own organization, distinguishing the person with formal sign-off from the person whose informal veto actually controls the outcome.
- Translate a governance finding, expressed in the language of risk, ethics, or compliance, into the specific operational metric the decision holder is measured on and already tracks.
- Select an ally correctly: someone the holder already trusts, not someone who agrees with you the loudest, and distinguish a genuine ally from a decoy who adds noise without credibility.
- Recognize a decision window, the specific recurring moment (a budget cycle, a go-live review, a board prep meeting) when the holder already has to decide something related to your ask, and time a recommendation to land inside it rather than beside it.
- Distinguish legitimate influence from manipulation, applying a bright ethical line so that evidence-based persuasion never slides into exploiting a bias, withholding a material fact, or manufacturing false urgency.
- Produce an influence map artifact for one live decision: the holder, their incentive, your evidence reframed in their metric, the named ally, and the specific timing of the ask, filed in your dossier as the artifact this topic produces.
- Rebuild a previously ignored governance recommendation using the four moves, and state concretely what would change about its outcome.
- Scale the toolkit to a multi-person committee decision, mapping which members actually carry the outcome and preparing a distinct, honest translation for each real holder rather than one generic version for the whole room.
- Recognize the escalation boundary: the point past which repeated, knowing refusal to act on clear evidence of serious harm calls for a formal escalation or reporting channel rather than a better-refined recommendation.
The ideas, one by one
Every organization runs a decision-rights system and a decision-influence system at once
The org chart tells you who signs off; it rarely tells you whose evidence actually gets read, whose call gets returned, or what a recommendation needs to survive contact with a real decision.
The four moves, applied in order: find the holder and their incentive, translate the evidence into their metric, secure a trusted ally, time the ask to an open decision window
Each move depends on the output of the one before it; skipping or reordering one is the most common reason a sound recommendation still fails to move anything.
Translation is not spin
Restating a true finding in the holder's own measured language is finding an honest, verifiable bridge between real evidence and a number the holder already tracks, never inventing a connection that is not really there.
An ally is chosen for the holder's trust in them, not for their agreement with you
A cheerleader the holder does not particularly trust adds noise; a credible ally, whose genuine independent agreement you have honestly earned, changes a recommendation from one voice into a pattern.
Timing rides an existing decision, it does not create a new one from nothing
A recommendation that arrives inside a decision window the holder was already going to act in is an input; the same recommendation sent cold is an interruption competing for attention against everything else.
The ethics line is bright: influence changes how true evidence is received; manipulation changes what the holder is allowed to see or exploits a bias they do not know they have
Every use of the toolkit has to survive being described honestly, after the fact, to the holder, the ally, and an auditor.
This is the most common unnamed skill in an entry-level governance job
Analyst and coordinator seats own no decision right and are hired precisely to surface what leadership will not surface on its own; a program that teaches frameworks and never teaches this has left out the part of the job that determines whether any of the frameworks ever get used.
The influence map is a governance record, not just a tactic
Filed in the dossier, it lets a later reviewer check whether the plan matched the outcome, the same accountability discipline every other artifact in this program carries (see Topic 13.1).
A committee decision is the same discipline applied to more than one name
Map who inside the body actually carries the outcome, translate for each real holder's own incentive, sequence allies deliberately, and land the ask on the body's own agenda rather than requesting a special session that invites extra scrutiny.
This skill compounds across a career, and cutting a corner spends it down fast
Honest, repeated use of the four moves builds accumulated credibility that makes future recommendations faster to move; a single fabricated metric, performed ally, or exploited moment of low scrutiny spends that credibility for a one-time gain.
The vehicle for the ask matters as much as its content
A written record and a verbal moment inside the decision window each carry different strengths; the strongest asks usually combine a short written artifact with a direct conversation, rather than relying on either alone.
There is a real boundary where influence stops and escalation starts
Repeated, knowing refusal to act on clear, verified harm is not a Move 4 timing problem to keep patiently reworking; recognizing that boundary, and using the organization's formal escalation channel, is itself part of doing this job well.
Listen to it
The same lesson, talked through by two hosts as episode 75 of the podcast.
Real cases
Each example below is read specifically through the four-move lens: who held the decision, how the evidence was positioned, who lent it independent credibility, and what moment it arrived in. The anchor case gets full deep treatment; the rest are read as supporting instances the program has already documented elsewhere, cited briefly and pointed back to their owning topic rather than re-narrated.
Example 1: The campaign against Google's Project Dragonfly moves a decision no employee held (2018 to 2019). This is the anchor case for this topic. In August 2018, The Intercept revealed that Google was building Project Dragonfly, a prototype search engine for China engineered to blacklist results, images, and autocomplete suggestions about human rights, democracy, and peaceful protest to satisfy Chinese government censorship rules. The engineers, researchers, and policy staff who objected held no authority to cancel a product senior leadership had already begun building; that decision sat with Google's top executives and, ultimately, Alphabet's board. Move 1 here was less a single diagnostic question than a slow, collective realization inside the company: no individual employee's objection alone would stop Dragonfly, only sustained pressure reaching the people whose own incentive (investor confidence, regulatory standing, avoiding a public relations and legal crisis) the project actually threatened. Move 2 showed up as evidence translated into more than one leadership-legible form: an internal letter signed by more than 1,400 employees, reported by The New York Times, stating plainly that staff lacked the information to make ethically informed decisions about their own work; and an Alphabet shareholder proposal filed ahead of the June 2019 annual meeting asking the company to formally assess Dragonfly's human rights impact, framed in exactly the risk-and-governance language a board is required to formally address; the proposal itself drew only about 1.76 percent shareholder support and, like nearly all Rule 14a-8 proposals, was legally non-binding, so its force came from the disclosure obligation and the public record it created, not from any power to compel the board's decision. Move 3 appeared when Jack Poulson, a senior research scientist on Google's own search team, resigned in protest effective August 31, 2018, and then wrote directly to US senators about his concerns; a credentialed insider stepping outside the company to say the same thing employees were already saying inside it gave the concern a kind of independent standing that internal complaints alone could not. Move 4 landed on July 16, 2019, when a Senate Judiciary subcommittee hearing on Google and censorship forced Karan Bhatia, Google's vice president of government affairs and public policy, to answer on the record, in public, whether Dragonfly still existed; he testified that Google had terminated the project. The lesson is not that an employee letter automatically kills a product; it is that the letter, the resignation, the shareholder proposal, and the hearing each spoke to a part of leadership's own accountability that no single channel could reach alone, and together they made it far harder for leadership to keep deferring the decision quietly. (The Intercept, "Google Plans to Launch Censored Search Engine in China, Leaked Documents Reveal," 1 August 2018; Gizmodo, "Here's the Letter 1,400 Google Workers Sent Leadership in August," reporting The New York Times' original account, 2018; The Intercept, "Senior Google Researcher Resigns Over China Search Engine," 13 September 2018; BuzzFeed News, "A Google VP Told The US Senate The Company Has 'Terminated' The Chinese Search App Dragonfly," 16 July 2019.)
Example 2: The hostile board defense, viewed as a decision the presenter also does not fully control. Defending an AI budget to directors who interrupt (see Topic 8.5) looks, on the surface, like a different situation: you are in the room, presenting, seemingly in control of the narrative. But the actual decision, whether the budget survives the quarter, sits with the board, not the presenter. The same discipline applies in miniature: know which director cares about which number before the meeting, and have an ally on the board prepared to back a specific line before it is challenged. The difference from this topic's toolkit is mainly scale and formality, not method.
Example 3: A change narrative that failed to reach the right holder. The Robodebt scheme's public narrative was aimed at taxpayers, not at the people the system actually acted on (see Topic 9.6). Read through this topic's lens, that failure is also a Move 1 failure at a systemic level: the story was built for an audience that was never the true decision holder over whether the harm continued, while the people and institutions who could have stopped it, given honest evidence framed in their own accountability, were not the ones being addressed. A change narrative and an influence map answer different questions, but both fail for the identical underlying reason when they are aimed at the wrong audience.
Example 4: The workforce map as evidence ready for translation. The workforce map built in an earlier topic (see Topic 9.1) is exactly the kind of evidence Move 2 depends on: task-level, quantified, already expressed in headcount and timeline terms that an operations holder recognizes as their own language. An analyst who has already built an honest workforce map has done half of Move 2's work before the influence map even begins, because the evidence is already close to the holder's metric rather than trapped in governance vocabulary that needs translating from scratch.
Example 5: The consultation process as an ally-recruitment structure. The works-council process from an earlier topic (see Topic 9.5) is, read through this topic's lens, an institutionalized version of Move 3: a body whose endorsement carries independent weight with leadership precisely because it is not the analyst's own voice. An analyst who has already built genuine trust with a works-council representative on an unrelated matter holds a ready-made ally for a future recommendation that representative would independently support, without having to build that relationship from nothing under time pressure.
Example 6: The honest ROI reckoning as a source of holder-ready metrics. The honest ROI work from an earlier topic (see Topic 8.1) measures what an AI system actually changed, in the same operational terms most holders are personally accountable for. An analyst preparing to translate a governance finding for a specific holder should check whether an honest ROI analysis already exists for the system in question; if it does, it is very often the fastest, most credible path to Move 2, because it was built and defended in the holder's own numbers from the start rather than composed afterward to persuade.
Example 7: A resistance signal, decoded, becomes the evidence itself. Reading a team's quiet refusal to adopt a tool as information rather than obstruction (see Topic 9.3) often surfaces exactly the kind of concrete, operational evidence Move 2 needs. A sales team's reluctance to use an AI scoring tool, decoded, might reveal that the tool's recommendations conflict with a metric the sales director is personally accountable for; that decoded resistance is not a separate problem from the influence toolkit, it is often the raw material an analyst needed to translate a governance concern into a holder's own language in the first place.
Example 8: The escalation boundary in miniature. Section 3J's boundary case is rare, but its shape appears in smaller form whenever a holder has already declined the same well-evidenced recommendation twice, with a properly built influence map each time. An analyst who runs the four moves correctly, more than once, against the same holder for the same serious finding and still gets no movement has gathered real evidence that the situation has crossed from an influence problem into a question for the organization's formal escalation or reporting channel, not a signal to keep refining the same map indefinitely.
Where people go wrong
- "If my analysis is correct, it will get acted on." No. Correctness is the entry price to the decision-influence system, not a ticket that moves anything by itself. A correct recommendation addressed to the wrong holder, stated in the wrong language, unsupported by a trusted voice, and sent at the wrong moment will sit exactly as unread as an incorrect one. Being right and being heeded are different skills.
- "I should escalate straight to the most senior person available." The most senior person is frequently not the real holder of the specific decision in question. Escalating past the actual holder without first identifying them wastes the senior person's attention on a decision they may not control either, and can damage your relationship with the true holder, who correctly reads being bypassed as a hostile move.
- "The ally should be whoever agrees with me most enthusiastically." An enthusiastic ally the holder does not particularly trust adds noise, not credibility, and can make the recommendation look fringe. The ally is selected for the holder's trust in them, and their agreement then has to be earned honestly on the merits, not assumed because they are friendly to you.
- "Framing my finding in the holder's metric is manipulative." It is manipulative only if the connection is fabricated. An honest, verifiable translation of a true finding into the language the holder already measures is not spin; it is making a true thing legible to the person who has to act on it. Refusing to translate, and insisting the holder should simply care because the finding is important in your own department's terms, is not more honest, it is just less effective and often less honest about how organizations actually work.
- "Waiting for the right moment is stalling." Deliberate timing to a genuine decision window is not the same as sitting on urgent information. A recommendation with real time pressure (an imminent safety risk, a legal deadline) should escalate through the appropriate emergency channel immediately; the timing move applies to recommendations that can honestly wait for the next natural decision point without the risk growing meanwhile.
- "Once I've influenced the decision correctly, the ethics question is settled." The ethics line has to be checked on every use of the toolkit, not once. A translation that was honest last time can become a fabrication this time if the underlying data has changed and you did not update it. Manipulation is a property of each specific act, not a status you earn immunity from by having behaved well before.
- "This toolkit is about being persuasive; persuasive people are naturally good at this." Natural charisma is not the mechanism here, and relying on it is a trap: a persuasive but unprepared ask, aimed at the wrong holder or timed to the wrong moment, fails for the same structural reasons an unpersuasive one does. The four moves are a substitute for charisma, not a supplement to it; a quiet, methodical analyst who does the homework in Move 1 will consistently outperform a charismatic one who skips it.
- "If the holder says no once, the decision is closed." A no at the wrong time, to the wrong framing, without an ally, is not the same evidence as a no after all four moves are correctly applied. Before treating a rejection as final, check honestly whether it was actually tested against the toolkit or whether it was a foreseeable failure of an unprepared ask.
- "Escalating to my own manager is the fastest way to move a decision I do not own." Going around the real holder to a manager who also has to persuade that same holder rarely accelerates anything, and it frequently damages the direct relationship the analyst needs for every future recommendation. Escalation is the right move only when the risk is genuinely urgent and the appropriate channel for that urgency exists; used as a default shortcut, it substitutes organizational friction for the actual work of Moves 1 through 4.
- "A committee decision just means I need more allies, proportionally." Recruiting a large number of low-influence allies is not the same as recruiting the one or two members whose objection actually carries the room. A committee decision requires the same discipline as a single-holder decision, mapping who really holds the outcome, applied to more than one name, not a numbers game where more voices automatically wins.
- "A holder who keeps saying no despite clear evidence just needs a better influence map." Past a certain point, repeated, knowing refusal to act on verified serious harm is not a Move 4 timing problem to keep patiently reworking; it is the escalation boundary described in Section 3J, and it calls for the organization's formal escalation or reporting channel rather than an ever-more-polished recommendation.
- "Building the influence map takes too long; I will just wing it in the meeting." Skipping the map does not remove the four moves' requirements, it only means they are checked, if at all, in real time under pressure, where a missed holder, an unvetted ally, or a fabricated-sounding metric connection is far more likely and far more costly to discover in the room than on paper beforehand.
- "A written memo and a verbal mention are interchangeable; the vehicle does not matter as long as the finding is correct." The vehicle affects whether the finding is actually received and retained: a detailed technical finding buried inside a verbal aside is easy to lose, and a simple, urgent finding trapped inside a long document a busy holder skims is easy to miss. Choosing the vehicle correctly, per Section 3L, is part of positioning the case, not a cosmetic afterthought.
- "Tracking my own success rate over time is unnecessary; I already know how I'm doing." A felt sense of "I'm getting better at this" is not the same evidence this program requires anywhere else, and it is not the standard this topic asks a learner to apply to it either. The three concrete signals in Section 3M (time to decision, the acted-on ratio, and holders proactively seeking input) exist precisely because an analyst's own impression of their improvement is the least reliable evidence available about it.
Questions people ask
- What is decision holder?
- The person whose formal or informal sign-off actually has to happen for a recommendation to become real, which is frequently not the person named on the org chart. Identified by asking who would actually have to object for the decision to stall.
- What is decision-rights system?
- The formal structure of who is authorized to approve a decision: titles, org charts, sign-off lines. Distinguished in this topic from the decision-influence system, which determines whose evidence actually gets read and acted on.
- What is decision-influence system?
- The informal structure that determines whose evidence gets read, whose call gets returned, and what a recommendation needs to survive contact with a real decision. Correctness gets a recommendation into this system; it does not by itself move anything inside it.
- What is the four moves?
- The repeatable, ordered toolkit for moving a decision you do not own: identify the holder and their incentive, translate evidence into the holder's own metric, secure a trusted ally, time the ask to a decision window. Each move depends on the output of the one before it.
- What is incentive (of a decision holder)?
- The specific metric or outcome a decision holder is personally measured on and accountable for, distinct from the abstract category (ethics, compliance, risk) a governance finding may be framed in natively.
Keep going
This lesson builds Adoption and change management, and that page shows the roles that hire for it. Every Certified AI Governance Professional (CAIGP) lesson.
Watch the lesson and prove it
Proving it happens inside the program: watch, explain it in your own words, and it goes on a record employers can check.
Watch the lesson and prove it →