Rehearse Discovery for an Executive Sales Meeting

Senior buyers rarely schedule time for a seller to collect basic facts. Their time is limited, so account teams need preparation, relevance, and attentive listening. Preparation does not remove discovery. Preparation gives a seller a useful starting view and a reason for one focused question. An enablement consultant helps the team test their view, hear a correction, and adjust the meeting path when an executive raises a different priority.

Begin with the decision near the meeting. An executive conversation might influence a priority, sponsor a working group, approve deeper evaluation, or close off a direction. “Build a relationship” does not guide preparation. A stronger aim sounds like, “Learn whether the operations leader sees approval delays as a current barrier before requesting a working session.” The team now knows which question matters, which evidence supports their starting view, and which answer changes their next step.

Ask the account team what they believe is changing at the customer. Look for known business events, earlier customer comments, account materials, or approved public information. Keep observed facts separate from assumptions. A reliable source might show a customer added two regions. A belief linking added regions with approval delays is a hypothesis. A seller who names the distinction has room to learn without defending a conclusion before hearing the buyer.

In a fictional workshop, consultant Imani asks Priya, an enterprise sales leader, “Why does your team worry discovery will waste an executive’s time?” Priya says, “Executives expect us to arrive informed.” Imani replies, “Preparation gives you a starting view. How will a seller test whether the view fits?” Priya offers, “We understand regional growth sometimes changes internal handoffs. Where are leaders spending more time than expected?” Imani asks what answer would alter the agenda. Priya says, “If handoffs are not an issue, we should ask about the executive’s current priority.”

Use enough context to show preparation, then leave space for correction. An executive does not need a long recital of account research. A seller might say, “We saw your team added two regions. Growth sometimes changes who owns decisions. Where does work slow today, if anywhere?” The buyer might confirm the premise, reject the premise, or introduce another concern. Each answer supplies direction. A long preface makes listening harder and pressures the buyer to accept a story formed without them.

Prepare a question map before the meeting. Write one hypothesis, one opening question, one follow up for confirmation, and one follow up for disagreement. For a handoff hypothesis, start with where work slows. If the executive mentions finance review, ask which decision creates the wait. If the executive says approval cycles are healthy, ask which operating priority needs attention instead. The map helps a seller remain present after an unexpected answer instead of returning to a memorized sequence.

A question does not equal discovery. The next question shows whether the seller heard the answer. Suppose an executive says, “Regional leaders do not agree on ownership.” A weak reply changes topic: “Would manager training help?” A stronger reply asks, “Where does ownership become unclear, and who first feels the delay?” The seller learns whether the concern involves assignments, escalation, measurement, or something else. Only after more context should anyone suggest a future discussion.

Review the account plan before senior meetings. Imani asks each seller to bring customer context they plan to mention, a source for each point, and the assumption hidden inside each point. A teammate listens for leaps. One seller says, “Ravi must worry about manager inconsistency after expansion.” Another asks which customer statement supports worry. The seller changes the claim into a question: “How are regional leaders maintaining manager routines during expansion?” The revised question respects uncertainty and gives Ravi room to describe his own concern.

Senior audiences often change the frame. A seller who prepares one route becomes rigid. During rehearsal, let the buyer challenge the premise. Ravi might say, “Approval is not our issue. Leaders need faster decisions before approval.” The seller should not force more approval questions. Priya responds, “Thank you for redirecting us. Which decisions take longest today, and what makes them hard to move?” Her response accepts Ravi’s direction and opens a more relevant line of discovery.

Do not turn a point of view into a product claim. A perspective starts a business conversation. “Teams adding regions often revisit leadership routines” is an observation for discussion, not proof a customer needs a program. Keep later service discussion connected to information the buyer shares. If Ravi describes unclear decision roles, Priya might ask whether a short session with operations leaders would help map where assumptions differ. A subject specialist handles detailed solution discussion later, once buyer priorities and participants are clear.

Use realistic pressure during rehearsal. Generic roleplay creates polite answers and limited learning. Bring an upcoming meeting, a real agenda, known stakeholders, and an actual hypothesis. Ask the colleague playing the buyer to interrupt, question relevance, and offer brief answers. Give the seller room for a pause before a follow up. A pause often leads to a better question than an automatic line from a prepared page.

In a fictional rehearsal, Marcus prepares for Dana, a regional operations executive. His starting view comes from a territory change and uneven manager expectations. Marcus opens, “We saw a territory change in your recent update. During similar changes, manager expectations sometimes differ across regions. Where are you seeing the greatest adjustment?” Dana says expectations are clear. Her concern is managers rebuilding plans after each forecast review. Marcus leaves his territory question behind and asks which part of forecast review leads to rebuilding. Dana says regional leaders use different assumptions.

Marcus has enough information for a disciplined next move. He does not claim a fix. He says, “Would a short discussion with regional leaders help us learn where forecast assumptions differ?” Dana agrees to consider a session and asks Marcus for a brief purpose statement. The note taker records her wording. After rehearsal, Imani asks Marcus what he will write. Marcus says, “I will frame our purpose around learning where forecast assumptions diverge, without proposing a program.”

Question quality improves through revision. Remove questions holding several issues at once. “How are you handling growth, manager consistency, forecast quality, and approval delays?” gives an executive too many paths. Choose the issue with the strongest available evidence. Ask one question, follow the answer, then decide whether another topic deserves time. Avoid language which corners a buyer. “Do you agree managers lack consistency?” demands agreement with a negative claim. “Where do manager routines differ across regions, if anywhere?” permits a more accurate answer.

For Marcus’s fictional follow up, Friday at 3 p.m. is his deadline. He opens a blank email, uses Dana’s phrase “forecast assumptions” in the subject line, and writes two sentences describing a short discussion with regional leaders. He then adds one line asking Dana to name an operations contact for scheduling. Before sending, Marcus compares every sentence with the note taker’s record and removes a sentence about manager expectations, since Dana did not raise manager expectations.