The Right Product Problem: Why Hardware Teams Struggle to Build What Actually Matters

Building the right product isn't about solving technical problems. It's about holding the tension between the people who solve them.

This is something I've learned the hard way across 20+ years of shipping consumer hardware. The products that succeed aren't the ones with the best specs in any single dimension. They're the ones where every discipline was pushed to its limit, and the team still found the sliver of overlap where all of it could be true at once.

The Venn diagram nobody draws

Every hardware product is a negotiation between competing priorities. Industrial design wants the product to look and feel incredible. Acoustics or sensing or optics wants the core experience to be flawless. Thermal engineering needs safe and comfortable operating margins. Mechanical engineering needs the thing to survive years of real-world use. Manufacturing needs it buildable at scale. And cost needs the whole package to ship at a price that makes the business work.

Each of those disciplines has a legitimate claim on the product. And each one, left unchecked, will optimize for their own domain at the expense of the others.

Picture a Venn diagram with all of those circles overlapping. The right product lives in the center, where every circle still intersects. The job of the product leader is to push every circle outward as far as it can go while making sure they still touch in the middle. A wide, comfortable overlap gives you a safe but mediocre product. The tightest possible center, where every discipline has been pushed to its limit and the overlap barely holds, that's where the best products live.

Where it goes wrong

The pattern I've seen repeatedly is simple: one discipline dominates, and the rest of the team accommodates.

The most common version is design-led. A strong industrial design vision drives the product, and engineering is expected to "figure it out" within those constraints. The result can look stunning on the shelf. But behind the scenes, the team is battling thermal issues that were baked in by form factor decisions made too early. Or dealing with manufacturing complexity that drives up cost and kills reliability. Or hitting supply chain problems because the materials and tolerances that make the design work aren't scalable.

The product ships. But it ships late, over budget, and with quality issues that erode trust with users. Sometimes it ships and then gets quietly killed a generation later because the economics never worked.

I've seen this pattern play out more than once across different companies. In one case, the design constraints were so far out of balance with manufacturability and cost that the right call was to kill the project entirely. In another, we were able to break the logjam by demonstrating with data that the Venn diagram had no center. There was no overlap. We had to reset the conversation before we could move forward.

The fix isn't a spec sheet

When teams hit this kind of impasse, the instinct is often to create a more detailed spec. More requirements. More documentation. Tighter tolerances.

That rarely helps. The problem isn't that people don't know the specs. The problem is that the disciplines aren't having the right conversations with each other.

The fix is better conversations. And those conversations start with trust.

Push for excellence first

Here's what I've found actually works: instead of asking disciplines to compromise early, push each one to be excellent in their own domain first.

This sounds counterintuitive. If the overlap is already small, why encourage people to push further apart?

Because that's exactly how you find the most ambitious version of the product. When you push a discipline leader to define what "great" really looks like in their area, two things happen. First, you learn what truly matters versus what's nice-to-have. There's a difference between what a discipline needs and what they want. Pushing for excellence forces that distinction to the surface. Second, you build trust. When an acoustics engineer sees that you genuinely care about the sound experience, not just checking a box, they trust you. And when you eventually come back and say "we need to negotiate on this specific parameter because thermal can't close the gap," they're willing to have that conversation honestly.

The same goes for every other discipline. Meet them where they are. Understand their domain deeply enough that they see you as an advocate, not an obstacle.

Becoming the negotiator

This trust is what earns you the right to negotiate.

On one of the most technically challenging products I worked on, the tension between four major disciplines nearly broke the program. Industrial design had a vision. Acoustics had performance targets tied to the core user experience. Mechanical had to incorporate complex thermal mitigations. And thermal engineering needed to ensure the product always operated in a safe and comfortable regime.

None of those teams were wrong. All of their concerns were legitimate. And at various points, it felt like there was no path forward that could satisfy all of them.

What made it work was not some clever technical trick. It was the fact that I had spent time with each discipline leader understanding what they truly needed. I had pushed them to define excellence in their own terms. So when we sat down to negotiate the overlap, I could speak each team's language. I knew which parameters had real flexibility and which ones were genuinely load-bearing. I had the trust to make calls, and the credibility to bring everyone along.

The product shipped. And it shipped with the design vision intact, the core experience hitting its targets, and the engineering doing its job quietly in the background, the way it should.

The people problem that isn't a problem

I sometimes hear leaders describe cross-functional tension as something to be managed or minimized. I think that's wrong.

The tension is the point. When disciplines push hard against each other, the product gets better. The design gets refined. The engineering gets sharper. Compromises happen in the right places instead of the easy places.

The job of the product leader isn't to eliminate that tension. It's to hold it. To make sure every voice is heard, every concern is real, and every tradeoff is conscious.

That's how you push every circle outward while keeping the center intact. Not by asking people to want less, but by understanding what they truly need and finding creative paths that let every discipline stretch further than they thought possible.

What this looks like in practice

If you're leading a hardware product team and the disciplines feel misaligned, start here:

Stop negotiating tradeoffs before you understand what "great" looks like for each discipline. Let them define it. Push them to stretch.

Separate needs from wants. Every discipline has non-negotiables and nice-to-haves. Your job is to help them tell the difference, and to hold the team accountable to the non-negotiables while creating flexibility everywhere else.

Use real user data to break ties. When two disciplines are stuck, the answer is almost always in how the user actually experiences the product. Data doesn't play politics.

Build trust before you need it. If the first time you're having deep conversations with a discipline leader is during a crisis, you're too late.

The right product is never the one that maximizes any single dimension. It's the one that pushes every circle in the Venn diagram as far outward as possible while keeping the center intact. That's a people skill, not a technical one.

And it's the skill that separates products that ship from products that matter.

If you're navigating this tension on your team right now, I'd love to hear what it looks like!