The 1:1 Template That Replaces Pipeline Review With Actual Coaching
A four-part structure — skill focus, evidence, practice rep, commitment — that gets a weekly 1:1 to actually develop someone, instead of just walking the same deals the CRM already shows.
Sit in on a hundred sales manager 1:1s and you'll see the same meeting wearing a hundred different deal names. "Where's Acme at?" "Did legal get back to you on Meridian?" "What do you need to close Northwind by Friday?" Thirty minutes of deal administration, dressed up as management, delivering nothing the CRM didn't already show before the call started. That's not coaching. It's a status meeting with a more expensive attendee list, and the fact that it happens weekly, forever, without making the rep measurably better at anything, is a big part of why so many teams plateau at roughly the skill level they hired at.
What pipeline review actually optimises for
Pipeline review persists because it solves the manager's problem, not the rep's. It calms forecast anxiety. It requires no diagnostic skill beyond recall of deal facts the manager already half-knows. And it feels productive in the moment — thirty minutes, several deals discussed, action items assigned — without ever requiring the manager to name a skill gap, produce evidence for it, or risk the mild discomfort of telling someone directly what they're doing wrong. It's coaching-shaped work that carefully avoids the one thing coaching actually requires.
The fix isn't to stop discussing deals. It's to stop treating deal discussion as the whole meeting, and to build a structure that makes the actual coaching happen whether or not the manager feels like doing the harder version of the job that day.
The four-part structure
1. Name the skill. Pick exactly one competency for this week, stated specifically enough that a stranger could recognise it in a recording. Not "communication." Not "confidence." Something like "asking a second consecutive open question after the prospect answers the first one" or "quantifying the cost of inaction before presenting a number." One skill, named precisely, beats three vague themes every time — a rep can't practise "be more strategic" between now and next Tuesday, but they can practise a specific, observable behaviour. A structured instrument like a Discovery Call Scorecard is useful here for a reason beyond scoring calls: it gives you a shared vocabulary of named competencies to pick from, instead of inventing new language for the same gap every week.
2. Cite the evidence. Not an impression — a moment. "At six minutes into Tuesday's call with Meridian, the prospect said their current process was 'fine, just slow,' and you moved straight to your pitch instead of asking what 'slow' was costing them." If you can't produce a specific, timestamped moment, you haven't earned the right to have this conversation yet. Go get the evidence first — listen to the call, pull the clip, then book the 1:1. A 1:1 built on opinion instead of evidence trains reps to argue with your feelings rather than examine their behaviour.
3. Run the practice rep. Four to six minutes, in the room, right now. Roleplay the exact scenario the rep will face again this week — not a generic objection drill, the specific situation from the evidence you just cited. This is the part managers skip most often, usually citing time, and it's the part that actually changes behaviour; naming a gap without rehearsing the fix is a lecture, not coaching. A loose structure like the GROW Model Coaching Conversation Script keeps the roleplay from sliding back into the manager talking at the rep for four minutes instead of the rep practising anything.
4. Set the commitment. One specific, checkable action for the next seven days, tied directly to the named skill, written down where both people can see it. "I will ask a follow-up question after every first answer to an open question, on every discovery call this week" is checkable. "I'll work on discovery" is not. The commitment only means something if next week's 1:1 opens by checking it — not by moving straight to the next deal.
What this looks like in the room
A twenty-five-minute version: five minutes on the two deals that genuinely need a decision this week — real pipeline still gets discussed, just not as the whole meeting. Then the four parts. Skill: "quantifying cost of inaction before proposing." Evidence: the Meridian clip, timestamped, quoted. Practice rep: five minutes rehearsing the exact follow-up question the rep should have asked, using this week's live deal as the scenario. Commitment: ask the cost-of-inaction question on every qualified call this week, and come back with what the prospect actually said. Twenty-five minutes, one skill, one piece of evidence, five minutes of rehearsal, one thing to check next week. That's the entire template.
Where managers sabotage this without noticing
| Failure mode | What it looks like | Why it defeats the point |
|---|---|---|
| Naming a trait, not a skill | "Be more confident on calls" | Nothing to rehearse, nothing to check next week |
| Evidence-skipping | Going straight from a vague impression to advice | Trains reps to negotiate your opinion instead of examining their behaviour |
| Cutting the practice rep for time | "We'll do the roleplay next time" | The rehearsal is the part that changes what happens on the next real call — everything before it is just description |
| Vague commitments | "Try to do better with discovery this week" | Unfalsifiable commitments can't be checked, so they quietly evaporate by the following Monday |
| No follow-up | Next 1:1 opens on a new deal, not last week's commitment | Reps learn within a month that commitments aren't actually tracked, and stop treating them as real |
Most managers who try this and quietly drift back to pipeline review by week three aren't lacking discipline — they're rebuilding the structure from a blank page every single week, which is exhausting, and exhaustion always loses to the path of least resistance. Start from an actual scaffold, like a Sales 1:1 Meeting Agenda Template, so the four parts are already sitting on the page before the meeting starts, rather than something you have to remember to construct under time pressure with a rep sitting across from you.
None of this requires abandoning the pipeline — that's what the CRM is for, and a manager should still glance at it before the call starts. It requires deciding that a 1:1 exists to build a skill that outlives this quarter's deals, not to say out loud, in a more expensive room, what a dashboard already told everyone an hour earlier.