Where a product manager's week actually goes — and why strategy keeps losing

The average manager spends ~13 hours a week in meetings; in software companies it's closer to 27. Across roles, ~60% of the workday goes to "work about work." For the PM — whose entire value is the strategic slice — that's the whole problem.

The meeting tax

• Managers spend an average of 13 hours/week in meetings — over 20% of a standard workweek. In global software companies, managers reported 27.5 hours/week (5.5 hours a day).
• Professionals spend about 4.75 hours/week just arranging ~15 meetings.
• Remote employees attend 50% more meetings than in-office staff.

"Work about work" eats the day

Asana's Anatomy of Work research found ~60% of the workday goes to "work about work" — coordination, status updates, searching for information — leaving roughly 27% for skilled work and only ~13% for strategic planning. For most roles that's an annoyance. For the PM, whose value is the strategic 13%, it's the job.

What's left for the PM

• PMs spend only about 27% of their time on strategy; ~73% on tactics and execution (Pragmatic Institute).
• Roughly 52% of a PM's time goes to unplanned "firefighting."
• 74% of product professionals spend fewer than 5 hours a month with customers.
• 61% say they want more time on strategy and believe it would change outcomes.

Why this compounds

The one role responsible for deciding what's worth building has the least uninterrupted time to decide it. Judgment work — talking to customers, synthesizing, choosing the next bet — gets displaced first when the calendar fills with coordination. So decisions default to the fastest input available: the loudest voice, the most recent complaint, the executive's hunch. That's a structural failure, not a discipline one. You can't out-willpower a calendar that's 60% coordination.