Toolkit · Product
Don't work harder in product.
AI drafts the PRD, synthesises the feedback and writes the release notes in seconds. Yet the PM week fills with status and syncs. The time saved is for understanding the problem, not narrating the roadmap again.
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 product week actually goes.
Product managers sit at the centre of everyone's coordination and pay for it in hours. The week goes to writing tickets, status updates, stakeholder syncs, reformatting roadmaps and triaging requests. Discovery, the actual work of deciding what to build, gets whatever is left.
Do this: Track five days in thirty-minute blocks. Tag each as discovery, writing, coordination, or status. Discovery is usually the casualty.
Shed
Kill the product work that should not exist.
The roadmap deck rebuilt every week for the same audience. The detailed spec for the feature that will not ship this quarter. The stakeholder sync that restates the board. The backlog grooming of tickets no one will ever build. Motion on the roadmap is not progress on the product.
Do this: Stop rebuilding your recurring roadmap artefact for two weeks. See who actually asks for the update.
Shift
Hand the durable, rule-bound work to AI.
First-pass PRDs from your notes. User-feedback synthesis across hundreds of responses. Ticket drafts. Release notes. Competitive scans. Research summaries. Build reusable templates so the writing stops being the work and becomes the by-product of the thinking.
Do this: Take user-feedback synthesis and write a reusable prompt that clusters it into themes. Use it on this cycle's inputs.
Shield
Defend the reclaimed hours from reabsorption.
A PM's calendar is the first thing every other team reaches for. Discovery and strategy time look optional because nothing external is chasing them. Default to no on syncs that could be written, and protect the block where you actually understand the problem before solving it.
Do this: Block a weekly discovery slot with no stakeholders in it. Defend it as the core of the role.
Spend
Reinvest in the work that does not scale.
Reclaimed hours refill with coordination by default. Spend them on understanding the customer problem, the prioritisation call nobody else can make, the cross-functional trust, the bet on what to build next. Judgement is what defines the product, and it does not come from a template.
Do this: Name the customer problem you have not had time to understand properly. Give it the first reclaimed block.