Product Sense in the Age of AI: Why Great Builders Are Addicted to What They Do

Some people just know when a product is right. You show them something and in 30 seconds they've found the three things that are off, and the one thing that's actually working. No user interviews. No data pulled. They just feel it.

I've spent years trying to understand what separates these people from everyone else. It comes down to one thing. They build for themselves.

Not "they skip user research." They do the research. They talk to users, they read, they observe. But the goal isn't to follow a process, it's to internalize. To absorb the insight so deeply that it stops living in a doc somewhere and starts shaping how they themselves experience the product. They become the user.

That changes how the whole loop works. They observe people not to collect data, but to understand why people behave the way they do. So when they sit down to design, they're not guessing. They're extrapolating from something they actually understand. Then they build, and they can evaluate what they built themselves. Multiple internal rounds. Refinements before a single user sees it. By the time they show someone, it's already been through five generations. Or fifty.

A builder without that internal model works differently. Build, can't tell if it's right, go to users. Build again, still can't tell, go back to users. The loop is long because every step needs external validation. They're not iterating, they're polling.

Same effort. Dramatically different velocity.

This is why engineers and designers who build tools for themselves have always had the edge. When you use what you're building, you don't have to imagine what "working" feels like. You feel it. The distance between you and the problem collapses.

So can you develop this?

Absolutely yes. But not the way most people try. The instinct is to study the craft, to become a master of the techniques, to collect frameworks and best practices. That's the wrong target. The goal isn't to become a master of the craft. It's to become a master of the usage. You have to embody the user, in all their shapes and forms, until you can inhabit their experience as if it were your own. Intuition isn't a gift you're born with. It's just internalized experience. And the only way to internalize the experience of others is to relentlessly pursue understanding them, until the line between observing them and being them disappears. Chase mastery of the user, and the intuition follows.

The length of that loop doesn't just determine how good your product gets, that's what people underestimate. It determines how much you enjoy the work.

Think about why games are so absorbing. You act, and you see the result instantly. You move, you hit the target, you get the feedback, you adjust, you go again. The loop between action and consequence is measured in seconds, and that tightness is what pulls you into flow. You lose track of time. You don't want to stop.

Most knowledge work is the opposite. You make a decision and find out if it was right in weeks. Months. Sometimes never. The feedback is so delayed and so noisy that you can't connect what you did to what happened. That disconnect is why so much of the work feels like a slog. There's no reward signal close enough to the action to matter.

The intuitive product maker has quietly solved this. 

Because they can evaluate their own work, the loop collapses to almost nothing. Design something, sense whether it's right, adjust, go again. The reward isn't out there in some future user test. It's immediate, internal, and constant. Every iteration delivers a small hit of yes, closer. That's the same mechanism that makes games addictive, except now it's pointed at building something real.

The process-oriented maker never gets that. Their reward is always external and always delayed, sitting at the end of a long validation cycle they don't control. They can't feel themselves getting closer, because they can't tell where they are. The work stays effortful instead of becoming flow.

That's the hidden gap. It isn't only that intuitive makers ship better products faster. It's that they're getting a dopamine hit on every cycle while everyone else is waiting for permission to feel good about their work.

Now add AI.

AI compresses the build step to almost nothing. Two weeks becomes two days. Two days becomes two hours. The loop gets shorter for everyone, but not equally.

AI is a multiplier on the internal loop. If you can evaluate what you're building yourself, AI gives you more cycles per day, more refinement before anyone else sees it. And because the loop was already tight, making it tighter is pure joy. The hits come faster. The flow deepens. The work stops feeling like work.

If you don't have that internal loop, AI just gets you to "I don't know if this is right" faster. You still need external validation at every step. You've sped up the part that was never the bottleneck, and the reward is still stuck at the far end of someone else's calendar.

Because the dopamine was never about building fast. It comes from knowing. From shipping something, using it yourself, and feeling it work. 

That tight, self-reinforcing loop is what creates flow, and it's what makes the best builders genuinely addicted to their craft.

You can't buy it or install it. You build it by becoming a real user of the thing you're making, and never stopping.