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.
Executives don't care about tactical benefits like 'five fewer clicks'. A crucial skill for modern sellers is to extrapolate that tactical user-level gain into a strategic business outcome. You must translate efficiency into revenue, connecting the dots from a daily task to the company's bottom line.
Enterprise leaders aren't motivated by solving small, specific problems. Founders succeed by "vision casting"—selling a future state or opportunity that gives the buyer a competitive edge ("alpha"). This excites them enough to champion a deal internally.
To get buy-in from skeptical, business-focused stakeholders, avoid jargon about user needs. Instead, frame discovery as a method to protect the company's investment in the product team, ensuring you don't build things nobody uses and burn money. This aligns product work with financial prudence.
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.
Buyers won't openly state their career risks, such as getting fired for a failed project. To uncover these fears, ask: 'What does success look like for you three months after this is deployed?' Their answer reveals their key success criteria, which are directly tied to their biggest perceived risks.
Sales conversations often rush to demo a "better" product, assuming the buyer wants to improve. The crucial first step is to help the prospect recognize and quantify the hidden costs of their current "good enough" process, creating urgency to change before a solution is ever introduced.
Structure your final presentation by calling out specific problems you learned from individual contributors by name. Then, immediately pivot to show how solving their problem directly contributes to the high-level business objective owned by the executive decision-maker. This makes every stakeholder feel heard and demonstrates their strategic value.
To capture an executive's attention, connect operational-level problems to their strategic business impact. A slow development cycle isn't just a process issue; explain how it directly causes delayed time-to-market, higher costs, and lost market share to competitors, which are the metrics an economic buyer truly cares about.
Bypass C-suite gatekeepers by interviewing lower-level employees who experience the problem daily. Gather their stories and pain points. Then, use this internal "insight" to craft a highly relevant pitch for executives, showing them a problem their own team is facing that they are unaware of.
Deals are lost when salespeople fail to spend enough time in discovery to understand the customer's true need. They must identify the 'moment of demand'—when the customer both recognizes their problem and is ready to decide—rather than rushing to the close with the wrong solution.