Strategy presentation examples

What should a strategy presentation accomplish?

What distinguishes a strategy presentation from a general company introduction or a report listing completed work is its focus on a specific decision. By the end, the audience should be able to answer these questions: What is being recommended, what evidence supports this choice, and what decision is being requested?

The methods in this guide are practical suggestions for preparing a decision presentation; they do not prove which strategy or outcome is right for your company. Connect the goal, evidence, trade-offs, prerequisites, and requested decision in your narrative.

Define the boundaries of the decision

Start by writing the decision statement: “Which feasible options must we choose among to achieve which goal?” If the goal is too general, comparing options can be difficult. For example, instead of “grow,” you might consider a more specific goal such as “increase usage among existing customers.”

Then answer these questions:

• Who will make the decision, and what approval is being requested?
• Which options can genuinely be considered?
• Which criteria matter to the decision when comparing options, such as customer impact, time, team capacity, cost, or risk?
• Which points are verified information, and which are assumptions or unanswered questions?

Choose criteria according to the decision at hand; you do not need to use the same criteria in every presentation. If the data comes from different periods or uses different definitions, say so. If you lack solid evidence, state the uncertainty and what needs to be verified rather than implying a definitive conclusion.

Compare the options and explain your rationale

Assessing options against shared criteria can help explain why one is preferred. Address each option in the same way, considering its expected contribution, required resources, significant risks, and opportunities forgone. Instead of saying “the best option,” explain under which goals and conditions the option seems suitable.

Also explain why the other options are not preferred for now. This lets the audience see not only the outcome, but also the rationale and limitations of the decision. Yale’s presentation guide recommends ordering key points with supporting evidence and making complex ideas understandable; you can use these suggestions to explain the options and their supporting evidence clearly: Yale’s presentation guide.

Example: Deciding whether to scale a new service

Entirely hypothetical example: A software company is deciding whether to scale a new service. The options below are not company data or forecasts of results.

1. Decision: “Which approach should we try for growth next quarter?” State the approval you are seeking at the outset.
2. Situation and goal: Summarize verified findings from customer interviews, usage observations, and information about team capacity. Add a date and source to each item; do not present unmeasured points as findings.
3. Options: A: a limited trial with existing customers; B: expansion to a new customer segment; C: first improve the service’s core experience.
4. Comparison: Assess each option in terms of customer impact, team effort required, implementation time, and uncertainty. Explain what qualitative descriptions such as “high/medium/low” are based on.
5. Recommendation and trade-off: If, hypothetically, you recommend option A, connect the rationale to findings from existing customers and available team capacity. Also note that access to new customers will be deferred.
6. Prerequisites and risks: Define who is responsible for the trial, what signals will be monitored, and the conditions for stopping or reassessing it. Say that the recommendation may change if the conditions are not met.
7. Decision and next step: Ask, “Do we approve trying option A with this scope and these checkpoints?” Record the owner and follow-up date.

To adapt this flow to team capacity or priorities for the period, see the project status presentation guide; if you need to address budget assumptions separately, you can use the budget presentation guide. Mississippi State University’s PDF titled “Example Strategy Meeting” can also be reviewed as additional example material; it does not replace verifying your company’s data: example strategy meeting presentation.

Organize slides around the decision flow

It can be helpful to give each slide a purpose: define the problem, present evidence, compare options, explain the recommendation, or request a decision. Try writing a headline that states the takeaway you want to convey rather than simply naming the slide’s topic. For example, instead of “Options,” you could write “A limited trial is more feasible, subject to capacity”; however, make the basis for this takeaway or the fact that it is an assumption clear on the slide.

Use the same criteria for the comparison, and do not cram in so much text that it becomes unreadable. You can keep the evidence needed for the decision in the main presentation and move details to supplementary material. State the source, date, and definition used alongside the relevant information.

Check the draft and sources

First, write the decision statement and list of options in plain text. Then match claims to their supporting evidence: data, observations, clearly labeled assumptions, or expert assessments. If you are preparing the presentation with a tool, verify anything you are unsure about regarding available features or access on your account in that product’s current help materials or in its interface. Editing the content manually also lets you review the options and decision flow.

In your final review, check that the sources genuinely support the relevant claims, that the data periods and definitions are comparable, and that the conditions attached to the recommendation remain visible. Do not remove uncertainty just to make the presentation seem more definitive.

What should you fix if problems arise?

If the presentation turns into a list of options: Put the goal and requested decision at the beginning. Explain each option’s contribution, requirements, risks, and trade-offs in the same format.

If the recommendation goes beyond the evidence: Narrow the claim to what the evidence supports. Label the assumption and state what observation would be needed to verify it; do not present an estimate as a measured result.

If the slides are crowded: Keep the evidence needed for the decision in the main presentation and move details to supplementary material. Do not remove important limitations just to make room.

Final checklist

• Are the goal and requested decision clear?
• Have realistic options been compared using shared, meaningful criteria?
• Are evidence, assumptions, and uncertainty distinguished from one another?
• Is it explained why the options not preferred have been ruled out for now?
• Are the recommendation’s prerequisites, risks, and follow-up step stated?
• Is the decision request phrased as a clear question?

Frequently asked questions

How many slides should a strategy presentation have?

Rather than aiming for a fixed number, consider whether each section is necessary to support the decision. If you have a time or template constraint, move details to supplementary material without removing important conditions and evidence.

Can you present if data is missing?

Show the available findings, assumptions, and points that need verification separately. State the recommendation conditionally, in light of those limitations.