Good Design Isn’t Enough: You Need Product Sense

We’ve already talked about the dangers of delayed feedback loops.

We’ve talked about getting too attached to our ideas and mistaking emotional investment for value.

Now let’s talk about the third silent killer of good product work — one that’s harder to spot because on the surface, it looks impressive:

Confusing good design with good product.

Because here’s the uncomfortable truth that too few teams admit:

You can craft something beautiful. You can nail the spacing, the micro-interactions, the visual hierarchy. You can present it in a perfect Figma prototype with elegant transitions.

And still solve absolutely nothing.

It used to be rare to find products that looked good. Teams would spend months building functionality, and only then ask someone to “make it pretty.”

But that world is long gone. Design systems are mature. AI can generate full-page layouts in seconds. And thanks to open-source kits, anyone with a little Figma experience can assemble something that looks polished.

In other words: “looking good” isn’t hard anymore.

But good judgment?

Knowing what to design — when, why, and how?

That’s rare. That’s what product sense gives you. It’s not about visual polish. It’s about knowing how to make things that matter.

You know this moment. You ship the new flow. The UI is clean. The interactions feel slick. The stakeholders nod in approval. The Figma vibes are immaculate.

And then… nothing.

Adoption doesn’t move. Support tickets don’t drop. The onboarding drop-off? Same as before.

It looks better. But it doesn’t work better.

Because the problem wasn’t styling — the problem was friction, confusion, misalignment, or irrelevance. And no amount of good design can fix the wrong solution.

This is the trap: we style around the problem instead of solving it.

People love to throw around the phrase “product sense” like it’s some sixth sense only certain people are born with.

It’s not magic. It’s not about having perfect instincts or being a design oracle.

It’s about pattern recognition and purposeful thinking.

Product sense is knowing:

1. What goal we’re trying to achieve — for the user and for the business

2. What matters at this stage of the product lifecycle

3. What trade-offs are worth making — and which are just cosmetic

4. What success looks like — and how we’ll measure it

It’s about clarity over cleverness, impact over aesthetics, and intentional design over impressive design.

The teams with strong product sense zoom out far enough to understand what happens after the screen is shipped.

This isn’t just a designer problem. Or a PM problem. It’s a systems problem.

Most teams aren’t encouraged to build with product sense — they’re conditioned to focus on what’s visible, immediate, and safe.

Stakeholders judge what they can see — the UI.

Teams celebrate what they can measure — story points, shipped tickets.

Designers and PMs fall back on what they can control — screens, flows, features.

So we default to surface-level work. And when there’s no shared strategy, no clear goal, no defined success criteria…

Everything becomes subjective. Suddenly, the conversation is about button colour. The corner radius. The font weight. The “vibe.”

And we wonder why progress stalls.

When teams don’t have product sense baked into their culture, they revert to style over substance. Not out of laziness — out of survival.

If you want to build better, you need to ask better. Not “Does this look good?” but ut questions rooted in business value that could solve actual user problems:

1. Does this reduce friction?

2. Does this shift user behaviour?

3. Does this get the user to value faster?

4. Does this align with our strategy?

5. What metric is this expected to move?

These are uncomfortable questions. They demand clarity — and accountability.

But they give you an anchor and believe me… If you don’t set a metric for your work, someone else will and it will end up being a subjective metric you might not be able to reach.

Without them, your product process becomes a guessing game — one where success is defined only by internal opinions and aesthetic approval.

You don’t need a crystal ball. You need curiosity, courage, and a bias toward impact.

Here’s the thing about design debates: Without data, they’re just… vibes.

You’re in the review, walking through your latest work and someone says:

“It doesn’t feel premium.”

“Can we make it pop more?”

“I don’t know, it just feels… off.”

How do you argue with “feels off”?

You can’t.

But when your work is tied to metrics — even directional ones — the entire tone of the conversation shifts.

“We’re seeing drop-off at this step. This version is designed to reduce friction and improve activation by 15%.”

“This isn’t just visual polish — this cuts average completion time by 30 seconds.”

“The primary goal here is clarity, not cleverness. The hypothesis is that simpler language will reduce confusion in our core funnel.”

Now you’re not just presenting screens. You’re showing strategy. You’ve moved the discussion from opinion to outcome.

From preference to purpose.

It’s not their fault. If you walk into a review and show a bunch of screens — people will comment on the screens.

That’s what they can see. That’s what they’re wired to respond to. But you can guide the conversation.

Before showing a single visual, start with:

1. The problem you’re trying to solve

2. The data or feedback that informed this direction

3. The hypothesis you’re testing

4. The success criteria you’re aiming for

When you lead with clarity, the conversation gets sharper. Now people are evaluating the logic — not the layout.

You turn passive feedback into active collaboration.

Instead of

“Can we make this blue?”

You get

“Is this the best solution for the goal?”

That’s a better room to be in.

Here’s a mindset shift that changes everything: Design is not the finishing touch, it’s not a layer you apply at the end, it’s not just about polish.

Design is a strategic lever. It influences:

1. How users sign up (acquisition)

2. How they activate (onboarding)

3. How they succeed (adoption)

4. How they feel about the experience (NPS)

5. How long they stay (retention)

Design connects user needs with business goals. It’s the translation layer between strategy, systems, and psychology.

The best designs don’t call attention to themselves — they disappear into the experience. Because they work.

If no one mentions the design, but your metrics go up?

You won.

Here’s where product sense really levels up: Sometimes the best design move… is to do nothing at all.

Or better:

1. Remove a step

2. Kill a feature

3. Fix the backend

4. Rename a label

5. Rewrite the copy

6. Automate the manual task

It’s not about how much you add — it’s about what you change.

Design isn’t always a screen.

Sometimes, it’s a strategic decision that reduces complexity and friction without anyone even noticing.

This is where product sense diverges from visual design entirely. Because the goal isn’t to impress — it’s to improve. And sometimes, restraint is the most impactful decision you can make.

You can either impress in the meeting or deliver in the wild.

Great design has power. But power without direction is just performance.

Good design is table stakes now.

What separates great teams is product sense — the ability to zoom out, ask better questions, and design for outcomes, not applause.

You don’t need more layers. You need more clarity.

Wrestling with the mindset-shift?

Lets activate the wayback machine and take you to some of the other pieces that form the foundation of this:

👉 Learn how to let go of ideas holding your product back

👉 Learn how to stop over-investing in the wrong ideas

Until next time, remember…

Build. Better. Products!