« Back to Pillar Page: Product Leaders Day India
Product Sense: Decoding the "Vibe" of User Behavior
Data tells you what is happening. It rarely tells you why. Great product managers don’t just read dashboards; they read people.
"Product Sense" isn't magic; it is the ability to internalize the user's problem so deeply that your intuition becomes an accurate predictor of their behavior.
I. The War Room: Storytelling Analysis
Analyzing high-stakes decisions where spreadsheets weren't enough.
Case Study A: When Jobs Ignored the Focus Groups
The Legend: Steve Jobs famously said, "It’s not the customer’s job to know what they want." He ignored market research for the iPad and iPhone.
The Takeaway: Many PMs use this as an excuse to ignore users. That is a mistake.
The Nuance: Jobs didn't ignore problems; he ignored user-proposed solutions.
The Trap: If you ask a user in 2005 what they want in a phone, they say "A physical keyboard like a BlackBerry, but smaller."
The Strategy: You must stop listening to the "Feature Request" and start listening to the "Struggle." Users are experts in their problems, but amateurs in design solutions.
The "Unless..." Rule: Do not ignore focus groups unless you are solving a problem the user cannot yet conceive of (a "0 to 1" innovation). For optimization (improving a checkout flow), listen to the focus group. For disruption, listen to your intuition.
Case Study B: The 40/70 Decision Framework
The Concept: Analysis Paralysis kills products. If you wait for 100% of the data, you are too late. The market has moved.
The Doctrine: Modeled after Colin Powell’s leadership theory:
- < 40% Information: You are guessing. Don't move yet.
- 40% - 70% Information: This is the "Zone of Intuition." You have enough signal to spot the trend, but not enough to guarantee safety. This is where high-impact product decisions happen.
- > 70% Information: You have missed the opportunity. The decision is now obvious to everyone (including your competitors).
II. Frameworks: Decoding the "Vibe"
1. The Qualitative Deep Dive (Reading Between the Lines)
When users speak, there is a "text" (what they say) and a "subtext" (what they feel).
- The Metric: NPS (Net Promoter Score) tells you if they are happy.
- The Vibe: Reading the support tickets and transcript pauses tells you why they are leaving.
The "Five Whys" interrogation technique:
User: "I want a download button for this report."
Bad PM: "Okay, putting it in the backlog."
Good PM: "Why do you need to download it?"
User: "To send it to my boss."
Good PM: "Why doesn't your boss log in?"
User: "She doesn't have a license."
Real Insight: The problem isn't a "download button"; the problem is strict permissions/licensing hindering collaboration. The solution might be a "Guest View" link, not a PDF export.
2. Data-Driven vs. Data-Informed
There is a massive difference between letting data drive the car and using data to check the map.
| Aspect | Data-Driven Approach |
|---|---|
| Philosophy | "The data decides." |
| Weakness | Optimized for local maxima. (e.g., You A/B test a button color to perfection but miss that the whole page is unnecessary). |
| Best For | Optimizing funnels, pricing tiers, performance bugs. |
III. Developing Product Sense
Product Sense is often treated as innate talent, but it is a muscle you can build.
- Immerse in the Domain: You cannot have intuition about a subject you don't study. If you work in Fintech, you should be reading financial regulation news, not just tech news.
- The "Prediction Game": Before every A/B test, write down your prediction and why you think it will win. If you are wrong, do a post-mortem on your own brain. Why did you misread the user?
- Dogfooding: Use your own product. Not just the "Happy Path," but the edge cases. Try to cancel your account. Try to change your password. Feel the friction.
Frequently Asked Questions (FAQs)
Q1: How do I defend a decision based on "Product Sense" to a data-obsessed VP?
A: Frame it as a "Strategic Bet" rather than a hunch. Use the phrase: "The quantitative data is silent on this because it’s a new behavior, but the qualitative signals (user interviews, support trends) suggest high demand. I propose we launch a minimal version (MVP) to generate the data you’re looking for." You are using intuition to generate the data they want.
Q2: Can Product Sense be taught to junior PMs?
A: Yes, through exposure. Force them to watch user sessions (using tools like FullStory) and sit in on customer support calls. "Sense" is just pattern recognition built over time. If they don't see the patterns, they can't develop the sense.
Q3: What if my gut says one thing and the A/B test says another?
A: Trust the A/B test behaviorally, but investigate the intent. If users are clicking a button you didn't expect, don't just accept it—figure out if they are clicking it by mistake, or if they are using the feature for a purpose you didn't design. Data shows "what," your gut investigates "why."
References & Further Reading
- "Inspired: How to Create Tech Products Customers Love" by Marty Cagan: The industry standard on why "Product Discovery" is just as important as "Product Delivery." SVPG - Silicon Valley Product Group
- "Continuous Discovery Habits" by Teresa Torres: A masterclass in how to keep your finger on the pulse of the user without getting overwhelmed. Product Talk
- "Thinking, Fast and Slow" by Daniel Kahneman: Essential for understanding cognitive biases. It explains why your "gut" is sometimes brilliant and sometimes terribly wrong. Book Summary / Concept Overview
