Backfill, redistribute, or pause: covering a PM's parental leave

Someone on your product team announces they're expecting. You're pleased for them, and about ninety seconds later a second thought arrives: what happens to the roadmap in Q2?

You have three options. Most teams take the third one without ever putting the first two on the table, which is a shame, because the choice is genuinely situational and the default is not always wrong. It's just rarely chosen.

Option one: pause the work

Stop the initiatives the PM owns. Let engineering pick up technical debt, infrastructure, or a platform investment that's been waiting for a quiet quarter. Restart in the fall.

This gets dismissed too fast. If your product manager owns one initiative, that initiative is genuinely deferrable, and you have a real backlog of engineering-led work that would benefit from a clear runway, pausing is the cheapest and most honest answer. Nobody is pretending. Nothing degrades quietly.

It stops working the moment the deferred initiative has a date attached to it — a customer commitment, a contract renewal, a compliance deadline. It also fails when the pause is nominal rather than real: the work officially stops, but stakeholders keep asking about it and someone starts answering. That's not a pause. That's option three with worse bookkeeping.

Option two: redistribute internally

Split the work across the team. The engineering lead takes prioritization, a director takes the stakeholder relationships, a designer picks up the discovery threads, and everyone agrees it's temporary.

Redistribution works when the quarter is already scoped and the team is executing a known plan. If the decisions were made in January and the job through June is shipping them, a strong team can carry that without a product manager in the seat. This is more common than the leave-coverage industry likes to admit.

It fails when the role carries live decisions. If your PM is the person who says no to the sales team, decides what engineering builds next, and holds the reasoning behind six months of tradeoffs, that doesn't distribute. It fragments. Three people each hold a piece of the context and nobody holds the whole thing, so the decisions still get made — just inconsistently, and by people whose actual job is something else.

The other cost is the one nobody puts in a spreadsheet: your engineering lead is now doing two jobs. For three weeks that's a favor. For four months it's a retention risk on top of the one you already have.

Option three: bring in coverage

Someone external owns the role for the duration. Which in practice splits again, because "bring in coverage" can mean two quite different things.

Hiring a temporary employee means a requisition, a search, interviews, an offer, and onboarding. Realistically six to ten weeks from decision to start date, plus four to six weeks of ramp. If the leave starts in twelve weeks you are already behind, and you're running a hiring process for a role that ends in four months — which is a hard sell to good candidates and tends to select for people between jobs rather than people who chose this.

Engaging a fractional or interim PM skips most of that. No requisition, no search, and someone whose entire professional practice is arriving quickly into unfamiliar teams. Two to three weeks to start, two weeks to useful.

Putting numbers on it

Rough shape for a senior PM going out for sixteen weeks. Your figures will differ, but the relative sizes tend to hold:

The number that changes the math isn't on that table. Roughly a third of women leave their roles within eighteen months of returning from parental leave, and the research consistently points at what they came back to rather than a change in what they want. Replacing a senior product manager — recruiting, lost productivity, ramp for the successor — comfortably exceeds a year of coverage. If the way you handle the leave affects whether they stay, that's the largest line item in the analysis and it never appears in the budget conversation.

How to actually decide

Four questions, in order:

• Does the work carry live decisions, or is it executing a settled plan? Settled plans redistribute. Live decisions don't.
• Is there a date on anything? A customer commitment or compliance deadline rules out pausing, whatever else is true.
• Who absorbs it if you redistribute — and are they already at capacity? If the honest answer is your engineering lead and they're already stretched, you're choosing between two retention risks rather than avoiding one.
• How much notice do you have? Under six weeks, a hiring process isn't available to you regardless of what you'd prefer.

Run those and the answer usually declares itself. Sometimes it's redistribution, and that's a fine outcome — reached deliberately rather than by drift.

Whatever you choose, decide it early

The worst version of this isn't picking the wrong option. It's picking none, letting the leave start, and discovering in week three that the work is quietly landing on whoever was closest to it. By then you have no handoff, no plan, and a team improvising a role that used to have an owner.

Your PM told you months in advance. That's the rare product transition you can actually plan for. Use it.

If coverage looks like the right call, here's how a leave coverage engagement is structured — and if you're weighing the models more generally, fractional versus contract covers that ground.

If you're the one heading out on leave rather than the one deciding, this covers how to raise it with your manager.