Learning Objectives

After completing this lecture, learners will be able to construct a federal stakeholder map that distinguishes statutory stakeholders (appropriators, authorizers, the GAO, the agency Inspector General, OMB desk officers, OPM, OSTP, and the Chief AI Officer designated under EO 14110) from operational stakeholders (program executives, union locals recognized under 5 USC chapter 71, contracting officers, Authorizing Officials under FISMA, privacy officers under the Privacy Act, and the public through FOIA requestors and Paperwork Reduction Act commenters). Learners will tailor messages for each audience so that an OMB desk officer receives a risk-and-cost framing tied to the M-24-10 rights-impacting and safety-impacting categories, a House Oversight staffer receives an accountability framing tied to GAO-21-519SP, an AFGE steward receives a workforce-impact framing tied to collective bargaining obligations, and a citizen receives a plain-language framing tied to the Plain Writing Act of 2010. Learners will manage expectations using phased commitment language tied to NIST AI RMF MEASURE and MANAGE functions, and will deliver a 15-minute executive briefing structured for a Deputy Secretary or agency Chief Operating Officer that covers strategic alignment, progress against M-24-10 inventory milestones, residual risk, and explicit asks for decision, dollars, and direction. Learners will identify next steps for their own agency context, including scheduling of quarterly AI governance board briefings, coordination with the Senior Agency Official for Privacy, and engagement with the agency public affairs office before any press release, Data.gov publication, or AI.gov use-case-inventory posting.

Key Topics Covered

This lecture covers five concrete capabilities. First, federal stakeholder mapping using an interest-influence matrix that recognizes OMB, GAO, the agency IG, CIGIE peer IGs, Congressional committees of jurisdiction (House Oversight, Senate HSGAC, and the appropriations subcommittees), the Chief AI Officer, the Chief Data Officer established under the Evidence Act, the Chief Information Officer under Clinger-Cohen, the Senior Agency Official for Privacy, and union representatives as first-class stakeholders rather than afterthoughts. Second, message tailoring that adapts the same underlying AI use case to five distinct registers: a controls-and-compliance register for the CIO Council and FedRAMP PMO; a value-and-risk register for OMB; a mission-impact register for program leadership at agencies such as the VA, IRS, CBP, SSA, or USDA; a workforce register for unions and OPM; and a plain-language register for the public, press, and the White House AI.gov use-case inventory. Third, expectation management using the three-horizon phased commitment model with explicit NOT-DOING statements to prevent the overpromise failure mode that killed IRS CADE 2, Healthcare.gov launch readiness, and the FBI Sentinel program. Fourth, executive-briefing technique using a 15-minute structure engineered for a Deputy Secretary, Under Secretary, or agency Chief Operating Officer, including a one-page read-ahead, a decision slide, a risk slide mapped to NIST AI RMF, and an explicit ask for a decision, budget, or direction. Fifth, a 12-month cadence plan that synchronizes internal governance board reviews, union consultation sessions, quarterly OMB touchpoints, annual CIO Council reporting, and the public AI use-case inventory refresh required by OMB M-24-10.

Why This Matters for Government

Federal AI initiatives rarely fail because the model is wrong; they fail because stakeholders were not aligned when the crisis arrived. The Department of Defense Project Maven contract with Google was technically sound and operationally valuable, but collapsed in 2018 because the company had not engaged its own engineering workforce as a stakeholder and had not helped DoD public affairs prepare the narrative. The IRS Direct File pilot succeeded in 2024 in part because Treasury, OMB, USDS, and the IRS Taxpayer Advocate were aligned on scope, phased expectations, and talking points months before launch. Stakeholder communication in government is additionally constrained by statutory and political realities that the private sector does not face: FOIA exposes internal emails, the Hatch Act restricts political advocacy by career staff, the Antideficiency Act restricts implied commitments of future funding, the Paperwork Reduction Act requires public comment on information collection, and the Anti-Lobbying Act restricts grassroots campaigns to pressure Congress. Every communication you author as a federal AI leader must therefore survive three tests: the FOIA test (would you be comfortable if this email appeared on the front page of the Washington Post), the IG test (would the agency IG find this communication accurate, timely, and within authority), and the oversight test (would a House Oversight or Senate HSGAC staffer reviewing this record conclude that the agency acted responsibly). This lecture, part of the L3 AI Strategist curriculum, equips senior managers, procurement officers under FAR Part 39, program directors, and newly designated Chief AI Officers with the frameworks needed to pass all three tests. It builds on the foundational principle anchored in NIST AI RMF GOVERN 1.1 that every AI system in federal service ultimately serves citizens, and on the OMB M-24-10 principle that rights-impacting and safety-impacting AI requires explicit, traceable, auditable stakeholder engagement. Whether you are operating an AI tool daily at CBP, EPA, or CMS, or setting enterprise strategy at the Department of Homeland Security or the VA, stakeholder management determines whether your AI initiative survives the next continuing resolution, the next IG audit, or the next change of administration.

