Before You Put Them on a Performance Plan

The moment before the decision

You’ve been watching it for weeks.

Maybe months.

Something is clearly off:

• output dropped
• ownership slipped
• follow-through is inconsistent

You’re considering a PIP.

The assumption underneath

A performance plan assumes something specific:

The employee understands the role, but is not meeting expectations.

That’s a strong assumption.

And often, it’s wrong.

What gets missed

Before performance drops, something usually changes:

• role scope shifted
• manager changed
• team structure evolved
• expectations moved

If that shift isn’t understood, the diagnosis is incomplete.

What gets misread

Managers often interpret:

• confusion → as lack of accountability
• hesitation → as lack of ownership
• inconsistency → as lack of discipline

But those behaviors can come from:

• unclear expectations
• role misfit
• structural friction

The hidden risk

A PIP formalizes the wrong story.

It tells the employee:

• the issue is execution
• the solution is effort

If the real issue is structural or contextual, this backfires.

You don’t fix the problem.

You accelerate the breakdown.

What to do before acting

Pause and diagnose:

• What changed before the decline?
• Was there a shift in role, manager, or expectations?
• Where does the employee seem unclear vs unwilling?

These are different problems.

They require different decisions.

The better path

If it’s a clarity issue:

• redefine expectations
• tighten feedback loops
• reduce ambiguity

If it’s a fit issue:

• adjust scope
• reconsider role alignment

Only if the role is clear and stable should you move to performance enforcement.

The takeaway

A PIP should follow clarity.

Not replace it.

Most teams don’t have a performance problem.

They have a diagnosis problem.

---

Before you formalize the solution, make sure you understand the problem.
That’s the difference between correction and damage.