The first responsibility of a manager is not to comfort, but to ensure performance; underperformance, left unaddressed, erodes team trust and organizational output. This isn't about being liked, it's about leading.

TL;DR

Addressing underperformance immediately and systematically is non-negotiable for effective management and team health. Managers must deliver direct, evidence-based feedback, establish clear, measurable expectations, and rigorously document all interactions to ensure accountability and fair process. The problem isn't often the underperformer's initial intent, but the manager's reluctance or inability to enforce performance standards.

Who This Is For

This guide is for new or aspiring managers within large, structured tech organizations (FAANG, high-growth unicorn) who are currently leading teams of 5-15 individual contributors. You are navigating your first performance review cycles and grappling with the uncomfortable necessity of addressing team members who consistently fail to meet expectations despite initial guidance. You understand that deferring these difficult conversations leads to systemic issues, but lack the specific playbook for execution, especially concerning documentation and the hard judgments required.

How do I accurately diagnose true underperformance in my team?

True underperformance is not merely a dip in output, but a consistent failure to meet clearly defined role expectations or project milestones, despite the necessary resources and coaching. In a Q3 debrief at Google, a hiring manager presented a case for a Product Manager on a critical launch failing to meet deadlines.

The initial reaction from the committee was to attribute it to "new manager syndrome" – perhaps insufficient onboarding or mentorship. However, after reviewing three months of JIRA tickets and weekly sync notes, it became clear the PM consistently missed deliverables by 3-5 days, repeatedly stated "I'll get to it" without follow-through, and failed to escalate blockers. The insight here is not just about observing the outcome, but scrutinizing the pattern of behavior leading to it.

The diagnostic process requires separating capability gaps from motivational issues or external dependencies. A capability gap might manifest as an inability to master a new skill despite training, while a motivational issue appears as a lack of effort or prioritization of non-work tasks. In one instance, a new engineer missed critical code review deadlines. My initial assumption was a technical gap. After a candid conversation, it was revealed he was struggling with a sick parent and his focus was elsewhere.

This wasn't underperformance in the traditional sense, but a life event requiring support, not a performance improvement plan. The first counter-intuitive truth is that many instances initially flagged as "underperformance" are, in fact, symptoms of unclear expectations, lack of resources, or personal challenges. Your role is not to immediately judge, but to investigate. This involves triangulating data: observed output, peer feedback, and the individual's self-assessment. Without this diligence, you risk addressing the wrong problem, which is not only ineffective but deeply unfair.

What is the best way to structure an initial feedback conversation with an underperforming report?

The initial feedback conversation must be direct, specific, and focused on observable behaviors and their impact, not subjective character assessments. I once observed a manager attempt to address an underperformer by saying, "You just don't seem like you're pulling your weight," which led to defensiveness and no actionable change. A productive conversation, however, requires a structured approach that outlines the problem, its impact, and what needs to change. This is not a discussion for "how are you feeling?" but "here are the facts."

Begin by stating the specific behavior and the observed output gap, backed by concrete examples. "Last week, you committed to delivering the PRD draft by EOD Friday. It was delivered Monday morning, delaying the engineering handoff by one full business day. This is the third time in two months a critical deliverable has been late." This approach grounds the discussion in undeniable reality.

Next, articulate the impact of this behavior: "This delay pushed back the team's ability to estimate and begin sprint planning, impacting our Q3 launch timeline." Then, open the floor for their perspective, not as an opportunity to deflect, but to understand underlying factors: "Can you help me understand what happened here?" Listen, but do not accept excuses that undermine accountability. Finally, state the expected change and the non-negotiable nature of the standard. This isn't a negotiation; it's an expectation reset. The second counter-intuitive truth is that most managers soften the message to avoid discomfort, which signals to the employee that the behavior is tolerable. Your goal is not to deliver bad news gently, but to communicate a non-negotiable performance standard clearly.

Here's a conversational script template for such a discussion:

