Product Intuition & Product Sense

Product intuition is not innate — it is developed through deliberate practice across three dimensions. Customer immersion: developing product intuition requires spending regular, unstructured time with actual customers — not surveys (too mediated), not analytics (too abstracted), but direct conversations and observations. PMs who conduct 2+ customer conversations per week develop product intuition faster than those who rely solely on data. The goal of these conversations is not to validate a specific hypothesis but to deepen the mental model of how customers think, what they value, and what confuses them. Product archaeology: studying how great products evolved over time — reading changelog histories, public post-mortems, founder interviews about product decisions — builds a library of mental models for what works and why. Using products extensively in adjacent categories reveals UX patterns, interaction designs, and positioning choices that can be applied to your own product domain. Hypothesize-test-reflect cycles: making explicit predictions about how customers will respond to product changes, observing the actual outcomes, and reflecting on the differences between prediction and reality. Over time, the gap between prediction and reality narrows — that narrowing is the development of intuition.

The relationship between product intuition and data is collaborative, not competitive. Data reveals what is happening; intuition provides the hypothesis and the interpretation. The failure modes at each extreme: pure intuition-driven teams ("I just feel like users want this") build features without validation, ship solutions to non-problems, and create products that reflect the PMs' preferences rather than the customers'. Pure data-driven teams ("the data shows users click this button, so we should add more buttons like it") measure the wrong things, mistake correlation for causation, and optimize locally without a sense of direction. Best-practice integration: intuition generates hypotheses and design directions; data validates whether those hypotheses are correct and guides the quantitative side of optimization. When data and intuition conflict, the correct response is neither to dismiss the data ("I know our customers, the data must be wrong") nor to ignore intuition ("the data says X, so we must do X regardless of what we think"). The conflict is a research signal — it means our mental model of the customer needs updating, or the data measurement is capturing the wrong behavior.

Product intuition is one of the hardest product competencies to assess in hiring because it cannot be demonstrated through credentials or resume items — it must be observed in real-time reasoning. Effective assessment formats: product critique exercise: "Take 10 minutes with [product X] and then walk me through what you think is working well, what is confusing, and what you would change first and why." This reveals whether the candidate notices the same issues experienced product professionals notice and whether their change suggestions show customer empathy or just feature accumulation. Metrics prioritization: "Given this product with these features and this customer base, what metric would you pick as your north star and why?" — assesses whether the candidate can connect feature usage to customer value and business outcomes. Product strategy scenario: "Our product's user growth has plateaued — what would you investigate first?" — assesses the candidate's ability to structure a product problem quickly and identify the right questions to ask. Product Ops hiring prioritizes candidates who demonstrate customer empathy (their reasoning starts with the customer), intellectual honesty (they acknowledge the limits of their analysis), and systems thinking (they see product problems in context rather than in isolation).