Before the PIP: diagnosing a slump

A rep who set nine meetings a month in the fall set three in February and two in March. The dashboard is unambiguous, and the standard corporate reflex is now loading: a performance improvement plan, thirty days, metrics attached. Here is the problem with that reflex. A PIP is a treatment, and the dashboard has only given you a symptom. Prescribing before diagnosing fails in medicine and it fails in management, because a slump is one of four different problems wearing the same numbers, and three of the four are fixable by moves a PIP never makes.

The four slumps

Skill. Something in the mechanics degraded. An opener drifted, a new objection is going unanswered, the meeting ask got soft. You find this in the recordings, not the metrics: pull five recent calls and five from the rep's good months and listen for the difference. The fix is coaching, and specifically one skill at a time, starting with whichever broken link sits earliest in the call.

Will. The mechanics are intact but the energy is gone: fewer dials, longer gaps between call blocks, the discretionary effort quietly withdrawn. Before labeling it attitude, check what the will is responding to. Months of unanswered dials, a changed comp plan, a promotion that went elsewhere, meetings that AEs no-show. Much of what reads as low motivation is a rational response to a broken loop, the point we made in call reluctance is a design problem. The fix is a direct conversation about what changed, and often a repair to the loop rather than to the rep.

List. The rep is fine and the territory died. A segment got exhausted, a data source went stale, the accounts that answered in October are picked over by April. This one hides best, because activity stays high while results fall, and it masquerades as a skill problem until you split the numbers: if connect and conversation rates collapsed while call quality held, the list is the patient. The test is cheap. Give the rep fifty accounts from a segment that is currently converting for someone else and watch what two weeks produce.

Life. Something outside work is taking the hours or the attention. You are not entitled to the details, and you do not need them. You need to offer slack honestly and watch whether the person takes it. A strong rep in a hard season is an asset worth carrying for a quarter; most come back, and they remember who carried them.

Diagnosis is a week, not a quarter

None of this requires a committee. Recordings, a split of the funnel numbers by segment, one honest conversation: a week of manager effort, most of it listening. The order matters, though. Check the list before you judge the skill, because a dead territory makes every rep look broken, and check the loop before you judge the will. A useful forcing question for yourself is whether a rep you consider strong would hit the number with this list and this loop. If the honest answer is no, the slump is not about the rep, a possibility we planned for in get a baseline before you set goals.

The PIP still exists at the end of this road, but as the last diagnostic, not the first: it is the tool for the case where the skill fix was coached, the loop was repaired, the list was proven live, and the numbers still did not move. Reaching for it first does not just misdiagnose the rep. It teaches the rest of the team that slumps are prosecuted rather than investigated, and reps on that team stop telling you the truth about their pipeline.

Diagnosing slumps is a management job, and it is one of the jobs baked into a CommandVA seat: recordings reviewed, funnels split by segment weekly, lists refreshed before they die, so a slump gets caught as a trend rather than a quarter-end surprise. If you are staring at a dashboard and drafting a PIP, book a strategy call first. Bring the numbers, and we will help you figure out which of the four you are actually looking at.