Reflections from a Workshop on Advocacy Presentations

By Paul Shotton, Advocacy Strategy / Advocacy Academy

Recently I ran a workshop with a public affairs team on presentation skills. The formal focus was visual representation, structure, and delivery. The discussion moved quickly beyond slides. We found ourselves talking about something more fundamental: how advocacy teams think, how they structure their work, and how they translate technical expertise into influence.

Many of the issues we work on are highly technical, scientific, and regulatory. The challenge is rarely a lack of substance. Teams are deeply knowledgeable. They understand the files. They know the data. The risk lies elsewhere. When we become immersed in detail, we can lose sight of the essential message. We can mistake explanation for persuasion. We can assume that clarity for ourselves automatically produces clarity for others.

A presentation is not simply a document projected onto a wall. It is an intervention. It is meant to produce an outcome. What became most valuable during the workshop was not the redesign of slides, but the open and constructive discussion within the team about how they work, how they draft, and what they are ultimately trying to achieve.

That workshop and discussion led to a number of clear realisations. The first concerned purpose.

1. Purpose: Internal or External?

Before drafting a single slide, we need to answer a simple but often neglected question: what is this presentation for? In the workshop, we drew a clear distinction between internal and external purpose. This may sound obvious, yet in practice the two are frequently blurred, which leads to confusion in structure and messaging.

An internal presentation may aim to align a team, clarify priorities, support a board decision, review progress, or structure a campaign. Its function is often to make thinking visible. It should show logic. It should clarify trade-offs. It should make progress measurable. It should equip decision-makers with enough clarity to act. The emphasis is on coherence and transparency.

An external presentation has a different task. It must persuade. It must translate complexity into a structured and accessible argument. It must connect technical substance to political or strategic implications. Above all, it must move the audience towards a defined position or action. These two purposes require different levels of detail, different framing, and different structural choices. A campaign plan is one example of an internal structure. A narrative arc is one example of an external structure. The models themselves are less important than the discipline of choosing structure consciously.

One of the most useful questions we discussed was this: when the presentation ends, what must happen? Is a decision required? Alignment? Approval? A change in behaviour? If that question is not clear to the presenter, it will not be clear to the audience. Purpose determines structure. Structure determines clarity. Clarity determines impact.

2. From Reporting to Persuasion

As we reviewed concrete examples together, another realisation emerged. Many advocacy presentations are strong on information. They describe context. They present evidence. They summarise developments. Fewer are strong on persuasion. There is a subtle but important difference between reporting and influencing. Reporting explains what is happening. Influencing makes clear what should happen next.

In technical policy environments, the temptation is to demonstrate depth. We show the data. We explain the regulation. We walk through the scientific detail. This builds credibility. It signals expertise. It reassures peers and stakeholders that the issue has been mastered. Yet credibility alone does not produce action. A presentation can be accurate, detailed, and technically sound, and still fail to influence.

Effective external presentations tend to follow a clear logic. They define the issue. They explain why it matters now. They present a structured pathway forward. They specify what is required from the audience. The call to action is not an afterthought. It is central. In practice, this is often the weakest element. The call to action is implied rather than stated. It is softened rather than clarified. Yet if we cannot articulate the desired outcome in simple and direct terms, it is unlikely to occur.

The same dynamic applies internally. A campaign update that does not clarify next steps or decision points remains descriptive rather than strategic. Moving from reporting to persuasion requires discipline. It requires us to step back from the detail and ask a harder question: what outcome are we designing this presentation to achieve?

3. The Discipline of Simplification

One of the strongest and most honest discussions during the workshop centred on data and technical content. In advocacy, we can work on files that are scientifically complex and legally nuanced. The level of expertise within teams is high, and that expertise is a genuine strength. However, it can also create blind spots.

When we know a subject well, we tend to explain it fully. We include caveats. We add background. We anticipate counterarguments. We demonstrate our mastery of the detail. The result can be clarity for insiders and confusion for everyone else. Several participants reflected on the need to aim for the lowest common denominator audience. This does not mean lowering standards or oversimplifying reality. It means recognising that even intelligent and experienced audiences may not share the same technical background, and that clarity requires deliberate effort.

