Presentation Creation Skill

Purpose

Communicate complex information clearly and persuasively to stakeholders. A BA must sell the "Solution" as much as define it.

Audience Analysis

Before opening PowerPoint/Figma/Lark Slides, ask:

1. •Who is the audience? (Execs, Devs, Users).
2. •What do they care about? (ROI, Tech details, Workflow).
3. •What is the goal? (Decision, Info sharing, Training).

Structure of a BA Presentation

1. The Executive Summary (Slide 1)

• •Problem: What is broken?
• •Solution: What are we doing?
• •Ask: What do you need from them today? (Approval, Budget, Input).

2. The Context (The "Why")

• •Current state issues.
• •Data backing up the problem.

3. The Core Content (The "What")

• •Requirements / Solution Design.
• •Use Visuals: Process maps, Wireframes, Charts. (No walls of text).

4. The Plan (The "How/When")

• •Timeline.
• •Next steps.

5. Q&A

• •Anticipate tough questions.

Visual Communication Rules

• •One Idea Per Slide: Don't cram.
• •Consistency: Same fonts, colors.
• •Diagrams > Text: People process images 60,000x faster than text.
• •Readable Fonts: Min 24pt for projection, 12pt for reading docs.

Presentation Types

Status Report

• •Focus: Progress, Risks, Blockers.
• •Tone: Professional, Transparent.
• •Format: Red/Amber/Green indicators.

Stakeholder Review (Sign-off)

• •Focus: Validation of requirements.
• •Tone: Collaborative, Detail-oriented.
• •Format: Walkthrough of wireframes/flows.

Training / Demo

• •Focus: How to use the system.
• •Tone: Encouraging, Educational.
• •Format: Live demo + Cheat sheets.

Tools

• •Lark Slides: Collaborative, simple.
• •Figma: Great for showing designs/flows directly.
• •PowerPoint/Keynote: Traditional standard.

Checklist

• • Did I state the objective upfront?
• • Is the language appropriate for the audience? (No jargon for execs).
• • Are the visuals clear?
• • Do I have a clear "Ask" or "Next Steps"?