User interviews often mislead founders because they capture what users say, not what they actually do. This gap between stated preference and real behavior leads to flawed product decisions, and in manufacturing, it results in costly tooling, unsold inventory, and capital loss.

---

There is a specific type of comfort that comes from running 20 user interviews. You have the quotes, you have the patterns, and your Notion doc is overflowing with “validation.”

I’m here to tell you that this comfort is a trap.

In my work as a product decision strategist, I see this cycle constantly. Founders believe that talking to users is the gold standard. But in the interview room, the participant is “performing helpfulness,” not revealing truth. In SaaS, this results in ignored features. In manufacturing, it results in ₹40 Lakhs of steel tooling cut for a product that the market never actually asked for.

“Users don’t behave in interviews. They perform.”

The Reality: Users are Unreliable Narrators of Their Own Behavior

The gap between what people say and what they do is called Social Desirability Bias, and it is the silent killer of product startups.

• A user says they want “minimalism” in an interview.
• At checkout, they reject the product because it “feels too light and cheap.”

The interview captures preference in the abstract; the market reveals preference in the concrete. Empathy without context is just an assumption. When that assumption moves to the factory floor, it stops being a “design insight” and becomes a capital event. This is the same trap I describe in why you don’t understand your user until you see them struggle.

Real-World Friction: The ₹2.8 Crore “Compact” Mistake

I observed a hardware startup that conducted 40 interviews. Every single person asked for a “compact, minimalist form factor.” The team listened. They locked the design, commissioned tooling in Asia, and placed a 10,000-unit MOQ.

At launch, the #1 complaint? The product felt “too small and cheap.” The users who asked for compact now wanted “substance.”

The cost of that gap? ₹2.8 Crore (approx. $340,000) in tooling rework and a 6-month delay that handed the market to a competitor. The interview captured an idea of minimalism, but the physical reality failed the “value perception” at the point of sale. Prototype proves possibility, not profitability.

Where the Research Breaks: A Systematic View

Using a systematic approach, we identify why interviews are “Hypothesis Generators,” not validators:

1. Enthusiast Bias

The people who agree to be interviewed are not your “average” customers. They are self-selected enthusiasts. If you build for the vocal minority, you will miss the mainstream majority that actually drives revenue.

2. The Framing Effect

The way you ask a question determines the answer. If you ask, “Would this feature make your life easier?” the answer is almost always “Yes.” That “Yes” is noise. It doesn’t signal a willingness to pay or a tolerance for switching costs.

3. Memory is Reconstructive, Not Archival

When a user tells you how they solve a problem, they give you a “cleaned-up” narrative. They forget the messy workarounds and the friction they’ve normalized. You get the story, not the system.

4. The Tooling Lock-In

In manufacturing, the lead times are 12–24 weeks. If your “validation” was just a conversation, you are betting your entire supply chain on a 45-minute Zoom call. Tooling locks mistakes into cost.

The Point of No Return

Once a product moves from the interview room to the production line, your risk profile changes:

• Conversations become purchase orders.
• Quotes become specifications.
• Assumptions become inventory.

At this stage, a research error is no longer a “pivot.” It is a write-off. You cannot “roll back” a shipping container of physical goods.

The Bottom Line: Strategy Over Sentiment

User interviews are the beginning of the process, not the end. A well-designed product without a strategy is just an expensive experiment. Where assumptions become capital, decisions become inventory. Don’t let your “confidence ritual” of 20 interviews blind you to the capital risk of a 10,000-unit production run. Match your financial commitment to the quality of your evidence — the principle behind the LSAR decision framework.

“Interviews generate confidence. Behavior generates truth.”

“Don’t build based on what users say. Build based on what they are willing to do when it costs them something.”

---

Frequently Asked Questions

Why do user interviews mislead product teams?

Because they capture stated preferences, which are influenced by social bias and artificial context. Users describe an idealized version of their behavior, not the messy reality of their actual purchasing decisions.

How should founders use user research without being misled?

Treat interviews as directional signals to generate hypotheses. Then validate those hypotheses with behavioral data — pre-orders, pilot sales, or observed usage — before committing capital to manufacturing.

What is the most dangerous interview insight?

The one that confirms what you already believed. Confirmation bias in research isn’t a design problem; it’s a leadership failure that leads to expensive, unvalidated bets. If you’re weighing a production decision, talk to L Saravanan first.