Executive Reporting · The Art of Reporting
Executive Reporting
What is executive reporting?
- Not 'what we did' but 'what we need you to decide'
- Preparing for likely questions keeps the main body short
- Bad news: early, accurate, and with alternatives
Refining an executive report doesn't just make the document shorter; it changes the starting point of its design. A draft written by a practitioner usually follows chronological order from kickoff to the present, but a report that supports a decision is built backward from the point where the executive has to say 'yes' or 'no.' It starts with the title. When 'XX Project Progress Update' becomes 'Request for Approval: XX Schedule Delayed by 3 Weeks,' what the meeting will discuss is settled within 10 seconds of its start.
Reports fall into four types: approval, decision request, progress update, and risk alert. Each calls for a different time allocation. An approval report is done with one line of request and three lines of rationale, but a decision request spends half its length comparing alternatives. An alert report is 30 seconds of facts, and everything else is response options. A workable format puts three lines of conclusion, three pieces of evidence, and one request on a single page, moving calculations, raw data, and meeting minutes to an appendix. If you prepare assuming the executive will listen for 7 minutes at most, with the rest as Q&A, sizing the report becomes easy.
You also need to tell a report apart from a consultation. A consultation is a setting for finding the answer together, so information can be spread out widely, but a report is where an answer the team has already narrowed down is submitted in a form ready for decision. That is why numbers need a point of comparison. 'Defect rate 1.8%' alone gives nothing to judge by, but '0.6 percentage points over the 1.2% target, improved from 2.4% in the same month last year' can be judged on the spot. A number without a benchmark invites questions, and once the follow-up questions pass three, the time allotted for the report is gone for good.
The most common misunderstanding is reading 'conclusion first' as 'assert it without evidence.' If the first sentence is strong but the answer to a question about the evidence is 'I'll check' twice, from that day on that person's conclusions become something to be verified. The second is the habit of treating a recommendation as overstepping and simply listing three alternatives. The decision then bounces back to the team and the same agenda item returns to the meeting two weeks later. The third is polishing bad news so long that it gets reported late. If you report on the day you become aware of a delay, renegotiating the delivery date, adding staff, and adjusting scope are all still possible, but if you sit on it for a month, the only option left is an apology.
John KimInstructor John Kim, author of B2B Marketing Design and CEO of Nanum Consulting
Ara LimSpecialist in global leadership, AI, and business communicationA practice that took shape in management communication, systematized by combining the Pyramid Principle with the executive summary tradition.
Let's look at a hypothetical case. Company A, a household goods maker (380 employees, KRW 120 billion (≈ US$89,780,000) in annual revenue), was implementing an MES at its new plant. Four months after kickoff, a delay in a partner's equipment delivery meant the planned go-live date would slip by 3 weeks, and Manager Kim of the Production Engineering team had to bring the issue to the Manufacturing Division head's weekly meeting.
- Manager Kim deleted the draft title 'MES Implementation Progress Update,' replaced it with 'Request for Approval: Go-Live Delayed by 3 Weeks,' and asked the division head's assistant to book a 10-minute slot in advance.
- The first sentence of the report was 'Please move the go-live date from November 3 to November 24,' and the cause was given in just two lines: a two-week delay in the partner's equipment delivery and the absence of one inspector.
- It includes a table comparing three options (delay, scope reduction, and added staffing) on cost and quality criteria, and below the table, one line in bold: 'Recommendation: 3-week delay, extra cost KRW 42 million (≈ US$31,400)'.
- When the division head asks, 'Why didn't you escalate this two weeks ago?', Manager Kim answers, 'I should have escalated it the day I was told of the delivery delay,' and then proposes a standard of a one-page report within 24 hours of recognizing a schedule risk.
- Because eight questions were prepared in advance and attached as an appendix, the meeting ended in 12 minutes and the delay was approved on the spot. By adjusting the scope of the packaging line, the extra cost dropped from KRW 42 million (≈ US$31,400) to KRW 26 million (≈ US$19,500).