Disclaimer: This post reflects what I’ve learned after roughly seven years in Product Management. Spanning volunteering, internships, and full-time roles. My views will likely evolve as I break more things and learn how to fix them better.
Have you ever looked at your calendar for the upcoming week and felt a genuine sense of despair?
It’s a common experience for me as a Product Manager. I start the week with a clear goal, but by Monday morning, your schedule is a solid wall of blue boxes. Realizing that 80% of my work hours were being swallowed by meetings.
PMs are “glues.” We sit at the intersection of business, technology, and user experience. This creates immense ambiguity and a tendency to get stretched thin. To survive, I had to stop just “working” and start following a specific framework for managing my time, attention, and sanity.
My Core Framework
At its core, a PM has two jobs:
- Solve for the User: Fixing pain points and “jobs to be done.”
- Solve for the Business: Creating products people actually want to pay for.
To balance these, I divide my day into two distinct phases: Defense (being reactive) and Offense (being proactive).
Phase 1: Start of the Day (Reactive Defense)
A Product Manager is a catalyst. Our job is to enable everyone else to do theirs. Because of this, the first few hours of my day are dedicated to “playing defense.”
1. Putting out fires: Before I check my to-do list, I check for emergencies. Is the production environment down? Is there an angry customer ticket that’s escalating? If there is a fire, my priority is to be the firefighter so the rest of the team can stay focused on building.
2. Clearing the path for Development: My developers are my most important “users” in the morning. I look for anything blocking them. This usually happens during the Daily Standup. My goal is to answer the question: “What can I do right now so they don’t have to stop working later today?”
3. Removing bottlenecks: I check if I am the one holding things up. Does Marketing need a final copy review? Does a Business Owner need a sign-off on a PRD shift? If I’m a bottleneck, the team stalls. I clear my “Review” queue before doing anything else.
Phase 2: When Things Settle (Proactive Offense)
Once the fires are out and the team is unblocked, I switch gears. This is where the actual “Product Management” happens, the forward-looking work.
4. Checking the Metrics I don’t look at every dashboard. I pick a few key metrics and frame them as questions:
- Is the adoption of the new search filter actually increasing, or are users ignoring it?
- Why did the transaction success rate dip at 3 PM yesterday? Asking questions makes the data actionable instead of just overwhelming.
5. Intentional Stakeholder Management I treat recurring meetings as a strategic alignment. Whether it’s weekly core team syncs or monthly product release updates, these are the channels where I advocate for the product vision. I also stay open to ad-hoc meetings with partners or analysts. These are the “sidequests” that often provide the best insights.
6. Focus Time for Strategic Thinking I try to block off “Deep Work” time on my calendar. This is solitary work: diving into competitor strategy, reviewing meeting notes, and mapping out the next phase of the roadmap. Without this, I’m just a project coordinator, not a product manager.
The Bottom Line
Product management is a balancing act between tactical firefighting and strategic forestbuilding. You have to be comfortable playing defense for half the day so that you’ve earned the right to play offense for the other half.
The goal isn’t to have an empty calendar; it’s to ensure the time you do spend moves the product toward the company’s vision.