TL;DR

A Performance Improvement Plan (PIP) is the wrong tool for first-time startup managers without HR. The real problem isn’t documentation—it’s misaligned expectations and lack of psychological safety. Use a 30-day "Performance Reset" instead: structured feedback, clear metrics, and weekly check-ins with a hard deadline. If no improvement, transition them out within 45 days.

Who This Is For

This is for first-time managers at seed or Series A startups (10-50 employees) who inherited a struggling direct report, have no HR business partner, and can’t afford legal exposure. You’re not firing someone for malice or fraud—you’re dealing with a mismatch in skills, effort, or cultural fit that surfaced after 3-6 months. If you’re at a company with an HR team, stop reading and escalate.

Why a PIP Is the Wrong Tool for Startups Without HR

The hiring manager in a 12-person fintech startup leaned across the table during a debrief and said, “I put her on a PIP, but now she’s crying in every 1:1 and the team is walking on eggshells.” The problem wasn’t the PIP—it was that the PIP was never designed for startups. It’s a corporate compliance document, not a management tool.

A PIP assumes three things that don’t exist in early-stage startups:

  1. A stable role definition (startups pivot every 90 days)
  1. An HR team to handle documentation and legal risk (you’re it)
  1. A 60-90 day timeline to observe improvement (startups can’t afford that)

The counter-intuitive insight: PIPs fail not because they’re too harsh, but because they’re too slow. In a startup, the cost of a misaligned employee compounds weekly—missed deadlines, team morale, founder distraction. A PIP’s 90-day window is a luxury you don’t have.

Not a compliance document, but a forcing function.

What to Use Instead: The 30-Day Performance Reset

In a seed-stage SaaS company, the engineering lead came to me after a failed PIP attempt. “I gave him 60 days, but nothing changed. Now I’m stuck.” The fix wasn’t more time—it was clearer stakes. We replaced the PIP with a 30-Day Performance Reset, a lightweight contract between manager and employee with three components:

  1. Single-Page Agreement: One document, signed by both parties, with:
  • 3 measurable outcomes (not activities)
  • Weekly check-in cadence
  • Hard deadline (30 days)
  • Explicit consequence: “If outcomes aren’t met, we’ll part ways.”
  1. Weekly Feedback Loops: 30-minute sessions, structured as:
  • What’s working (1 item)
  • What’s not (1 item)
  • Adjustments (1 action)

No surprises at day 30.

  1. Exit Plan: Pre-written transition email drafted on day 1, ready to send if outcomes aren’t met. This removes the emotional burden of firing and forces the manager to confront reality early.

The insight: People don’t improve because of documents—they improve because of clarity and consequences. A 30-day reset creates both without the legal baggage of a PIP.

Not a softer PIP, but a faster feedback loop.

How to Frame It to the Employee (Script Included)

The worst moment in my first management role was telling someone they were failing. I used vague language, and they left the meeting thinking they had 6 months to fix things. They didn’t.

The script that works:

“This isn’t a PIP—it’s a reset. We’re not documenting for HR; we’re giving you a clear path to succeed in the next 30 days. Here are the three outcomes we need to see by [date]. If we hit them, we’ll talk about your role moving forward. If not, we’ll part ways. I’ll give you feedback every week so there are no surprises.”

Key principles:

  • No blame: “This isn’t about your effort—it’s about the outcomes we need.”
  • No negotiation: The outcomes are non-negotiable. The how is flexible.
  • No ambiguity: “Part ways” means fired. Don’t say “transition” or “explore other opportunities.”

The counter-intuitive truth: Employees often thank you for the clarity. The ones who push back (“This feels unfair”) are the ones you’d fire at day 30 anyway.

Not a performance conversation, but a role negotiation.

What Metrics to Use (And What to Avoid)

In a debrief with a hiring manager at a 20-person marketplace startup, she said, “I put ‘improve communication’ on the PIP, but how do I measure that?” The answer: You don’t. Vague metrics are worse than no metrics.

Use these instead:

  • Output-based: “Ship feature X by [date] with 0 critical bugs” (not “improve code quality”)
  • Behavioral: “Attend all standups on time for 30 days” (not “be more engaged”)
  • Team-based: “Get sign-off from PM on 3 designs by [date]” (not “collaborate better”)

Avoid:

  • Effort metrics: “Work harder” or “show more initiative”
  • Subjective traits: “Be more proactive” or “improve attitude”
  • Process metrics: “Submit weekly reports” (unless the report directly ties to an outcome)

