how pms should actually spend their time

Every PM I have trained — every single one — has the same complaint in their first month on the job. “I am in meetings all day and I have no time to think.”

They say it like it is an accident. Like the calendar attacked them while they were sleeping. It is not an accident. It is the default. The default state of a PM’s calendar is 80% meetings, 15% Slack, and 5% actual product work. And unless you fight that default every single week, you will spend your entire career as a meeting coordinator who occasionally writes a PRD.

This is not a time management problem. It is a career problem. The work you spend your time on determines whether you get promoted or plateaued. And the tragedy is that most PMs are doing the wrong work and calling it productivity.

The LNO Framework: not all work counts equally

Shreyas Doshi, former PM at Stripe and Twitter, created the LNO framework. It is the single most useful mental model I have found for PM time allocation. I teach it in every Pragmatic Leaders cohort and the reaction is always the same — people stare at their calendars in horror.

LNO stands for three categories:

Leverage work. This is work where the quality of your output matters disproportionately. A well-written strategy doc that aligns the team for six months. A customer interview that reframes the problem entirely. A prioritisation decision that kills three features and focuses the team on the one that matters. If you do Leverage work at 80% quality versus 100% quality, the difference in outcome is massive.

Neutral work. This is work that must be done competently but where extra effort yields diminishing returns. Sprint planning. Status updates to stakeholders. Reviewing QA results. Writing release notes. If you do Neutral work at 80% versus 100%, the outcome difference is marginal. Good enough is good enough.

Overhead work. This is work that adds near-zero product value but consumes time. Sitting in a meeting where you are CC’d “for visibility.” Formatting a slide deck that nobody will reread. Responding to a Slack thread that would resolve itself in two hours. Attending a “sync” that has no agenda and no decisions. If you do Overhead work at 0% versus 100%, the outcome difference is negligible.

Here is the problem: most PMs spend about 20% of their time on Leverage work, 20% on Neutral, and 60% on Overhead. Then they wonder why they are not making an impact.

The fix is not “work harder.” The fix is to ruthlessly reclassify your work and change the ratio.

How to classify your work

Take your calendar from last week. Every meeting, every block, every task. Classify each one:

It is Leverage if: the output directly shapes product direction, user experience, or team alignment. Strategy documents. Customer discovery. Pricing decisions. Hiring interviews. The PRD for your highest-priority feature. Coaching a junior PM whose growth you are responsible for.

It is Neutral if: it must happen for the team to function, but your specific contribution does not change the outcome dramatically. Sprint planning (assuming you prepared beforehand). Stakeholder updates where you are reporting known information. Bug triage. Routine backlog grooming.

It is Overhead if: removing it would not change any product outcome. Status meetings with no decisions. “Visibility” meetings where you sit and listen. Formatting slides. Responding to Slack questions that someone else on the team could answer. Attending a cross-functional meeting that your engineering lead is also attending.

The honest ratio for most PMs is shocking. The target ratio? At least 40% Leverage, 30% Neutral, 30% Overhead. You will never eliminate Overhead entirely. But you can cut it in half.

The maker vs manager problem

Paul Graham wrote about this in 2009. Managers operate on one-hour blocks. Their day is a sequence of meetings. Makers — programmers, designers, writers — operate on half-day blocks. One meeting in the middle of a maker’s afternoon destroys the whole afternoon.

PMs are both. You are a manager when you run standups, align stakeholders, and unblock engineers. You are a maker when you write a strategy document, analyse user research, or design an experiment. And most PM calendars are optimised entirely for the manager side.

The result: you never get a three-hour block to think deeply about the product. Your strategy work happens in 25-minute gaps between meetings. Your PRDs are written at 9pm because the day was wall-to-wall calls. Your customer interviews are squeezed into lunch breaks.

This is not a personal discipline failure. It is a structural failure. Your calendar is not designed for the work you need to do.

Calendar architecture

The solution is to design your calendar instead of letting it happen to you.

Protect mornings for maker work. Block 9am to 12pm, three days a week, as “no meetings.” Not “tentative” — declined. If someone books over it, decline. If your manager books over it, have a conversation about why you need maker time. Every senior PM I know who produces high-quality strategy work protects their mornings.

Batch meetings into afternoons. Stack your syncs, 1:1s, and stakeholder updates into two or three afternoon blocks. A day with six meetings spread across 8 hours is a wasted day. A day with six meetings packed into 3 hours gives you 5 hours of real work.

Create a “no meeting” day. Wednesday or Thursday works best. This is the day you write. You do deep analysis. You prepare for the sprint. You think about the product instead of talking about the product. Guard this day with your career.

Audit weekly. Every Friday, spend 10 minutes looking at next week’s calendar. For every meeting, ask: “What decision will this meeting make? Do I need to be in the room for that decision?” If neither answer is clear, decline or send a delegate.

India-specific: the meeting culture problem

I need to talk about this directly because it affects every PM working in India and nobody writes about it.

The over-meeting default. Indian tech companies — especially post-Series B — develop a meeting addiction. Every decision requires a meeting. Every meeting requires a follow-up meeting. Every follow-up meeting requires a “quick sync” to discuss the follow-up. I have seen PMs at Indian startups with 35+ meetings a week. That is not product management. That is professional meeting attendance.

