The Interview Trap:
The "Feature-First" Mistake
The interviewer gives you a blank slate: "Design a 'Health & Wellness' app for elderly people." Most candidates dive straight into solutions: "I’d add a heart rate monitor, a pill reminder, and an emergency button." Stop. This is a "Product Sense" interview, and the goal isn't to see how many features you can list—it's to see how you identify a gap in the market. If you don't define the "User" and their "Pain Points" before naming a single feature, you’ve already lost the senior-level bar.
The Core Framework: The "EMPATHY-SCALE" Method
To design a product that actually sticks, you must move from Problem Discovery to Scalable Solution.
1. E-mpathize (Define the Persona)
"Elderly people" is a demographic, not a persona.
- The Strategy: Narrow the scope to a specific subset with a clear need.
- The Soundbite: "I won't design for 'all' elderly people. I’ll focus on 'Independent Seniors living alone who are managing chronic conditions.' Their primary emotional need isn't just health tracking; it's the anxiety of a health event occurring while no one is around to help."
2. M-ap the Pain Points
What is the "Job to be Done" that current solutions are failing at?
- The Strategy: Identify the frictions in their current routine.
- The Soundbite: "I see three main pain points: 1. Information Overload (too many pills/vitals to track), 2. Cognitive Friction (complex smartphone UIs), and 3. The Isolation Gap (health data exists in a vacuum, not shared with family)."
3. P-ropose the "North Star"
What is the one thing this product must do to be successful?
- The Strategy: Define the core value proposition in one sentence.
- The Soundbite: "Our 'North Star' is Peace of Mind through Proactive Oversight. We aren't just a tracker; we are a bridge between the senior and their support network."
4. A-rchitect the MVP (Minimum Viable Product)
Don't build a spaceship; build a skateboard.
- The Strategy: Pick 3 features that solve the core pain points.
- The Soundbite: "For the MVP, I’d prioritize: 1. Voice-First Logging (removing UI friction), 2. Family Dashboard (closing the isolation gap), and 3. Predictive Alerts (notifying family if a vitals trend looks abnormal, before it's an emergency)."
5. T-est & H-one (Success Metrics)
How do we know if we've actually solved the problem?
- The Strategy: Pick one "Leading Indicator" and one "Lagging Indicator."
- The Soundbite: "I’ll measure success through Retention (Are they logging daily?) and our 'Counter Metric': Inbound Calls from Worried Family Members. If the app is working, family anxiety should decrease because they have transparency."
6. Y-SCALE (Future Vision)
How does this become a billion-dollar business?
- The Strategy: Think about data ecosystems and expansion.
- The Soundbite: "To scale, we move from a consumer app to a Healthcare Platform. We can integrate with insurance providers to lower premiums for active users or connect directly with EHRs (Electronic Health Records) so doctors see real-time data during checkups."
The Product Sense Rubric
Interviewers grade you on your ability to handle ambiguity.
PhaseGoalWhat they are looking forClarificationDefine Constraints.Did you ask "Why now?" and "What's the goal?"User ResearchSegment Users.Did you avoid "Generalizations"?PrioritizationFocus.Did you use a framework (like RICE) to pick features?Trade-offsRealism.Did you acknowledge what you are not building?
Think Like a Founder
Product Sense is the "Soul" of Product Management. It’s the ability to see a mess of human needs and turn it into a clear, elegant roadmap. Whether you're in an interview or starting a new project at work, the "EMPATHY-SCALE" framework ensures you aren't just building "stuff"—you're building value.
The Kracd Prep Kits contain the "Product Sense Blueprints" for the 50 most common design prompts (e.g., "Design an ATM for kids," "Design a kitchen for the blind") used by Meta and Google.
- For PMs: Master the art of product discovery with the PM Prep Guide.
- For TPMs: Bridge the gap between user needs and system architecture with the TPM Prep Kit.
FAQs
Q: What if the interviewer says "Money is no object"?
A: Still prioritize. Even with infinite money, you have "Cognitive Load" constraints. If you launch 20 features at once, the user will be overwhelmed and the product will fail.
Q: How do I handle "Disruptive Competitors"?
A: Don't copy them. Identify their weakness. If a competitor is "Feature Rich but Complex," your strategy should be "Simplicity and Speed."
Q: Is "Product Sense" just for new products?
A: No. You use it every time you decide to add a major new feature to an existing product. You go back to the "Empathy" stage to ensure that new feature actually serves the user's current needs.
.png)
.png)
.png)
.jpg)
.jpg)
