Don't just ask executives what they want to achieve, as this puts them on the spot. Instead, proactively formulate a hypothesis about their goals and challenges. Presenting this gives them a concrete starting point to react to, confirm, or correct, leading to much faster alignment.

A discovery tree is a map that guides questioning from a simple situation (e.g., using spreadsheets) to operational problems, then to executive problems (e.g., compensation mistakes), and finally to critical business impact (e.g., retention risk). This ensures you uncover problems worth solving.

Structure discovery calls by mapping problems across four levels: Situation (what they do), Operational Problem (champion's complaint), Executive Problem (VP's concern), and Business Impact (C-level metric). This framework provides a logical path for your questions, moving from tactical to strategic issues.

Don't just solve the problem a customer tells you about. Research their public strategic objectives for the year and identify where they are failing. Frame your solution as the critical tool to close that specific, high-level performance gap, creating urgency and executive buy-in.

Discovery has three levels: Situation (what they do), Operational Problem (a day-to-day annoyance for a champion), and Executive Problem (the business impact). Sales reps fail when they solve operational issues without connecting them to the executive-level "so what" that justifies a purchase.

The "Discovery Tree" maps problems in three layers: Situation (how they do it today), Operational Problem (daily annoyance), and Executive Problem (C-level risk, e.g., getting sued). Focusing only on operational issues leads to small deals; connecting them to executive-level risks is necessary to justify a large investment.

Prospects often state facts like "our sales process is complex." This is not a problem that gets budget. AEs must dig deeper for the root cause (e.g., single-threaded deals) and then the business problem (e.g., low win rate affecting fundraising) to build a compelling case for the CFO.

Don't memorize canned discovery questions, which makes you sound robotic. Instead, internalize the relationship between a prospect's Situation, the operational Problems it creates, and the business Impact of those problems. This "tree" lets you navigate the conversation naturally and effectively.

Frame sales problems in terms of executive concerns. Instead of focusing on "prospects don't pick up the phone" (a rep's problem), translate it to "inefficient pipeline generation" or "AEs aren't self-sourcing," which are strategic priorities for VPs and CROs.