Balancing research, intuition, and influence.

After nearly two decades designing products across industries, from big tech giants to fast-moving startups, I’ve realized the most impactful designs aren’t always the flashiest or most complex. They’re the ones that emerge from clarity of thought, deep empathy, and the ability to drive alignment around a shared vision.

Here’s what I’ve learned really matters in product design, not just to get things built, but to make sure they matter.

Start with research. But don’t end there.

Research is your compass. It grounds you in the problem space and gets you out of your own head, which, for designers, is sometimes the hardest part.

You don’t need a 60-page deck or a six-month ethnographic study. But you do need insight. Whether that’s a quick pulse-check with users, a friction audit, or a series of unfiltered Slack messages, start by listening. You’re not just trying to find pain points, you’re looking for patterns, mental models, and unmet needs.

But here’s the thing: data has a shelf life. It tells you what was true. Your job is to interpret that data and project what could be true. That’s where intuition comes in.

Trust your intuition. Especially when the data is noisy.

Some of the best product calls I’ve made came from a gut sense that something was off. That a friction point wasn’t just a UX flaw, but a trust issue. Or that a low-converting flow wasn’t about the buttons, it was about the tone, timing, or emotional context.

Intuition gets a bad rap in data-driven orgs. But when you’ve done the reps, when you’ve studied behavior, tested ideas, and made enough mistakes, your intuition becomes a reliable tool. Not infallible, but sharp.

So lead with research. But when you feel that nudge, a subtle contradiction or a pattern nobody else sees, lean into it.

Design is part science, part art. The best work lives in the tension between the two.

Frame problems, don’t just solve them.

One of the biggest shifts I made as a designer was moving from problem-solving to problem-framing.

It’s easy to jump to solutions, wireframes, prototypes, mockups. But the real leverage is in defining the right problem. That means asking better questions:

Are we solving for the user’s actual goal, or just improving a broken flow?
Is this a usability issue, or is it about trust, clarity, or motivation?
Is the problem behavioral, technical, or organizational?

Stakeholders don’t always know how to think this way, and that’s okay. It’s your job to guide the conversation. Frame the problem well, and alignment follows naturally.

Influence is earned, not given.

You can design the best solution in the world, but if nobody’s bought in, it won’t ship.

Influence isn’t about being the loudest in the room or having the perfect pitch. It’s about building credibility over time. Delivering consistently. Asking smart questions. Knowing when to push, when to listen, and when to let go.

I’ve learned to speak the language of product, engineering, and business. I focus on shared goals, not design purity. And I invite feedback early, not just to avoid rework, but to co-create solutions that stick.

Design is a team sport. Influence isn’t about winning, it’s about elevating the game for everyone.

Final thought: Elegance over complexity.

At the end of the day, I’m drawn to elegant solutions, the kind that feel obvious after you see them. They’re simple, not simplistic. Confident, not clever. Grounded in truth, but shaped by vision.

The real craft of product design isn’t in the pixels. It’s in how you think, how you listen, and how you bring others along.

Design isn’t just what it looks like or how it works. It’s how it solves, how it feels, and how it matters.

What actually matters in product design was originally published in Design Tension on Medium, where people are continuing the conversation by highlighting and responding to this story.