Product Manager Busywork: How to Make Product Management Fun Again
Most PMs spend under a third of their week on the craft they were hired for. Here is where the time goes, which chores to hand to AI, which work to keep, and a 30-day plan to get the craft back.
Share
Product manager busywork, the chasing, copying, summarising and status-reporting around the real job, takes most of a PM's week. In Pragmatic Institute's survey of 2,474 product professionals, only 27% of time went to strategic work, against the 53% respondents said it should be. Making product management fun again means handing that assembly work to software and spending the freed hours on customers and decisions.
Key takeaways
The craft gets the smallest share. PMs report a 27% strategic, 73% tactical split, and most spend under 5 hours a month gathering customer feedback (Pragmatic Institute, 2019).
It is a job-design problem, not a motivation problem. Knowledge workers spend about 60% of their time on work about work (Asana) and are interrupted every two minutes (Microsoft, 2025).
AI is good at the chore, not yet at the craft. 40% of product leaders report high AI impact on documentation, against 17% on strategic planning (Product Institute, 2026).
Saved time gets refilled unless you assign it. Decide in advance where reclaimed hours go: customer conversations, decisions and reviewing what shipped.
Evidence links are the mechanism. When every claim in a spec traces back to a customer, defending a decision takes minutes instead of an evening.
How do product managers actually spend their time?
Product managers spend most of their time on tactical and coordination work, and much less on the strategic and customer work they consider the core of the job. The best long-running data comes from Pragmatic Institute's annual survey. In its 2019 edition:
27% strategic, 73% tactical. Respondents spent just over a quarter of their time on strategic activities, the work that finds the next market, product or innovation.
53% is what they wanted. The same respondents said they should spend 53% of their time on strategy.
The vast majority spent under 5 hours a month gathering customer and evaluator feedback.
Source: Pragmatic Institute, 2019. One respondent's advice to their CEO summed it up: "Be suspicious of product managers who spend more time with PowerPoint than with customers."
Broader workplace data shows the same shape. Asana's Anatomy of Work research, based on over 10,000 knowledge workers, found about 60% of the day goes on communicating about tasks, hunting for documents and managing shifting priorities, about a quarter on skilled work and 13% on strategic planning (Asana). Microsoft's 2025 Work Trend Index, combining telemetry with a survey of 31,000 workers in 31 markets, found people are interrupted every two minutes during core hours, 275 times a day, and receive 117 emails daily (Microsoft, 2025).
The chore crowds out the craft because it is urgent, visible and feels like progress. Spending four hours assembling context for a roadmap review looks like work, and it is work. It is just not the work that requires a product manager.
Three forces keep it that way:
Information is scattered. Feedback sits in Slack, call notes, support tickets and analytics. Engineers feel this too: in Atlassian's 2025 survey, finding information was the top time drain, and developers spent only 16% of their time coding (Atlassian, 2025).
Claims need proof. Every roadmap call gets challenged, so PMs spend evenings hunting for the customer quote that backs it.
Coordination scales with people. Each new stakeholder adds status updates, meetings and messages. Microsoft found 57% of meetings are ad hoc calls without a calendar invite.
None of this is laziness or poor discipline. It is how the job is set up. Fixing it means changing the setup, not trying harder.
What is the craft of product management?
The craft is the part only a product person can do: understanding customers deeply, choosing which problem is worth solving, shaping a solution and judging whether it worked. It is also, for most PMs, the part that made them want the job.
Practitioners describe it consistently:
User empathy and quick decisions. Andrew Ng says he values PMs with very high user empathy who can make product decisions quickly, updating their mental model of users with every new data point (The Batch, 2025).
Continuous customer contact. Teresa Torres notes that strong discovery teams talk to customers about once a week, so few decisions get made without customer input (Product Talk, 2021).
Judging risk. Marty Cagan frames product work around four risks: value, usability, feasibility and viability (SVPG, 2023).
Why does this feel good? Teresa Amabile and Steven Kramer's research on motivation in creative work points to progress. Their advice to managers: "Help them take a step forward every day" (HBR, 2011). A week of copying quotes between tools rarely feels like a step forward. A week that ends with a sharper decision does.
The cost of losing the craft is not only morale. Pendo's 2019 analysis of 615 product subscriptions found 80% of features in the average product were rarely or never used (Pendo, 2019). Less time with customers makes that outcome more likely. More on that in why most features go unused.
Which PM tasks should you hand to AI, and which should you keep?
Hand AI the work that gathers, sorts and drafts. Keep the work that chooses, commits and judges. A practical split:
Task
Chore or craft?
Who does it
Transcribing and tagging customer calls
Chore
AI, with spot-checks
Pulling feedback from Slack, support and sales notes into one place
Chore
AI
Finding the customer quote that supports a claim
Chore
AI, with a link to the source
First draft of a problem statement or PRD
Chore
AI drafts, PM rewrites
Weekly status update
Chore
AI drafts from tracker data, PM edits
Clustering feedback into themes
Mixed
AI proposes, PM challenges
Talking to customers
Craft
PM
Choosing which problem to solve
Craft
PM, with the team
Saying no and explaining why
Craft
PM
Judging whether a release worked
Craft
PM, with data AI pulls
The pattern matches what product leaders report. In Product Institute's 2026 survey of 309 leaders, 40% saw high AI impact on documentation and knowledge management, but only 17% on strategic planning and roadmapping (Product Institute, 2026). AI is already good at the chore. The craft is still yours.
Use this four-week plan. The numbers in the example are illustrative; replace them with your own.
Week 1: Audit your time. Log every 30-minute block for five working days as craft (customers, decisions, shaping, reviewing outcomes) or chore (assembling, copying, chasing, reporting). Say the log shows 11 of 45 hours as craft, about 24%, close to the Pragmatic average.
Week 1: Name your three biggest chores. For example: compiling feedback before planning (6 hours), writing the weekly update (2 hours), finding evidence for roadmap debates (4 hours).
Week 2: Automate or kill each one. Connect feedback sources so they collect in one place with links to the original. Draft the weekly update from tracker data. Stop any report nobody has replied to in a month.
Week 2: Pre-commit the freed hours. Put them in the calendar before they disappear: for instance, three 30-minute customer calls and one 2-hour decision block every week.
Week 3: Ship one evidence-linked spec. Write one spec where every claim links to a customer source. Time how long the next stakeholder challenge takes to answer.
Week 4: Re-audit. Log another five days. A realistic target is moving from about a quarter of your time on craft to about 40%. If chore hours came back, find where they came from.
Only if you decide where the saved time goes. Time saved by tools tends to be refilled by more of the same: more meetings, more messages, more requests. Product Institute found that only 36% of product leaders said AI was strengthening how their organisation works, while 23% said it was exposing existing weaknesses (Product Institute, 2026).
So the goal is not more PM output. It is narrower: which hours you get back. Maker time, discovery time and decision time are what make the job feel like building again, and they matter more as coding gets cheaper and deciding becomes the bottleneck (see the PM-to-engineer ratio in the AI era). Protect those hours on the calendar first, then automate what fills the rest.
Common mistakes when cutting product manager busywork
Automating a report nobody reads. Kill it instead. Automation makes useless work cheaper, not useful.
Trusting summaries without sources. An AI summary that cannot point to the original call or ticket creates new chores: checking it.
Letting saved hours drift back into meetings. Book customer and decision time before the week fills.
Handing off decisions with the drafts. If the AI's first draft becomes the plan because nobody challenged it, you gave away the craft.
Skipping the audit. Without a baseline, you cannot tell whether anything changed.
This approach works less well where the chore is mandated, such as compliance reporting in regulated industries. There, automate the assembly and keep the sign-off.
Where Specky fits
Specky is built to take the assembly work off the PM's plate. It reads customer calls, feedback, Slack, Jira and analytics into a Product Graph and drafts specs where every claim links back to the customer who said it, so defending a decision takes a glance rather than an evening. To try the idea without signing up, paste a messy piece of customer feedback into the free feedback-to-spec tool and see what comes back.
Frequently asked questions
How do product managers spend their time?
Mostly on tactical work. In Pragmatic Institute's 2019 survey of 2,474 product professionals, 27% of time went to strategic activities and 73% to tactical ones, while respondents said 53% should be strategic. Most spent under 5 hours a month gathering customer feedback. Wider studies show knowledge workers spend about 60% of their day on work about work.
What counts as product manager busywork?
Busywork is work that moves information without adding judgement: compiling feedback from several tools, copying quotes into documents, writing status updates from tracker data, chasing people for updates and formatting slides. It is necessary, but it does not require a product manager's skills, and AI tools now handle much of it well.
Can AI make product management more enjoyable?
It can, if the time it saves goes to customer conversations, decisions and reviewing outcomes. AI is strongest at documentation and synthesis today. The risk is that saved hours fill with more meetings. Pre-commit the reclaimed time on your calendar, and keep the decisions with people.
How much of a PM's week should be strategic?
Product professionals in Pragmatic Institute's survey said about 53% should be strategic, against the 27% they reported. Department heads and executives wanted an even higher share. A realistic first target for most individual PMs is moving from about a quarter to about 40% within a month, then holding it.
Why do product managers burn out?
Common causes include constant interruptions, coordination load and too little time on the work that feels meaningful. Microsoft's 2025 data shows interruptions every two minutes during core hours. Research on motivation by Amabile and Kramer points to daily progress on meaningful work as a key driver of engagement, which busywork rarely provides.
GDPR-aligned. EU workspace data is stored in Frankfurt, Germany. GDPR and EU data Built in Vienna, Austria. A product of influence solutions fm GmbH (FN 675374y). Imprint 14-day trial. Card required, and nothing is charged until day 14. 30-day refund after subscribing. See pricing