WHY STAKEHOLDER COMMUNICATION MATTERS

Stakeholders are the people and institutions with formal or informal interest in or influence over your AI initiative, and in federal service they come with statutory authority that private-sector stakeholders rarely possess. The OMB desk officer assigned to your agency under Circular A-11 has de facto authority to slow your budget cycle. The agency Inspector General, operating under the IG Act of 1978, has subpoena authority over your records. The House and Senate committees of jurisdiction can compel testimony, freeze apportionments through the appropriations process, and direct GAO to audit your program under 31 USC 712. The union local recognized under 5 USC chapter 71 has a statutory right to bargain over changes in working conditions, which OPM and FLRA have interpreted to include AI deployment that materially changes how work is performed. The Senior Agency Official for Privacy, under OMB M-17-12, must approve any Privacy Impact Assessment before a rights-impacting AI system enters production. If you treat any of these actors as a post-launch courtesy notification rather than a pre-launch stakeholder, your initiative will be stopped, slowed, or publicly embarrassed.

Effective federal stakeholder communication serves five purposes that compound. First, it builds shared understanding of scope so that OMB, the CIO Council, and the agency AI governance board describe the initiative the same way in writing. Second, it surfaces statutory risks early, including Privacy Act System of Records Notice requirements, Paperwork Reduction Act triggers, and 508 accessibility obligations, so that they enter the schedule rather than arriving as launch-blocking surprises. Third, it develops internal advocates, particularly among career senior executives whose continuity across administrations is what actually sustains multi-year AI programs. Fourth, it manages expectations so that neither a Cabinet Secretary nor a subcommittee chair believes the AI system will do something it cannot do, which is the failure mode that destroyed trust in early predictive-policing deployments at the state and local level and in the VA Genisis scheduling modernization. Fifth, it builds durable accountability by creating a written record that, should the system fail, the agency engaged the right parties at the right time with the right information, which is what the GAO, IG, and Congress will look for in any post-incident review.

Why this matters more in government than in industry: multiple audiences must be served simultaneously, not sequentially; competing interests must be balanced without violating the Antideficiency Act, the Hatch Act, or the Anti-Lobbying Act; every communication is potentially FOIA-releasable and discoverable; skepticism is high because many stakeholders have lived through failed modernization programs such as FBI Sentinel, USDA MIDAS, Air Force ECSS, and DoD DIMHRS; and risk aversion is structurally encoded in Federal Acquisition Regulation Part 39, the FISMA authorization-to-operate process, and the Privacy Act. These are not bugs; they are the constitutional features of a republic that funds its government through annual appropriation and holds it accountable through Inspectors General and Article I oversight. Your stakeholder plan must be designed for that environment, not against it.

CORE CONCEPTS: STAKEHOLDER MAP, MESSAGE TAILORING, EXPECTATION MANAGEMENT

