Product Sense

Building Product Intuition: A Daily Observation Practice

MMeelni Team
November 10, 2025
8 min read

Building Product Intuition: A Daily Observation Practice

"You just have really strong product sense."

This is a common compliment after a successful product interview. But here's the truth: Product sense isn't something you're born with—it's something you build.

Systematic observation gives you more examples to draw from when discussing users, trade-offs, and product decisions. Over time, that practice can make product critique feel more natural.

This post shares an observation framework that helps candidates develop stronger product intuition through deliberate practice.

What Product Intuition Really Means

Product intuition is your ability to predict what features or experiences will resonate with users and become successful. It's pattern recognition built from thousands of micro-observations about:

  1. What motivates people (desires, pain points, behaviors)
  2. How people react to things (interfaces, messaging, flows)

The good news? You're already equipped to build this skill. You're a person. You use products. You react to things. You just need to pay attention systematically.

The Product Critique Framework

Every time you try a new app, visit a website, or experience any product, run through this framework. Repeating the exercise helps you compare observations and notice patterns.

Phase 1: Before You Even Open It

Most candidates skip this phase entirely. That's a mistake—first impressions are formed before the first click.

Ask yourself:

How did this come to your attention?

  • Word of mouth from a friend? (Why did they tell you?)
  • Article or review? (What made you actually download it?)
  • Recommended algorithm? (What does that say about you?)
  • Repeat exposure? (What finally tipped you over?)

What's your one-line summary of what this does? Write it down. Compare it to your summary after using the product. The delta tells you how well the product communicates its value.

What's the buzz?

  • Does it feel popular? Useful? Innovative?
  • Did you check ratings and reviews? What stood out?

This phase teaches you about positioning, marketing, and value proposition—critical for product sense interviews when you need to explain "why now?" or "how does this fit the market?"

Phase 2: The First 3 Minutes

Just like with people, most product opinions form in the first few minutes. Time yourself. Spend exactly as long as you normally would (probably 2-5 minutes, not 30).

Onboarding & Sign-up:

  • How many steps? Easy or friction-heavy?
  • Was verification smooth or frustrating?
  • Did they explain why they need certain permissions?

Self-Explanation:

  • Was it immediately clear what the app does?
  • Did you read the intro messaging, or skip it? (If you skipped it, why?)
  • Did the UI feel familiar, or did you need to explore?

Emotional Response:

  • Did anything make you smile? (Illustration, copy, clever interaction?)
  • Did anything frustrate you? (Confusing navigation, slow load, unclear buttons?)
  • Did you feel smart, efficient, delighted, or annoyed?

Delivery on Expectations:

  • Did the product match what you thought it would be?
  • If it's a content app: was the content engaging?
  • If it's a utility: did it solve the problem meaningfully?

Time Spent:

  • How long did you actually use it?
  • If you spent longer than planned, what kept you engaged?

This phase teaches you about user experience, activation, and first-run engagement—exactly what product sense interviews test when they ask "How would you improve onboarding?"

Phase 3: The Next 7 Days

A first impression cannot show retention or habit formation. Track behavior over time to examine why people return or leave.

Usage Frequency:

  • Did you open it again? When? Why?
  • What triggered you to return? (Push notification? Friend mention? Habit?)
  • Has it become a regular part of your routine? If not, why not?

Comparative Analysis:

  • How does this compare to similar products?
  • What does it do better? Worse?
  • What would make you choose this over alternatives?

Broader Market Perspective:

  • What do other people think? (Read reviews, blog comments, tweets)
  • Ask friends from different demographics—do they see it differently?
  • Does their impression match yours? Why or why not?

Make a Prediction:

  • How successful will this app be in a year?
  • Write it down. Be specific. Create a stake in the ground.
  • This is how you combat hindsight bias and actually learn.

This phase teaches you about retention, stickiness, and product-market fit—critical for questions like "What makes a product successful long-term?"

Phase 4: The Retrospective (6-12 Months Later)

This phase turns a prediction into a calibration exercise.

Were you right?

  • Check back on your prediction. How'd you do?
  • If you were wrong, why? What did you miss?
  • How were your personal preferences different from the broader market?

Calibration: Understanding where your taste diverges from other users helps you avoid treating personal preference as universal evidence.

Example: Maybe you hated an app's aggressive notifications, but it grew 10x because notifications drove retention for the target demographic (busy parents who needed reminders).

How This Shows Up in Interviews

When you practice product critique systematically, interviews become pattern matching:

"Improve Instagram Stories" You've already analyzed Stories vs. Snapchat, TikTok, BeReal. You know what works (ephemeral, low-pressure posting), what doesn't (over-edited content), and where the white space is.

"Design a product for new parents" You've observed how your friend with a baby uses apps differently (one-handed, interruptible, during 2am feedings). You've seen which apps she deleted and which became essential.

"Why did Product X fail?" You've made predictions. You've been wrong. You've learned what actually matters vs. what sounds smart in theory.

Connect Observations to an Interview Answer

Use the observations to make each part of a product answer more concrete:

Product Motivation/Mission → Clarity on value prop and market positioning Target Audience → User segmentation based on real behavior patterns Identifying Problems → Pain points from journey mapping Developing Solutions → Features that address observed needs

Your Practice Plan

Week 1-2: Critique 5 apps you already use. Write down observations.

Week 3-4: Critique 5 new apps. Make predictions.

Week 5-8: Critique every product experience (booking travel, ordering food, using ATM). Talk through your observations out loud.

Ongoing: Check back on old predictions. Calibrate.

How Meelni Accelerates This

Product critique builds intuition, but product interviews test articulation. You can have great insights but still bomb if you can't structure your thinking under pressure.

Meelni lets you choose a PM practice question, answer it out loud in a mock interview, and review feedback after the completed session. Use that feedback to choose the next part of your answer to practice.

Start practicing now and put your product observations to the test.


Remember: product intuition grows from noticing behavior, recording predictions, and revisiting what you got wrong. Start with one product today.

M

Ready to practice out loud?

Put the framework into action in a voice mock interview, then review feedback after the completed session.

Start practicing now