New Manager at Meta: Handling Underperformer Feedback Script

How should a new manager at Meta frame feedback to an underperformer?

The correct framing is a data‑driven, future‑focused conversation that separates the employee’s behavior from their identity. In a Q3 debrief, the senior PM challenged my opening line because it sounded like a personality attack. I pivoted to “I’ve noticed three specific output gaps in the last sprint; let’s discuss how we can close them together.” The problem isn’t the employee’s lack of effort — it’s the manager’s failure to anchor feedback in observable metrics.
The first counter‑intuitive truth is that empathy does not equal softness. Meta’s leadership expects you to be ruthless with the data while remaining supportive in tone. Use the “Signal vs. Noise” framework: isolate the signal (the metric that truly matters, such as 5% drop in click‑through rate) and discard noise (personal work style). State the signal first, then ask the employee to co‑design a remediation plan.
Script excerpt:

Manager: “In sprint 12 you delivered 7 % fewer ad impressions than the target of 1.2 M. That 84‑k shortfall is the signal we need to address.”
Employee: “I see. What contributed to the gap?”
Manager: “The data shows two missed optimization flags. Let’s prioritize fixing them this week and reconvene on Friday.”
The script forces the conversation to stay on concrete outcomes rather than vague feelings. It also signals to senior leaders that you are capable of “driving performance at scale.”

What signals do senior leaders look for in a feedback conversation?

Senior leaders look for three signals: (1) the manager’s ability to articulate a measurable performance delta, (2) the employee’s acceptance of ownership, and (3) a clear timeline for improvement. In a recent HC meeting, the director asked, “Did you give them a 30‑day improvement window?” When I answered “We will monitor weekly,” the director pushed back. The signal isn’t the frequency of check‑ins — it’s the existence of a documented Performance Improvement Plan (PIP) with a 30‑day horizon.
The second counter‑intuitive insight is that “frequency does not equal rigor.” A manager who schedules daily stand‑ups without a formal PIP appears indecisive. Conversely, a manager who sets a 30‑day deadline, outlines two measurable milestones, and then follows up at the 10‑day and 20‑day marks demonstrates execution discipline.
Script excerpt for the PIP kickoff:

Manager: “You have until Nov 15 to raise your weekly active users metric from 1.8 M to 2.1 M. We will measure at the end of each week. If you meet the 10‑day checkpoint, we will celebrate the win; if not, we will adjust the scope.”
The senior leader’s mental model is “clear delta, clear deadline, clear consequence.” Failure to embed any of those three triggers a perception of managerial weakness, which can jeopardize your promotion track.

When is the right time to involve HR in a performance issue at Meta?

Involve HR the moment you draft the first formal PIP, not after the employee has repeatedly missed informal check‑ins. The mistake most new managers make is waiting until the third missed deadline to bring HR in, which creates a perception that the manager tried to “handle it alone.” In a Q1 debrief, the VP told me, “If you wait three weeks, you’ve already handed the employee a narrative of neglect.” The correct timing is at the moment you lock in the 30‑day plan and document the expected outcomes.
The third counter‑intuitive truth is that “early HR involvement is a signal of procedural rigor, not of conflict escalation.” HR’s role at Meta is to ensure the process is compliant with internal policy and to provide a neutral witness. By looping HR in at the PIP creation stage, you protect both the employee and yourself from later disputes.
Script for the HR hand‑off email:

Subject: “Performance Improvement Plan – [Employee Name] – Effective Oct 1”
Body: “I am initiating a 30‑day PIP for [Employee] to address a 5 % shortfall in ad‑impression delivery. The plan includes two weekly milestones. I have attached the draft for HR review and sign‑off. Please confirm receipt and let me know if any compliance adjustments are needed.”
The moment you send this email, you have a timestamped record of the process, which senior leadership will cite if the case ever escalates.

How can a new manager document the feedback process to protect against future disputes?

Document every feedback touchpoint in a shared, time‑stamped Google Doc that is visible to both the employee and HR. In a recent HC review, the hiring manager complained that “the notes were buried in an email thread,” which meant the manager could not prove the conversation happened. The problem isn’t the employee’s denial — it’s the manager’s lack of a durable audit trail.
The fourth counter‑intuitive insight is that “over‑documentation does not erode trust; it builds credibility.” Each entry should contain: (a) the date, (b) the metric discussed, (c) the agreed‑upon action, and (d) the next review date. Use the “Performance Funnel” template: top‑line metric, root‑cause hypothesis, experiment, result.
Example entry:

Date: Oct 3 2024
Metric: Weekly active users = 1.78 M (target = 2.10 M)
Action: Run A/B test on ad‑slot allocation; deliver two experiments by Oct 10.
Next Review: Oct 12 2024
By sharing this doc with HR and the employee, you create a transparent record that senior leaders can audit. If the employee later disputes the feedback, the doc provides an immutable timeline.

Preparation Checklist

Review the latest Meta Performance Management Playbook; focus on the “Data‑First Feedback Loop” chapter.
Pull the employee’s last three sprint metrics; calculate the exact delta in ad‑impression volume.
Draft a 30‑day PIP template with two measurable milestones; align dates with the next sprint calendar.
Schedule a 60‑minute one‑on‑one in Outlook; add HR as a CC to the meeting invite.
Work through a structured preparation system (the PM Interview Playbook covers “Signal vs. Noise” with real debrief examples, so you can rehearse the script).
Create a shared Google Doc titled “[Employee] Performance Plan Oct 2024”; pre‑populate the first entry with today’s date.
Prepare three concise “ownership” questions to ask the employee (e.g., “Which two levers will you adjust to hit the 2.1 M target?”).

Mistakes to Avoid

BAD: “I think you’re not pulling your weight.” GOOD: “Your delivery this sprint was 84 k below target; let’s identify two concrete actions to close the gap.” The former attacks identity; the latter isolates behavior.
BAD: “We’ll talk about this next week.” GOOD: “We will meet on Oct 12 to review the A/B test results and decide next steps.” The former leaves the timeline ambiguous; the latter creates a hard deadline that senior leaders can verify.
BAD: “I’ll handle this on my own and update you later.” GOOD: “I’ve copied HR on this email to ensure the process is compliant; I’ll send you the updated PIP by end of day.” The former signals avoidance of procedure; the latter demonstrates procedural rigor.

FAQ

What if the employee disputes the performance numbers?
The judgment is to fall back on the shared Google Doc and the sprint dashboards; those are immutable sources. If the employee claims a data error, you reference the Meta Analytics Dashboard (snapshot taken on Oct 2 2024) and invite a neutral data engineer to validate.

How long should the follow‑up meetings be after the PIP is issued?
Each follow‑up should be 30 minutes, scheduled at the 10‑day and 20‑day marks. The 30‑minute slot forces focus on the two milestones and leaves room for rapid decision‑making.

When can I move from a PIP to a termination at Meta?
If the employee fails to meet both milestones by the 30‑day deadline and the documented review shows no improvement, you present the case to the senior director and HR. The termination decision must be made within five business days after the final review meeting.amazon.com/dp/B0GWWJQ2S3).