topic
Report writing prompts
Status reports, exec summaries, the brief nobody briefed you for.
333 prompts live in report writing next drop in 09:43
- work Summarise a Quarter of Scattered Project Updates Into One Coherent Narrative
Turn three months of scattered updates into one narrative the steering group will follow.
- work Summarise a Quarter of Scattered Project Updates Into One Board-Ready Page
Turn three months of scattered standups into one page the board will read.
- work Generate a Status Update That Actually Gets Read
Turn scrappy project notes into an update people actually read.
- work Summarise a Technical Design Doc Into an Executive Version Nobody Skips
Turn a technical design doc into something a busy exec will actually read.
- work Summarise a Sprawling Technical Discussion Into a Decision Record
Turn a rambling technical thread into a decision record people will use.
- work Explain a Project Delay to Stakeholders Without Sounding Defensive
Explain a project slip without sounding like you are making excuses.
- learn Translate Specialist Research Findings for a Cross Disciplinary Audience
Translate specialist findings for smart people from a different field entirely.
- learn Critique Your Own Argument for the Weakest Link Before Anyone Else Does
Find the hole in your argument before someone else finds it in the room.
- work Translate Technical Jargon Into Something a Non Technical Stakeholder Will Read
Turn an engineering update into something a stakeholder will not skim past.
- learn Check Your Own Essay Paragraph for a Missing Argument
Find out if your paragraph is arguing something or just describing it.
- work Translate Technical Work Into Language a Non-Technical Stakeholder Will Act On
Explain finished technical work to someone who does not care how it was built.
- work Generate a Status Update Email That Actually Gets Read
Turn a messy week of notes into a status email people actually finish.
- work Translate a technical incident report into an update your customers can read
Turn an internal incident report into a status update customers will actually understand.
- work Translate a technical incident report into a plain English update for non technical stakeholders
Turn an engineer's incident report into something a director will actually understand.
- work Critique a draft performance review before you send it to your report
Catch the vague line in your review before your report does.
- work Compress a quarter's worth of project updates into a five minute leadership read
Turn three months of scattered status notes into a five minute board read.
- work Critique a colleague's project update before it goes to your manager
Catch the vague phrase that is quietly hiding a slipping deadline.
- work Summarise a Client Feedback Survey Into Three Themes for the Team
Turn a pile of client survey responses into three themes the team can actually act on.
- work Generate a Crisis Communication Holding Statement Within the Hour
Get a holding statement out fast without accidentally admitting liability.
- work Translate a Dense Technical Postmortem Into an Executive Summary
Get the board level version of a technical postmortem, without losing what actually matters.
- work Explain a Budget Variance Report to Non Finance Stakeholders
Get a budget variance report explained in language non finance people actually use.
- work From Meeting Minutes to a Report People Will Actually Read
Turn raw meeting minutes into a tidy report of decisions and actions.
- work Find Out What Each Section of Your Report Is For
Learn what every report section is for before you write a word.
- work Shrink Ten Pages of Technical Detail into an Executive Summary
Compress technical detail into an executive summary that survives a 90-second read.