liveBook · Manning

Performance improvement plan

As explained in Think Like a Software Engineering Manager

A performance improvement plan is a formal documented plan specifying performance expectations, support, milestones, and consequences for an employee who is not meeting requirements.

A performance improvement plan (PIP), also called a Performance Empowerment Plan, is a formal, documented, time-bound plan for an employee who continues to miss performance expectations despite coaching. It defines actionable improvements, timelines, monitoring, and possible consequences. section 4.5.1

A PIP differs from an earlier coaching plan in several important ways:

  • It is more formal, shorter, and more tightly time-bound. section 4.5.1
  • It uses more direct action items, estimated timelines, and robust documentation. section 4.5.1
  • Human resources is typically involved in the process. section 4.5.1
  • It serves as a final opportunity to improve before potential termination. section 4.5.1

Example: continued missed deadlines

John received coaching, learning resources, clarified expectations, and regular progress reviews documented by email. When he continued to miss deadlines, a PIP became the next step, with direct actions, time limits, and clearly communicated consequences. section 4.5.1

How Think Like a Software Engineering Manager covers it

How deep it goes
Explains purpose, timing, documentation, HR involvement, and consequences, but does not specify a universal PIP template.
Examples
Uses a missed-deadlines scenario involving coaching, learning resources, weekly reviews, email documentation, and eventual escalation.
What it assumes
Assumes clear expectations, prior coaching, feedback, and progress monitoring; distinguishes a PIP from those earlier interventions.
What you can do after
Practice/perform a documented escalation from coaching to time-bound performance actions with explicit consequences.
How it connects
Connects performance improvement plans with performance expectations, coaching plans, feedback, monitoring, documentation, human resources, and termination.

Also explained in

Compare how 3 books explain performance improvement plan →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.