Most coaching sessions have an information problem and a retention problem. The information problem: the manager spends most of the session telling the rep things, rather than having the rep work through the problem themselves. The retention problem: even when good ideas come out of a session, they fade because nothing follows up on them.
Thirty minutes is enough time to do meaningful coaching, but only if the structure is right. This is what we have seen work from working with early-access sales managers, and what shapes how Brevity approaches coaching session design.
Before the Session: One Specific Focus
The most common coaching session failure happens before the session starts. The manager has a general sense of what they want to work on but no specific anchor: "we'll talk about how the last few calls went" or "let's review your pipeline." These are not coaching sessions. They are check-ins, and they produce check-in outcomes: the rep reports status, the manager offers encouragement or concern, and nothing changes.
Effective coaching sessions start with a specific observation tied to a specific behavior. This comes from call data, from a deal debrief, or from the manager's own observation. The specificity matters. "Your discovery calls could be stronger" is not a coaching anchor. "In three of your last four discovery calls, you moved to demo stage before the prospect had confirmed budget authority" is a coaching anchor. You can run a session around that. You cannot run a session around the general version.
If you are using call analysis tools, the preparation work is partly done for you. Brevity's analysis segments calls and surfaces patterns across sessions, which means the manager arrives with specific moments rather than general impressions.
Minutes 0-5: Establish the Anchor Together
Do not arrive with the observation already fully formed and handed to the rep. Arrive with the question. "What do you think happened in that discovery call last Tuesday?" or "Walk me through how you usually handle the budget conversation." This opening serves two purposes: it tells you how much self-awareness the rep has about the issue, and it gives the rep ownership of the diagnosis.
A rep who arrives at the same observation the manager had, through their own reflection, will own the solution differently than a rep who was told what the problem is. The manager's observation is still the anchor. The rep just got there themselves.
This opening also surfaces whether the manager's diagnosis is actually right. Sometimes it is not. A rep who explains their reasoning in a way the manager had not considered changes the shape of the session. That is a good thing.
Minutes 5-20: Practice, Not Discussion
The most common mistake in the middle of a coaching session is spending it talking about what the rep should do differently. Discussion generates understanding. Practice generates capability. They are not the same thing.
Once you have established the specific behavior to work on, spend the bulk of the session practicing it. Run the scenario. Have the rep practice the discovery question sequence. Role-play the objection handling. Do it again. Adjust. Do it again.
This feels uncomfortable for managers who have not run sessions this way. It feels like there is not enough to say. That discomfort is actually a sign the session is working. A rep who has practiced a behavior three times in fifteen minutes has more to show for the session than a rep who listened to fifteen minutes of guidance.
The specificity of the focus makes this possible. If the session is about "being a better listener," you cannot practice it in fifteen minutes in any meaningful way. If the session is about how to respond when a prospect says "we already have a solution," you absolutely can practice that three times and get better.
Minutes 20-28: One Takeaway, Written Down
At the end of the practice segment, the manager and rep should agree on exactly one behavioral change the rep will try in their next three calls. Not five things. Not a general improvement area. One specific thing: "In the next discovery call where the prospect hasn't confirmed budget authority, I will ask this specific question before moving to the demo stage."
That takeaway gets written down by the rep, in their own words. Not in the manager's notes. In the rep's notes, phone, or wherever they will actually see it before their next call. The act of writing it matters. Verbally agreeing to try something produces worse follow-through than writing a specific commitment.
Minutes 28-30: Set the Check-In
The session ends with a specific follow-up trigger: "After your next three discovery calls, let's take ten minutes to debrief on whether you tried this and what happened." Not "let's talk next week." A specific trigger tied to a specific event.
This is the piece that closes the loop. Coaching without a follow-up mechanism trains reps that the session is the end of the process. Sessions with built-in check-ins train reps that the session is a checkpoint in a longer learning cycle. The latter is what actually changes behavior over time.
What This Structure Does Not Fix
This framework works when the manager has the right information going in and when the rep is willing to engage with the practice honestly. It does not fix a situation where the manager's diagnosis is wrong, where the rep is not psychologically safe enough to practice in front of their manager, or where there is no follow-up infrastructure to close the loop.
We are not claiming that thirty minutes is enough time to develop any sales skill. Complex skills like multi-threading a deal or running an enterprise discovery call take months of deliberate work. What thirty minutes is enough for: moving a specific behavior in a specific scenario. That is a smaller target than most managers aim for, and it is the right target.
Better coaching sessions are not about talking more or more skillfully. They are about narrowing the scope until the session can actually produce a change, and then following up to see if it did.
