TL;DR

Why Do PIPs Fail for First-Time Managers at Startups?

PIPs are a legal formality that delays inevitable termination while destroying morale. For first-time managers at startups, the alternative—structured coaching with clear exit criteria—is faster, cheaper, and leaves the door open for future rehire. Here's how to implement it.


Why Do PIPs Fail for First-Time Managers at Startups?

PIPs fail because they are adversarial by design. The moment you present a PIP, you've told your manager two things: we don't trust you to improve, and we've already decided you're leaving. This creates defensive behavior, not behavioral change.

In a Q3 debrief at a Series B startup I advised, the founding team spent $40,000 on HR legal review for a PIP that lasted 6 weeks and ended in termination anyway. The manager, a strong individual contributor promoted too early, spent those 6 weeks updating her LinkedIn rather than her execution. The PIP didn't fail because of poor documentation. It failed because the format itself signals abandonment.

The startup context makes this worse. First-time managers often lack formal training—they were promoted for technical skill, not people management. A PIP assumes the person knows how to improve and simply isn't trying. Coaching assumes they may not know how, and provides the scaffolding to figure it out. At a company with 50 employees, you don't have the luxury of HR infrastructure to manage adversarial processes. You need outcomes.

The counter-intuitive truth: terminating someone after a failed PIP often takes 90 days and costs 2-3x their salary in lost productivity, recruiting fees, and legal exposure. A structured 30-day coaching arc with defined checkpoints can resolve the same situation in half the time with a fraction of the damage.


What Does Coaching Instead of Firing Actually Look Like?

Coaching instead of firing is a structured 2-to-4-week intensive with weekly written check-ins, specific behavioral metrics, and a named coach (internal or external). It is not a conversation. It is not "let's touch base next month." It is a documented, time-boxed intervention with clear success criteria.

The structure I recommend: a 30-day plan with three checkpoints (day 7, day 14, day 30). Each checkpoint has 2-3 specific behavioral outcomes measured by observable evidence—not gut feeling. For a manager struggling with 1:1s, the evidence might be: "Completed 4 consecutive 1:1s with agenda documents shared 24 hours in advance, with at least 3 action items captured per session." That's a metric. "Better 1:1s" is not.

I witnessed a hiring manager at a growth-stage fintech implement this precisely. His new engineering manager had been on track for PIP territory—missed delivery commitments, three direct reports filed anonymous complaints. Instead of the PIP, he structured a 30-day coaching arc with the VP of Engineering as coach.

By day 14, the manager had redesigned her 1:1 structure and retained two of the three complaining reports in skip-level conversations. The third had already accepted an offer elsewhere. The manager wasn't fired. She was moved to an IC track 6 months later and is now a senior technical lead.

The key difference: coaching requires the manager to be willing. If they believe the process is theater, it will be. You need explicit buy-in at the start. That means the first conversation cannot feel like a warning. It has to feel like investment.


📖 Related: Headspace PM portfolio projects that stand out in interviews 2026

How Do You Structure a 30-Day Coaching Plan?

A 30-day coaching plan has five components: a diagnostic conversation, defined success metrics, a named coach, weekly written reflections, and a decision checkpoint. Without all five, you're improvising.

The diagnostic conversation happens in the first 48 hours. You ask: "What's the hardest part of this role for you right now?" Not "why are you struggling." The distinction matters. Struggling implies failure. Hardest part implies normal difficulty that can be addressed. You document their answer verbatim. If they say "I don't know how to prioritize when everything is urgent," that's your coaching target.