The federal stakeholder map is constructed on an interest-by-influence matrix with named roles rather than generic archetypes. LEADERSHIP in a federal AI context means the Secretary or agency head, the Deputy Secretary or COO, the Chief AI Officer designated under EO 14110 section 10.1(b), and the Performance Improvement Officer under the GPRA Modernization Act; their interest is mission, political exposure, and statutory compliance, and their communication cadence is a quarterly executive briefing plus an annual strategic review. PROGRAM STAFF means the operational owners at the component or bureau level, such as an IRS Wage and Investment director, a CBP Office of Field Operations director, a CMS Center for Program Integrity director, or a VA Veterans Benefits Administration director; their interest is throughput, quality, and job impact, and their cadence is monthly operational reviews plus ad-hoc incident notifications. IT LEADERSHIP means the agency CIO under Clinger-Cohen and FITARA, the CISO under FISMA, and the Chief Data Officer under the Evidence Act; their interest is ATO readiness, FedRAMP boundary, data provenance, and continuous monitoring, and their cadence is a standing architecture review board and a quarterly risk reporting cycle. COMPLIANCE AND LEGAL means the agency General Counsel, the Senior Agency Official for Privacy, the Alternative Dispute Resolution office, the Equal Employment Opportunity office, and the Ethics office under 5 CFR 2635; their interest is Privacy Act compliance, civil rights compliance under Title VI and Section 504, and alignment with OMB M-24-10 minimum practices; their cadence is pre-decisional consultation before every major design choice. EMPLOYEE REPRESENTATIVES means the recognized unions, typically AFGE, NTEU, NFFE, or IFPTE, whose bargaining rights under 5 USC 7106 and 7114 attach before any material change in working conditions; their cadence is statutory notice plus bargaining on impact and implementation. PUBLIC means citizens, advocacy organizations such as EPIC and the ACLU, the regulated industry, state and local partners, and the press; their interest is fairness, privacy, accuracy, and recourse; their channels are the AI.gov use-case inventory, agency public affairs, the Federal Register, and congressional constituent services.

Message tailoring translates the same underlying AI use case into the register each audience needs. For LEADERSHIP the register is strategic and decision-focused: this AI initiative advances a specific strategic objective in the agency strategic plan; the expected value is quantified; the residual risk has been assessed against the NIST AI RMF; the investment over the Future Years appropriation is itemized; the asks are budget, direction, and a decision. For OMB the register is categorical: under M-24-10 this use case is classified as rights-impacting or safety-impacting or neither, the minimum practices are met or have a documented extension, the AI use-case inventory entry is current, and the cost-benefit analysis aligns with Circular A-94. For the CIO and CISO the register is technical and controls-based: the system operates within an existing ATO or requires a new ATO, the FedRAMP authorization of the underlying cloud is High or Moderate, the data flows are mapped against FISMA boundaries, and the continuous monitoring plan is in place. For COMPLIANCE the register is risk-and-fairness: the Privacy Impact Assessment is published, the System of Records Notice is updated if applicable, the disparate-impact testing across protected classes is documented, the Section 508 conformance is attested, and the human-in-the-loop for rights-impacting decisions is specified. For PROGRAM STAFF the register is operational: here is how work changes, here is the training schedule, here is the performance standard during transition, and here are the feedback channels. For EMPLOYEE REPRESENTATIVES the register is impact-and-implementation: here is the scope of the change, here is the timeline, here is the training investment, here are the commitments regarding position management, and here is the bargaining schedule. For the PUBLIC the register is plain-language and rights-based: here is what the system does, here is what it does not do, here is how you can appeal an adverse decision, and here is where you can file a complaint with the agency IG or the Office of Special Counsel.

Expectation management is the discipline of stating in writing what the system will do and what it will NOT do, on what schedule, at what confidence level, with what human oversight, and at what cost. In federal service the largest failure mode is implicit over-promise; the largest success factor is explicit phased commitment. A credible phased statement reads: Phase 1 (Months 1 through 6) establishes data governance, the Privacy Impact Assessment, the ATO package, the union bargaining, and the training curriculum; Phase 2 (Months 7 through 12) runs a pilot within a single bureau with full human review of every output, measured against a baseline; Phase 3 (Months 13 through 18) expands to production with risk-tiered human review and continuous monitoring, with explicit kill-switch criteria tied to fairness, accuracy, and privacy metrics drawn from NIST AI RMF MEASURE. Every phase has a pre-committed decision point at which the AI governance board reviews evidence and decides to proceed, revise, or stop, and that decision is minuted and available to the IG and GAO on request.

EXECUTIVE BRIEFINGS, CADENCE, AND RISK PATTERNS

