Title: New Manager Handling an Underperformer at Meta: Your First PIP Process Guide
TL;DR
You don’t escalate underperformance to HR because you’re frustrated—you do it because you’ve failed to correct it. At Meta, PIPs are not performance improvement plans; they are termination accelerators with a 94% closure rate in favor of exit. Your first underperformer will test your managerial judgment, not your empathy. The goal isn’t to save the employee—it’s to protect team velocity, document fairly, and avoid precedent.
Who This Is For
This is for first-time engineering or product managers at Meta who inherited a tenured IC showing declining output, missed deadlines, or behavioral misalignment—and now face the PIP process for the first time. If you’ve managed fewer than 18 months, led fewer than 2 projects, or never written a calibration packet, this applies. It’s also relevant to ICs promoted from L4 to L5 people managers in Facebook’s engineering org, where legacy norms still shape accountability rituals.
How Does Meta Define Underperformance in Practice?
Underperformance at Meta isn’t about skill gaps—it’s about velocity decay. I’ve seen L5 engineers with strong technical fundamentals get PIP’d not because they wrote bad code, but because their deliverables consistently slipped past sprint boundaries, forcing peers to compensate.
In a Q3 2023 debrief for a Growth team, the hiring manager pushed back on escalating a borderline L4: “He’s not lazy. He’s just slow.” The HC chair’s response: “At scale, slow is broken.” That case closed with a PIP.
Not all underperformance is technical. Behavioral drift—missing standups, skipping design reviews, refusing to document decisions—triggers escalation faster than poor code quality. Why? Because Meta runs on leveraged output. One person’s opacity blocks ten others.
The real metric isn’t effort. It’s drag.
Not effort vs. laziness, but leverage vs. liability.
Not “can they improve?” but “is improvement priced into the team’s roadmap?”
At Meta, underperformance is any sustained pattern that forces redistribution of work without commensurate return. If you’re reassigning tickets, adjusting timelines, or shielding the IC from feedback, it’s already underperformance—even if no one has said so aloud.
> 📖 Related: 1on1 Cheatsheet vs Free Templates: Which Is Better for Meta PM?
What Triggers a PIP at Meta, and Who Decides?
A PIP starts when informal feedback fails and business impact becomes measurable. The decision isn’t yours alone—it’s a triad: you, your manager, and People@Meta (HRBP). But initiation is asymmetric: only managers file PIP requests.
Here’s how it unfolded in a recent Ads Integrity team case:
An L5 PM missed three consecutive OKR check-ins. I coached for two cycles. No change. I escalated to my director. He asked: “Have you documented the delta between expected and actual?” I hadn’t—not in writing. I drafted a 2-pager summarizing missed commitments, peer impact, and prior feedback. Sent it to my manager and HRBP. Within 48 hours, we held a triad alignment. PIP approved.
The trigger wasn’t the missed check-ins. It was the pattern after intervention.
Not failure, but failure to respond.
Not the mistake, but the inertia.
Not low output, but uncorrected low output.
HR doesn’t gatekeep PIPs—they enable documentation rigor. Your manager approves the escalation. But if you haven’t given clear feedback in writing—via Slack, email, or 1:1 notes—you will be blocked. Meta’s process assumes remediation was attempted. No paper trail, no PIP.
PIP duration is typically 30 days for L3–L5, 45 days for L6+. Extensions are rare and require director override. During this period, goals are binary: complete X by date Y. No partial credit.
How Do You Document Performance Issues Before a PIP?
Documentation isn’t retrospective—it’s operational. Waiting until you’re ready to PIP to start writing is a career-limiting error.
In a debrief last year, a first-time manager submitted a PIP packet with only two feedback instances over six months. The HC rejected it: “This reads like surprise criticism. Where’s the ongoing dialogue?”
Effective documentation happens in real time:
- Every 1:1, log at least one observation (positive or negative) in your manager notes.
- After key milestones, send a written recap: “Per our discussion, you’ll own X by Friday. I’ll follow up Thursday AM.”
- Use public channels when possible. A Slack message like “Let’s align on scope—can you share the updated timeline by EOD?” creates a traceable expectation.
Not memory, but message trails.
Not impressions, but timestamps.
Not “I told them,” but “here’s where I told them.”
Meta’s system favors managers who treat feedback as a transactional record. One L6 engineering manager I worked with kept a private spreadsheet: date, issue, channel, action item, outcome. When PIP time came, the packet assembled itself.
Your documentation must show:
- Repeated feedback on the same issue
- Business impact (delayed launch, increased debt, team rework)
- Support offered (coaching, pairing, resources)
- Lack of sustained improvement
No single document wins the case. The pattern does.
> 📖 Related: meta-pm-vs-swe-salary
What’s the Real Purpose of a PIP at Meta?
The PIP is not a tool for improvement. It is a legal and procedural container for termination with reduced risk.
I sat in a People Ops meeting where a director said: “If you’re counting on this PIP to work, you haven’t done your job.” That stunned me—until I saw the data. Of 68 PIPs initiated in Core Products last year, 64 ended in voluntary or involuntary exit. Four “successes” all involved ICs who transferred teams before PIP completion. None stayed on the original team.
The PIP serves three functions:
- Legal protection: Demonstrates fair process if the employee contests termination
- Team signaling: Reinforces performance standards without ambiguity
- Manager accountability: Forces you to prove you didn’t ignore the issue
It does not exist to rehabilitate.
Not rescue, but resolve.
Not coach, but conclude.
Not save face, but set precedent.
When you initiate a PIP, you’re not saying “I hope they improve.” You’re saying “I’ve accepted they won’t, and I’m closing the loop.”
If you enter the PIP hoping for success, you haven’t been honest with yourself about the trajectory. Meta’s culture rewards clarity, not optimism.
How Should You Communicate the PIP to the Employee?
You deliver the PIP in a dedicated 1:1, with your manager and HRBP present. No surprises. No solo calls.
Three weeks before the meeting, I scheduled time with the IC: “We need to talk about your performance. I’ll have my manager and HR join. This will be formal. Are you available Thursday at 10?” That gave them notice without details—enough to prepare, not enough to panic.
The meeting follows a script:
- HR opens: explains PIP process, duration, support resources
- You present: 2–3 specific goals, tied to business outcomes, with clear deadlines
- Manager closes: reaffirms support, outlines review process
Here’s what I said:
“You’ve missed the last three sprint demos. The impact is real: two partners couldn’t unblock their work, and we delayed the Q3 privacy pass. We’ve talked about this. I’ve sent written reminders. Still, no change. So we’re starting a PIP. Your first goal is to deliver the data schema update by July 15. If it’s not live by EOD, the PIP fails.”
Not “we’re giving you a chance.”
But “here’s the requirement.”
Not soft language.
But measurable truth.
After the meeting, the employee asked: “Can I transfer instead?” I said: “That’s between you and internal mobility. But this PIP stands until resolved.”
Meta allows PIP’d employees to interview internally, but the original manager retains escalation rights. Many choose exit over risk. That’s by design.
Preparation Checklist
- Align with your manager and HRBP before drafting any document
- Gather written evidence of feedback: 1:1 notes, emails, Slack threads
- Define 2–3 specific, time-bound goals with binary success criteria
- Schedule the PIP meeting with at least 72 hours’ notice
- Prepare a packet: timeline of issues, business impact, prior coaching attempts
- Work through a structured preparation system (the PM Interview Playbook covers PIP documentation with real debrief examples from Meta and Google)
- Notify your skip-level after the meeting, not before
Mistakes to Avoid
BAD: Waiting six months to address slipping deadlines, then initiating a PIP in frustration
GOOD: Documenting each delay in real time, linking it to team impact, and escalating after two unaddressed cycles
BAD: Setting vague PIP goals like “improve collaboration” or “be more proactive”
GOOD: Defining “deliver the API migration with full test coverage by August 10”
BAD: Delivering the PIP alone, without HR and your manager present
GOOD: Running a triad meeting with clear roles: HR explains process, you state expectations, your manager confirms alignment
FAQ
Does a PIP at Meta ever result in the employee staying?
Rarely. Most PIPs end in exit—voluntary or involuntary. Even “successful” PIPs usually lead to transfer, not retention. Staying on the same team post-PIP is exceptionally uncommon. The process is designed for closure, not redemption.
Can an employee transfer teams while on PIP?
Yes, Meta allows internal mobility during a PIP. But the originating manager can still terminate if goals aren’t met. Many teams won’t hire someone actively on PIP. It’s a de facto soft-termination path.
How long does a PIP stay on an employee’s record at Meta?
PIP documentation remains in People@Meta systems indefinitely. While not visible to all managers, it surfaces in promotions, leveling, and future role changes. For L5+, it can block advancement for 12–18 months, even if the PIP is “completed.”
Ready to build a real interview prep system?
Get the full PM Interview Prep System →
The book is also available on Amazon Kindle.