The PMO that stopped writing status reports

The situation

A portfolio office supporting around thirty concurrent projects spent most of Thursday and Friday assembling a weekly pack. Project managers emailed updates in different formats. Analysts rekeyed them into a deck. By the time leadership read it, the data was a week old and nobody fully trusted it.

What changed

The work was mapped task by task. Three quarters of it was collection and formatting. A drafting agent was given read access to the project tool, the risk register and the meeting notes, and a brief: produce a one-page status per project in the house format, flag anything that changed since last week, and never invent a number. An analyst reviews each draft, corrects it, and the corrections feed back into the next week’s brief.

The result

Pack preparation moved from two days to a morning. More importantly, the pack became current. Leaders started asking better questions because the “what changed” section was accurate. The analysts moved onto dependency and risk work the office had never had time for.

What it teaches

• Automate the collection, keep the judgment with people.
• The brief given to the agent matters more than the model behind it.
• Trust in reporting comes from the “what changed” line, not from more pages.

A composite drawn from our engagement work and published practice. Details are generalized and no client is identified.