The 15-minute federal executive briefing is engineered for a Deputy Secretary, Under Secretary, Assistant Secretary, agency COO, or Component Head. Minute 0 to 2 is strategic alignment: this initiative advances objective X in the agency strategic plan, is listed as use case Y in the AI use-case inventory, and is classified under M-24-10 as rights-impacting, safety-impacting, or neither. Minute 2 to 5 is progress: against the phased plan last quarter we completed these milestones, did not complete these milestones for these reasons, and are on or off schedule against the approved baseline. Minute 5 to 8 is risk: the top three residual risks drawn from the NIST AI RMF risk register are these, the mitigations in place are these, and the items requiring your decision are these. Minute 8 to 11 is value: the measured benefit to date is this, the forecast benefit through end of phase is this, and the indirect benefits to workforce and public trust are these. Minute 11 to 13 is resources: to proceed through next phase we need this budget line, this personnel authorization, this data-sharing agreement, and this policy clearance. Minute 13 to 15 is the ask: do you approve proceeding to phase 2, do you direct us to accelerate or slow, and do you commit the resources listed. A good briefing answers the executive's three questions before they ask them: is this legal, is this working, and is this worth the political and fiscal cost. A one-page read-ahead circulates 48 hours in advance through the front office staff secretary, a single decision memorandum with named signatories accompanies the briefing, and minutes are filed to the governance record within 5 business days.

The 12-month cadence synchronizes internal and external reviews. Weekly the program team meets for operational review; monthly the AI governance board meets to review risk, metrics, and incidents; quarterly the agency Chief AI Officer briefs the agency head, the CIO Council representative, and OMB; semi-annually the program reports to GAO, the IG, and the Congressional committees of jurisdiction through regular budget, oversight, and inventory channels; annually the program participates in the AI use-case inventory refresh under M-24-10 and the strategic plan update under GPRA Modernization. Union consultation sessions run on a schedule negotiated in the collective bargaining agreement, typically monthly for active projects with material workforce impact. Public communication runs through the agency public affairs office and is coordinated with the White House AI.gov site for any newsworthy milestone.

Five risk patterns dominate stakeholder failure in federal AI initiatives. Risk 1, OVER-PROMISING, occurs when a program director commits in writing to benefits the model cannot deliver at current maturity; the mitigation is explicit NOT-DOING statements and phased commitments tied to measured baselines. Risk 2, THIN CHANGE COMMUNICATION, occurs when the program explains the model but not the work redesign, leaving the frontline workforce ambushed; the mitigation is pairing every technical rollout with an OPM-approved competency framework update and a CHCO-sponsored training plan. Risk 3, DISMISSING CONCERNS, occurs when legitimate questions from unions, privacy advocates, or the public are treated as obstacles rather than inputs; the mitigation is documenting every concern, the response, and the owner, and publishing the log where appropriate. Risk 4, PREACHING TO BELIEVERS, occurs when the program engages only friendly audiences and neglects skeptics on appropriations staff, authorizing staff, or IG; the mitigation is scheduled outreach to skeptical audiences with the same rigor as to friendly ones. Risk 5, FOIA BLINDNESS, occurs when internal communications are drafted assuming privacy that FOIA does not grant; the mitigation is writing every email, slide, and memo to the standard of the morning newspaper front page.

Glossary: Stakeholder Map, an interest-influence matrix naming federal statutory and operational stakeholders. Message Framework, the registered translation of a single use case into leadership, OMB, CIO, compliance, program, labor, and public registers. Executive Briefing, a 15-minute structured briefing for a Deputy Secretary or COO with a one-page read-ahead and a decision memorandum. Expectation Management, explicit phased commitments with NOT-DOING statements, measured baselines, and pre-committed decision points. Change Communication, coordinated communication about work redesign and workforce implications, negotiated with recognized unions. FOIA Test, IG Test, and Oversight Test, the three standards every internal communication must pass in federal service. Next steps for the learner: map your stakeholders using named federal roles; tailor your messages to seven registers; commit to phased language with NOT-DOING statements; prepare a 15-minute briefing; schedule quarterly CIO Council, OMB, and governance-board engagement; coordinate with public affairs before any external disclosure; and maintain the written record to the FOIA, IG, and oversight standards.

Related Lectures

L3 3.1.1 Developing an Organizational AI Strategy, 120 minutes, lecture plus workshop. L3 3.1.2 AI Maturity Assessment, 90 minutes, workshop plus tool. L3 3.1.3 Prioritization Frameworks for Government AI, 90 minutes, workshop. L3 3.1.7 Workforce Planning for AI. L3 3.1.9 AI Strategy for Different Government Contexts.