Performance Improvement Plans the Right Way

When Elena joined a 90-person logistics company in Lagos, the customer support team had a habit everyone hated. Managers called a document a "PIP" only after they had already decided to fire someone. Employees knew it. Managers knew it. The document was not a plan. It was a receipt.

That is the fastest way to make performance management look dishonest.

A performance improvement plan should do two things at the same time: give the employee a real, structured chance to improve, and create a clear record if the role still cannot work. If either half is fake, the plan fails.

Use a PIP for the right problems

A PIP is for performance gaps that can be described, measured, supported, and reviewed within a defined period. It is not the right tool for every issue.

Use a PIP when:

• The employee is missing clear role expectations.
• The gap has continued after normal coaching.
• The manager can define what acceptable performance looks like.
• The company can offer support that might realistically help.
• The timeline is long enough for change to show.

Do not use a PIP when:

• The issue is serious misconduct.
• The role is redundant.
• The manager cannot explain the gap beyond "attitude."
• The employee has not received basic feedback before.
• The timeline is so short that success is impossible.

Set the timeline deliberately

Most PIPs run 30, 60, or 90 days. The right length depends on the role and the behavior being measured.

Thirty days can work for simple, high-frequency tasks: attendance, ticket handling, basic sales activity, documentation habits, or response times. Sixty days is better for roles with weekly outputs such as project delivery, account management, or manager behaviors. Ninety days is appropriate when the employee needs to demonstrate sustained change across a cycle, such as a quarter of sales pipeline management or a full sprint planning process.

Do not choose a short timeline because the manager is tired. Choose the shortest fair timeline in which success can be observed.

Write goals that leave no room for guessing

The employee should be able to read the PIP and answer three questions:

• What exactly must change?
• How will success be measured?
• What support will the company provide?

Use observable measures. If the gap is quality, define the defect rate, rework level, customer complaint count, or review standard. If the gap is communication, define the behavior: status update by 4 p.m. every Friday, stakeholder escalation within one business day, meeting notes sent within 24 hours. If the gap is leadership, define the expected routines: weekly one-to-ones, documented delegation, sprint retro actions, or team engagement response.

Include support that matches the gap

Support is not decoration. A PIP without support reads like a trap.

Match the support to the problem:

• Skill gap: training, shadowing, examples of good work, practice sessions.
• Prioritization gap: weekly planning, written priorities, reduced conflicting work.
• Quality gap: checklists, review gates, peer review, sample outputs.
• Manager behavior gap: coaching, leadership training, HR check-ins, employee feedback.
• Attendance or reliability gap: schedule review, accommodations process where relevant, written expectations.

Hold the conversation like an adult

The first PIP meeting should not feel like an ambush. The manager should be direct about seriousness and equally direct about the company's desire to see improvement.

A useful opening:

"This is a formal performance improvement plan. That means the concerns are serious, and your employment may be at risk if the expectations are not met. It also means we are giving you a clear plan, support, and review dates so you know exactly what success requires."

Then walk through the document slowly. Ask the employee to explain the expectations back in their own words. Not as a test, but as a clarity check.

Document employee comments. If they raise a medical issue, protected leave, harassment concern, workload impossibility, or lack of resources, pause and assess before forcing the process forward.

Check in weekly

A PIP that disappears until day 30 is poor management. Weekly check-ins create fairness and better evidence.

Each check-in should cover:

• Progress against each metric.
• Evidence reviewed.
• What changed since last week.
• What support was provided.
• What support is still needed.
• Whether the employee agrees with the progress summary.
• The next week's priorities.

Know what success looks like

Success means the employee meets the stated expectations by the deadline and can sustain the improvement without extraordinary manager effort. Do not move the goalposts because the manager has lost confidence. If the employee meets the written plan, say so.

Failure means the employee does not meet the stated expectations despite support and reasonable opportunity. The evidence should be visible in the weekly notes, not discovered at the final meeting.

Sometimes the answer is extension. Extend only when there is a clear reason:

• The employee improved materially but needs one more cycle.
• A business event disrupted the measurement period.
• The company did not provide promised support.
• A medical, accommodation, or leave issue changed the timeline.

Do not extend because the manager is avoiding a hard decision.

Use a real PIP example

Here is a condensed example for a customer success manager:

Success measures:

• Update renewal forecast every Friday by 3 p.m. with next step, risk level, decision maker, and expected close date.
• Achieve 85 percent forecast accuracy for two consecutive monthly reviews.
• Escalate any account with red risk within one business day.
• Complete renewal strategy notes for the top 15 accounts by the first Monday of each month.

Support:

• Manager reviews forecast every Tuesday for 30 minutes.
• Senior CSM provides two shadow sessions.
• RevOps creates a dashboard for at-risk renewals.
• Workload reduced from 42 accounts to 34 during the plan.

Timeline:

• 60 days, with weekly check-ins.
• Final review on July 31.

Possible outcomes:

• Successful completion and return to normal coaching.
• Extension up to 30 days if substantial progress is shown.
• Role reassignment if a suitable opening exists.
• Termination if expectations are not met.

Key takeaways

• A PIP is a real improvement plan, not a staged paper trail.
• Use specific, measurable goals and a timeline that fits the work.
• The company must provide meaningful support.
• Weekly check-ins protect both fairness and evidence quality.
• If the employee succeeds, honor the plan.
• If dismissal follows, the PIP should make the reason clear and unsurprising.