The form was six steps long. The data said it worked. Completion rates were acceptable. The funnel wasn’t leaking in any obvious way.
But something felt wrong.
I kept going through the flow myself, over and over, and there was this friction I couldn’t name. Not a bug. Not a usability error you could point to in a heuristic evaluation. Just a feeling that the user was doing too much thinking at step three.
So I cut it. Removed the step entirely. Replaced a confusing post-address input with something simpler. 30% more users continued the form.That was at Sell2Rent, where I’m the sole product designer in a 35-person company. And it was one of several CRO changes I made based on a mix of data and something harder to explain: the gut feeling that the numbers weren’t showing the full picture.
What Your Gut Actually Is (It’s Not Magic)
Product intuition gets mystified. People either worship it or dismiss it. The reality is simpler and more useful than either camp admits.
Your gut is pattern recognition running faster than your conscious mind. Every product you’ve used, every user interview you’ve sat through, every A/B test result you’ve read, all of that gets compressed into something that feels like instinct but is really just experience processing at speed.
There’s actual neuroscience behind this. The Iowa Gambling Task demonstrated that the body detects risk before the conscious mind can articulate it. Participants showed physiological stress signals when reaching for “bad” options before they could explain why those options were bad. Your body is doing math you can’t see.
For designers, this means something specific: the more real products you’ve shipped, the more real users you’ve watched struggle, the faster your pattern recognition becomes. It’s not a gift. It’s accumulated reps.
The Data Paradox: Why Numbers Alone Don’t Ship Great Products
Data-driven decision making is the default religion in startups. And for good reason. Companies that use data systematically are more likely to acquire and retain customers.
But here’s the paradox I’ve lived through multiple times: data is backward-looking. It tells you what users did within the constraints you already built. It’s excellent at incremental improvement. It’s terrible at telling you when the whole frame is wrong.
At Keller Offers, we had NPS 90 from prototype testing. Every deliverable approved. The project still failed. Not because the data was wrong, but because the data was measuring the wrong thing. We were testing prototypes with a small internal group while the structural problems—management absence, unilateral dev decisions—were invisible to any metric.
Data tells you what is happening. Intuition tells you why. Competitive advantage comes from how you prioritize and act when the signals conflict or when the numbers look fine but something doesn’t feel right.
When Your Gut Lies to You
Trusting your gut without checkpoints is how you ship your own preferences instead of what users need. I’ve done it. Most designers have.
The three biases that hit product designers hardest:
Confirmation bias is the most dangerous. You have a hypothesis about a feature, so you unconsciously cherry-pick the data that supports it and dismiss the rest. The fix is simple but uncomfortable: before you ship, spend 30 minutes trying to disprove your own idea. If it survives, it’s probably real.
Anchoring hits in design reviews. The first solution presented becomes the reference point. Everything after gets compared to it, not evaluated on its own merit. I’ve learned to present the option I’m least attached to first.
Availability bias is the one that kills prioritization. The CEO mentions something in a meeting, or a loud customer writes an angry email, and suddenly that issue feels urgent. Track patterns over time. One anecdote is noise. Ten anecdotes are signal.
The Framework I Actually Use
After 8 years in startups, I’ve landed on a simple decision matrix. Not because frameworks are inherently useful, but because this one keeps me honest.
High risk, low clarity: invest in research. Talk to users. Watch them use the product. Don’t trust your gut here because you don’t have enough reps in this specific context. This is where I spend time with tools like Optimal Workshop or Pagesense before touching Figma.
Low risk, high clarity: trust your gut, ship fast, measure later. If you’ve solved this type of problem before and the downside of being wrong is small, move. Speed matters more than certainty.
The dangerous zone is medium risk, medium clarity. That’s where most product decisions actually live. And that’s where the discipline matters most: structure your gut feeling into a hypothesis. “I think removing this step will increase form completion by 15% because users are making a cognitive switch they don’t need to make.” Now you have something testable instead of something arguable.
What Y Combinator Gets Right About Product Sense
Y Combinator defines product sense as the intuition for what makes a product “good” and the empathy to build what people love. That’s a useful definition because it doesn’t separate the analytical from the instinctive.
Paul Graham’s framing is even more precise: great startup ideas come from “noticing” real problems, not from sitting in a room brainstorming “plausible-sounding” concepts. Noticing is a gut function. You see friction because you’ve trained yourself to see friction.
The counterintuitive part—and the part most relevant to designers—is that startups often violate standard instincts. The “safe” path is usually wrong. The feature that seems too simple to ship is often the one that works. The design that feels unfinished is sometimes more honest than the polished version.
This is something I’ve seen firsthand. At Sell2Rent, my best CRO wins weren’t additions. They were removals. Cutting a confusing step. Replacing a legal popup with a pre-checked checkbox. The gut said “this is too much.” The data confirmed it after.
How to Train Your Design Gut (Without Waiting 8 Years)
Product intuition isn’t a personality trait. It’s a skill built through deliberate practice. Here’s what actually works:
Use every product critically. Not casually. When you download a new app, pay attention to your first 30 seconds. Where did you hesitate? What confused you? What delighted you? Julie Zhuo calls this “product critiques” and it’s the single fastest way to build pattern recognition without shipping anything.
Build your knowledge from the outside in. Start with the customer’s life, not the product’s features. Merci Victoria Grace frames this as a hierarchy: understand the person, then their problems, then their use cases, and only then the features. Most designers start at the feature layer and wonder why their intuition feels shallow.
Talk to users in ways that produce real data. The Mom Test by Rob Fitzpatrick is the best framework for this: ask questions that avoid biased, polite answers. Don’t ask “would you use this?” Ask “what did you do last time you had this problem?” The difference between those two questions is the difference between performative feedback and actual signal.
Shadow customer support. Seriously. Spend two hours a week reading support tickets or sitting with the CS team. You’ll develop intuition for user pain faster than any research sprint.
The Startup Ecosystem Where This Matters Most
I’m a Colombian designer working with US startups, and there’s something specific about the Latin American ecosystem that makes product sense even more critical.
The region has evolved into a high-growth environment spanning 20+ countries and 660 million people. Brazil and Mexico concentrate 70% of regional venture capital, with fintech absorbing 61% of VC dollars to solve real gaps in financial inclusion.
But here’s what matters for product designers: in a tighter investment market where capital efficiency is the priority, design decisions carry more weight. You can’t A/B test everything when your runway is 14 months. You can’t run a three-week research sprint for every feature when you’re the only designer in a 35-person company.
That’s my reality at Sell2Rent. And it’s the reality for most product designers in Latin American startups. You need enough intuition to move fast and enough discipline to validate the bets that matter. The designers who thrive in this environment aren’t the most creative or the most data-literate. They’re the ones who know when to trust the pattern recognition and when to stop and test.
The Real Answer: A Loop, Not a Choice
“Can you trust your gut?” is the wrong question. The right question is: “Have you built a gut worth trusting?”
The best product designers I’ve worked with don’t choose between data and intuition. They run a loop. Intuition generates the hypothesis. Data validates or kills it. The result feeds back into intuition, making the next hypothesis sharper.
After 8 years in startups, from pure UI work at Mentive to running CRO and marketing automation at Sell2Rent, the loop is what I trust. Not my gut alone. Not the dashboard alone. The conversation between the two.
Document the hypotheses. Test the ones that matter. Ship the ones that survive. That’s the whole framework.
Document the hypotheses. Test the ones that matter. Ship the ones that survive. That’s the whole framework.
Want to see how I apply data and instinct in real projects? Check out my case studies or connect with me on LinkedIn.