Purpose
By the end of this lesson, you will be able to plan a report’s structure before building it, starting from the decision it needs to support.
Lesson Explanation
A useful report starts not from the raw data, but from the decision the report needs to support: “should we renew this vendor contract,” “which region needs additional headcount,” “is the marketing campaign working.” Starting from raw data and hoping a useful structure emerges tends to produce a report that’s comprehensive but doesn’t clearly answer anything.
Once the decision is clear, work backward: what specific numbers or comparisons would actually inform that decision, what time period is relevant, and what level of detail does the audience actually need (a summary figure, or a full breakdown)?
A genuinely useful planning habit: sketch the report’s section headings and rough content BEFORE opening the raw dataset, based purely on what the decision requires – this prevents the temptation to include a calculation or chart simply because the data happens to be available, rather than because it’s actually relevant to the decision at hand.
A report structure that works well in most business contexts: a brief summary of the key finding or recommendation first, followed by supporting detail, followed by any caveats or data limitations – front-loading the answer rather than making the reader wait for it at the end.
Practice Questions
1. A manager starts building a report by opening the raw sales dataset and exploring what’s there, without first defining what decision the report needs to support. What risk does this lesson identify with this approach?
View Answer
The resulting report tends to be comprehensive but doesn’t clearly answer anything specific, since it wasn’t built around a defined decision from the start.
2. A report needs to help leadership decide “should we renew this vendor contract?” What should be defined first, before opening any raw data, per this lesson’s approach?
View Answer
What specific numbers or comparisons would actually inform that renewal decision – e.g., cost trends, service quality metrics, comparison to alternatives.
3. Why does this lesson recommend sketching section headings and rough content BEFORE opening the raw dataset?
View Answer
It prevents including a calculation or chart just because the data happens to be available, rather than because it’s genuinely relevant to the decision the report needs to support.
4. What report structure does this lesson recommend as generally effective: leading with a summary, or leading with detailed background information first?
View Answer
Leading with a brief summary of the key finding or recommendation first, followed by supporting detail and caveats – front-loading the answer.
5. A report is being built to help decide “which region needs additional headcount.” What kind of comparison would likely be central to this report, based on working backward from the decision?
View Answer
A comparison of workload, output, or capacity metrics across regions – whatever specific measure would actually indicate where additional headcount is genuinely needed.
6. A 20-page report is produced containing every available metric from a dataset, with no clear recommendation or highlighted finding. What does this lesson suggest went wrong in the planning process?
View Answer
The report likely wasn’t built starting from a specific decision it needed to support, leading to a comprehensive but unfocused result.
7. Why might starting from “what decision does this report support” help determine the appropriate level of detail for the audience?
View Answer
Different decisions and audiences need different levels of detail – a quick summary figure might suffice for one decision, while a full breakdown might be necessary for another, and this becomes clear once the actual decision and its audience are identified.
8. A report is being planned to assess “is the marketing campaign working?” List two specific numbers or comparisons that would likely be relevant to include, working backward from this decision.
View Answer
Examples could include: campaign cost versus revenue generated (ROI), conversion rate compared to a previous campaign or baseline, or lead volume before and after the campaign launch.
9. A report leads with five pages of raw data tables and background context before finally stating its main recommendation on the last page. Is this consistent with the structure this lesson recommends?
View Answer
No – this lesson recommends front-loading the summary or recommendation first, rather than making the reader wait until the end for the actual answer.
10. Why might exploring raw data first, before defining the decision, tempt someone to include irrelevant calculations in a report?
View Answer
Once you’ve already calculated something interesting from the data, there’s a natural pull to include it in the report, even if it doesn’t actually inform the decision the report is meant to support.
11. A well-planned report includes a one-sentence key finding at the top, three supporting charts in the middle, and a caveat section noting a data limitation at the end. What structure does this reflect?
View Answer
The structure this lesson recommends: summary/finding first, supporting detail next, caveats/limitations last.
12. A report needs to help decide between two vendor options. Before opening the pricing spreadsheet, what should the report planner define first, per this lesson’s guidance?
View Answer
The specific criteria that matter for this vendor decision (like cost, reliability, contract terms) and what comparison would actually help distinguish between the two options – working backward from the decision itself.