Run an Adoption Review When Managers Stop Coaching

Usage declines deserve a careful adoption review. Begin with one narrow question: where did a manager led coaching habit lose space in the week? Activity reports show recorded participation. They do not establish skill growth, program value, manager effort, or seller intent. A low count offers a starting point for inquiry, not a verdict on people.

Build a short record before speaking with anyone. Pull one defined period, assigned teams, manager names, completed reviews, practice sessions, and recurring meetings known within account records. Place every entry beside a source and date. A report differs from a manager recollection. A calendar invitation differs from a completed discussion. Those distinctions keep a review factual when memories differ.

Choose a comparison with a purpose. One active group beside one quiet group often offers more useful detail than an account wide average. Look for similar seller roles, related sales work, or a shared launch date. The comparison does not rank people. Instead, use those records to locate a practical difference. East holds a Tuesday forecast meeting. West moved forecast work into individual sessions after a territory change. Those facts point toward schedule and context rather than blame.

In a fictional planning meeting, CSM Dana says, “East completed three manager reviews during August. West completed none. I want to understand each weekly rhythm before we select a next step.” Enablement leader Rob replies, “West received a new manager with a larger territory.” Dana asks, “Which meeting carries forecast discussion now, and who attends?” Rob answers, “The manager holds short individual sessions on Wednesday. No shared review exists.” Dana records both statements without calling West disengaged.

Dana then requests a short manager interview. Her opening stays direct. “I am reviewing how coaching fits beside current work. The activity record shows no completed shared reviews during August. What replaced the earlier meeting?” A manager during a territory handover might describe a changed schedule, uneven seller availability, unfamiliar deal stages, or an agenda crowded by new decisions. None of those answers proves a lasting problem.

Prepare specific questions before each interview. Ask which existing meeting reaches relevant sellers, how long the manager controls the agenda, which call type provides a useful coaching moment, and what would make a five minute review relevant. Ask about the latest meeting where coaching had a place. Request detail. “Who attended?” “What filled most of the time?” “Where did the agenda run long?” A concrete recollection provides a sounder starting point than a broad statement about workload.

Listen for a workflow decision rather than a promise. A fictional manager might say, “My team needs support with late stage calls, yet a separate review has no place on my calendar.” Dana avoids a larger program pitch. She asks, “Would you select one Friday call and reserve eight minutes during Wednesday’s meeting for a discussion?” Rob approves or declines the experiment. The manager selects a call and meeting slot. State each decision plainly so no one assumes a hidden commitment.

Keep evidence and explanation apart in the review sheet. Dana uses three fields: verified activity, manager explanation, and next experiment. Under verified activity, she writes, “No completed shared review during August, report dated September 2.” Under manager explanation, she writes, “Wednesday individual sessions replaced Monday group forecast meeting after territory handover, interview dated September 4.” Under next experiment, she writes, “Manager selects one late stage call on Friday and leads one discussion during Wednesday session for two weeks.” The sheet records a plan without presenting interpretation as fact.

Set a clear scope for every review. Do not ask a manager to explain every training outcome in one meeting. Focus on the behavior under review. When the account agreed on manager led call review, discuss meeting access, call selection, and manager time. A sales leader who wants a broader performance discussion needs a separate owner or forum. This keeps a workflow review from becoming an unsupported debate about revenue or seller skill.

Rob worries about asking managers for more effort. Dana recognizes his concern and keeps the decision small. “The record shows no shared review. We are testing whether one existing session holds room for one call moment.” Rob asks whether managers need a prompt. Dana offers one sentence: “Bring one call where a buyer question changed the direction of discussion.” The manager chooses the call. Sellers understand why preparation matters.

During the review, show information in sequence. Start with the agreed adoption plan. Show the activity record. Share manager explanations in their own words, without turning one person’s view into an account wide claim. Then seek a decision about the experiment. Dana asks, “Does the Wednesday session offer room for an eight minute call discussion during the next two weeks?” A yes needs an owner, date, and source for follow up evidence. A no needs an alternate meeting or an agreement to pause.

Fictional manager Leila accepts Dana’s proposal. Leila says, “Wednesday begins with deal updates. I will place the call discussion after the second update and before open items.” Dana asks who will select the recording. Leila answers, “I will choose Friday afternoon and send a time marker by Monday.” Rob adds, “I will attend the first session and report whether the agenda held.” Their language establishes a workable sequence. No one claims an outcome before either session occurs.

After the first session, collect evidence tied only to the experiment. Did Leila select a call? Did the Wednesday discussion occur? How many sellers attended? Which part of the agenda changed? A short manager note answers each question. Dana does not need a lengthy survey or a broad seller score. If Leila reports a late time marker, Dana records timing as an obstacle. If the discussion lasts twelve minutes and displaces deal updates, Dana records duration. Both details inform a later choice.

Adjust one element during the second session rather than rebuilding the process. If discussion ran long, Leila asks sellers to listen from minute twelve through minute sixteen before Wednesday. If no useful call appeared, she asks every seller to nominate one prospect question by Tuesday. If individual meetings reduced attendance, she moves discussion into a standing team call. Each adjustment responds to one observation from the first session.

The customer owns the diagnosis. Dana organizes evidence, asks focused questions, and makes next actions visible. She avoids saying a report proves managers stopped caring. A report shows recorded activity only. Managers and sales leaders provide context around meeting changes, territory shifts, and priorities. Place their explanations beside the record with a date and named source.

For a fictional practice, give a colleague this setup: East recorded three August reviews, West recorded none, and West changed managers on August 5. Open with the activity sheet. Ask fictional Leila which recurring meeting still exists and what one call review would cover. When Leila selects Wednesday at 10:00, enter “Leila sends one late stage call marker by Monday, September 14” in the next experiment field. Send Leila a dated follow up note before ending the practice.