Explore Coaching Needs When Manager Spans Grow

A larger manager span changes the shape of coaching long before a dashboard shows a problem. A revenue leader still sees forecast calls, team meetings, and full calendars. Sellers still receive direction. Individual preparation often loses its place. A manager who listened to a customer call before Friday now reads notes on Monday. A rehearsal becomes a reminder. New hires wait for feedback. An account executive should begin with work managers lost, rather than lead with a broad answer to workload pressure.

Ask for a picture of one useful week before the reorganization. Ask which meetings occurred, who attended, and what each manager did between meetings. Details give a discovery conversation somewhere to go. “We coached often” gives little material. “Each manager listened to one customer call for every seller and spent twenty minutes preparing a difficult next step” gives a usable starting point. Then ask which parts survived after more direct reports arrived. The gap between those routines points toward a practice worth testing.

In a fictional discovery call, Tessa, a revenue leader, tells Omar, “Each manager now supports fourteen sellers, and coaching feels uneven.” Omar says, “Walk me through last Tuesday for one manager.” Tessa explains managers ran a forecast meeting, answered internal requests, and held a team meeting. Omar asks, “Where did one seller receive feedback tied to a customer conversation?” Tessa pauses. “Managers sometimes comment during a group call.” Omar replies, “Which seller moments need private review instead of a group comment?” Her answer names new seller discovery calls and late stage account conversations.

Omar has learned enough. Group meetings still happen. Individual review has weakened around moments where sellers face pressure. He does not need to propose a full operating redesign. A limited trial asks whether a protected slice of an existing meeting leads to better preparation.

In a fictional planning session, Tessa invites Priya and Daniel, two frontline managers. Priya says, “My team meeting already takes forty five minutes. Another activity will draw pushback.” Omar asks, “Which part of the meeting changes most often?” Priya says the final fifteen minutes become open discussion. Daniel adds, “We often finish forecast early during weeks without a major deadline.” Omar proposes a trial. Each manager selects one seller conversation for those final fifteen minutes. The manager asks the seller to state the buyer situation, the missing fact, and the purpose of the next conversation.

The trial has a clear shape without treating every team alike. Managers choose a live opportunity. Sellers bring one recent interaction instead of an account history. The group hears enough detail to learn, while discussion stays inside a short window. A manager redirects vague language. “The buyer is interested” becomes “What did the buyer agree to examine before your next meeting?” The manager does not solve a deal in public. The manager helps the seller leave with a sharper question or a better prepared conversation.

Before suggesting a routine, learn what evidence managers already use. Some teams save call recordings. Others rely on seller notes or short account updates. Do not assume a recording library exists or insist upon one. Ask, “What would a manager look at before giving feedback?” If a manager has a calendar invitation and the seller’s notes, build from those materials. If recordings are available, ask whether managers have time to review a short section before the meeting. The routine should fit evidence already available during a normal week.

A leader sometimes worries public review embarrasses sellers. Treat this concern as design input. Ask which discussions belong in a group and which should move to a private setting. A seller who missed a basic preparation step might need private coaching. A seller who needs help framing a buyer question might benefit from peers hearing several approaches. Record this distinction. Without a shared boundary, managers either avoid useful discussion or turn every meeting into a full account inspection.

In a fictional roleplay, Omar plays a seller and Daniel plays the manager. Omar says, “My contact told me they need better visibility.” Daniel responds, “Show me your CRM notes.” Omar gives a long update. Omar stops the roleplay and asks Daniel to try a question tied to a decision. Daniel says, “Which person named visibility as a concern, and what decision are they trying to make?” Omar responds, “The operations lead raised the concern during a planning call and wants a way to compare regional activity before a meeting next month.” Daniel asks, “What will you ask before your next meeting?” The exchange gives Daniel a coaching opening.

Use practice like this to separate a request for information from a question advancing seller judgment. A manager needs account facts. Facts gain value when they lead toward a decision. During preparation, ask managers to mark one question they use often and one question they avoid. The avoided question often exposes uncertainty. For example, a manager might ask about close timing every week yet avoid asking who will challenge a proposed change. Naming this pattern gives enablement work a precise focus.

Agree on a limited review period. Four consecutive weeks gives managers enough chances to use the routine under ordinary pressure. Ask managers to record simple observations after each session. Which seller moment did they review? Did the seller identify a missing fact? Did the seller leave with a next conversation purpose? A leader does not need a complicated scorecard for an early test. Notes from managers and sellers show whether the routine fits their calendar and whether discussion becomes more useful.

At the midpoint, bring managers together for fifteen minutes. Ask where the routine failed. Perhaps a forecast meeting ran long twice. Perhaps a manager chose a deal with too much history. Perhaps sellers arrived without a recent customer interaction. Turn each problem into a smaller design decision. A long meeting sometimes calls for one seller rather than two. Too much history sometimes calls for a rule requiring one conversation from the previous seven days. Missing preparation sometimes calls for a reminder sent before the meeting. Keep changes tied to what happened, rather than a vague wish for stronger coaching.

Use the manager’s language when reviewing results with Tessa. Ask Priya which seller prompt drew a useful answer. Ask Daniel where a seller arrived unprepared. Then ask Tessa whether the team needs a protected fifteen minute window, a different preparation request, or private follow up for specific moments. Those choices arise from observed work, not from a claim about every growing team. Omar should write down one choice, the owner, and the next meeting where managers will use the routine.

For a fictional practice session, draw three columns on a page. Label them former coaching habit, present constraint, and existing meeting. Ask a teammate to play a leader whose managers gained five new sellers after a territory change. Request one calendar event, one recent seller moment, and one source of evidence. When your teammate says the team has no time, offer a four week trial using the final fifteen minutes of an existing meeting. End by asking which manager will select next Tuesday’s seller conversation before noon on Monday, then write Priya’s name beside Tuesday on the practice calendar.