The week that tells you whether you have a product job

The first time I declared a meeting moratorium, I didn't ask permission. I told my team I'd be off the calendar for a week, declined every existing invite, and went heads-down. Nobody pushed back. A few people said they wished they could do the same.

They could have. Nothing was stopping them. They just didn't.

You've probably seen the version of this I've been seeing for years: product people in meetings five, six, seven hours a day, then "catching up" on the actual work at night or on the weekend. The roadmap drifts. Judgment dulls. Teams ship the wrong things because their PM hasn't had an unbroken hour to think this week, or last week, or the week before. And we call it normal.

A bit of context, since I've been thinking about it: the average executive now spends 23 hours a week in meetings, up from 10 in the 1960s. For a lot of product managers I talk to, 23 sounds optimistic.

If your job is to think — synthesize what customers are saying, weigh tradeoffs, decide what not to build, and write down a story your team can act on — and you do not have time to think, you do not have a product job. You have an attendance job wearing a product job's clothes.

Most "burnout in PM" essays head straight for systems and culture. Both matter. But there's a smaller move that has to happen first, and it has to come from you.

You have to know what you need to be successful.

You'd think that would be obvious. It isn't. A lot of people I know have never had the experience. They started a job and on day one their calendar was already full, with meetings scheduled before they turned the laptop on. Then the next job. Then the next. They've never had a stretch of uninterrupted thinking long enough to find out what they're capable of when their attention isn't being shredded into 30-minute pieces.

If that's you, here's the experiment. Take a week. Block the entire calendar. Decline every single meeting. Tell your team and your stakeholders in advance, professionally and clearly: "I'm taking next week heads-down on [X]. I won't be in meetings. Here's how to reach me if something is genuinely on fire." Then do it.

One of two things will happen.

The first: you'll have the most productive week you've had in a year. Strategy memos that have been half-finished for months will get finished. The decision you've been ducking will get made. You'll feel something most product people haven't felt since their first job: traction. If that's how it goes, congratulations. You now have evidence of what your professional life can be when you protect it. Use that as your floor.

The second: you'll find yourself adrift. The meetings are gone, and there's nothing else for you to do. No deep work waiting. No artifact only you can produce. No problem only you can solve. If that's what happens, the meetings weren't the problem. They were concealing the problem. Time for an honest look at the role, your skills, and whether the job you have is the job you want.

Either outcome is useful. The only bad outcome is not running the experiment.

You already know how to do this, by the way. You do it every quarter for your product. Define what success looks like, scope what fits inside the constraint, decline what doesn't fit, make the case to stakeholders for why. That is the skill. Setting your own boundaries is the same move, applied to your calendar instead of your roadmap. You're not learning a new discipline. You're applying one you already use, in a place you haven't used it yet.

A meeting moratorium isn't a permanent posture. Most weeks I'm in a normal-ish number of meetings, and most of them are useful. But the bar I hold them to — clear purpose, a real decision being made, the right people in the room, something that's true after the meeting that wasn't true before — exists because I learned what the alternative cost me. I had to taste deep work before I could defend it.

Your calendar isn't full because of other people. Your calendar is full because you accepted the invites. The system is happy to keep filling it. The only thing that changes the pattern is you deciding what you need, and then defending it like a professional.

That's part of what it means to be a product leader, whether you're a PM, a designer, an engineer, or a founder. Other people aren't going to design your professional life for you. You're the only person in the room who knows what the work actually requires.

Take the week. See what you get done. If it goes well, tell me about it.

— Matthew

P.S. This was prompted by Matthew Hall's piece on why PM burnout is structural, which is worth your time. He's right that the role as currently designed is the deeper problem. The week-long experiment above is what I think you can do now, regardless of whether your org ever redesigns it.