You Don’t Understand Your User Until You See Them Struggle
You don’t understand your user until you observe their behavior under real-world constraints. Interviews and surveys capture stated preference, but only real-world struggle reveals actual behavior. In physical product development, ignoring this gap leads to costly design errors, tooling waste, and unsellable products.
Good morning. Most product teams are currently sitting on a mountain of “user data” that is functionally useless. They have personas with names and hobbies, they have survey results with high NPS scores, and they have interview transcripts filled with “positive feedback.”
I’m here to tell you that’s just noise dressed up as insight.
At lsaravanan.com, I approach user research through the lens of Design Thinking and industrial reality. In SaaS, a misunderstood user costs you a few sprints. In physical product development, it leads to something far more damaging: tooling that locks the wrong design into metal. When you commit ₹20 Lakhs to a mold based on what a user said they liked in a focus group, you aren’t innovating. You’re destroying capital.
“Users don’t behave in interviews. They perform.”
The Reality: Users Are Unreliable Narrators of Their Own Behavior
Users don’t lie maliciously; they lie structurally. They tell you what they wish they did or what they think sounds reasonable in a quiet office.
- In a focus group, they say they want “simplicity.”
- On the factory floor, they bypass your “simplified” digital interface because a physical workaround is 3 seconds faster.
The struggle is the only real data. Until you see a user fight with your product in their actual environment—under their actual constraints—you don’t have a signal. Empathy without context is just an assumption.
Real-World Friction: The Seven-Figure Interface Error
I recently analyzed an industrial equipment manufacturer that spent 18 months developing a new operator interface. They ran interviews. They built beautiful prototypes. Controlled lab testing said “Proceed.”
Six months after deployment, line efficiency dropped 11%. Support tickets jumped 40%. Why? The interface was designed for how operators said they worked. But under real production pressure, the operators defaulted to old habits because the new “clear” design required three screen taps for a task they used to do in one physical motion.
The tooling was already committed. The redesign cost hit seven figures. They had understood the user’s words, but they had never watched the user struggle under the pressure of a live assembly line. A well-designed product without a strategy is just an expensive experiment.
Where the Research Breaks: A Systematic View
Using a systematic approach, we identify the points where “research” becomes a liability:
1. Personas Replace People
A persona is a fiction used for alignment, not for capital decisions. In manufacturing, a persona that looks right on paper fails when the actual operator is wearing heavy gloves or working in low light.
2. Controlled Environments Produce Controlled Behavior
Demos and guided walkthroughs don’t replicate reality. Real users are distracted and rushed. If your product performs perfectly in a demo but collapses in deployment, you didn’t test the product—you tested the demo.
3. Tooling Locks Mistakes into Cost
The moment you commission a mold, your design assumption becomes a financial position. There is no “hotfix” for a steel mold. Every unit produced carries the cost of the behavior you failed to observe.
The Point of No Return
Once a product moves into production, the nature of your risk shifts fundamentally. At this stage:
- Observations become design decisions.
- Design decisions become tooling.
- Tooling becomes inventory.
Misunderstanding user behavior at this stage is no longer a research error. It is a financial loss. You cannot iterate on a shipping container full of finished goods.
Strategy Q&A (Behavioral Validation Audit)
Q: What is the difference between user feedback and user behavior? A: User feedback is what people say they do. User behavior is what they actually do under real constraints. Strategy must be built on behavior, not feedback.
Q: Why do user interviews fail to predict real product success? A: Interviews capture “stated preference”—what people think they want. Real behavior is “revealed preference”—what people actually do under constraint. Strategy must be built on what users do, not what they say.
Q: How does poor behavioral research impact manufacturing costs? A: It turns capital into dead inventory. If a design is built on assumed behavior, and that behavior doesn’t manifest on the production line, you are left with tooling and stock that serve no market need. Tooling locks mistakes into cost.
The Bottom Line: Observation as a Financial Control
Behavioral research isn’t a “design phase.” It is a financial control. The cheapest version of being wrong is being wrong before the mold is cut. Every hour spent watching a user struggle in their actual environment saves multiples in post-production corrections.
Where assumptions become capital, decisions become inventory. Watch the struggle before you commit the capital. Because once your assumptions become tooling, correction is no longer iteration—it is cost.
