How to Reclaim 10 Hours a Week as a PM
You can reclaim roughly 10 hours per week by categorizing every meeting into four buckets (essential, valuable-but-optional, low-value, delegatable) and then applying six decision rules: require agendas, skip meetings where you do not speak, justify recurring meetings quarterly, keep standups to 15 minutes, batch similar meetings, and protect two 2-hour focus blocks.
I tracked my time for 4 weeks. The result: 25 hours per week in scheduled meetings. Another 6 hours in ad-hoc conversations and Slack threads that functioned as meetings. That left about 9 hours for the actual work of product management. Discovery, analysis, writing specs, thinking.
Nine hours. For a 40-hour week. And I was not an outlier. When I shared this with other PMs, most reported similar numbers. Some were worse.
The problem is not that PMs attend meetings. Many meetings are necessary. The problem is that PMs accept meetings by default instead of by design. Here is how to change that.
The Audit
Take your calendar from last week. Categorize every meeting into one of four buckets:
Bucket 1: Essential. You must attend and actively contribute
These are meetings where your absence would block a decision or harm the outcome. Examples:
- Sprint planning (you are setting priorities)
- Customer calls (you are doing discovery)
- Design reviews for your product area (you are providing product context)
- 1:1s with your manager and direct reports (relationship and coaching)
For most PMs, this is 8-12 hours per week. If it is more, you are either managing too many initiatives or your team relies on you for decisions that should be delegated.
Bucket 2: Valuable but optional. You benefit from attending but are not essential
These are meetings where you gain context or provide input, but the meeting would proceed fine without you. Examples:
- Engineering standups where you are not actively unblocking anyone
- Cross-team syncs where your area is not on the agenda
- All-hands and town halls
- "FYI" status meetings
For most PMs, this is 6-10 hours per week. This is your biggest opportunity for reclaiming time.
Bucket 3: Low value. The meeting itself is unnecessary
These are meetings that exist because of organizational inertia, not because they produce value. Examples:
- Status meetings that duplicate information available in written updates
- Recurring meetings that have lost their purpose ("we've always had this meeting")
- Meetings with no agenda or clear outcome
- "Brainstorm" sessions with 10+ people (these rarely produce actionable ideas)
For most PMs, this is 4-8 hours per week. All of it should be eliminated.
Bucket 4: Someone else should attend
These are meetings where product input is needed, but it does not need to be you specifically. A designer, engineering lead, or another PM could represent the product perspective.
For most PMs, this is 2-4 hours per week. Delegate all of it.
The Decision Rules
Once you have categorized your meetings, apply these rules:
Rule 1: Every meeting must have an agenda and an expected outcome
If a meeting does not have an agenda shared at least 24 hours in advance, decline it. This is not rude. It is professional. You are signaling that your time has value and that you want to contribute meaningfully.
Send this message when declining: "I'd love to contribute. Could you share an agenda so I can determine if I'm the right person to attend? If so, I'll prepare accordingly."
Most meeting organizers will either add an agenda (improving the meeting for everyone) or admit the meeting does not need you (freeing your time).
Rule 2: If you are not speaking, you should not be attending
Count the number of meetings last week where you did not speak for more than 2 minutes. Those meetings did not need you. You were an audience member, not a participant.
For meetings where you need the information but do not need to participate: request a recording or written summary (tools like Loom make this easy). This takes 5 minutes to review instead of 30-60 minutes to attend.
Rule 3: Recurring meetings need quarterly justification
Every recurring meeting should be reviewed once a quarter. Ask: "If this meeting did not exist, would we create it?" If the answer is no, cancel it.
A surprising number of recurring meetings were created for a specific purpose (launch coordination, incident response, new team onboarding) and continued long after the purpose was served.
Rule 4: Standups are for unblocking, not status
If your daily standup takes more than 15 minutes, it has become a status meeting. Status should be shared async (Slack, Jira updates, Loom videos). The synchronous standup should focus exclusively on blockers and decisions that need the whole team.
If you are not the one unblocking or being unblocked, you can skip the standup and read the async summary.
Rule 5: Batch similar meetings
Context switching between a customer call, a sprint planning session, a 1:1, and a strategy meeting in the span of 4 hours is exhausting. Cal Newport has written extensively about the cost of context switching. Each transition costs 10-15 minutes of mental reorientation.
Batch similar meetings together:
- Customer conversations on Tuesday and Thursday mornings
- Internal alignment (sprint planning, standups, design reviews) on Monday and Wednesday
- Strategic work (roadmap updates, retros, planning) on Friday
This creates blocks of coherent work instead of a fragmented mosaic.
Rule 6: Protect two 2-hour blocks per week
Paul Graham described the tension between maker's schedule and manager's schedule. PMs live in both. Block two 2-hour windows on your calendar as "Focus Time." Treat them as immovable. These blocks are for the work that only you can do: writing product specs, analyzing data, reviewing customer research, thinking about strategy.
If someone tries to book over your focus time, decline and suggest an alternative time. If your organization does not respect focus time blocks, use an out-of-office auto-reply during those windows.
The Audit in Practice: Before and After
Before (a real PM's week)
| Time | Monday | Tuesday | Wednesday | Thursday | Friday |
|---|---|---|---|---|---|
| 9:00 | Standup | Standup | Standup | Standup | Standup |
| 9:30 | Sprint planning | Cross-team sync | Design review | Engineering 1:1 | Retro |
| 10:00 | (continued) | Status meeting | (continued) | Marketing sync | (continued) |
| 10:30 | Stakeholder call | Product team sync | Analytics review | Customer call | All-hands |
| 11:00 | (continued) | (continued) | Focus time | (continued) | (continued) |
| 11:30 | Sales enablement | Customer call | (continued) | QA review | Focus time |
| 1:00 | Manager 1:1 | Roadmap review | Sprint grooming | Partner meeting | Planning |
| 1:30 | (continued) | (continued) | (continued) | (continued) | (continued) |
| 2:00 | Engineering sync | UX review | Customer call | Strategy meeting | Customer call |
| 2:30 | (continued) | (continued) | (continued) | (continued) | (continued) |
| 3:00 | Backlog grooming | Sales call | Team meeting | Product review | Demo prep |
Total meetings: ~30 hours. Focus time: ~3 hours.
After applying the audit
| Change | Hours saved |
|---|---|
| Cancel daily standup attendance (read async summary instead, attend Mon/Wed only) | 1.5 hrs |
| Cancel status meeting (replaced with async Slack update) | 1 hr |
| Decline cross-team sync (not relevant this quarter, read notes) | 1 hr |
| Delegate sales enablement to product marketing | 1 hr |
| Cancel QA review (engineer handles directly, flags issues async) | 0.5 hrs |
| Merge analytics review into design review | 0.5 hrs |
| Skip all-hands (watch recording at 2x speed) | 1 hr |
| Decline marketing sync (attend bi-weekly instead of weekly) | 0.5 hrs |
| Decline partner meeting (not relevant to current priorities) | 1 hr |
| Cancel demo prep (engineers demo directly, PM provides context async) | 0.5 hrs |
| Move backlog grooming from weekly to bi-weekly | 0.5 hrs |
Total saved: ~9 hours per week.
The resulting calendar has 21 hours of meetings and 19 hours of focus time. Not perfect, but a significant improvement. Those 9 hours go to customer discovery, spec writing, data analysis, and strategic thinking. The work that actually moves the product forward.
How Do You Sustain a Lean Calendar?
Monthly calendar review
On the first Monday of each month, spend 15 minutes reviewing your calendar for the previous month. Count meeting hours vs. focus hours. If the ratio is trending in the wrong direction, apply the audit again.
The "hell yes or no" rule
When a new meeting invite arrives, ask: "Is this a hell yes?" If it is not, decline or propose an async alternative. The default should be declining, not accepting. Most PMs operate with the opposite default, which is how calendars fill up.
Teach your team
If you are a PM lead or manager, teach this audit to your team. PM burnout is almost always correlated with meeting overload. A team that protects focus time ships better products, has better morale, and retains talent longer. For specific formats and facilitation techniques, see the guide on running effective product meetings.
Your calendar is a reflection of your priorities. If it is full of meetings, your priority is meetings. If that is not what you intend, audit it. Reclaim the time. Use it for the work that only you can do.