In this article
Making the audience the hero is a communication metaphor. It does not mean flattering them, inventing their feelings or casting people who disagree as villains. Their agency matters more than the presenter's preferred ending.
Make presentation stories relevant to the audience
Duarte's audience-as-hero approach places the speaker in a supporting role. A practical workplace application is to begin with the audience's responsibilities rather than your own achievements.
Write down who will use the recommendation, who must approve it and who will bear the extra work. These may be different people.
Ask what each group already knows, what they need to decide and what could reasonably make them hesitate. Do not assume resistance means they have failed to understand your vision.
Your presentation should help people evaluate a choice. It should leave room for a justified “not yet” or “not in this form.”
Replace self-focused openings
A self-focused opening often lists the presenter's experience, the team's achievements and the project's importance. Some of that information may be relevant, but it rarely explains the audience's immediate problem.
Hypothetical example: A team introduces a new reporting template to regional managers.
The self-focused version says: “Our central team has spent months developing a sophisticated reporting system.”
An audience-focused version says: “You need to explain exceptions quickly without rebuilding the same report each week. This template is designed to make those exceptions visible, and today we need your feedback on whether the fields support your review.”
The revised opening gives managers a task and a voice. It does not promise the template has already saved time.
Show the obstacle fairly
Describe the obstacle as a condition or constraint where possible: unclear ownership, inconsistent definitions, limited access or a competing deadline.
Avoid making another department the villain. That framing can obscure the process issue and encourage defensiveness.
If people disagree about the problem, acknowledge the disagreement before presenting your solution. “Some teams find the current template sufficient; others cannot record the exceptions they need” is more useful than “everyone is frustrated.”
This also prevents false consensus. A story should not imply broad support that has not been established.
Offer tools, not rescue
The speaker's role is to provide useful evidence, options and support. Show what listeners can do with the information.
For a process change, include a worked example and an escalation route. For a strategic proposal, show alternatives and the assumptions that distinguish them. For training, let people practise the judgement rather than watch you demonstrate expertise repeatedly.
Make dependencies visible. If the new approach requires access, training or extra capacity, include those needs in the proposal.
Do not tell an audience they are empowered while withholding the authority or resources needed to act.
Adapt the same proposal for different listeners
A single story may need different emphasis across groups.
| Audience | Central question |
|---|---|
| Senior sponsor | Is the benefit worth the commitment and risk? |
| Implementing team | What changes in our work, and what support exists? |
| Adjacent department | What responsibility or dependency moves to us? |
| Customer-facing staff | What can we explain accurately to customers? |
The facts should remain consistent. Adapt the relevance, not the evidence.
If groups share the room, signal the different responsibilities explicitly. A short section for implementers can prevent an approval-focused talk from overlooking practical work.
Leave space for a different ending
An audience-centred presentation invites questions that could change the proposal. Build in a point where listeners can challenge the assumptions.
Ask, “What would make this difficult to use?” or “Which exception have we missed?” A request for applause is not a substitute for feedback.
Be clear about what is open for discussion. If a legal requirement or final decision is fixed, say so rather than offering a false choice.
If the audience identifies a serious flaw, acknowledge it and explain the follow-up. Protecting the story's neat ending should not take priority over improving the work.
Check whose work the future requires
An attractive audience-centred story can still overlook the people who will implement the proposal. List the tasks required after approval and identify who will perform them.
Ask whether those people are represented in the discussion. If not, gather their input before promising a smooth transition.
Pay attention to additional administration, training and maintenance. These tasks can disappear from a presentation that focuses only on the final benefit.
Represent implementation concerns as design information rather than resistance to progress. A colleague pointing out a workload problem may be protecting the proposal from failure.
If you cannot resolve a concern in the room, record the question and owner. The audience remains an active participant when its concerns can change the plan, not merely decorate a final slide.
Test whether the audience has agency
Read your draft and count the decisions the audience is allowed to make. If they appear only as people who need convincing, revise.
Check pronouns too. Replacing “we” with “you” does not automatically make a presentation audience-centred; the underlying structure must recognise listeners' actual role.
Visit Storify and storytelling in presentations for related techniques. Storytelling in meetings can help when the discussion is more collaborative than formal.
For your next opening, write the audience's task, obstacle and choice in three sentences. Introduce your expertise only where it helps them judge the support you are offering.
AI-assisted researched guidance from PeakBelt. Hypothetical examples are labelled in the text. See our editorial approach.