Repair a Coaching Cadence After a Busy Quarter
Work with managers to restart a practice routine after urgent sales work displaced the routine.
A busy quarter often displaces manager coaching. Forecast work, staffing changes, major deals, and customer escalations take over familiar meeting time. A pause does not settle whether a routine deserves another attempt. First, build an accurate account of how prior sessions worked and where sellers still receive help. Start with one behavior, one existing meeting, and one manager owner. A small restart creates a useful test without creating an extra program.
Review the old cadence without blame. Ask when reviews stopped, which work displaced them, and whether any part survived inside another meeting. A manager might say coaching disappeared, then describe giving detailed feedback during deal review. Ask how a seller receives feedback now. Ask who selects a conversation excerpt. Ask who records a retry and checks progress later. Those answers show whether a team needs a new structure or a repair to an existing habit.
In this fictional practice situation, CSM Cal meets regional manager Rosa after leadership review. Cal asks, “When did call review stop?” Rosa replies, “Forecast pressure took Fridays from mid June through quarter close.” Cal asks, “Which meeting still brings sellers and managers together?” Rosa says, “Tuesday deal review. Every minute has a competing use.” Cal asks, “Where does your group decide whether an implementation concern deserves follow up?” Rosa answers, “After deal selection.” Cal proposes ten minutes for one seller’s customer moment. Rosa agrees to test one session with an active opportunity.
Cal has found a decision Rosa already makes and connected coaching evidence to work on her agenda. His proposal does not ask her to restore every Friday review. A separate invite would add attendance questions and leave purpose unclear. Yet Tuesday deal review should not turn into an unfocused listening session. Before scheduling, Rosa and Cal agree on one question. A seller brings a moment after a buyer raises implementation. Rosa listens for whether the seller explored impact, identified decision ownership, or set a next conversation. Feedback and retry planning end after ten minutes.
Name ownership before anyone searches for material. Rosa chooses a seller by Thursday afternoon. The seller selects a short excerpt and sends a note before Monday noon. The note names one decision where help is needed. Rosa listens ahead of Tuesday and writes one observation plus one question. Cal keeps the session record and confirms access through the team’s existing process. Clear ownership protects preparation time. Without named owners, a seller searches at the last minute, a manager arrives without context, and feedback turns into broad opinion.
In the fictional Rosa session, seller Nia writes, “I want to know whether I identified who owns the implementation review.” Rosa hears a buyer raise implementation. Nia answers with a timeline, then moves on. Rosa says, “You gave dates after the concern. Which question would show who needs to approve review?” Nia responds, “Who besides you needs to sign off before implementation starts?” Rosa asks Nia to say the question in a natural reply. Nia practices a full response, then chooses a live customer conversation for her retry.
Different schedules call for different containers. Rosa might reserve ten minutes every other Tuesday. A manager with a rotating calendar might select one deal review each month and book the next date before leaving the current one. A new manager might ask an experienced peer to observe a first session. A team working through urgent renewals might focus on renewal conversations instead of new opportunities. Keep the observed behavior and retry. Change meeting length, participant count, or source conversation only when local work requires a change.
Time objections deserve a calendar question rather than a debate. In a fictional practice conversation, manager Devon says, “My team has no room for coaching before the next forecast.” Cal asks, “Which meeting asks you to assess a seller’s judgment this week?” Devon answers, “Pipeline review on Wednesday.” Cal asks where stalled conversations come up. Devon points to the final fifteen minutes. Cal asks whether one selected customer moment would help assess why a deal stalled. Devon agrees, with a two minute excerpt chosen before Wednesday. Cal records the seller, behavior, meeting slot, and end time.
Protect seller dignity during review. Rosa begins with Nia’s stated goal rather than playing an excerpt without context. She asks Nia what she hoped the buyer would do next. After listening, Rosa names one observable choice. She avoids a label such as “Be more confident.” Nia receives a question and a chance to try a revised response. Other attendees add observations only when Rosa invites them, and each observation refers to the same moment. This structure keeps a practice session from becoming a public scorecard.
Use evidence suited to a small routine. Attendance alone says little. Rosa checks whether Nia arrived prepared, whether Rosa named an observable behavior, whether a retry was chosen, and whether a later conversation produced a follow up note. She asks Nia whether feedback felt specific enough for use. She asks herself whether advance listening fit Tuesday preparation. After each session, choose one next action. Repeat the format, shorten preparation, move to another existing meeting, or pause until material access is resolved.
Keep a concise discussion record after every attempt. Record date, meeting, seller, customer moment, behavior, feedback point, retry, owner, and next check in. Plain language makes later review easier. “Nia will ask who owns implementation review during Thursday customer discussion” gives Rosa an observable follow up. “Improve discovery” does not. Share the record only with people involved through the established team channel. The record should describe what was heard and agreed, not an interpretation of buyer intent.
Use the record when a session misses its mark. Suppose Arun arrives with a five minute excerpt and an unclear request. Rosa does not spend Tuesday sorting through every detail. She asks Arun to choose one buyer response before the next session and write his intended outcome in one sentence. Cal records preparation as incomplete, then leaves the behavior field open. This separates an unfinished session from a failed seller. Arun receives a clear preparation task, and Rosa retains a useful ten minute slot for another seller if needed.
Two weeks later, Rosa meets Cal and Nia for fifteen minutes. Rosa says advance listening took longer than expected. Nia says she used her revised question in a later conversation, yet the buyer asked for a follow up with an operations lead. They keep the Tuesday slot and shorten preparation. Nia now sends a two sentence note plus a one minute excerpt. Rosa sets the next session for September 16 and chooses seller Arun. Before leaving, she opens the calendar, adds Arun’s Monday deadline, and writes the exact behavior he will bring to review.
Practice these next
Use a strong manager’s coaching routine as evidence for an adoption conversation across other teams.
Give a support executive a fact based update plan while technical investigation continues.
Build an ownership plan when product changes reach agents after customers have already begun asking questions.
Review agent behavior and customer impact when contact routing changes across service teams.
How a customer success manager can communicate confirmed facts while an incident review remains open.
A customer success manager prepares an executive discussion with verified adoption records and clear decision ownership.