How the problem develops
Each week someone copies dates, open actions and blockers from several tools into a slide deck. The report is out of date before the meeting starts. The same effort repeats because the reporting structure and source fields are not defined.
What to check first
- Identify which sections repeat unchanged and which require a decision or interpretation.
- For each number or status, name the source, reporting period and owner of corrections.
A better process
- Define a small recurring report with stable operational fields.
- Collect the fields at a stated cutoff and link back to their sources.
- Separate factual updates, missing information and commentary requiring review.
What a system can do
Gather approved project updates, assemble a draft summary and flag source failures or missing fields.
Where people stay in control
The system must not invent progress, explain disputed delays or score individual employees.
Benefits and tradeoffs
The useful outcome
The team can spend the meeting discussing exceptions instead of compiling the same data.
The tradeoff
A regular report can preserve an unhelpful format. Remove sections nobody uses before making them cheaper to produce.
Test before going live
Compare a generated draft with the source at the same cutoff, including a missing update and a failed connection. Neither should appear as healthy progress.