topic
Report writing prompts
Status reports, exec summaries, the brief nobody briefed you for.
333 prompts live in report writing next drop in 10:23
- work Translate a Technical Status Update for a Non-Technical Boss
Shrink a technical status update to what your boss actually needs.
- creative Summarise a Long Blog Draft Into a Tight Opening Hook
Find the argument buried in a long draft and lead with it.
- work Translate an Incident Report Into a Plain-English Executive Update
Turn a technical bug report into an update your boss can actually read.
- work Summarise a Stack of Customer Support Tickets Into a Weekly Themes Report
Turn a week of raw support tickets into a themes report leadership can act on.
- work Summarise a Failed Product Launch Into a Postmortem for Leadership
Write the postmortem that actually explains what went wrong, without the blame.
- work Translate a Board-Level Ask Into an Engineering Roadmap Trade Off
Turn a vague board ask into a roadmap trade-off your team can actually plan.
- work Explain a Technical Architecture Decision in a Design Review Document
Write up an architecture decision so it still makes sense in six months.
- work Critique a Restructuring Plan Before You Present It to the Board
Stress-test a restructuring plan before the board finds the hole in it.
- work Critique a Draft Job Advert Before You Post It
Catch the job advert language that quietly filters out good candidates.
- work Explain a Database Query Plan to a Non-Technical Product Manager
Turn a query execution plan into something a product manager can act on.
- work Summarise a Technical Postmortem for Leadership
Turn a forty-page technical postmortem into what leadership needs to know.
- work Reframe a Missed Deadline for a Client Update
Tell a client you missed the deadline without it reading like an excuse.
- work Plan a Return-to-Office Announcement That Doesn't Cause a Revolt
Plan a return-to-office announcement that survives the all-staff channel.
- work Critique a Stakeholder Update Email for Buried Bad News
Find the bad news you accidentally hid inside your own status update.
- work Explain Your Team's Velocity Trend to a Sceptical Manager
Explain a dip in sprint velocity before your manager decides it is a crisis.
- work Explain an Engineering Decision to a Non-Technical Stakeholder
Explain a technical call to someone who signs the budget, not the code.
- creative Summarise a Non-Fiction Chapter into Podcast Show Notes
Turn a dense chapter into show notes listeners actually read before pressing play.
- work Translate a Technical Bug Report into a Stakeholder Update
Turn engineer speak into a message your stakeholders will actually read.
- work Summarise a Long Meeting Transcript into Structured Minutes
Turn an hour of crosstalk into minutes people will actually read.
- work Plan a Sprint That Fits the Team's Actual Capacity
Plan a sprint the team can actually finish, not just the one you hoped for.
- work Generate a Project Status Report from Rough Notes
Turn a week of scrappy notes into a status report worth reading.
- work Translate Technical Findings From a QA Report Into Business Impact
Turn a technical QA report into a business impact summary a stakeholder can act on.
- work Summarise a Quarter's Worth of Scattered Engineering Incidents
Turn a quarter of incident reports into the one pattern leadership actually needs to hear.
- work Reframe the Same Old Status Update Nobody Reads Anymore
Rewrite the status update so someone might actually read it this time.