Start the Report with a Problem
This workbook helps you build stronger data slides by turning numbers into a clear story. You will practise framing the problem, choosing the right insight, and preparing a slide that gives the audience a reason to care.
Core Flow
Use this sequence whenever you prepare a data-related report.
Today’s focus: Problem. Your first job is to help the audience know what deserves attention.
Why Start with Problem?
Data does not speak clearly on its own. A problem gives the audience a lens. It tells them what to notice, why it matters, and what kind of thinking is needed.
Problem gives data a purpose
Many reports begin with a chart, table, or dashboard. The audience can see the numbers, but they still need to guess what matters.
A problem statement helps the audience understand the reason behind the data. It turns the report from a data dump into a focused story.
A problem does not always mean something is wrong. It can also be a gap, risk, opportunity, uncertainty, decision need, or learning need.
- Gap: Performance is below target.
- Risk: A pattern may create future issues.
- Opportunity: A positive pattern deserves focus.
- Uncertainty: The data raises a question.
- Decision need: A choice must be made.
- Learning need: People need to interpret the data better.
Activity 1: Data Without Direction
10 minutesInstruction: Review the data below. Do not solve it yet. First, write what you think the presenter wants the audience to notice.
Activity 2: Same Data, Different Problem
15 minutesInstruction: Read the three problem frames. Choose which frame gives the clearest direction for a management presentation.
Problem is the audience’s entry point. It does not need to be dramatic. It needs to make the data relevant.
Module 2 is locked
Enter the facilitator code to continue.
How to Write a Problem Statement Hook
A problem hook connects the presentation objective, audience concern, and data situation. It helps the audience understand why the topic matters now.
The hook is not a decoration
A good hook is not a dramatic slogan. It is a clear problem statement that guides the audience into the report.
The hook should answer three questions:
- What is happening?
- Why does it matter to this audience?
- What tension, risk, gap, opportunity, or decision does the data create?
Basic formula:
Use this when the audience needs to see why the data matters to them.
Activity 1: Clarify the Objective
12 minutesInstruction: Select the objective that best matches the presentation. Then write what the presentation should achieve.
| Objective | Purpose | Sample Problem Direction |
|---|---|---|
| Inform | Help the audience understand what happened. | What changed, improved, declined, or stayed the same? |
| Persuade | Convince the audience that something deserves attention. | Why should this issue matter now? |
| Influence | Shift how the audience thinks or prioritises. | What should they see differently after this report? |
| Decide | Help the audience choose between options. | What choice needs to be made? |
| Warn | Highlight early risk before it becomes serious. | What pattern may become a problem later? |
| Train | Help the audience learn how to read the data. | What interpretation skill do they need? |
| Align | Get different stakeholders to see the same issue. | What common understanding is needed? |
Activity 2: Audience and Pain Point
18 minutesInstruction: Choose the audience. Then describe what they care about in relation to the objective.
Activity 3: Write the Hook
15 minutesInstruction: Use the formula to write three versions. Choose the strongest one.
Module 3 is locked
Enter the facilitator code to continue.
Examples of Problem Statements
The same data can create different problem statements. The objective and audience decide the angle.
Base Data Situation
Sales increased by 12% this month, but 80% of the growth came from one product category.
Audience: Sales Director
| Objective | Problem Statement |
|---|---|
| Inform | Sales grew this month, but the growth is concentrated in one product category. |
| Persuade | The sales increase deserves attention because it may be less stable than it appears. |
| Decide | The sales team needs to decide whether to scale the winning product or reduce dependency risk. |
| Warn | If growth continues to rely on one product category, next month’s target may become harder to protect. |
| Influence | The current pattern suggests that sales focus should shift from total growth to quality of growth. |
Objective: Persuade
| Audience | Problem Statement |
|---|---|
| CEO | The growth looks positive, but it may not be sustainable if it depends heavily on one category. |
| Sales Director | The growth is encouraging, but the team needs to manage category dependency before the next target cycle. |
| Marketing Team | The sales pattern suggests that campaign support may need to focus on the category driving actual growth. |
| Finance Team | The revenue increase needs to be reviewed for dependency risk and margin quality. |
| Frontline Team | The team needs to understand which product behaviour is driving growth so that selling efforts can be sharper. |
Activity 1: Spot the Lens
20 minutesInstruction: Read each statement. Identify the likely objective and audience.
| Problem Statement | Likely Objective | Likely Audience |
|---|---|---|
| The service score improved, but repeated complaints about response time suggest that customer frustration has not fully reduced. | ||
| The team needs to decide whether next month’s improvement effort should focus on speed or resolution quality. | ||
| This trend is useful for learning how a positive average can hide a weak segment. | ||
| Although total performance is improving, the gap between high and low performers is widening. |
Activity 2: Rewrite for a New Audience
20 minutesInstruction: Use the same data situation. Rewrite the problem hook for two different audiences.
Strong problem framing is audience-specific. The same number can support different stories depending on what the audience needs to understand, decide, or act on.
Module 4 is locked
Enter the facilitator code to continue.
Practice Writing the Problem Statement
You will receive the objective and audience. Your task is to identify the relevant pain points, write the problem statement, then unlock the mock data to choose the insight that best supports your audience.
Your Practice Scenario
You are preparing a short data-related report for a monthly business review.
Section 1: Select the Relevant Pain Points
25 minutesInstruction: Some pain points below are relevant. Some are distractions. Select the pain points that truly match the objective and audience.
Use this structure:
Section 2 is locked
Complete Section 1 first. Enter the facilitator code to view the mock data.
Section 2: Pick the Insight for This Audience
35 minutesInstruction: Review the mock data. Do not use every chart. Choose the chart or data point that best supports your problem statement for Senior Management.
Choose the strongest insight for Senior Management. Do not pick a chart just because it looks interesting. Pick the insight that supports the problem statement and objective.
A strong presenter does not show every possible chart. A strong presenter chooses the chart that helps the audience understand the problem and move toward the right decision.