# The Prep Work Before a Coaching 1:1 Is the Coaching. The Meeting Is Just Delivery.

> Most managers treat 1:1 prep as five minutes of CRM-scanning. That's why the conversation changes nothing.

By Greg McCallum, founder of PeerLab. Published 2026-11-18 in Coaching & 1:1s. Source: https://www.peerlab.ai/blog/coaching-1on1-prep-is-the-coaching/

If your rep leaves a 1:1 with the same skill gaps they walked in with, the problem almost certainly started before you sat down. Not in the room. Before it. The meeting didn't fail you. You arrived at the meeting without a diagnosis, and a conversation without a diagnosis is just a catch-up with a calendar invite.

This is the part most coaching advice skips, because it's not glamorous. It doesn't involve active listening frameworks or the perfect question. It's just work you do alone, quietly, before the rep shows up. And it's the work that determines whether anything changes.

## Why the meeting can't do what you're asking it to do

Most managers walk into a coaching 1:1 with a vague impression. Something like: "Emma's pipeline looks light" or "Jake seems to be struggling with enterprise accounts." That's not a diagnosis. That's a symptom, loosely observed.

What happens next is predictable. The manager asks open questions hoping the conversation will surface the real issue. The rep talks. The manager listens. Something comes up that feels relevant. The manager offers some advice. The rep nods. The meeting ends. Nothing moves.

The error is structural. You cannot build a diagnosis inside the meeting, because the meeting is too short, too social, and too reactive for that. The rep is performing. You are managing the relationship in real time. Neither of you is in a good position to do careful diagnostic thinking.

The conversation can only deliver a diagnosis that already exists. If you don't have one before you start, you're not coaching. You're chatting.

## What proper prep actually looks like

It is three things, done in sequence, in about 20 minutes if you do it regularly.

**1. Pick one competency. One.**

Not "Emma's prospecting." A specific competency within prospecting. Is it cold call opening? The ability to create urgency in a voicemail sequence? The quality of her pattern interrupts? If you use a structured framework, name the competency precisely. If you don't, write a single sentence that describes the behaviour you're examining.

The reason to pick one is that reps cannot absorb skill feedback on multiple dimensions in a single sitting, and managers who try to cover everything end up covering nothing. One competency, examined properly, produces movement. Five competencies, touched lightly, produces a rep who feels vaguely criticised.

**2. Find two or three pieces of concrete evidence.**

Not impressions. Evidence. This means call recordings, email copy, deal notes, pipeline data, or anything else you can point to. You are looking for specific moments: the sentence where the discovery question collapsed into a feature pitch, the email subject line that buried the hook, the stage where every deal seems to stall.

If you cannot find two pieces of evidence for the competency you've chosen, either you haven't looked properly or you've chosen the wrong competency. Either way, that's useful information and you should know it before the meeting, not during it.

This is where a tool like the [Cold Call Talk-to-Listen Ratio Scorecard](https://www.peerlab.ai/library/cold-call-talk-to-listen-ratio-scorecard/) earns its place: not in the meeting, but in your prep, as a concrete artefact you've already reviewed before the conversation starts.

**3. Form a falsifiable hypothesis.**

Not "Emma struggles with discovery." That's a verdict. A hypothesis sounds like: "I think Emma is running her discovery questions in the right order, but she's not pausing long enough after each one to let the prospect elaborate, so the calls produce surface-level intel rather than buyer logic."

Falsifiable means the rep could prove you wrong. That matters, because sometimes they do. The hypothesis gets tested in the conversation, not confirmed by it. If you arrive with a verdict, you'll hear everything through it. If you arrive with a hypothesis, you'll stay genuinely curious, and the rep will feel that difference.

## The discipline that separates good managers from box-tickers

Here is what I have seen across three CCO roles and roughly 400 managers I've worked alongside or developed: the ones whose reps improve consistently do not have better instincts in the room. They do better work before the room.

They review a call recording on Tuesday morning, not on the walk from their desk to the meeting room. They write a sentence or two about what they observed before they open the conversation. When the rep says something that contradicts their hypothesis, they update it rather than bulldozing through.

The ones whose 1:1s produce nothing treat prep as the thing they do when there's time. There is never time. The 20 minutes gets cannibalised by the pipeline call or the Slack thread. So they arrive empty-handed and hope the conversation does the work.

It doesn't.

## A simple prep structure you can run every week

| Step | What you're doing | Time |
|---|---|---|
| Pull one competency | Review recent activity, pick the highest-leverage skill gap | 5 min |
| Find the evidence | Two to three specific, citable moments | 10 min |
| Write the hypothesis | One sentence, falsifiable, behavioural | 3 min |
| Prep one question | The question that tests the hypothesis without telegraphing the answer | 2 min |

Total: 20 minutes. If you're doing this for eight reps weekly, that's under three hours of focused prep time for all your 1:1s. That is not a time problem. That is a priority problem.

The [Team Skill-Gap Heatmap Generator](https://www.peerlab.ai/library/tools/team-skill-gap-heatmap-generator/) can help you decide which competency to focus on for which rep each week, particularly if you're trying to triage across a larger team and you want something more systematic than gut feel.

## What the meeting is actually for

Once you have your competency, your evidence, and your hypothesis, the meeting has a clear job. It is for delivery, testing, and agreement.

You share what you observed, specifically and without judgment. You ask the question you prepared. You listen to whether the rep's account matches your hypothesis or complicates it. You update the hypothesis if needed. You agree on one thing to practise before the next session, and you write it down.

That's it. The meeting is not the place for discovery. The discovery already happened. The meeting is the place for the rep to receive a clear, evidence-based picture of one skill gap and to leave with a concrete next step.

Thirty minutes in the room is plenty for that. It is nowhere near enough to do everything that some managers try to cram into it, and it is exactly the reason so many 1:1s produce goodwill without producing growth.

The coaching happened before you said hello. The meeting is just the handoff.
