Toolkit · Project management
Don't work harder in project management.
AI drafts the status report, writes the meeting actions and summarises the risk log in seconds. Yet the week is all reporting. Time saved is for unblocking the work, not narrating it.
The five moves are a sequence, not a menu. You cannot reclaim a week you have never measured, and you should never automate work that should not exist. Work them in order. Skip a step and the gains leak away.
See
Where the PM week actually goes.
Project managers live in the reporting layer and rarely measure how thick it has become. The hours go to status reports, chasing updates, reformatting plans, meetings and the admin of keeping a tracker green. The actual unblocking, the part that moves a project, fights for room.
Do this: Track five days in thirty-minute blocks. Tag each as unblocking, reporting, chasing, or meetings. Reporting usually dominates.
Shed
Kill the project work that should not exist.
The status report that restates the tool anyone could open. The meeting held to prepare the next meeting. The plan updated weekly for an audience of one. The RAG status argued over rather than acted on. Reporting on progress is not the same as making it.
Do this: Replace your most elaborate status report with a three-line summary for two weeks. See if anyone wants the detail back.
Shift
Hand the durable, rule-bound work to AI.
Status-report drafts from the tracker. Meeting notes and actions from a recording. First-pass plans. Stakeholder-update drafts. Risk-log summaries. Build the instruction once so reporting becomes a by-product rather than the job.
Do this: Take status reporting and write a reusable prompt that drafts it from your tracker. Edit and send this week.
Shield
Defend the reclaimed hours from reabsorption.
A PM's saved hour is immediately claimed by another update or another meeting. The unblocking and forward-thinking work has no deadline of its own and quietly loses. Protect the time to solve the real risk rather than report on it.
Do this: Ringfence a weekly block to clear the project's biggest blocker. Keep status work out of it.
Spend
Reinvest in the work that does not scale.
Reclaimed hours refill with reporting by default. Spend them on the dependency nobody spotted, the stakeholder relationship, the judgement call on a trade-off, the team unblock that only a human can broker. Coordination that needs trust is the part no tool delivers.
Do this: Name the risk the RAG status keeps amber. Use the first reclaimed block to actually resolve it.