The right underperformer feedback script at Meta is short, specific, and tied to a next checkpoint. In a calibration room, vague language gets read as weak judgment, not empathy. Not a therapy session, but a performance agreement: state the miss, the impact, the standard, and the date you will review it again.
TL;DR
The right underperformer feedback script at Meta is short, specific, and tied to a next checkpoint. In a calibration room, vague language gets read as weak judgment, not empathy. Not a therapy session, but a performance agreement: state the miss, the impact, the standard, and the date you will review it again.
Who This Is For
This is for the first-time Meta manager who inherited a capable person who is missing deadlines, shipping sloppy work, or creating friction in reviews. It is also for the manager who came through a 5- to 7-round interview process and is now discovering that the hard part is not getting the title, but naming a performance gap cleanly without hiding behind softness.
What should I say in the first underperformer conversation at Meta?
The first conversation should be a reset, not an autopsy. In a Q3 calibration, I watched a manager lose credibility because he opened with "I think there may be some alignment issues," and the room heard avoidance. The managers who land this conversation lead with the facts, the business impact, and the next expectation.
Use a script that sounds like a decision, not a diagnosis. Say what happened, when it happened, and what it broke.
A usable opening is this:
"On the last two reviews, your draft came in after the decision window and the team had to rework the plan. The issue is not effort. The issue is delivery against the team’s timeline. I need the next version by Thursday at 3 p.m., and I will judge it against these three criteria."
That script works because it is observable. It is not abstract. It gives the other person a target.
The problem is not that the conversation is hard. The problem is that most new managers try to make it emotionally comfortable instead of operationally clear. Not a surprise attack, but a reset.
A second move matters. Pause after the facts and let the person respond. Do not fill the silence with extra justification. In these conversations, overexplaining reads like uncertainty. A manager who can sit through 10 seconds of silence usually looks more in control than the one who keeps talking.
If the person pushes back on intent, do not debate motive. Bring the discussion back to output. The conversation is about what the work did, not what they meant.
How direct should I be about performance?
Very direct, but not theatrical. Meta does not reward managers who hide a performance problem under soft phrasing, because soft phrasing creates two versions of the truth: one in your 1:1 and one in calibration. The room will trust the calibration version, not the polite version.
In a manager skip I sat in, the director stopped the discussion and asked, "Is this a can-fix or can't-fix issue?" The manager had spent five minutes describing a late PRD with words like "not fully proactive" and "needs more ownership." Nobody in the room could tell whether the person was underperforming or merely miscalibrated.
That is the organizational psychology point: vagueness feels kinder to the speaker, but it feels less safe to everyone else. People do not relax when the standard is unclear. They get anxious.
Say the gap plainly. If the issue is output, say output. If the issue is judgment, say judgment. If the issue is responsiveness, say responsiveness. Not bluntness, but precision.
A good rule is to make the conversation short enough to repeat back. If your summary takes more than 30 seconds, you probably have too much commentary and not enough signal.
Try this wording:
"This is a performance gap, not a style preference. I need the deliverable to meet the review window, and I need it to meet the bar without last-minute rework."
That phrasing matters. It says the standard is measurable. It also avoids turning the conversation into a personality critique, which is where new managers often go wrong.
The worst mistake is saying, "I just want to make sure you feel supported," and then never stating the actual miss. Support is not the same as clarity. A manager can be kind and still be exact.
What script works when the issue is output, not attitude?
The right script changes when the person can do the work but is not delivering it reliably. That is the most common trap for new managers at Meta. They talk about attitude because attitude is easier to describe than a broken operating habit.
In one cross-functional review, a manager kept saying an engineer "wasn't being proactive." The real problem was simpler: deliverables were arriving after the review slot, the PM was re-baselining twice, and the team was burning time on rework. The fix was not a pep talk. The fix was a deadline, an artifact, and a checkpoint.
Use this structure:
"When X happens, Y breaks. I need Z by a specific time. If that is not realistic, tell me before the deadline, not after."
That is the difference between a vague manager and a credible one. Not a motivation conversation, but a timeline conversation.
If the person is strong but late, do not talk about their potential. Potential is irrelevant when the current work is slipping. The organization cares about present output.
If the person is smart but chaotic, do not call it a communication issue unless communication is the actual blocker. Many managers hide behind generic labels because they sound safer. They are not safer. They are weaker.
A useful line is:
"The problem is not your competence. The problem is that the work is arriving in a state that forces others to absorb your missed timing."
That line separates skill from execution. It also makes the impact visible to the person hearing it.
If the issue is repeated, name the pattern. A single miss can be a mistake. Two missed checkpoints in 30 days is already a signal. By the third conversation, you are no longer discussing isolated incidents; you are discussing a management problem.
How do I document feedback without sounding like I'm building a case?
Documenting feedback is not about prosecution; it is about memory. In a calibration room, the manager with clean notes gets taken seriously because the organization trusts records more than recollections. The manager with a foggy story gets asked for dates, examples, and follow-through.
Write the record the same day. Keep it short. Four lines are enough:
- What happened.
- When it happened.
- What you said the expectation was.
- What the next checkpoint is.
That is it. Anything longer usually turns into self-justification.
A follow-up note should sound like operating context, not a legal brief. Send it after the conversation so there is no ambiguity about the expectation.
Example:
"Today we discussed the missed review deadline on the product spec. The expectation is that the next draft arrives by Thursday at 3 p.m. and includes the approval path, decision criteria, and open risks. We will review it together on Friday."
That kind of note is useful because it is portable. If the issue escalates, your manager and HR do not need interpretation. They need a sequence.
The organizational principle here is simple: memory decays, and calibration rewards consistency. Managers who rely on recollection are usually the ones who get surprised later.
Not a case file, but a shared operating record.
When should I escalate to my manager or HR?
Escalate early when the pattern is real, the person is resistant, or the issue touches policy, conduct, or retaliation risk. A new manager loses authority by waiting until the problem is fully broken. The better move is to keep your manager informed after the first serious feedback conversation, not after the second failed checkpoint.
In practice, that means you do not wait 60 days to tell your manager that the same deliverable slipped twice. You tell them after the first miss if it already affects team output. If the person is defensive but still engaged, you keep managing it. If the person rejects the premise, misses two explicit checkpoints, or blames everyone else, you widen the circle.
HR is not there to make the conversation nicer. HR is there to manage process and risk. If you are dealing with conduct, harassment, retaliation, or a documented policy issue, pull HR in immediately. If it is pure performance and the person is responsive, stay with your manager until the pattern changes or hardens.
The mistake new managers make is waiting for certainty. Certainty comes too late. Escalation is about decision rights, not punishment.
In a manager debrief, the strongest leaders were never the ones who waited for a catastrophic miss. They were the ones who surfaced the issue while there was still time to correct it.
Preparation Checklist
Prepare the conversation like a manager who expects to be challenged, because you will be.
- Write down the exact miss in one sentence. Use dates, deliverables, or decisions. No adjectives.
- Write the business impact in one sentence. If it hurt a launch, a review, or a partner team, name it.
- Decide the next checkpoint before the meeting. Use 7, 14, or 30 days, not "soon."
- Draft your opening and closing line before you walk in. A 90-second script beats improvisation.
- Align with your manager if the issue already affects team output or could become a formal performance case.
- Send a same-day follow-up note that captures the expectation and the date of review.
- Work through a structured preparation system (the PM Interview Playbook covers feedback framing, calibration language, and real debrief examples that map cleanly to this kind of conversation).
Mistakes to Avoid
The biggest mistakes are not technical. They are linguistic and managerial.
- BAD: "You need to be more senior."
GOOD: "Your last two deliverables missed the review window. I need the next one by Tuesday at 2 p.m."
- BAD: "Everyone is frustrated with you."
GOOD: "The team had to redo the launch doc after your version missed the decision criteria."
- BAD: "Let's revisit this in a few weeks."
GOOD: "We will review this next Tuesday against these three outputs and decide whether the pattern has changed."
The pattern behind these mistakes is the same. New managers use vague language when they should use evidence. They use future tension when they should use present facts. They use social discomfort to avoid making the standard visible.
FAQ
- Should I say "performance issue" in the first conversation?
Yes, if the gap is about delivery, judgment, or reliability. Do not hide the label when the facts support it. Clarity early is less damaging than ambiguity that drifts for 30 days.
- How soon should I follow up after the conversation?
Same day. Waiting even 24 hours creates room for disagreement about what was said. A short written note locks the standard and the checkpoint.
- What if the person gets defensive?
Stay on the facts and repeat the expectation. Do not litigate intent. If the response is resistance rather than engagement, that is itself a signal that the issue may need escalation.
Ready to build a real interview prep system?
Get the full PM Interview Prep System →
The book is also available on Amazon Kindle.