Avoiding the Elephant in Customer Interviews

Some customer interviews fail because the founder asks biased questions. Others fail because the founder asks only comfortable questions.

Avoiding the elephant happens when the conversation stays pleasant while the riskiest assumption remains untouched.

The founder asks about workflow, preferences, frustrations, and nice-to-have improvements. They do not ask about budget, authority, priority, legal constraints, switching cost, implementation burden, or whether the target customer can actually adopt the product.

The call feels useful. The dangerous assumption survives because nobody challenged it.

The elephant is idea-specific

For a consumer habit app, the elephant may be whether the problem is painful enough to change behavior.

For a B2B SaaS tool, it may be who controls budget.

For a healthcare product, it may be compliance, procurement, or integration with existing systems.

For a school product, it may be whether teachers feel the pain but districts make the purchase.

For a marketplace, it may be whether one side is reachable before the other side exists.

The elephant is the question that could force a pivot.

Comfortable questions are not always bad

Workflow questions matter. Frequency questions matter. Tooling questions matter. The mistake is not asking them. The mistake is using them to avoid the sharper issue.

Imagine a founder building software for school administrators. They ask teachers:

• "How often do you create lesson materials?"
• "What tools do you use?"
• "Would saving time be helpful?"
• "What would make the workflow smoother?"

Those questions may reveal useful context. But if the business depends on school purchasing, the founder also needs:

• "Who would approve paying for this?"
• "Where would the budget come from?"
• "Have similar tools been rejected before?"
• "What policy or privacy requirements would block adoption?"
• "Is this problem important enough to compete with other priorities?"

The elephant is often uncomfortable because it can make the idea smaller.

Ask the killing question earlier

Founders often save risky questions for later because they want rapport first. Some rapport helps, but waiting too long can turn the interview into a tour of safe details.

Try this structure:

1. Open with a recent incident.
2. Understand the current workaround.
3. Ask one or two workflow follow-ups.
4. Ask the elephant.
5. Then return to details if the idea survives.

Example:

"You mentioned the team loses time reconciling this every week. Who would actually own the decision to pay for a fix?"

Or:

"It sounds painful, but you have also lived with it for a while. What would make this important enough to change this quarter?"

Or:

"If we solved the user workflow but required IT approval, what would happen?"

These questions are not rude. They are respectful of reality.

What real founders report

In Hacker News discussions about talking to customers, experienced commenters often separate learning from selling and warn that founders bring preconceived notions into conversations. The elephant is usually attached to those preconceived notions. It is the assumption the founder most wants to keep.

Discovery should put pressure there.

If the idea cannot survive the budget question, the adoption question, or the priority question, better to learn that before building.

How Vera trains this

In Vera, avoiding the elephant is a critical mistake because it lets the conversation stay low-stakes. The AI customer will answer the surface question and withhold the hidden blocker until the founder asks directly.

That mirrors real life. Customers often do not volunteer the fatal constraint. They answer what you ask.

The training move is to name the risk:

"The thing I am most unsure about is whether this is urgent enough to pay for. How has that played out before?"

That question may hurt the idea. Good. That is what discovery is for.