"Thank you for meeting. I want to discuss a pattern I've observed in your recent work. Specifically, over the past three weeks, [Project X] deliverables have been consistently submitted 1-2 days past their agreed-upon deadlines. For example, the [specific component] was due last Tuesday, but I received it on Thursday morning. This delay directly impacted [specific downstream team/project] by [quantifiable impact, e.g., pushing back design review by 2 days, delaying engineering sprint by 1 day]. Can you walk me through the factors contributing to these missed deadlines?"

[Listen actively, take notes. If excuses arise, pivot back to accountability.]

"I understand the challenges you're describing. My expectation, and the team's standard, is that committed deadlines are met or proactive communication occurs at least 24 hours in advance with a revised plan. The current pattern is not meeting the bar for this role.

Moving forward, for [specific project/deliverable], I need you to ensure [specific action, e.g., the delivery is on time, or you proactively communicate obstacles by noon the day prior]. I will be checking in on [specific future milestone] to ensure we're on track. Is there anything specific you need from me to meet this expectation?"

How do I set clear, measurable expectations and accountability for an underperformer?

Establishing clear, measurable expectations is paramount; vague objectives like "improve communication" are useless for performance management.

Instead, define success in terms of specific, observable, and quantifiable outcomes. For an underperforming Product Manager struggling with cross-functional alignment, the expectation should not be "be a better collaborator." It should be: "Within the next two weeks, you will schedule and lead a 30-minute sync with Engineering and Design leads for Project Alpha, producing documented meeting notes and a clear set of agreed-upon action items, circulated within 2 hours of the meeting." This specificity leaves no room for ambiguity.

Accountability is not about punishment, but about ensuring commitments are met. In a performance improvement plan (PIP) I helped craft for an engineer, one key metric was reducing critical production bugs. The initial draft stated "reduce critical bugs." We refined it to "reduce critical P0/P1 production bugs assigned to your team by 50% over the next 30 days, as measured by our bug tracking system (JIRA)." This level of detail provides an objective baseline for evaluation.

The third counter-intuitive truth is that you are not building a path to termination, but a pathway to performance. If the individual cannot meet these concrete, measurable targets, it's not a failure of their effort, but a mismatch between their capabilities and the role's requirements, which then simplifies the subsequent difficult decisions. This framing shifts the focus from fault-finding to objective assessment, enabling a more dispassionate and fair evaluation. Each expectation must be tied to a specific project or responsibility, have a clear deadline, and ideally, an objective measure of completion.

What is the critical process for documenting and following up on performance feedback?

Thorough documentation and consistent follow-up are not optional; they are the bedrock of fair and defensible performance management. The process begins immediately after the initial feedback conversation. Send a concise email summarizing the discussion, key takeaways, agreed-upon actions, and next steps. "Following up on our conversation today, we discussed [specific underperformance behavior and its impact]. We agreed that going forward, you will [specific action/expectation]. We will check in on [date/milestone] to review progress. My door is open for any questions as you work through this." This creates a contemporaneous record.

Follow-up meetings should be scheduled at regular, defined intervals – typically weekly or bi-weekly – to review progress against the established metrics. In a high-stakes scenario involving a principal engineer, my director meticulously logged every interaction: meeting dates, specific deliverables reviewed, whether expectations were met, and any new issues or positive shifts. This cumulative record, over an 8-week period, formed an irrefutable body of evidence. Without this diligent record-keeping, any subsequent performance review or HR escalation becomes subjective and vulnerable to legal challenge.

The fourth counter-intuitive truth is that documentation protects everyone involved, not just the company. It provides clarity to the employee about where they stand and demonstrates due process, which is critical if the situation ultimately leads to a performance improvement plan (PIP) or separation. A PIP typically outlines a 30-day or 60-day period with concrete, measurable goals, regular check-ins, and the clear consequence of continued underperformance. Failing to document correctly means you are not truly managing, you are simply hoping.

When is the right time to escalate an underperformance issue beyond initial feedback?