Simplification is not the simplification of thought. It is the simplification of expression. This distinction matters. It requires discipline to reduce a complex argument to its essential components without distorting it. Data must be digestible. The key insight must be visible. The “so what” must be explicit. Evidence must be translated into implications. What does this mean for competitiveness, resilience, cost, or timing? What changes as a result?

We also discussed the importance of differentiating audiences. An internal expert group may require more depth and technical explanation. A board may require risk, options, and consequences. An external policymaker may require clarity, alignment with broader objectives, and a focused request. One structure does not fit all contexts. The discipline lies in choosing what to include and, equally, what to leave out.

In practical terms, this often means reducing text, sharpening headlines, and placing the key takeaway at the top of the slide. It means ensuring that each slide carries one central idea rather than multiple competing messages. It means resisting the temptation to include every element that might be relevant. The discipline of simplification is uncomfortable because it forces prioritisation. Yet without it, influence becomes diluted.

4. Structure Before Design

The workshop did address visual principles. We reviewed examples of dense slides and cleaner alternatives. We discussed hierarchy, white space, and consistency. However, the deeper point was not aesthetic. It was structural.

Design cannot compensate for unclear thinking. A well-formatted slide that lacks a clear message remains unclear. A visually attractive chart that does not answer a question remains decorative. Structure must come first.

Internally, structure may involve making campaign logic visible. It may show how priorities link to objectives, how objectives connect to stakeholders, and how tactics relate to measurable outcomes. The aim is to make reasoning transparent and traceable so that colleagues and decision-makers can follow the logic without effort. Externally, structure often follows a narrative arc. Define the issue. Explain why it matters now. Present a pathway forward. Specify what should happen next. When this logic is explicit, persuasion becomes easier because the audience is not required to reconstruct the argument themselves.

We also reflected on the role of templates. Templates are not neutral tools. They embed assumptions about what a presentation should contain and how it should be structured. They signal what good looks like. They influence how much thinking versus reporting is expected. When templates are inconsistent or unclear, teams improvise. When they are aligned with purpose, they support discipline and coherence across the organisation.

Investing in a small number of strong structural slides can therefore have disproportionate impact. Not because they look better, but because they make thinking visible and repeatable. Clarity is not accidental. It is designed.

5. Building Communication Infrastructure

As the discussion progressed, attention shifted from individual presentations to systems. Many teams produce decks reactively. A meeting is scheduled. A presentation is required. Slides are drafted, revised, and finalised. The process repeats. This approach is understandable, yet it often leads to inconsistency and duplication of effort.

One of the practical conclusions from the workshop was the value of building communication infrastructure rather than simply producing decks. This may involve developing a small library of reusable structural slides: a clear problem framing slide, a stakeholder map, a campaign logic overview, a policy timeline, a structured options and recommendation slide, a concise KPI dashboard, or a clear “decision required” slide. When these core elements are defined and agreed, teams do not start from zero each time. They adapt and refine what already exists.

The same logic applies beyond PowerPoint. Infographics, one-pagers, and key visual explainers can form part of an asset library. Over time, this builds consistency and strengthens credibility. We also discussed process. Strong collaboration already existed within the team. The opportunity was to formalise it lightly through clearer ownership of templates, defined roles in drafting, and constructive feedback before finalisation. Not bureaucracy. Simply clarity. Small structural adjustments can have significant cumulative effects.

What This Revealed

The session became a conversation about how public affairs teams think and operate. It revealed how easily we can drift from purpose, how quickly technical detail can overshadow strategic clarity, and how often calls to action are implied rather than explicit.

It also revealed something encouraging. When given the space, teams are capable of open and constructive reflection about their own practice. That reflection is valuable in itself. In complex policy environments, expertise is expected. It is not differentiating. Clarity is differentiating.

The teams that influence effectively are not those with the most slides or the most data. They are those who design communication around outcome, structure their arguments deliberately, simplify without distorting, and make action explicit. Presentations are not peripheral to advocacy. They are a visible expression of how clearly we think. If we want to be seen as strategic partners, our presentations must reflect strategic discipline.