Performance Improvement Plan (PIP) Guide for Managers

---

When a junior engineer falls short, managers often face a painful choice: drift along in frustration or initiate a process that feels like a firing. To handle this ethically, you must treat the Performance Improvement Plan (PIP) as a structured reset, not a slow-motion exit.

This guide covers how to diagnose the root cause, write scorable goals, and pair every requirement with concrete support.

1. Clarify the Purpose: Rescue, Reset, or Exit?

Before drafting a single goal, answer this blunt question: Are you trying to rescue, reset, or exit this engineer?

• Rescue: Intensive coaching to bridge a skill gap.
• Reset: Formalizing expectations that were previously vague.
• Exit: Documentation for a decision already made.

If you treat an almost-certain exit as a "coaching plan," your goals will be dishonest.

Liane Davey argues that PIPs should only be used when there is a credible path to improvement. If you don't believe they can pass, negotiate a severance instead.

2. Diagnose Before You Prescribe

If you skip diagnosis, you end up with vague instructions like "be more proactive."

The Three Gaps:

• Skill: They lack technical ability (e.g., debugging).
• Behavior: They have the skill but don't apply it (e.g., late for standup).
• Context: The environment is broken (e.g., no onboarding).

A skill gap needs training. A behavior gap needs clear expectations. A context gap needs you to fix the system.

3. Write Goals That Are Scorable

For a junior engineer, vague goals are a death sentence. You must write goals that a neutral observer can score.

• Bad: "Write better code."
• Good: "Write tests for all new features covering the happy path and one edge case."
• Bad: "Communicate more."
• Good: "Post a daily update in Slack by 10 AM listing yesterday's work and today's blockers."

The Rule: If you cannot measure it, you cannot manage it.

4. Pair Every Goal with Support

A PIP that lists outcomes without support is just a test. For a junior, that is rarely fair.

The Support Contract: For every goal, list the resource you will provide.

• Goal: "Ship 3 independent tickets."
• Support: "Daily 15-minute unblocking sessions with Senior Engineer X."

Research shows that modest investments in training yield disproportionate gains. If you aren't willing to invest the time, don't pretend you're offering a fair chance.

5. Define the Cadence

A PIP without regular check-ins is a "see you in 60 days" trap.

The Schedule:

• Weekly: 1:1 focused strictly on PIP progress.
• Mid-Point: A formal review at 30 days.
• Ad-Hoc: Immediate feedback when a major milestone is hit or missed.

Frequent touchpoints serve as emotional stabilizers. They signal that you are paying attention and that improvement is visible.

6. Be Honest About the Outcome

At the end of the timeline, you owe the engineer a clear, honest verdict.

The Three Paths:

• Success: Goals met; return to normal management.
• Partial: Some improvement; extend with narrowed scope.
• Failure: Core goals missed; transition to exit.

Do not keep them guessing. Transparency is the only way to maintain dignity for everyone involved.

Remember: A PIP is a structured reset, not a slow-motion exit.

Do This Next: The PIP Prep Checklist

Before you deliver the document, audit your plan against these four items.

• [ ] The Diagnosis: Have I written down whether this is a skill, behavior, or context gap?
• [ ] The Math Test: Can a stranger read these goals and score them Yes/No?
• [ ] The Support Pledge: Have I secured the time of a mentor to help them?
• [ ] The Honesty Check: Have I explicitly told them that termination is a possible outcome?