Escalation becomes necessary when initial feedback and a reasonable period of support fail to produce the required performance improvement, or when the severity of the underperformance poses immediate risk. The "right time" is not arbitrary; it follows a predictable path of neglected expectations and documented failures.

After 2-3 cycles of direct feedback, followed by agreed-upon action items, and a documented failure to meet those action items, it's time to engage HR and your skip-level manager. This is not about seeking permission to manage, but about engaging stakeholders who will ultimately support the next phase, which is often a formal Performance Improvement Plan (PIP).

In a debrief concerning a senior manager whose team was consistently missing key OKRs, my VP pushed to escalate after only 6 weeks of direct feedback. The rationale was simple: the impact on the 200-person organization was too great to allow a prolonged remediation period. This demonstrated that the timeline can be compressed based on impact and role seniority. The critical judgment here is not about your personal comfort, but about the objective impact on the business.

If the individual's lack of performance is impacting customer trust, financial targets, team morale, or critical project timelines, the need for formal intervention is immediate. When you reach out to HR, you should have a clear timeline of events, documented feedback conversations, and the specific, unmet expectations. This isn't a casual chat; it's a presentation of a case for formal action. Your role as a leader is to make tough calls for the greater good of the organization, not to extend grace indefinitely at the team's expense.

Preparation Checklist

  • Review the underperformer's official job description to ensure your expectations align with the role.
  • Gather specific, recent examples of underperformance: missed deadlines, bug reports, negative peer feedback, project failures. Quantify impact where possible.
  • Document all prior informal feedback given, including dates, specific issues discussed, and any agreed-upon actions.
  • Draft specific, measurable, and time-bound expectations for improvement. These should be 3-5 key outcomes, not a laundry list.
  • Schedule a private, uninterrupted meeting. Block 45-60 minutes to allow for a thorough discussion.
  • Work through a structured preparation system (the PM Interview Playbook covers frameworks for difficult conversations and performance management reviews with real-world scenarios).
  • Anticipate potential responses (defensiveness, excuses, emotional reactions) and plan how you will pivot back to the core issue and accountability.

Mistakes to Avoid

  1. Delaying the Conversation:
  • BAD: A new manager noticed an engineer was consistently late on minor tasks but hoped it would self-correct, delaying formal feedback for three months. By then, the engineer felt blindsided and resentful when the issue was finally raised, leading to a more entrenched problem and a longer recovery period.
  • GOOD: The manager addresses the first instance of missed deadline directly in a 1:1, stating, "I noticed the feature spec wasn't delivered by Friday. What happened?" This immediate feedback establishes expectations early and prevents small issues from compounding into larger performance gaps.
  1. Being Vague or Subjective:
  • BAD: A manager tells a designer, "Your work isn't up to par, and you need to improve your attitude." This feedback is unhelpful, unmeasurable, and focuses on subjective character traits, leaving the designer confused about how to improve.
  • GOOD: The manager states, "Your last two design prototypes for Project Nova missed key accessibility requirements outlined in our design system, specifically contrast ratios and keyboard navigation. This requires an additional 8 hours of engineering work to correct. Moving forward, all prototypes must pass a pre-submission accessibility check." This is specific, measurable, and tied to objective standards.
  1. Failing to Document and Follow Up:
  • BAD: A product lead had multiple informal chats with a PM about missing stakeholder updates. He felt he had

More PM Career Resources

Explore frameworks, salary data, and interview guides from a Silicon Valley Product Leader.

Visit sirjohnnymai.com →

FAQ

How many interview rounds should I expect?

Most tech companies run 4-6 PM interview rounds: phone screen, product design, behavioral, analytical, and leadership. Plan 4-6 weeks of preparation; experienced PMs can compress to 2-3 weeks.

Can I apply without PM experience?

Yes. Engineers, consultants, and operations leads frequently transition to PM roles. The key is demonstrating product thinking, cross-functional collaboration, and user empathy through your existing work.

What's the most effective preparation strategy?

Focus on three pillars: product design frameworks, analytical reasoning, and behavioral STAR responses. Mock interviews are the most underrated preparation method.