There was a season a few years back where I was checking Slack before my feet hit the floor in the morning. Responding to emails during dinner. Thinking about roadmap priorities during my daughter’s volleyball game.
I wasn’t working more hours than anyone else on my team. I was just never NOT working.
Product management does this to people. (HBR’s research on burnout confirms it’s systemic, not individual.) You own the outcome but you don’t own the resources. You’re the one the CEO asks when numbers are off, the one engineering pings when priorities conflict, the one the customer success team escalates to when a big account is unhappy. The role is designed to pull you in every direction at once.
I was hired to replace the previous PM who burned out. He had replaced a PM who had burned out. Now, I was burning out. Not dramatically. I didn’t quit or have a breakdown. It was the slow kind, where you stop being excited about the work and start just surviving it. Where your family gets the leftover version of you and even that feels like it’s running on fumes.
Here’s what I’ve changed since then. I’m not going to pretend I’ve got it all figured out, but I’m in a fundamentally better place than I was, and most of it came from a few non-negotiable decisions.
Protect Your Time Like It’s a Product Requirement
I have a hard rule: home by 5:30 for dinner. No exceptions. Not for a board prep. Not for a product review. Not for a “quick sync” that will definitely run long.
I also block a 90-minute gym window in the middle of my day and an hour for reading first thing in the morning. These aren’t nice-to-haves. They’re on my calendar as immovable blocks, the same way a meeting with the CEO would be.
When I first started doing this, I felt guilty. Like I was being less committed than my peers. What I actually found is that the constraints made me sharper.
When you know you have to be done by 5:30, you stop saying yes to the third “alignment meeting” of the day. You get ruthless about prioritization because you have to be. The artificial scarcity forced better decisions about where my time went.
Automate Everything You Touch Twice
My theme for this year is automate as much as possible. Every hour I spend on repetitive work is an hour I’m not spending on the high-leverage thinking that actually moves the business forward.
Status reports, data pulls, recurring communications, task routing, inbox triage: if I do it more than twice, I build a system for it.
Some of these are sophisticated (automated morning briefings that synthesize email, calendar, and tasks into a single digest). Some are dead simple (a Slack reminder template so I don’t have to think about weekly check-ins).
The compounding effect is real. Each small automation frees up 15-30 minutes. Stack enough of them and you’ve recovered entire blocks of deep work time that used to disappear into operational overhead.
Your Team Is Your Leverage
The biggest burnout trap for PMs is thinking you need to be involved in everything. You don’t. You need to be clear about what matters, set the direction, and then trust your team to execute.
I used to review every analytics pull. Now my analytics lead knows what I care about and surfaces the insights, not the data.
I used to write every A/B test hypothesis. Now my growth marketer proposes them and I weigh in on priorities.
I used to attend every customer call. Now my PM partner handles the S4K side entirely and we sync weekly.
Delegation is about building capability on your team so that your time is spent on the decisions only you can make. If you’re the bottleneck for everything, that’s a sign of a system that’s one illness away from breaking.
Make Peace with “Good Enough”
Perfectionism will eat you alive in product management. There’s always one more edge case to account for, one more stakeholder to consult, one more data point to gather before making a decision.
I’ve learned to ask: “Is this decision reversible?” If yes, make it fast and move on. You can adjust later. If no, take the time you need.
But most decisions in product are reversible, and treating every one like it’s permanent is a fast track to analysis paralysis and the chronic stress that comes with it.
Shipping at 80% with the ability to iterate beats shipping at 100% three months late. And honestly, your users can’t tell the difference most of the time.
Faith and Purpose as Anchors
This one’s personal, so take it for what it’s worth. For me, faith is the thing that keeps work in perspective. I care deeply about what I do (I’m building products that help the church grow, and that mission matters to me). BUT it’s not the entirety of who I am.
When I remember that, it’s easier to close the laptop. It’s easier to be present at dinner. It’s easier to let go of the meeting that didn’t go well, the metric that’s off target, the feature that shipped with a bug.
Whatever your version of that anchor is (faith, family, community, a creative pursuit), guard it. Don’t let the urgency of product work crowd out the things that actually sustain you.
The Bottom Line
Burnout in product management comes from working without boundaries, without leverage, and without recovery.
Set the boundaries. Build the leverage through automation and delegation. Protect the time that restores you.
Your value is measured by the clarity of your decisions and the impact of what you ship. The version of me that protects his time, trusts his team, and goes to the gym at 11am is a better PM, a better leader, and a better husband and father than the one who was grinding 14 hours a day and calling it dedication.