Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

In the in-person quarterly example, Hormozi asks what the person wants to have happen; the answer is that it will be more fun. He then asks what that means, how you know, and so what, pushing the discussion toward a measurable output effect rather than an emotional preference.

Related Insights

Prospects often describe wants (e.g., "a more efficient system"), which are not true problems. Asking about the motivation behind their desire forces them to articulate the underlying pain that actually drives a purchase decision.

Asking prospects "what do you think?" yields vague, polite feedback. Instead, try to sell them on a tangible outcome for a specific price. Their willingness or hesitation to buy provides much more direct and honest feedback on the value of your proposed solution.

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.

Hormozi stopped asking 'can we' or 'could we' because people said no after judging the value without his full context. Asking 'what would it take?' assumes success and gets a concrete price. He can then decide whether the trade is worth it, instead of letting someone else make the call for him.

When a buyer asks a question like, "Can we do five?" don't just give an affirmative answer. First, confirm you can, then immediately ask a clarifying question like, "What are you thinking there?" This uncovers the context, motivation, and potential new opportunities hidden behind their initial inquiry.

The goal of asking questions isn't just for you to gather information. It's a Socratic dialogue designed to help stakeholders think differently and arrive at the real need themselves. By guiding their thought process, you build deeper alignment and co-create a better solution, rather than just extracting requirements for yourself to fulfill.

When a stakeholder proposes a specific feature (a "form factor"), don't debate it directly. Instead, "ladder up" the conversation by asking a series of "why" questions to uncover the user behavior, desired outcome, and ultimately, the root problem being solved.

Instead of asking a vague question like 'What can margins be?', anchor the conversation by positing a specific, aggressive number: 'I think you can do 25% margins. Tell me why I'm wrong.' This forces a more detailed, data-driven response rather than a generic, non-committal answer.

To gain buy-in, guide people to your desired outcome through a curated series of questions. This allows them to feel like they are discovering the solution themselves, creating a powerful sense of ownership. They are more likely to commit to a conclusion they feel they helped create.

While many question words exist, effective negotiation questions should primarily start with "what" or "how." "What" is best for uncovering obstacles (e.g., "What stands in the way?"), and "how" is for mapping implementation (e.g., "How do we get this done?"). This specificity feels deferential and triggers deep thought.