Success metrics come from the diagnostic. You negotiate 3 outcomes, not 10. For a manager failing at delegation, the metrics might be: (1) Assign a project to a direct report by day 3 with documented scope and deadline. (2) Receive a status update from that report without following up, by day 10. (3) Complete a delegation retro (what worked, what didn't) with your coach by day 14.

The coach is not their manager. It is someone with positional authority to give feedback but no direct reporting relationship to them. This prevents the coaching conversation from collapsing into the performance conversation. At a 30-person startup, this might be a senior IC or an external coach. At larger startups, it might be someone from a sibling team.

Weekly written reflections: the manager writes 200 words on what went well, what didn't, and what they're changing. The coach responds in 48 hours with specific feedback. This creates a paper trail that protects everyone if termination becomes necessary, and it creates accountability that PIP documentation rarely achieves because PIPs are backward-looking.

The decision checkpoint on day 30 is binary: met criteria or not. If met, you formalize a 60-day follow-on period with lighter touch. If not, you move to transition planning. There is no extended PIP. The coaching arc was the intervention.


What Conversations Should You Have Before Termination?

Before any termination, you have three conversations: the diagnostic, the coaching commitment, and the transition. The diagnostic happens before the coaching decision is made. The coaching commitment happens when you agree to the plan. The transition happens when the coaching period ends.

The diagnostic script:

"I've noticed some friction in how your team is operating, and I want to understand your perspective before we figure out next steps. What's the hardest part of this role for you right now?"

Then you listen for 5 minutes without responding. You take notes. You do not problem-solve in this conversation. The goal is to understand their mental model of the problem.

The coaching commitment script:

"What I'm proposing is a focused 30-day coaching period. [Name] will work with you as your coach. We'll have three check-ins with specific outcomes we've agreed on. At the end of 30 days, we'll make a decision about your role here. I'm committing to this because I think you can succeed here, and this is what success looks like. Does this feel fair?"

Note: "Does this feel fair?" is not the same as "Do you agree?" Fair is a judgment call. Agreement can be coerced. Fairness is harder to argue with.

The transition script (when coaching fails):

"I'm going to be direct. At the end of the coaching period, you didn't meet the criteria we set together. I'm not going to extend this. What I can do is a 4-week transition period where we work together on your next role—I'll be a reference, I'll give you feedback on your resume, and I'll make introductions where I can. I'd like to end on good terms. Are you open to that?"

This script works because it offers dignity. The manager knows termination is coming, but they leave with a runway and a reference. For a startup, this matters: the ex-employee will talk to future candidates.


📖 Related: Braze product manager tools tech stack and workflows used 2026

When Does Coaching Work vs. When Should You Cut Losses Immediately?

Coaching works when the gap is skill, not will. If a manager doesn't know how to run effective 1:1s, coaching can teach that. If a manager knows and refuses—because they believe micromanagement is leadership, or because they're checked out—coaching won't fix it.

The diagnostic conversation reveals this. If they say "I know I should do X, but I don't have time," that's will. If they say "I didn't realize that was expected," that's skill. You can teach skill. You cannot coach around will.

Cut losses immediately in three scenarios: (1) Integrity violations—lying to stakeholders, hiding problems, throwing direct reports under the bus. (2) Active disengagement— they've mentally left and are coasting to severance. (3) Values mismatch that can't be coached— treating employees dismissively, taking credit for others' work, refusing to learn.

I sat in on a hiring committee where the founder pushed back on immediate termination for a director who had lied to a client about product timeline. The HR lead said: "We could coach them on communication. We cannot coach them on honesty." The director was terminated within a week. No PIP. No coaching arc. The decision was correct.

The rule: if you'd never re-hire this person, don't waste 30 days pretending you might.


How Do You Document Everything Without Creating Legal Risk?

Documentation protects everyone—but bad documentation creates liability. The standard: factual, specific, contemporaneous, and consistent.

Factual means you document what happened, not how you felt about it. "Manager missed deadline for Q3 roadmap" is factual. "Manager showed lack of commitment to deliverables" is interpretation. Legal counsel will destroy interpretation on cross-examination.

Specific means you use observable evidence. "In the 1:1 on October 3rd, the manager interrupted the direct report 7 times before the direct report stopped speaking" is specific. "The manager doesn't listen" is not.

Contemporaneous means you document within 24 hours of the event. Documentation written after a termination decision looks like rationalization. Documentation written at the time looks like management.

Consistent means your written documentation matches your verbal feedback. If you told the manager "great job on the presentation" in person and wrote "needs improvement on executive communication" in the file, you have a credibility problem.

The coaching documentation—weekly reflections and coach feedback—creates a longitudinal record that a court will view favorably if the termination is challenged. It shows you invested in the person, gave specific feedback, and tracked progress over time. That's the legal case for coaching over PIP.


Preparation Checklist

  • Conduct the diagnostic conversation within 48 hours of identifying a management performance issue—do not wait
  • Define 3 specific, measurable behavioral outcomes before the coaching period begins—do not negotiate outcomes during the coaching period
  • Assign a named coach with no direct reporting relationship to the manager—conflicted coaches create legal exposure
  • Require weekly written reflections (200 words minimum) from the manager and written coach feedback within 48 hours—verbal feedback does not protect you
  • Schedule three explicit checkpoints (day 7, day 14, day 30) on the calendar before the coaching period starts—informal check-ins disappear
  • Prepare a binary decision framework for day 30: met criteria or not, with no ambiguity about what "met" means
  • Draft the transition conversation script in advance—you will not be articulate in the moment without rehearsal

Work through a structured preparation system (the PM Interview Playbook covers this territory with real debrief examples from hiring committees who reviewed coaching arc decisions—not performance reviews, but the structural decisions about when to intervene and when to exit).


Mistakes to Avoid

Mistake 1: Delaying the intervention because you hope it will resolve itself.

BAD: "She's been struggling for 3 months, but maybe she'll figure it out."

GOOD: Performance issues that persist beyond 4 weeks rarely self-correct. The diagnostic conversation should happen at week 4, not week 12.

Mistake 2: Coaching without defined exit criteria.

BAD: "Let's do a coaching period and see how it goes."

GOOD: "If you deliver the Q4 roadmap by November 15th with stakeholder sign-off, you've met the criteria. If not, we'll move to transition planning." Ambiguity benefits no one.

Mistake 3: Using the coach as therapist rather than accountability partner.

BAD: "I want you to feel supported, so take this time to reflect on what you want."

GOOD: Coaching is structured intervention with specific targets. If the manager needs emotional support, that's an EAP referral, not a coaching arc.


FAQ

Can you fire someone without a PIP if you're concerned about wrongful termination risk?

Yes. PIPs are not legally required in any US state. Coaching arcs with documented checkpoints are actually stronger legal protection than PIPs because they demonstrate investment in retention before termination. Consult employment counsel for your specific jurisdiction, but the absence of a PIP does not create liability if you have contemporaneous documentation of specific behavioral issues and the coaching period.

What if the manager refuses the coaching period?

If a manager declines a structured coaching arc, that's your answer. Willingness to engage in structured feedback is itself a signal. At that point, you move directly to transition planning. Do not coerce participation—you cannot coach someone who doesn't want to be coached.

How do you handle founders who want to terminate immediately for cultural reasons?

Founders often conflate "I don't like this person" with "this person should be terminated." The coaching period serves a filtering function: it gives the founder's instinct time to be validated or overturned by evidence. If the manager still fails coaching after 30 days with specific metrics, the founder's instinct is confirmed. If they succeed, the founder learns something about their initial read. Either way, the documentation from the coaching arc gives the termination legal backbone.amazon.com/dp/B0GWWJQ2S3).

Related Reading