The “sir” culture status meeting. In many Indian companies, there are recurring meetings that exist purely because a senior leader wants to “stay in the loop.” Nobody makes decisions in these meetings. Nobody challenges what is presented. The PM presents a status update, the leader nods, and everyone leaves. These meetings are 100% Overhead. The information could be a two-paragraph email. But the meeting persists because declining a meeting with a VP feels culturally inappropriate.

Here is what I tell PMs in my cohorts: respecting hierarchy does not mean donating your calendar. Send a written update before the meeting. Propose a fortnightly cadence instead of weekly. Suggest an async format. Most senior leaders, when given the choice between reading a crisp one-page update and sitting in a 30-minute meeting, will choose the update. They are in too many meetings too.

WhatsApp as a constant interrupt. This is uniquely Indian. In the US, Slack is the work messenger and it has presence indicators, do-not-disturb, and channel-based organisation. In India, product decisions happen in WhatsApp groups — sometimes the same group that has Good Morning messages from the sales team. WhatsApp has no threading, no search worth using, and no concept of async. Every message is urgent because every message pings your phone.

The fix: move product decisions out of WhatsApp and into a tool with threading. Slack, Teams, even a shared Notion doc. Keep WhatsApp for logistics only — “running 5 minutes late” or “the demo room is booked.” If your team insists on WhatsApp, mute the group and check it twice a day at fixed times.

How time allocation changes with career stage

The LNO ratio should shift as you grow. The mistake most PMs make is keeping the same time allocation at every level.

APM / Junior PM (0-2 years). Your Leverage work is execution quality. Writing clear tickets. Running a tight sprint. Shipping on time. Your ratio should be roughly 30% Leverage (excellent execution), 40% Neutral (learning the rituals), 30% Overhead (you will attend meetings you do not need to be in — this is normal while you learn which ones matter). The single most important thing at this stage: get fast at Neutral work so you free up hours for Leverage work. A PM who takes 3 hours to write a sprint recap is losing time they could spend on user research.

PM / Senior PM (3-5 years). Your Leverage work shifts to strategy and discovery. Customer interviews. Competitive analysis. Defining the roadmap. Coaching junior PMs. Your ratio target: 40% Leverage, 30% Neutral, 30% Overhead. At this level, you should be declining meetings aggressively. You should have a protected calendar. If you are still attending every standup and every stakeholder sync in person, you are operating like a junior PM with a senior PM title.

Group PM / Director (5+ years). Your Leverage work is people and portfolio. Hiring the right PM. Coaching them to be autonomous. Making the three or four decisions per quarter that shape the product portfolio. Your ratio target: 50% Leverage, 20% Neutral, 30% Overhead. Overhead stays high because organisational work (budgets, exec reviews, cross-team alignment) comes with the role. But your Leverage work should be the work only you can do — decisions nobody else in the organisation is positioned to make.

The weekly calendar audit

This is the one habit. Not a framework. Not a system. One habit.

Every Sunday evening or Monday morning, spend 15 minutes with your calendar for the upcoming week. For every meeting:

1. What is the decision or outcome? If there is no clear answer, it is probably Overhead.
2. Do I need to be in the room? If someone else can represent you or if your input is not required for the decision, decline.
3. Can this be async? Status updates, FYI meetings, “alignment syncs” with no agenda — all of these can be a Slack message or a Loom video.
4. Is this Leverage, Neutral, or Overhead? Label it mentally.

Then look at the ratio. If more than 40% of your week is Overhead, start declining. Not all of it — pick the two or three lowest-value meetings and reclaim those hours.

Do this every week for a month. You will recover 5-8 hours per week. That is the difference between a PM who writes a strategy doc that changes the product direction and a PM who “never has time” for strategy work.

Common objections

“I can’t decline meetings with senior people.” You can decline meetings with anyone if you provide the information they need in another format. Send a pre-read. Propose an async update. Offer a 10-minute slot instead of 30. Senior people are not offended by efficiency — they are offended by being uninformed.

“Everything on my calendar is important.” No, it is not. If everything is important, nothing is prioritised. Pick the three things this week that will still matter in six months. Those are important. The rest is Neutral or Overhead.

“My team needs me available.” Available does not mean interruptible. Block maker time, but keep Slack on for urgent issues. Set expectations: “I check messages at 12 and 4. If something is on fire, call me.” Your team will survive three hours without you in a meeting.

“My company culture does not allow this.” Then change the culture, one meeting at a time. Start by protecting one morning a week. Show that your output improves. Other PMs will notice. Culture changes when someone demonstrates that the alternative works.

The compound effect

Here is why this matters beyond weekly productivity.

A PM who reclaims 6 hours per week from Overhead and redirects them to Leverage work gains 300 hours per year. Three hundred hours of strategy, discovery, customer research, and deep thinking that their peers are not doing.

Over two years, that PM has invested 600 extra hours in the work that drives promotions, shapes product direction, and builds a reputation. Their peers have invested those same 600 hours in status meetings and Slack threads.

This is why some PMs progress from IC to Senior in three years and others are still in the same role after five. It is not talent. It is not luck. It is where they spend their hours.

The calendar does not lie. Audit it. Fix it. Audit it again. Every week.

Where to go next

• Understand the full shape of a PM’s day: A Day in the Life
• Build the habits that compound over a career: Deliberate Skill Building
• Make your meetings count when you do attend them: Running Meetings
• Use recovered time for the transition that matters: IC to Senior PM