Generate the weekly operating brief from source systems
A concise operating brief arrives with KPI movements, exceptions, decisions needed, owners, and links to source evidence.
The problem
The weekly review is assembled manually from status messages, spreadsheets, tickets, and whatever leaders remember to mention.
What you get
A working system with the steps, tools, checkpoints, and expected return made explicit.
- Setup
- 90 minutes
- Back each week
- 4 hours
- Difficulty
- assisted
Expected return
The working case
A planning estimate, not a guaranteed result. Measure the first four weeks against your own baseline.
192
hours returned per year
At 4 hours/week across 48 working weeks.
1
week to earn back setup
Compare the setup estimate with the weekly time returned.
Operating contract
Input
The source material, constraints, and examples a human would need to do this work well.
Checkpoint
A person reviews judgment calls, sensitive content, unfamiliar tools, and irreversible actions.
Success signal
Track time returned, corrections required, and exceptions. Keep it only if the measured result compounds.
Before you start
- ·Named KPI owners
- ·Source links for operating data
The steps
- 01
Define the fixed brief: outcomes, KPI deltas, exceptions, decisions, commitments, and previous actions.
- 02
Pull read-only data and owner updates into a dated evidence bundle.
- 03
Draft the narrative with links and clearly label missing updates.
Copy this prompt
Draft the weekly operating brief. Lead with material changes, not activity. For every statement include its source link. Separate facts, owner commentary, and decisions required. Inputs: [bundle]
- 04
The operating lead approves the brief and records decisions back in the system of record.
What it runs on
- Notion
Brief and decision record.
- Linear
Project and issue evidence.
- Google Sheets
KPI source where needed.
Where this goes wrong
- Activity volume is not an outcome.
- Never bury an unresolved decision inside generated prose.
Definition of done
Run it for four weeks. Then make it earn its place.
- □ Baseline the manual time before launch.
- □ Keep a human approval step for consequential output.
- □ Record corrections and exceptions, not just successes.
- □ Expand, revise, or retire it after the first review.
Build the system around it
Related workflows
If this one stops working, tell us. Three reports in a month and it leaves the library until a person has looked at it again.