Overview
Even when reporting the same content, some people get an "OK" in 30 seconds, while others explain for 5 minutes and still hear "So what's the conclusion?" The difference is not the amount of information but the order. This skill rearranges scattered facts in your head into a conclusion-first structure and refines your reporting and explanations to match the listener's type.
Trigger Keywords
report, how to report, top-down, conclusion first, report to superior, report to team leader, how to explain, key summary, organize report, verbal report, explain easily
Workflow
Step 1: Start with the purpose of the report in one line
A report is not a boast but a tool to help the other person make decisions. First, define it in one line.
- What should the other person decide, approve, or be aware of through this report?
- Type classification: ① Approval request (please decide) ② Progress sharing (just so you know) ③ Problem report (I need help)
→ The purpose must be clear for the conclusion to be clear. If the purpose is vague, the report gets long too.
Step 2: Conclusion first (top-down structure)
Put the key sentence at the very front. Background and process come after.
| Order | Content | Example |
|---|---|---|
| ① Conclusion | The single most important sentence | "I request approval to proceed with Plan A." |
| ② Evidence | 1–3 key points supporting the conclusion | "20% cost savings, schedule shortened by 1 week." |
| ③ Risks & alternatives | Risks and other options you should know about | "However, dependence on outsourcing increases." |
| ④ Request & next steps | What the other person needs to do | "If you approve today, we'll start tomorrow." |
→ "Starting step by step from the background" is not a report but a retrospective. Throw out the conclusion first, and go deeper when questions come.
Step 3: Match your superior's type
Even the same conclusion gets different amounts of detail depending on the other person's tendencies.
- Conclusion type (busy executive): One-line conclusion + numbers. Omit details until asked; keep them in an appendix.
- Detail type (meticulous superior): After the conclusion, prepare evidence, data, and verification process. Prepare for expected questions in advance.
- Relationship type (values context): Add a line about who is affected and why, and stakeholder reactions.
- Anxious type (risk-sensitive): Present risks and countermeasures as a set to reassure them.
→ If you prepare answers by anticipating 2–3 questions the other person will ask in advance, a report won't turn into a meeting.
Step 4: The order of explanation that sticks in the other person's brain
When an explanation doesn't get through, it's usually because you skipped a premise the listener doesn't know.
- Start from what the other person already knows: Compare a new concept to something familiar
- Whole → Parts: Big picture (why/what) first, details (how) later
- One at a time: One piece of information per sentence. Don't cram it in with conjunctions
- Anchor with numbers and examples: Instead of "a lot," use "3 times," "for example…" to pin down abstractions
Step 5: 30-second compression + separate appendix
- 30-second version: Conclusion + 1 piece of evidence + request. Make it work even in an elevator.
- 3-minute version: The above + all evidence + risks and alternatives.
- Appendix: Set aside data, process, and details separately and wrap up with "I have the materials if you need them."
→ Don't pour everything out from the start; prepare in layers. Let the other person decide the depth.
Usage examples
Example 1: "The project looks like it'll be 2 weeks late—how should I report this to the team leader?" → Reorganize as conclusion first ("Expecting a 2-week schedule delay; reporting with a recovery plan") → 1 line on the cause → 2 recovery alternatives → the form of decision needed
Example 2: "I need to explain a new feature to a non-developer executive, but they keep not understanding" → Start with a familiar analogy → Value of the whole first → Explain the operation one step at a time → Anchor with numbers and screen examples
Example 3: "Every time I report, I talk too long and the conclusion comes at the end" → Conclusion·evidence·risk·request 4-block template → 30-second/3-minute two versions + prepare 3 anticipated questions
Deliverables
- One-line report purpose (approval/share/problem)
- Conclusion-first 4-block report script (conclusion·evidence·risk·request)
- Report variations by boss type
- 30-second/3-minute two versions + appendix separation plan
- 2–3 anticipated questions and answers
Precautions
- Conclusion-first is not "omitting background" but "putting background later." Bring it out the moment it's needed.
- The worse the news, the faster and more conclusion-first you should report it. Hiding it loses trust.
- Numbers must be exact. Reporting with rough figures erodes trust with detail-oriented bosses.
Related skills
- moai-comms:meeting-facilitator: Facilitating when a report leads into a meeting
- moai-comms:feedback-loop: Interim reporting and feedback requests during progress
- moai-comms:conflict-handler: Responding to difficult bosses and reactions
- moai-office:docx-generator: Organizing verbal reports into written reports
When not to use this skill
- Writing documents and reports themselves: For written deliverables, use
moai-office/moai-content. This skill focuses on speech and structure. - Official performance review meetings: Evaluation and rating feedback
moai-hr:performance-reviewuses. - Writing marketing copy and persuasive phrasing: Copy aimed at external audiences uses the
moai-contentseries.
Source
General workplace reporting and explanation framework (BLUF, conclusion first, reporting by boss type) + reference to user vault notes. Wording and examples are independently composed based on South Korea in 2026.