Stop Over-Formalizing Customer Discovery

Founders often make customer discovery too official.

They ask for an hour. They send a calendar invite titled "customer development interview." They prepare a survey. They open with "thanks for agreeing to be interviewed." Then they wonder why the answers feel polished, careful, and low-energy.

The over-formalizing mistake turns a learning opportunity into a favor.

Formality changes the customer's posture

When a conversation becomes an official interview, the customer may try to be a good participant. They answer the question asked. They wait for the next prompt. They avoid rambling. They make the conversation neat.

But early discovery often needs the opposite. You want the side story. The complaint. The messy workaround. The moment where the customer says, "Actually, the weird part is..."

Too much formality can suppress that.

This is one reason The Mom Test emphasizes casual conversation and taking responsibility for asking good questions. The goal is not to run a perfect research ritual. The goal is to learn true things without making the other person perform.

Keep the ask small

Instead of:

"Could we schedule a 60-minute interview so I can learn about your workflow?"

Try:

"Quick question: how did you handle the last time this came up?"

Instead of:

"Can I send you a survey?"

Try:

"What did you do the last time the report was late?"

Instead of:

"I am conducting customer development research."

Try:

"I am trying to understand how people deal with this in real life."

The smaller opening makes it easier for the conversation to begin. If the topic is genuinely painful, the customer will often keep talking.

Use structure privately

Avoiding formality does not mean being unprepared. You should still know what you need to learn:

• The riskiest assumption.
• The target segment.
• The last specific incident.
• The workaround.
• The cost or consequence.
• The buying path or constraint.

Just do not force the customer to feel your structure. Keep the checklist in your notes. Let the conversation feel human.

For example, your private checklist may say "payment history." Your spoken question can be:

"Have you ever paid anyone or bought anything to make this less painful?"

Your private checklist may say "current workaround." Your spoken question can be:

"What do you do today when it happens?"

Good discovery is structured listening, not theatrical interviewing.

When formal interviews are useful

There are contexts where formal research is appropriate: enterprise procurement research, regulated industries, usability studies, or later-stage product validation with clear tasks. The mistake is using that level of ceremony before you know what you are trying to learn.

At the idea stage, the best conversations often happen in the wild:

• After someone complains in a community.
• During a sales call where a tangent appears.
• In a founder's network when a relevant problem comes up.
• In a support thread.
• In a short follow-up after a demo.

The opportunity may not look like a research session. Take it anyway.

How Vera trains this

In Vera, over-formalizing can make the AI customer bored or polished. The customer gives acceptable answers but does not naturally open up. To recover, the founder needs to ask simpler, more grounded questions:

"What happened last time?"

"How did you deal with it?"

"Why was that annoying?"

That is the practice: less ceremony, more truth.