Performance improvement plans (PIPs) are one of the most difficult responsibilities an engineering manager faces. Done well, a PIP can genuinely help a struggling engineer get back on track. Done poorly, it becomes a demoralising formality that damages trust and accelerates departure. This guide covers how to approach PIPs with fairness, clarity, and genuine intent to help.
Understanding Performance Improvement Plans
A performance improvement plan is a structured process for addressing sustained underperformance. It defines specific, measurable goals that an engineer must achieve within a set timeframe - typically thirty to ninety days - along with the support and resources the manager will provide. A PIP is not the first step in addressing performance issues; it is a formal escalation after informal feedback and coaching have not produced sufficient improvement.
PIPs carry significant weight. They affect the engineer's confidence, their relationship with the team, and their career trajectory. Before initiating a PIP, ensure that you have exhausted less formal approaches: direct feedback, adjusted expectations, additional support, and clear documentation of the gap between expected and actual performance.
Be honest with yourself about the intent behind the PIP. If you genuinely believe the engineer can improve and you are committed to supporting them, a PIP can be a powerful tool. If the PIP is merely a legal formality before termination, that dishonesty will be apparent and will damage your credibility with the entire team.
- PIPs are formal escalations after informal coaching has not produced improvement
- They define specific, measurable goals with a clear timeframe
- Ensure genuine intent to help - a PIP should not be a pre-termination formality
- Exhaust informal approaches before initiating a formal PIP
Structuring an Effective PIP
An effective PIP is specific, measurable, and achievable. Vague goals like 'improve code quality' are unhelpful because neither you nor the engineer can objectively assess whether they have been met. Instead, specify observable outcomes: 'Reduce code review revision cycles from an average of four to two or fewer,' 'Complete assigned stories within sprint commitments for three consecutive sprints,' or 'Receive positive peer feedback on collaboration from at least two team members.'
Include the support you will provide: weekly check-ins, pairing sessions, mentorship from a senior engineer, reduced workload to allow for focused improvement, or training resources. A PIP that sets expectations without providing support is not a genuine improvement plan - it is a countdown to termination.
- Define specific, measurable, and achievable improvement goals
- Set a clear timeframe - typically thirty to ninety days
- Include the support and resources you will provide
- Schedule regular check-ins to assess progress and adjust as needed
Managing PIP Conversations
The initial PIP conversation is critical. Approach it with empathy but clarity. Explain the performance gap using specific examples, present the improvement plan, and ask the engineer for their perspective. They may have context you lack - personal challenges, unclear expectations, or systemic blockers that contributed to the underperformance.
Throughout the PIP period, provide frequent, honest feedback. If the engineer is making progress, acknowledge it explicitly. If they are not, address it immediately rather than waiting for the end of the PIP period. The engineer should never be surprised by the outcome - every check-in should provide a clear signal of where they stand.
Navigating PIP Outcomes
A PIP has three possible outcomes: the engineer meets the goals and returns to good standing, the engineer makes meaningful progress and earns an extension, or the engineer does not meet the goals and the process leads to separation. Each outcome requires thoughtful handling.
If the engineer succeeds, celebrate the improvement genuinely. Do not hold the PIP against them going forward - they demonstrated resilience and growth under pressure, which are valuable qualities. If the engineer does not succeed, handle the separation with dignity and respect. The team will be watching how you treat their colleague, and your behaviour in this moment will define their trust in you.
Common PIP Management Mistakes
The most common mistake is using a PIP as a surprise. If the engineer did not know they were underperforming before the PIP conversation, you failed as a manager. PIPs should be the culmination of an escalating feedback process, not the beginning of one.
Another frequent error is setting unachievable goals to ensure the engineer fails. This is unethical and will be obvious to your team. If you have already decided to terminate, have the integrity to do so directly rather than using a PIP as a fig leaf. Your team's trust in you depends on your honesty in these situations.
Key Takeaways
- Exhaust informal feedback and coaching before initiating a formal PIP
- Set specific, measurable, achievable goals with genuine support
- Approach PIP conversations with empathy, clarity, and honesty
- Provide frequent feedback throughout the PIP period - no surprises at the end
- Handle all outcomes with dignity - your team is watching how you treat people
Frequently Asked Questions
- How long should a PIP last?
- Thirty to ninety days is typical, depending on the nature of the performance gaps and the complexity of the improvement goals. Thirty days is appropriate for clearly defined, quickly measurable goals. Sixty to ninety days is appropriate for more complex improvements like communication skills or technical depth. The timeframe should be long enough for genuine improvement but short enough to maintain urgency.
- Should I tell the team that someone is on a PIP?
- No. PIPs are confidential between the manager, the engineer, and HR. Disclosing someone's PIP status to the team is a breach of trust and may have legal implications. If team members notice changes in the engineer's assignments or workload, you can explain that you are working with the engineer on their development without disclosing the PIP specifically.
- What if I inherit an engineer who is already on a PIP?
- Review the PIP documentation thoroughly. Meet with the engineer to understand their perspective and reestablish the relationship. Assess whether the goals are fair and achievable. You may need to adjust the plan based on your assessment, but do so in collaboration with HR. Your fresh perspective can be an advantage - you can evaluate the situation without the baggage of the prior relationship.
- How do I prevent PIPs from becoming necessary?
- Provide continuous, honest feedback. Most performance issues are addressable when caught early. Regular one-on-ones, clear expectations, and a culture of direct feedback prevent small performance gaps from growing into PIP-worthy issues. When you notice early signs of underperformance, address them immediately with specific, actionable feedback.
Access PIP Templates
Access performance improvement plan templates, feedback documentation guides, and difficult conversation frameworks designed for engineering managers handling underperformance with integrity.
Learn More