Lesson 6: Report Drafting and Synthesis

It is 11:30 AM. You have a pile of raw notes, bullet points, or data, and you need to compile a formal report or executive summary. Asking an AI to “write a report” results in wordy, school-essay style paragraphs. Use formal corporate registers, metrics, and structured directives to generate sharp documentation.

The Report Swap Table

#	Generic Term	Precise Alternative	Output Benefit
1	Write a report	Draft an executive briefing	Triggers professional structures (Summary, Key Findings, Action Items).
2	Sound professional	Objective, authoritative register	Removes emotional filler, buzzwords, and sales-like hype.
3	Important numbers	High-impact metrics / Variance	Directs focus to statistical changes and milestones.
4	What should we do	Strategic recommendations	Returns prioritized, actionable next steps instead of advice.
5	What went wrong	Project post-mortem / Root causes	Triggers technical fault analysis and prevention protocols.

---

Example 1: Executive Briefing

• Noob Prompt: Write a report about our sales.
• Pro Prompt: Draft an executive briefing from these sales figures, focusing on key milestones.
• Alternative Scenario Combinations:
  • Scenario A: Tech Feasibility ➡️ Draft an executive briefing summarizing the technical feasibility of this migration, focusing on architectural blockers.
  • Scenario B: Regulatory Audit ➡️ Draft an executive briefing detailing our GDPR compliance audit findings.
  • Scenario C: Marketing Performance ➡️ Draft an executive briefing summarizing our Q2 ad campaign ROI, focusing on cost-per-acquisition (CPA).
• Why It Works: Specifying the type of briefing (technical, regulatory, marketing) prompts the AI to focus on industry-specific variables (GDPR rules, CPAs, blockers) rather than general concepts.

Example 2: Objective Tone

• Noob Prompt: Make this report sound professional and smart.
• Pro Prompt: Rewrite this report in an objective, authoritative register.
• Alternative Scenario Combinations:
  • Scenario A: Incident Analysis ➡️ Rewrite this server incident description in a neutral, post-mortem register. Avoid emotional blame.
  • Scenario B: Performance Review ➡️ Rewrite this performance feedback in an objective, professional register, focusing on growth areas.
  • Scenario C: Journalistic Press ➡️ Rewrite this product announcement in a journalistic, objective register for media distribution.
• Why It Works: Register prompts like “post-mortem,” “professional,” or “journalistic” strip away conversational fluff and enforce high-level neutrality.

Example 3: Extracting Key Metrics

• Noob Prompt: Tell me what the most important numbers are in this spreadsheet.
• Pro Prompt: Extract all high-impact metrics showing a variance greater than 10%.
• Alternative Scenario Combinations:
  • Scenario A: Cost Audit ➡️ Extract all accounts showing a cost variance greater than 5%, listing the discrepancies.
  • Scenario B: Server Latency ➡️ Synthesize these server logs, isolating latency spikes with a deviation of 20%.
  • Scenario C: Survey Drops ➡️ Summarize this customer survey data, highlighting categories with a satisfaction drop of 15% or more.
• Why It Works: Adding mathematical threshold constraints (5%, 20%, 15%) forces the AI to act as a data filter, skipping trivial data points.

Example 4: Actionable Recommendations

• Noob Prompt: What should we do next based on this report?
• Pro Prompt: Formulate 3 strategic recommendations based on these findings, ordered by feasibility.
• Alternative Scenario Combinations:
  • Scenario A: Cost Reductions ➡️ Formulate 3 cost-reduction recommendations, ordered by speed of implementation.
  • Scenario B: Product Roadmap ➡️ Propose 3 software features for the next release, ranked by customer value and development effort.
  • Scenario C: HR Hiring Latency ➡️ Suggest 3 recruiting strategies to reduce hiring latency, ranked by resource requirements.
• Why It Works: Specifying ranking parameters (“feasibility,” “speed,” “effort”) forces the AI to evaluate trade-offs rather than outputting generic ideas.

Example 5: Post-Mortem Analysis

• Noob Prompt: Write a summary of what went wrong in our project.
• Pro Prompt: Draft a project post-mortem, isolating root causes and corrective actions.
• Alternative Scenario Combinations:
  • Scenario A: Campaign Failure ➡️ Draft a post-mortem for the failed ad campaign, isolating target-audience discrepancies and corrective actions.
  • Scenario B: Release Delay ➡️ Draft a retrospective on the software release delay, isolating dependencies and timeline corrections.
  • Scenario C: Budget Overrun ➡️ Draft a post-mortem on the budget overrun, isolating cost deviations and allocation corrections.
• Why It Works: Formatting queries around “root causes” and “corrective actions” forces the AI to output productive solutions rather than stories of failure.

---

Put It Into Action

Pick one of the exercises above:

1. Open your favorite AI tool, paste the Noob Prompt, and look at the response.
2. In a brand-new chat session, paste the corresponding Pro Prompt or one of the Alternative Scenario Combinations.
3. Compare the outputs. See how different vocabulary mixes completely shift the focus, structure, and quality of the response!