🟩 Canonical Text
PRODUCT
INTUITION
This is a deep sense of what the customer truly needs and where the market is going, even before the data proves it. It's an empathy for the user combined with an understanding of technology and business, allowing a leader to make bold bets on what will resonate.
INTUITION
This is a deep sense of what the customer truly needs and where the market is going, even before the data proves it. It's an empathy for the user combined with an understanding of technology and business, allowing a leader to make bold bets on what will resonate.
🟩 One-Line Description
Possesses an innate sense of user needs and future market opportunities.
🟩 Light-Side Copy (Core Challenge)
Makes bold bets on what will resonate with users, even before the data proves it.
🟩 Shadow-Side Copy (Key Demands)
May override contradictory data or fail because it's proven wrong.
Guiding Question
What does the user really need, not just what they are asking for?
✍️ Deeper Examples (Next Edit)
Why This Matters:
Data is a rearview mirror; it tells you where you’ve been, not where the road is turning. Product Intuition is the ability to see the "invisible" needs of the user before they can even articulate them. In a world of commoditized features, this capability allows a leader to make high-conviction leaps that create entirely new categories or reset the standard for excellence.
Leader Moves:
• The "Extreme User" Immersion: Spend time watching how the most frustrated or most creative users "hack" your product to solve their problems.
• Synthesize the "Job to be Done": Look past what the user says they want (features) to the emotional or functional "job" they are trying to hire the product to do.
• Low-Fidelity Prototyping: Build "ugly" versions of an idea quickly to test for a visceral "gut" reaction from users rather than polite feedback.
• Articulate the "Why" Behind the "What": Don't just demand a feature; explain the specific user tension it resolves so the team understands the logic of the intuition.
• Market Pattern Matching: Look at successful products in completely unrelated industries (e.g., gaming mechanics applied to fintech) to find transferable "delight" factors.
Data is a rearview mirror; it tells you where you’ve been, not where the road is turning. Product Intuition is the ability to see the "invisible" needs of the user before they can even articulate them. In a world of commoditized features, this capability allows a leader to make high-conviction leaps that create entirely new categories or reset the standard for excellence.
Leader Moves:
• The "Extreme User" Immersion: Spend time watching how the most frustrated or most creative users "hack" your product to solve their problems.
• Synthesize the "Job to be Done": Look past what the user says they want (features) to the emotional or functional "job" they are trying to hire the product to do.
• Low-Fidelity Prototyping: Build "ugly" versions of an idea quickly to test for a visceral "gut" reaction from users rather than polite feedback.
• Articulate the "Why" Behind the "What": Don't just demand a feature; explain the specific user tension it resolves so the team understands the logic of the intuition.
• Market Pattern Matching: Look at successful products in completely unrelated industries (e.g., gaming mechanics applied to fintech) to find transferable "delight" factors.
✍️ Practices (Next Edit)
When To Use (signals/triggers this card is right):
• You are in a Zero-to-One arena where no historical data exists to guide the way.
• Incremental optimizations (A/B testing) have plateaued and the product feels "boring" or commoditized.
• User research is coming back contradictory or lukewarm—indicating the users themselves don't yet know what's possible.
• A competitor is gaining ground through "soul" and "experience" rather than just specs and price.
When Not To Use (misuse risk):
• In Sustaining/Optimizing phases where clear data is available and small errors have massive downstream costs.
• When your "intuition" is actually just a personal preference or a desire to see your own idea come to life (ego vs. empathy).
• In safety-critical or high-compliance environments where "gut feel" cannot override verified evidence.
Example Scenario: A team building a fitness app is looking at data showing users drop off after three weeks. Most suggest "more push notifications." The leader using Product Intuition realizes the drop-off isn't about forgetfulness, but about the loneliness of the workout. Against the data-driven "notification" path, they bet on a "social ghost" feature where you see a friend's past workout while you train. The bet pays off because it addresses the unstated emotional barrier of isolation.
• You are in a Zero-to-One arena where no historical data exists to guide the way.
• Incremental optimizations (A/B testing) have plateaued and the product feels "boring" or commoditized.
• User research is coming back contradictory or lukewarm—indicating the users themselves don't yet know what's possible.
• A competitor is gaining ground through "soul" and "experience" rather than just specs and price.
When Not To Use (misuse risk):
• In Sustaining/Optimizing phases where clear data is available and small errors have massive downstream costs.
• When your "intuition" is actually just a personal preference or a desire to see your own idea come to life (ego vs. empathy).
• In safety-critical or high-compliance environments where "gut feel" cannot override verified evidence.
Example Scenario: A team building a fitness app is looking at data showing users drop off after three weeks. Most suggest "more push notifications." The leader using Product Intuition realizes the drop-off isn't about forgetfulness, but about the loneliness of the workout. Against the data-driven "notification" path, they bet on a "social ghost" feature where you see a friend's past workout while you train. The bet pays off because it addresses the unstated emotional barrier of isolation.
✍️ Anti-Pattern (Next Edit)
What shadow side looks like in the wild:
• The Ego Architect: Dismissing valid, contradictory data as "people just not getting it yet."
• The Feature Factory: Pushing through a series of "hunches" that result in a bloated, confusing product that lacks a core identity.
• User Contempt: Believing that "users don't know what they want" to such an extent that you stop listening to their actual pain points.
• The Lone Genius: Making "bold bets" in a vacuum without bringing the team along on the logic, leading to low morale and "execution friction."
• The Ego Architect: Dismissing valid, contradictory data as "people just not getting it yet."
• The Feature Factory: Pushing through a series of "hunches" that result in a bloated, confusing product that lacks a core identity.
• User Contempt: Believing that "users don't know what they want" to such an extent that you stop listening to their actual pain points.
• The Lone Genius: Making "bold bets" in a vacuum without bringing the team along on the logic, leading to low morale and "execution friction."
✍️ Evidence Signal (Next Edit)
What observable behaviors would prove this card is working:
• The "Aha" Moment: Users describe the product as "exactly what I needed" even though they never asked for those specific features.
• High Feature Adoption: New initiatives see immediate, organic pickup without heavy marketing or "nudge" tactics.
• Differentiation Gap: The product begins to look and feel fundamentally different from competitors who are just following the same data trends.
• Predictive Success: The leader’s "bets" consistently translate into market wins or shifts in user behavior that later show up in the data.
What observable behaviors would prove this card is failing:
• The "Solution in Search of a Problem": Shipping high-effort features that no one uses or understands.
• Constant Pivoting: Changing the product direction every time the leader has a "new feeling," resulting in whiplash for the engineering team.
• Metric Decay: Core engagement or retention numbers drop while the leader continues to double down on "the vision."
• The "Aha" Moment: Users describe the product as "exactly what I needed" even though they never asked for those specific features.
• High Feature Adoption: New initiatives see immediate, organic pickup without heavy marketing or "nudge" tactics.
• Differentiation Gap: The product begins to look and feel fundamentally different from competitors who are just following the same data trends.
• Predictive Success: The leader’s "bets" consistently translate into market wins or shifts in user behavior that later show up in the data.
What observable behaviors would prove this card is failing:
• The "Solution in Search of a Problem": Shipping high-effort features that no one uses or understands.
• Constant Pivoting: Changing the product direction every time the leader has a "new feeling," resulting in whiplash for the engineering team.
• Metric Decay: Core engagement or retention numbers drop while the leader continues to double down on "the vision."
