Renew a Coaching Program With Uneven Manager Adoption

Uneven manager adoption deserves an honest renewal review. Participation numbers describe activity, not program value or manager intent. A renewal conversation needs a shared record, local context, and a limited test before price receives attention. An enablement leader deserves room to decide whether a routine fits current teams. A renewal manager earns trust by naming weak participation plainly and by refusing to turn guesses into explanations.

Start with the meaning of each record. A completed review might mean a manager opened a session, submitted a note, or held a scheduled discussion. Each event describes a different behavior. Ask which event appears in every field. Ask whether all regions follow one schedule. Compare matching reporting periods rather than a full quarter beside a partial month. A monthly total hides a manager who worked steadily during January and stopped in February. A weekly view shows where a conversation needs more detail.

Bring a short fact record to the review. Include active managers, scheduled reviews, completed reviews, and comments supplied by customer participants. Put a source and date beside every entry. Keep possible causes in a separate section called questions. Low activity might follow a manager change, a blocked calendar, an unclear expectation, or no local owner. None of those explanations belongs in a report until a customer participant confirms one. This separation keeps the meeting focused when different leaders remember events differently.

In a fictional account review, Alex shares a table covering March through August. He says, “Twelve of twenty four managers recorded one or more reviews. Six recorded reviews during five or more months. North recorded forty two reviews. East recorded nine. Do these records include every completed session?” Priya, a fictional enablement leader, asks her operations lead to check. She then says, “North uses Friday reviews. East changed managers in June.” Alex records both statements as context. He does not label either region successful or failing.

Alex next studies North with Priya. He asks who selected Friday, how missed sessions receive attention, and where managers find examples of feedback language. Priya introduces Morgan, a fictional regional director. Morgan explains, “Each manager brings one call and one question. We spend ten minutes on a call before our team meeting. A new manager sits with an experienced manager for a first review.” Alex asks Morgan for the meeting invitation and a blank review note. Those items reveal whether the habit rests on a usable structure or entirely on Morgan’s personal effort.

The East record needs separate interviews. Alex speaks with two fictional managers one at a time. One says, “I joined in June. My calendar has forecast sessions and hiring interviews, yet no coaching block.” Another says, “I saw a review process during onboarding, then no leader asked for a record.” Neither answer proves opposition to coaching. Both answers point to a missing operating detail. Alex records the exact words, then asks Priya which small experiment she wants first: a calendar block, a sample note, or a director request.

Priya chooses a calendar block because East managers control their own schedules. She selects four managers with active seller teams. Morgan agrees to share his Friday invitation and his blank note. Each selected manager places one weekly coaching session on a calendar for four weeks. Alex will send Priya a weekly count of scheduled and completed sessions. After week two, Priya will ask every participant, “What made this routine easy or hard to keep?” The question seeks useful friction without asking managers to defend a low number.

Write each action beside one owner and one date. Alex owns a weekly count and a brief check in note. Priya owns the director request and manager selection. Morgan owns the example invitation and note. Each selected manager owns a scheduled session. If someone must approve an action, name the approver beside the working owner. Shared ownership often leaves everyone waiting. A compact action record gives Priya a way to notice a missed step before four weeks pass.

Keep commercial terms beside program judgment, rather than in front of program judgment. Priya asks why her organization should renew licenses when half of managers have little activity. Alex replies, “The record shows uneven use. We have four East managers testing a weekly routine through September twenty eighth. After attendance and manager comments arrive, we will discuss the participating group and an appropriate license count with procurement.” He offers no promise about a turnaround. Priya has an honest choice between a smaller group, a revised routine, or an end to the program.

A discount request needs the same calm record. In the fictional meeting, Priya says, “Procurement will ask for a lower price because half our managers did not participate.” Alex answers, “Please include procurement after we review the four week record. I will bring current usage, the tested group, and a proposal for the next period. Their team will see the same record.” This reply respects procurement and avoids a price concession tied to an untested prediction. Alex also asks Priya what decision procurement needs from her before a terms meeting begins.

After every conversation, update one renewal document. Put the reporting window first. Separate confirmed usage, customer context, unanswered questions, actions, owners, and review date. Limit broad circulation of individual manager names where possible. Send Priya a short draft before sharing more widely and ask, “Which statement needs correction before other leaders read this?” An early correction prevents a later dispute over a remembered remark. Priya also sees where a detail lacks a source and where a follow up question needs an owner.

Watch signals during the test instead of waiting for a final total. A manager who schedules sessions and records no review might need help with the note. A manager who records every review without comments might treat the process as administration. A director who attends one meeting and vanishes might leave managers without reinforcement. Alex raises one observed signal at a time. He asks Priya for a response shaped by a manager’s local conditions. He does not propose one universal remedy for every region.

On September twenty eighth, Alex and Priya reopen their fictional record. Three of four managers scheduled four sessions. Two completed every session. One missed two sessions during a hiring week. Their comments favor a ready agenda and request more examples of feedback language. Priya chooses another month with the four managers. Morgan agrees to lead a short practice session using an anonymized call. Alex waits for Priya’s participant list before recording a proposed license count.

Priya ends the meeting by opening her calendar with Alex present. She sends Morgan a request for the anonymized call by October first, invites the four managers to an October eighth practice session, and asks Alex for the next weekly activity note on October fifteenth. Alex places those dates in the renewal document before the call closes.