ElevateU Practical AI
Explore Pro ↗Sign in
← Back to Edition

Free guide / Presentations

A blank presentation starts with a clear question.

Build an outline around what your audience needs to understand.

Start here

Give AI the audience, the decision needed and the facts you have. Request an outline with missing evidence marked as placeholders.

What you need

  • Presentation goal / topic
  • Audience
  • Desired slide count (default 8 to match Day 1 demo)
  • Any must-include points (optional)

Use information you’re allowed to share with your approved AI tool.

Give it a try.

  1. Replace the placeholders with relevant, non-sensitive source material.
  2. Paste the prompt into your approved chat assistant.
  3. Compare every fact, owner, number and date against the input. Edit before using.
Copy, then replace the placeholders
Create an 8-slide executive presentation outline for the goal below.

For each slide provide:
- Slide title
- 3–5 speaker bullets (outcome-focused, no filler)
- Suggested visual (chart, table, diagram, or simple layout note)

Structure preference (adapt only if the goal truly needs it):
1) Executive Summary
2) Current Snapshot
3) Key Drivers / Problems
4) Opportunity Map
5) Playbook / Approach
6) Quick Wins
7) Metrics
8) Next Steps / Ask

Rules:
- Do not invent statistics, quotes, or case studies
- Use placeholders like [metric] or [customer example] where data is needed
- Keep language executive-clear and global-English friendly
- This is a structured first draft, not finished slide design

Goal: [e.g., improving customer retention]
Audience: [e.g., leadership team]
Must include: [optional bullets]
- Do not add new commitments, causes, meetings or deadlines. Preserve uncertainty.
- Keep proposals separate from agreed actions; mark missing information as TBD.

See the difference.

Illustrative example, not a recorded AI response.

“Make me a presentation about our project.”

Who is it for, and what decision should it help them make?

Read the full input and example

Input

Goal: improving customer retention
Audience: leadership team
Must include: onboarding friction, enterprise risk accounts, FAQ + pause on feature emails

Example output

1) Executive summary
- Goal: improve customer retention.
- Focus: onboarding friction, enterprise risk accounts, FAQ and feature-email pause.
- Decision required: [confirm the specific ask].
Visual: goal and three focus areas.

2) Current snapshot
- Retention baseline: [data needed].
- Enterprise risk: [account evidence needed].
- Onboarding friction: [observations needed].
Visual: table with unfilled metric cells.

3) Onboarding friction
- Describe observed issues: [evidence needed].
- Affected users: [data needed].
- Avoid asserting a cause without evidence.
Visual: evidence list.

4) Enterprise risk accounts
- List accounts: [names needed].
- Explain risk signals: [evidence needed].
- Confirm review owners: [TBD].
Visual: risk table.

5) FAQ and feature-email pause
- Clarify the intended FAQ scope.
- Confirm the status and scope of the pause.
- Identify dependencies: [TBD].
Visual: dependency diagram.

6) Proposed next actions — not agreed
- Validate the source data.
- Ask for owners.
- Agree dates before committing.
Visual: draft checklist.

7) Measurement proposal
- Candidate measure: retention [baseline TBD].
- Candidate measure: onboarding completion [baseline TBD].
- Confirm availability and definitions.
Visual: blank scorecard.

8) Next steps
- Confirm the decision sought.
- Assign owners only after agreement.
- Set dates only after confirmation.
Visual: open questions list.

Check before you use it.

  • The response is a draft; it can omit or misread details.
  • Do not add commitments, infer decisions or treat proposed actions as agreed.
  • Use an employer-approved tool and remove confidential or personal information.
Tools, review date & evidence

ChatGPT · Claude · Gemini · Microsoft Copilot (and similar). For slide apps, paste the outline into your deck tool; do not claim auto-designed finished slides.

Illustrative example reviewed for fidelity on 18 September 2026. No recorded execution in external AI tools; compatibility is a text-format expectation, not a tested-model claim.

Reviewed 2026-09-18.

Sign in to save resources →

Saves stay in this browser. Cross-device syncing is planned.

A useful next read

A meeting is over. What happens next? →