Ask About Specifics, Not Generic Behavior

Generic behavior questions sound harmless:

"What do you usually do?"

"Do you ever have this problem?"

"How do people normally handle it?"

"Is your inbox always under control?"

The customer can answer all of them honestly and still give you weak data. Generic questions invite generic self-description. People talk about the version of themselves they believe in, not the messy incident where the pain actually appeared.

The problem with "usually"

"Usually" smooths out the interesting parts.

A customer might say, "We usually stay on top of customer follow-ups." That may be true in the broad identity sense. But the startup opportunity may live in the exception: the enterprise renewal where notes were scattered, the handoff after a salesperson left, the angry customer who fell through the cracks.

Specific incidents reveal:

• Sequence.
• Tools.
• Workarounds.
• People involved.
• Consequences.
• Emotion.
• Money or time spent.
• Constraints the customer forgot to mention at the abstract level.

Generic answers hide those details.

Rewrite the question around the last time

Weak:

"Do you ever struggle with meal planning?"

Stronger:

"When was the last time dinner planning went badly? What happened?"

Weak:

"How do you normally onboard new clients?"

Stronger:

"Walk me through the most recent client onboarding from signed contract to first successful outcome."

Weak:

"Do people on your team care about documentation?"

Stronger:

"Tell me about the last time missing documentation caused rework."

The phrase "last time" is useful because it forces time, place, and sequence into the conversation.

Ask for the movie, not the summary

A strong discovery question gets the customer to replay the scene:

"Where were you?"

"Who noticed the problem?"

"What did you open first?"

"What happened next?"

"How long did that take?"

"What did you do when that failed?"

"Who cared about the outcome?"

This may feel slow, but it prevents you from building on slogans. The customer's summary is often neat. The movie is messy. Startups usually live in the mess.

Why surveys often miss this

Surveys tend to ask generic questions because they need standardized answers. That can be useful later when you know the variables you are measuring. Early discovery is different. You often do not yet know the important variables.

A founder on Reddit asking how to validate an idea will often get advice to talk to target users, ask about current workflows, and listen for repeated pain. That advice is right, but the useful part is the repeated pain, not the act of talking. Repetition only matters if each conversation produces specific enough stories to compare.

Five vague conversations do not equal a pattern. Five specific stories might.

How Vera trains this

In Vera, generic behavior questions produce generic answers. The AI customer may say they "usually try to stay on top of it" or that the problem "comes up sometimes." Those answers sound plausible but do not reveal hidden evidence.

To improve the truth score, the founder has to anchor the question:

"When was the last time?"

"What did you do?"

"What did it cost?"

"What happened next?"

That habit is small, but it changes the quality of the entire interview.