Your 1:1s Are Status Meetings Wearing a Coaching Costume
If the average manager 1:1 got minuted, most of it would read as a pipeline update. That's not coaching — it's admin with a whiteboard.
Sit in on fifty manager 1:1s, unannounced tally in hand, and count one thing only: how many times a named skill — not a deal, not a stage, not a number — gets mentioned. Discovery questioning. Multi-threading. Objection handling, named as objection handling rather than described as "pushed back and I got them past it." I have run this audit across three companies. Fifty conversations booked in the calendar as "coaching 1:1." Four skill mentions. The other forty-six minutes of every meeting, on average, was deal status delivered to an audience of one.
That is not a coaching problem. It is a labelling problem, and it is worth being blunt about because the mislabel does real damage. A manager who spends 1:1 time asking "where's that Acme deal at" and "when's the contract coming back" is doing legitimate management work. Pipeline needs eyes on it. But calling that coaching, and reporting it up the chain as coaching, lets an organisation believe development is happening when what is actually happening is a status update with slightly better furniture.
The tell is what gets named
Here is the test, and it takes about ninety seconds to run on any 1:1 you have just sat in on or recorded. Go through the transcript and mark every sentence as one of two things: a statement about a deal (stage, value, timeline, next step, who's involved) or a statement about a skill (a named competency, a specific technique, a level of proficiency, a gap, a rep). If your tally comes back 90/10 in favour of deals, you did not run a coaching 1:1. You ran a forecast review with a rep in the room instead of a spreadsheet.
Here is why it matters more than it sounds. Deal talk and skill talk produce different outcomes for the business over completely different timeframes. Deal talk moves this quarter's number, maybe. Skill talk moves every quarter's number, because the rep who gets better at discovery questioning carries that skill into the next fifty deals, not just the one you happened to discuss on Tuesday. A manager who only ever reviews the deal is optimising for a number that resets to zero in ten weeks. A manager who names and grows the skill underneath the deal is compounding.
Why it happens, and it is not laziness
Most sales managers were promoted because they were the best rep on the team, not because anyone taught them how to coach. Pipeline review is the safe default because it requires no diagnostic skill — you just ask "what's happening with X" and listen. Naming a skill gap requires the manager to have watched or heard the actual behaviour, identified what was missing, and to have a vocabulary for it. That is a harder skill than most managers were ever trained in, so the conversation drifts to the thing that is easy to talk about: the deal.
There is also a structural reason. Most sales organisations run a weekly forecast cadence, and the 1:1 sits right next to it on the calendar. It is trivially easy for a manager, thirty seconds into a 1:1, to default to "so where are we on the Acme renewal" because that is the question they just asked in the forecast call an hour earlier. The muscle memory is deal-shaped because the surrounding rhythm of the business is deal-shaped. Nobody built a rhythm around skill development, so skill development borrows fifteen seconds at the end of a conversation that was never really about it.
What the two conversations actually look like
| Status meeting wearing a coaching costume | Actual coaching | |
|---|---|---|
| Opens with | "Where are we on [deal]?" | "I want to talk about the discovery call with [prospect] on Tuesday." |
| Central subject | The account | The behaviour |
| Vocabulary used | Stage, close date, next step, blocker | Named skill, specific technique, level, gap |
| What gets assigned | A task on the deal ("send the MSA by Friday") | A practice rep on the skill ("run three cold discovery calls this week leading with the pain question before the demo request") |
| What the rep remembers a month later | Nothing — it was about someone else's account by then | A specific thing they got better at |
| Who it serves | This quarter's forecast accuracy | This rep's entire tenure |
Neither side of that table is illegitimate on its own. The problem is when the left column is the entire meeting and the manager still calls it coaching on the calendar invite.
The fix costs you nothing but discipline
You do not need new software, a new methodology, or a training budget to fix this. You need one rule: every 1:1 must name a skill in the first two minutes, and the deal, if it comes up at all, comes up as evidence for the skill conversation rather than the other way round. "The Acme call is a good example of where your discovery questioning stalled — let's use it" is a coaching sentence. "Where's Acme at" is not, no matter how warmly you ask it.
If you want structure rather than a rule you're trying to hold in your head, restructure the meeting itself. A fixed agenda that puts the skill conversation first and the deal check second, rather than the other way round, does most of the work by itself — the Sales 1:1 Meeting Agenda Template forces the ordering. And if you are not sure whether your own 1:1s have drifted, run the ninety-second tally test above on your last three recordings, or use something more formal like the Coaching Effectiveness Scorecard for Managers to check the ratio properly rather than trusting your own memory of how the conversation went, which will flatter you.
The other thing worth fixing is the feedback itself once you do name the skill. "You need to be better at discovery" is not coaching either — it is a verdict with nowhere to go. Feedback that names the specific behaviour, the impact it had, and the specific alternative behaviour is what actually changes what a rep does on the next call. The SBI Feedback Model Cheat Sheet is the fastest way to get that structure into your head before your next 1:1, not after it.
The number that should embarrass you
If you want a harder version of the ninety-second test, count minutes instead of sentences. Time how long you spend, across a working week, talking about deals versus talking about skills, across every 1:1 you run. Most managers who do this for the first time are startled by the ratio — not because they didn't know pipeline dominated, but because they assumed the coaching minutes were bigger than they turned out to be. The number rarely lies, which is exactly why most managers have never actually run the clock on it.
Your reps do not need another person checking on the Acme deal. Legal, finance and your own forecast call already do that job adequately. What they need is one person in the building whose job, in that thirty minutes, is to make them measurably better at something specific by Friday. If that person is you and it isn't happening, the fix isn't a new tool. It's renaming the meeting honestly, and then making the content match the new name.