Advocacy
Situation
A major organizational change can be technically sound and still be difficult to move. Internal teams understand the rationale in detail. External audiences experience something else: a cost, a timeline, a new rule, a perceived risk, a change to something familiar, a question about who benefits. In this case the organization was preparing to communicate a consequential move across a complex stakeholder environment. The underlying work was substantial. The communications challenge was that different audiences were evaluating the decision through different priorities, different levels of knowledge and different definitions of risk. A launch campaign alone would not solve that.
Decision
The organization did not need attention. It needed permission to move. That permission could not be manufactured by repeating one message more loudly. It depended on whether people could understand the decision, locate their own interests within it, see credible evidence behind it, and know how the organization would handle uncertainty and trade-offs. The communications problem therefore sat upstream of creative production. Before deciding what to publish, the organization needed to understand the environment surrounding the decision.
We mapped the decision ecosystem: who held formal authority, who could influence them, who would experience the change directly, which technical voices carried credibility, and where local, sector or institutional concerns could reshape the wider narrative. A narrative risk map identified where the evidence was strongest, where confidence was weakest, which assumptions were being made internally, and where an information gap could become a reputational problem. Audience segmentation moved beyond demographics: stakeholders were grouped by their relationship to the decision — what they stood to gain, lose, protect, question or influence.
Foresight added another layer. Rather than designing communications for one expected future, the team worked against several plausible conditions around the decision: delay, cost pressure, leadership change, external controversy, shifting economic conditions, stakeholder resistance, or an unrelated event that changed public attention. The point was not to predict exactly what would happen. It was to build a communications strategy that would still work when the environment changed.
Movement
The campaign connected executive communications, stakeholder engagement, research translation, media strategy and digital content, sequenced around decision moments rather than a content calendar. Senior leaders carried the institutional case. Technical voices explained the evidence. Stakeholder-facing materials answered the questions that mattered in specific contexts. Stakeholder conversations were treated as intelligence sources rather than ceremonial engagement, and monitoring looked for recurring questions, emerging resistance and gaps in understanding, returning what it found to the strategy. The campaign did not operate as a megaphone. It operated as a feedback system.
What the organization gained was a clearer way to tell communications problems apart. An information gap was not automatically read as opposition. A trust problem was not treated as a messaging problem. A substantive concern was not dismissed as misunderstanding. A stakeholder issue was not assumed to require a public campaign. That distinction improved the quality of communications decisions, and made communications part of the infrastructure for moving the decision forward.
