The preceding essay argued that every organization's most consequential priorities rest on independent stakeholders it can influence but cannot command — regulators, communities, elected officials, investors — and that this dependence, unlike finance or risk or supply chain, has no system of record. The argument was structural. The evidence is not. It sits in the public record of proceedings that turned against capable organizations whose engineering was sound, whose resources were ample and whose objectives were clearly defined, and that lost anyway, on the judgment of stakeholders they did not adequately understand.
What follows are three such proceedings, drawn from three industries and three venues. They have almost nothing in common at the surface. A utility seeking a transmission route, a trade association fighting a ballot initiative, a developer seeking local approval for a campus. Read structurally, they are the same case told three times — and each one exposes the same missing capability.
A note on terms. The discipline of strategic communication (lowercase) is mature: it concerns how organizations understand and align the stakeholders whose actions determine whether a strategic priority advances. Strategic Communication (capitalized) is the product category built to operationalize that discipline. The unit of management in both is neither the message, the audience, the channel nor the campaign. It is the chain that runs from an organization's strategic priority, through the independent stakeholders whose discretionary action that priority requires, to the outcome. Those stakeholders are the hard case by design. Internal actors can be moved through hierarchy; dependent external actors through contract or procurement. Regulators, communities, elected officials, editorial boards, advocacy groups and institutional investors can be moved by none of these. They can be influenced. They cannot be directed. That is precisely why they so often decide the outcome — and why the work of understanding them, scattered as it is across functions, tools and institutional memory, so rarely adds up to a governed whole.
Consider an investor-owned utility whose resource plan treats expanded transmission capacity as a standing strategic priority — directional, continuing, never permanently finished, driven by load growth and regional reliability. To advance it, the utility sets a discrete objective: approval to site and build a high-voltage line along its preferred corridor. The engineering case may be sound, the reliability need documented, the route consistent with a regional plan. None of that is sufficient, because the objective carries a requirement the utility cannot satisfy by argument alone. It needs commission approval of a defensible route, and that approval rests on the judgment of people it can petition but not command.
That requirement came due in Kansas in May 2026, when the Kansas Corporation Commission approved part of Evergy's proposed 345-kV transmission project but denied the company's route east of U.S. Highway 77 through the Flint Hills, directing Evergy to perform a new routing study for the eastern portion and citing the region's unique ecology and the potential impact on oil-and-gas operations in the affected counties.[1] The line could advance — but not as proposed, and not without lost time and resources.
Strip the case to its architecture and the chain appears. The priority produced an objective; the objective carried a requirement — route approval — that the utility could not meet on its own; and the requirement rested on stakeholders whose posture the utility did not control: the Commission, but also the landowners, ranchers, conservation interests and oil-and-gas operators whose objections shaped the record the Commission ultimately read. The evidence that moved them — routing studies, ecological analysis, land-use impact, public testimony — and the activities meant to engage them — open houses, hearings, filings, revisions — all existed somewhere in the organization. The question is whether they were governed as one chain or held in pieces across the functions that produced them.
A system of record would not make the route easy, and it would not guarantee approval. It would make the chain visible: ownership assigned to each part of it, evidence surfaced as the stakeholder environment shifted, leadership holding one view of whether the project was advancing toward approval or quietly accumulating the risk that the engineering case had been made while the stakeholder conditions for that route to survive review had not. That second distinction is where the outcome was decided.
The same structure governs a contest that looks nothing like a routing study. A trade association's priority is to protect a core commercial interest its members share. A specific threat materializes — a ballot initiative requiring automakers to make vehicle telematics data accessible to owners and independent repair shops — and the priority resolves into an urgent objective: defeat the measure at the polls. Here the requirement is not engineering but persuasion. The association cannot simply state its opposition; it must move enough voters, validators and allied stakeholders to believe the initiative is bad policy, while preventing the other side from defining the question in simpler moral terms.
That is the contest the automakers lost in Massachusetts in 2020. Their opposition ran through a dedicated ballot committee — the Coalition for Safe and Secure Data, funded by major manufacturers and backed by the industry's trade group, the Alliance for Automotive Innovation — which raised substantial funds and warned that expanded telematics access could create privacy and safety risks; the supporters framed the measure as the right to repair the car you own at the shop you choose. The voters chose the simpler frame, roughly 75 percent to 25 percent.[2]
The lesson is not that the privacy and safety arguments were unserious. It is that a message can be internally plausible and still fail in the environment where the outcome is decided — that resources do not overcome message-market mismatch. The decisive stakeholders were not the association's members but the voters, repair shops, consumer advocates, press outlets and safety validators whose posture the campaign needed to read in something close to real time: which arguments were gaining credibility, which were losing it, and whether the organization's own assumptions still matched what the electorate believed. A government-affairs tracker would have recorded officials; a media monitor would have surfaced coverage; a campaign dashboard would have logged spend and polling. None of them is organized to answer the strategic question — whether the chain from priority to outcome was strengthening or coming apart — and a ballot campaign can come apart long before election day. The value of governing the chain is the chance to see that loss forming while there is still time to change course.
The pattern recurs a third time when growth depends on putting something physical in a specific place. A company's priority requires new assets — a data-center campus, a plant, an energy facility. It finds a viable site, secures the capital, perhaps wins the receptive ear of state economic-development officials with the promise of tax revenue and jobs. And still the objective turns on a requirement headquarters cannot satisfy: local approval, granted by people whose judgment is shaped by local concern rather than the company's strategic plan. Residents care more about emissions, water, traffic, rural character, property values, benefit-sharing and whether the developer has been straight with them, and local officials may support development in general but reject specific proposals that lack community buy-in.
In April 2025, the Pittsylvania County Board of Supervisors voted six to one to deny Balico's rezoning request for roughly 750 acres near Chatham, Virginia — a data-center campus with on-site power generation — after months of public concern. Board members cited project layout, building profile, expected emissions, limited local job benefit, a lack of clarity in the proffers and insufficient community buy-in; residents had raised environmental, traffic, energy and rural-character objections throughout.[3] The capital was available, and the site viable, but lacking local approval the rest did not matter.
This is the case that most sharply exposes how stakeholder posture is actually built — and missed. Opposition rarely arrives as a single event. It accumulates through a stream of local signals: a resident's comment at a hearing, a Facebook group forming, a local article on water use, a planning-commission note about missing detail, a supervisor's remark about trust. Each looks manageable alone; together they can show that the environment has already turned. Governing the chain means connecting those signals to the objective they threaten — and, crucially, distinguishing what they are evidence of. If residents kept raising distrust of the developer rather than any narrow technical point, the organization faces not a fact gap but a legitimacy gap, and the two demand different work. A fact gap yields to better evidence — a cooling technology that materially reduces water draw, surfaced to whoever owns that objection. A legitimacy gap does not; it requires earlier engagement, credible third-party validation, clearer local benefit and more transparent commitment. An organization that cannot tell the two apart will keep answering the wrong one. This is not a claim that strategic communication manufactures consent — it does not — but that organizations need a disciplined way to know what stakeholders believe, why they believe it and whether the work distributed across the building is changing the posture that determines the outcome.
The three cases differ by industry, venue and stakeholder. The structure does not. Each organization held a strategic priority; each set an objective that would advance it; each objective carried some number of requirements the organization could not satisfy alone; each requirement rested on independent stakeholders whose actions decided it; and each stakeholder environment generated evidence, objections and activity that had to be understood as it moved. In every case, people were already working — capably — on pieces of the problem.
So the gap is not effort, and the remedy is not a louder version of what already failed. These organizations were already engaging stakeholders; "engage more" was not the missing instruction. They were already communicating; "communicate better" was already being attempted. They were already tracking the issue in considerable detail. What none of them effectively governed was the chain itself: the logic that binds priority to objective to requirement to stakeholder to evidence to activity to outcome, each its own managed set of workflows owned by different teams and offices. And so leadership briefed from partial records, functions worked from different vocabularies and different pictures, institutional memory sat in inboxes and slide decks, and weak signals stayed weak until they were decisive. The regulator's concern, the voter's intuition, the community's distrust each became visible as a strategic constraint only after the cost had been paid.
A system of record changes the architecture without centralizing the people. It does not pull stakeholder work into one department; it makes the logic of that work shared while ownership stays with those closest to the subject matter — the regulatory lead owning the regulatory record, the community-relations lead the community record, the policy lead the evidence, the communications lead the message framework, the executive team the integrated chain. Logical centralization, not organizational centralization.
This is also why the adjacent tools, strong as many are, do not close the gap. A government-affairs platform tracks officials, bills and activity. A media-intelligence platform monitors coverage and sentiment. A stakeholder database holds contacts; a project tool assigns tasks; a survey platform collects feedback; a CRM manages relationships. Each is valuable inside its domain, and none is organized around the chain — priority, objective, requirement, stakeholder posture, evidence, message, activity, outcome. That is the category distinction. Strategic Communication does not begin with a channel, a contact or an issue feed; it begins with the organization's strategy and asks what stakeholder action each priority requires, then records the rest against that spine. The next essay examines the adjacent landscape directly. Many of those platforms are mature and genuinely useful to the functions they serve. The cases above show only that domain-specific strength is not the same thing as chain-level governance.
Organizations do not lose transmission routes, ballot campaigns and facility approvals — or rate cases, permits and market-access fights — because they lack tools. They lose when the decisive stakeholder dependency is never governed as part of the strategic architecture. That is the problem strategic communication exists to solve.
Think of a case inside your own organization: a moment when an independent stakeholder delayed, reshaped or decided an effort tied to a real priority. Where was the evidence held? Who owned the stakeholder record? Who knew whether the message was working? Who saw the risk forming early enough to act? If the answers were scattered across functions, inboxes, spreadsheets, decks and memory, the failure was not simply execution. The entire chain was not effectively governed.
Notes
KMUW / Kansas News Service, "Kansas regulators tell Evergy to rethink transmission route through the Flint Hills," May 13, 2026. ↩︎
Ballotpedia, "Massachusetts Question 1, 'Right to Repair Law' Vehicle Data Access Requirement Initiative," 2020. ↩︎
Cardinal News, "Pittsylvania rejects data center project that has dominated county conversation for 6 months," April 16, 2025. ↩︎