Include Seller Voices in a Coaching Evaluation

Enablement leaders sometimes design a polished program yet miss moments sellers find difficult during live conversations. A representative council gives an evaluation a direct line to field experience. The account executive should present the council as a discovery group with a clear purpose and limits. Sellers describe obstacles, recall buyer language, and test scenario ideas. Leadership owns program choices, content approval, funding, and rollout timing. A council works best when every participant understands this division before the first invitation arrives.

In this fictional planning session, Jordan meets Mei, an enablement vice president. Jordan says, “Your leaders selected discovery training. Several sellers said existing scripts feel distant from live deals. I propose a small council focused on real discovery moments.” Mei asks whether Jordan means a survey. He replies, “A conversation gives us detail surveys often miss. Which sellers hear objections your managers want to address?” Mei names two enterprise sellers and two commercial sellers. Jordan asks each participant to bring one anonymized conversation moment and explain the decision they faced.

Before choosing participants, agree on the question the council needs to answer. “What do sellers think?” produces broad and difficult material. “Which buyer statements leave sellers unsure how to continue discovery?” produces a useful starting point. Jordan records a single purpose for Mei: gather field language and scenario ideas for a discovery evaluation. He excludes performance ratings, compensation concerns, product complaints, and debate about leadership decisions. Those topics deserve their own process. A narrow purpose helps sellers prepare and keeps the meeting from becoming a complaint session.

Selection affects the quality of discussion. Ask a customer leader who hears different deal types, market segments, and levels of experience. Do not treat one outspoken seller as a stand in for every person in the field. In Mei’s fictional council, an enterprise seller describes long account cycles, while a commercial seller describes fast first meetings. One seller joined three months ago. Another has worked through several planning cycles. Their examples expose different conditions without claiming each experience represents the whole sales organization.

Invite sellers with enough context to contribute, then state what participation involves. Jordan writes: “Please bring one anonymized moment from a recent discovery conversation. Note the buyer’s words, your next decision, and what support would have helped. We will not review individual performance or select training content during this session.” He asks participants to remove names, company details, prices, and information from private records. He also tells them how long the session lasts and who will see their input. A clear invitation reduces anxiety and leads to better preparation.

The meeting structure should leave more room for seller examples than presentation. Jordan begins with the purpose, the boundaries, and a short reminder about anonymity. He then gives each participant time to describe a situation without interruption. After each example, he asks, “What did the buyer say?” “What decision did you need to make next?” and “What manager response would have helped?” These questions move discussion from vague frustration toward material for enablement review. He records the words used by the seller before translating anything into program language.

Suppose an enterprise seller says, “The buyer wanted proof our process would fit a complex account, and I did not know which question would move us forward.” Jordan does not supply a script on the spot. He asks what details the buyer had already shared and what the seller hoped to learn. The seller says the buyer mentioned several business units and a long approval path. Jordan records a scenario idea: buyer raises complexity, seller needs to clarify decision process. The wording stays close to the field example without naming a customer or claiming a universal solution.

Mei asks whether a council recommendation becomes training material. Jordan answers with the agreed boundary: “The council supplies examples and questions. Product marketing and sales leadership review material before use.” He writes this beside the output document. This approach respects seller expertise while keeping approval with leaders who own program direction. Sellers should not leave believing every suggestion will appear in a workshop. Jordan closes each meeting by explaining when leaders expect to review the themes and how participants will receive an update.

Capture output in a simple record. Use one entry for the buyer language, one for the seller decision, one for possible scenario use, and one for the open question. For example, a record might say buyer asks how a process fits several business units. The seller needs to choose a follow up question. The scenario idea involves mapping decision participants. An open question asks which information sales leadership wants explored during discovery. Leave out judgments about the seller. Keep direct words separate from the note writer’s interpretation. This makes later review more reliable.

Watch for a few common complications. A participant might begin naming a customer or colleague. Stop gently and ask for a generalized version. A manager might want to debate training design during the council. Put the idea in an open questions section for leadership review. One seller might speak for most of the session. Jordan uses a round of equal time, then asks quiet participants whether their situation differs. If a seller shares a problem outside the stated scope, he notes the topic and tells Mei after the session rather than redirecting every conversation toward a training answer.

Feedback after the meeting builds trust without creating a promise. Jordan sends participants a short record of themes, with customer details removed. He asks whether their example was represented accurately. He tells them product marketing and sales leadership will review scenario ideas in the following two weeks. He does not say a new program will follow. If leaders decide another direction, Mei still sends a brief update explaining which field themes they reviewed. Sellers then see their contribution entered a real decision process, even when no immediate change follows.

Run a fictional practice session with a colleague before inviting a customer council. One person plays a seller who opens with, “Leadership never understands the field.” The facilitator replies, “Give me one recent moment and the decision you faced.” Ask for buyer words, a decision point, and desired manager support. When the seller begins discussing a compensation policy, thank them, mark the topic outside scope, and return to the stated purpose. Notice whether your questions draw out a specific event rather than a broad opinion.

End the practice by filling one council record from the fictional conversation. Write the buyer’s words as spoken, name the seller decision, and add one open question for leadership. Read the entry to your colleague. Revise any phrase which adds a judgment or identifies a customer, then place the cleaned entry in the agenda for the first council meeting.