Deciding what a report is for before automating it
Automating a report that nobody acts on produces the same inaction, faster. Before building anything it is worth writing one sentence per report: who reads it, what decision it supports, and what they would do differently if the number moved.
Reports that survive that sentence are usually a small minority, and that is the useful finding. Most recurring reports exist because someone once asked for them, and the person who asked has moved on. Retiring them frees the attention that the remaining ones need.
- One sentence: reader, decision, action if the number moves
- Reports without an owner retired, not automated
- Frequency matched to how fast the number can change
- Distribution list reviewed when people change roles