The insight: Metrics should be binary—either they’re met or they’re not. If you can’t answer “Did they do this?” with a yes or no, the metric is useless.

Not “show improvement,” but “deliver X by Y.”

How to Handle the Team (Without Destroying Morale)

The engineering team at a 15-person startup stopped inviting their struggling peer to happy hours. When I asked why, they said, “We don’t want to make it awkward.” The manager’s silence had created a vacuum, and the team filled it with gossip.

The rule: If the team knows the person is struggling (and they always do), you must address it. Not with details, but with direction.

Script:

“[Name] is working on some priorities with me. For the next 30 days, I’ll handle their feedback directly. If you have concerns, bring them to me. After 30 days, we’ll reassess.”

Key moves:

  • Control the narrative: Don’t let the team speculate.
  • Protect the employee: No public feedback or side conversations.
  • Signal stability: “We’ll reassess” implies a plan, not chaos.

The insight: Teams don’t need transparency—they need confidence in leadership. Your job isn’t to explain the situation; it’s to prevent it from becoming a distraction.

Not “be transparent,” but “be decisive.”

When to Escalate to the Founder (And When to Handle It Yourself)

The first-time manager at a 25-person startup waited until day 28 of a 30-day reset to tell the founder. The founder’s response: “Why am I hearing about this now?” The manager’s mistake wasn’t the delay—it was assuming the founder didn’t need to know.

Escalate to the founder when:

  • The employee is in a mission-critical role (e.g., first sales hire, lead engineer)
  • The reset outcomes aren’t met by day 20
  • The employee has equity or a high salary (legal risk)
  • The team is visibly affected (morale, gossip, missed deadlines)

Handle it yourself when:

  • The role is replaceable (e.g., junior marketer, support rep)
  • The employee is new (<3 months) and the reset is a formality
  • The founder is already stretched thin (e.g., fundraising, product launch)

The counter-intuitive truth: Founders don’t want to be involved in every firing, but they do want to be involved in every risk. Escalate early, not late.

Not “keep the founder out of it,” but “give them a heads-up.”

Preparation Checklist

  • Draft the 30-Day Performance Reset document (use the template in the Startup Manager Playbook, which includes real examples from seed-stage companies).
  • Schedule weekly 30-minute check-ins for the next 4 weeks (put them on the calendar now).
  • Write the transition email (draft it on day 1, even if you don’t send it).
  • Identify a replacement candidate (start sourcing on day 1—don’t wait for day 30).
  • Brief the founder (send a 3-sentence email: “[Name] is on a 30-day reset. Outcomes: [X, Y, Z]. I’ll update you on day 20.”).
  • Prepare for the day 30 conversation (script it in advance).
  • Document everything (emails, check-in notes, outcomes) in a single folder.

Mistakes to Avoid

BAD: “Let’s give them another 30 days to improve.”

GOOD: “If the outcomes aren’t met by day 30, we part ways. No extensions.”

The problem isn’t generosity—it’s indecision. Startups move too fast for second chances. If the reset fails, the cost of keeping them is higher than the cost of firing them.

BAD: “I’ll handle this myself—I don’t want to bother the founder.”

GOOD: “I’m looping in the founder on day 1. Here’s what I’m doing.”

The problem isn’t autonomy—it’s isolation. Founders need to know about risks, not just successes. Escalate early, even if it feels like over-communication.

BAD: “I’ll tell them they’re on a PIP.”

GOOD: “This is a 30-day reset, not a PIP. Here’s what success looks like.”

The problem isn’t the tool—it’s the framing. A PIP carries legal baggage and emotional weight. A reset is a clean slate with clear stakes.

More PM Career Resources

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

Visit sirjohnnymai.com →

FAQ

Isn’t this just a PIP with a different name?

No. A PIP is a legal document designed to protect the company in case of a lawsuit. A 30-day reset is a management tool designed to give the employee a clear path to succeed or fail fast. The difference is in the intent, not the format.

What if the employee quits during the 30 days?

That’s a win. It means they recognized the role wasn’t a fit, and you avoided a messy firing. Always have a replacement candidate lined up by day 15.

How do I fire someone if the reset fails?

Use the transition email you drafted on day 1. Keep it short: “Today is your last day. Here’s your final paycheck and next steps.” No debate, no negotiation. If they push back, say, “This isn’t a conversation—it’s a notification.”