A Performance Improvement Plan is one of the most consequential tools a manager can use. That is precisely why it should not be the first moment an employee learns that something is wrong.
When a formal plan arrives as a surprise, the problem is larger than the employee's performance. The management system has failed to make expectations, evidence, feedback and consequences visible early enough. A PIP may still be necessary, but it is now carrying work that should have happened before the document existed.
This distinction matters because performance management is not a sequence of isolated events. It is a continuous system. People need to understand what good performance means, receive evidence about where their current work differs from that standard, have a fair opportunity to respond, and know what happens when improvement does or does not occur.
The formal plan is therefore not the beginning of performance management. It is a late-stage intervention inside an existing leadership process.
Performance Problems Usually Become Visible Before They Become Formal
Most performance concerns do not appear in a single instant. They accumulate through missed commitments, recurring quality issues, weak communication, unreliable ownership, repeated technical mistakes, ineffective collaboration, or a gap between the role's expectations and the person's current behavior.
The signals may be ambiguous at first. One missed deadline proves little. A defect may be caused by unclear requirements. A difficult quarter may reflect a system problem rather than an individual one. That is why managers need evidence instead of impression.
A useful progression is:
Expectation
↓
Observed work
↓
Evidence of a gap
↓
Feedback and clarification
↓
Support and opportunity to improve
↓
Follow-up
↓
Escalation if the gap persists
↓
Formal PIP when appropriate
Each stage reduces ambiguity. If the process jumps from "observed work" directly to "formal PIP," the employee is forced to reconstruct months of unspoken expectations while also processing the threat implied by formal escalation.
CIPD's current performance-management guidance emphasizes that employees need to understand what is expected and have the skills, resources and support required to succeed while remaining accountable for their work. Its evidence review on feedback also stresses that feedback can improve or damage performance depending on how it is delivered and integrated into the broader management process.
That is an important reminder. Feedback is not automatically useful because it exists. It needs specificity, context and a path forward.
Expectations Must Exist Before Evaluation
A manager cannot reasonably hold someone accountable to a standard that has never been made visible.
That does not require an exhaustive specification for every task. Senior roles, especially in engineering, often include judgment, ambiguity and broad responsibility. But ambiguity in the work is different from ambiguity in the standard.
An engineer may have freedom in how to solve a problem while still being expected to communicate risk early, test changes responsibly, collaborate with peers and own production consequences. A technical lead may have discretion over architecture while still being expected to create clarity for the team, expose trade-offs and avoid decisions that create unnecessary operational risk.
A PIP that introduces these expectations for the first time is doing two jobs badly. It is both defining the role and evaluating the person against that newly defined role.
Before formal escalation, the employee should already be able to answer several questions:
| Question | What good management makes visible |
|---|---|
| What is not meeting expectations? | Specific behavior, outcome or recurring pattern |
| What evidence supports that conclusion? | Concrete examples, not general labels |
| What needs to change? | Observable changes in behavior or output |
| What does acceptable performance look like? | A sufficiently clear standard |
| How will progress be evaluated? | Defined signals, checkpoints or outcomes |
| What support is available? | Coaching, clarification, resources or training |
| What timeframe applies? | A realistic period tied to the nature of the gap |
| What happens if improvement does not occur? | Clear consequences without theatrical threat |
This does not remove accountability. It makes accountability possible.
Evidence Protects Both Sides of the Conversation
Managers sometimes avoid specificity because it feels confrontational. They say someone "needs to show more ownership" or "is not operating at the expected level." Those phrases can be useful summaries, but they are not sufficient evidence.
What did ownership look like in the role? What happened instead? What was the consequence? Was this an isolated event or a pattern? Was the expectation communicated? What changed after prior feedback?
Evidence protects the employee from being judged against a manager's shifting interpretation. It also protects the manager from turning the process into an argument about personality.
A useful performance conversation separates three things:
Person
≠
Observed behavior
≠
Impact of that behavior
The manager's responsibility is to evaluate work and role fit, not to reduce a person's identity to a period of weak performance.
This matters even more during a PIP because formal pressure tends to make every conversation feel larger than the immediate facts. The more consequential the process becomes, the more disciplined the manager should become about evidence.
Support and Accountability Are Not Opposites
Weak performance management often swings between two extremes.
In one, the manager protects the employee from difficult feedback for too long. Problems are softened, delayed or described indirectly. The employee receives encouragement without enough clarity to know what must change.
In the other, management becomes purely punitive. The employee is given a list of failures and told to fix them, but receives little help understanding root causes, priorities or expectations.
Neither is strong leadership.
Psychological safety does not mean removing consequences. Accountability does not mean withholding support. A serious improvement process needs both.
Support may include clearer priorities, more frequent feedback, pairing with a stronger peer, coaching on a specific skill, removing conflicting assignments, clarifying decision rights, or creating smaller checkpoints where progress can be observed.
The point is not to make the standard easier. The point is to remove avoidable ambiguity about how to reach it.
Employee agency also matters. A PIP should not turn the employee into a passive object being managed. They should understand the concerns, ask questions, propose changes, identify blockers and demonstrate improvement through their own work.
The PIP Is a Formal Period, Not a Surprise Trial
Once a formal PIP becomes necessary, it should consolidate an already-understood concern into a more explicit structure.
The plan should make the performance gap, required changes, support, evaluation criteria and timeframe unambiguous. It should not suddenly reveal a collection of old grievances that were never discussed.
The manager also needs to resist a common failure mode: changing the criteria during the process.
If the plan begins with reliability, communication and delivery expectations, success should not later depend on unrelated impressions such as whether the employee "seems more senior" or "feels more proactive." If new evidence reveals a genuinely important issue, it can be discussed. But formal success criteria should not move simply because the employee is getting close to meeting them.
A PIP is not useful if the employee cannot know whether they are succeeding.
A PIP Must Have an Ending
The most important structural property of a PIP is that it ends.
That ending has at least two legitimate forms.
In the first, the employee does not make the required change. Expectations were explicit. Evidence was discussed. Support and opportunity were provided. The evaluation criteria were known. The improvement was still insufficient.
In that case, leadership may need to end the employment relationship.
In the second, the employee meets the agreed expectations and demonstrates meaningful improvement.
In that case, leadership needs to end the PIP.
Organizations sometimes understand the first obligation and neglect the second. They are prepared to escalate failure, but not prepared to close the chapter after success.
That inconsistency damages the credibility of the entire process.
When the PIP Does Not Succeed
A failed PIP should not produce a theatrical final confrontation.
If the process was conducted properly, the final conversation should not be the first time the employee hears the core facts. The manager should not need to relitigate every example or win a debate. The history has already been discussed.
The leadership responsibility is clarity.
The decision can be difficult without being vague. It can be direct without being cold. It can acknowledge the person's effort or strengths without creating false uncertainty about the outcome.
The distinction between a person's value and a role-performance decision matters here. Employment decisions are consequential, but they do not require moral judgment about the person.
Avoiding the conversation usually does not protect anyone. It extends uncertainty for the employee, shifts additional load to the team and teaches the organization that explicit standards do not necessarily lead to action.
This article does not prescribe HR or legal procedure. Those depend on jurisdiction, company policy and individual circumstances. The leadership principle is narrower: if a formal process establishes explicit expectations and the required change does not occur, management must be willing to act consistently with the process it created.
When the PIP Succeeds, Trust Must Actually Be Restored
The successful outcome deserves equal seriousness.
If the employee has met the agreed expectations, the manager cannot say "the issue is resolved" while continuing to behave as if it is unresolved.
A successfully completed PIP should return the employee to normal professional expectations.
That does not require amnesia. The past remains part of organizational history. Managers are allowed to remember what happened. But historical context should not become a permanent interpretive filter through which every future event is viewed.
The wrong model is:
PIP completed
↓
Permanent suspicion
↓
Every mistake treated as regression
↓
Reduced autonomy
↓
Career ceiling
A healthier model is:
Performance concern
↓
Explicit expectations
↓
Support + accountability
↓
Demonstrated improvement
↓
Restored trust
↓
Normal autonomy
↓
Continued development
↓
Career progression
The employee does not need to become exceptionally cautious to prove they deserve to remain. They need to demonstrate that they can meet the role's expectations.
Accompaniment Is Not Micromanagement
Managers often become uncertain after a successful PIP. They want to avoid repeating the problem, so they increase monitoring. Some follow-up is reasonable. The question is whether the manager is continuing normal leadership or creating indefinite probation by another name.
Accompaniment looks like regular one-to-ones, clear goals, useful feedback, coaching, discussion of blockers, periodic progress review and development planning.
Micromanagement looks like constant checking, unnecessary approval gates, repeated requests for justification, treating ordinary mistakes as evidence of relapse, reduced autonomy without current cause, and repeatedly reminding the employee that they were once on a PIP.
The difference is not frequency alone. It is purpose.
A weekly one-to-one can create autonomy if it helps remove ambiguity and unblock work. A daily status request can destroy autonomy if it exists mainly to reassure the manager that the employee is still under control.
Strong managers should ask the same question after a PIP that they should ask for any employee: what level of structure helps this person succeed at the level expected of the role?
Recovery Should Eventually Become Development Again
The goal of a successful PIP is not to bring someone back to the minimum acceptable line and freeze them there.
Once improvement is sustained, the management conversation should move from recovery back to growth.
The employee should again be eligible for meaningful responsibility, challenging work, increasing autonomy, capability development and progression based on current readiness.
This does not mean promotions should ignore recent history. Career progression still depends on sustained evidence. But a past PIP should not become an automatic ceiling.
A career framework is useful here because it gives manager and employee a language that is larger than the improvement plan. The conversation can return to capabilities, scope, influence, technical depth, leadership and the evidence required for the next level.
The important shift is psychological and operational:
The question eventually stops being "Are you still performing adequately?" and becomes "What are you becoming ready to do next?"
That is not sentimental. It is simply consistent performance management.
Leadership Has to Be Consistent With Its Own Verdict
A PIP is an unusually explicit management mechanism. Because of that, its credibility depends on consistency before, during and after the formal period.
Before the PIP, expectations should already exist.
During the PIP, evidence, support, accountability and success criteria should remain clear.
At the end, the organization must accept the result it has established.
If the employee did not make the required change, leadership must be prepared for a difficult decision.
If the employee did make the required change, leadership must be prepared to genuinely move forward.
Both require integrity.
The best outcome of a successful PIP is not an employee who works in permanent fear of another mistake. It is an employee who understands the expectations, has demonstrated the ability to meet them, has rebuilt sufficient trust and can return attention to becoming better at the work.
From there, leadership returns to what it should have been doing all along: creating context, setting expectations, giving feedback, removing avoidable ambiguity, creating opportunities and helping people become ready for the next step.
References
- CIPD. Performance management: An introduction. 2026. https://www.cipd.org/en/knowledge/factsheets/performance-factsheet/
- CIPD. Performance feedback: An evidence review. 2022. https://www.cipd.org/uk/knowledge/evidence-reviews/performance-feedback/