Your product has a personality. You just didn't design it.

The motor hums. The button clicks. The confirmation beeps. The system goes silent while it thinks. Your user has already decided — in five seconds — whether your product feels cheap or premium, friendly or cold, trustworthy or annoying. That decision was made without your involvement.

The car door test

Close a Mercedes door. Now close a Dacia door. The difference isn't the material — it's that someone at Mercedes designed the sound of the door closing. The weight, the resonance, the finality of the thud. It communicates solidity, precision, money well spent. That sound was engineered, tested, and refined. It's not an accident.

The automotive industry understood decades ago that sound is brand. Every engine note, every turn signal click, every parking sensor tone is a design decision. The rest of the product world hasn't caught up.

Your product makes sounds too. The question is: did anyone decide what they should communicate?

See also: Sound carries more information than you think →

What happens when nobody is responsible

Here's how product sound typically works. The engineering team builds the product. At some point, someone realizes it needs audio feedback. The firmware developer picks a beep frequency. The UI designer says "sound isn't my department." The product manager says "we'll handle that later." Later arrives, and there's no budget.

The product ships with whatever sounds the last person to touch it happened to choose. A default tone from a component library. A beep that was meant as a placeholder and became permanent. Or — increasingly common — no sound at all, because nobody could agree on what it should be.

All of these are design decisions. They were just made by accident instead of on purpose. And they communicate: indifference, laziness, "we didn't think about you."

Sound is not audio decoration

There's a fundamental difference between "we need a nice sound for the startup" and "how should the encounter with this product feel?"

The first is an asset order. You browse a sound library, pick something that doesn't offend, and ship it. The second is a design question. It requires understanding who the user is, what context they're in, what emotional state the product should create, and what the silence between interactions should feel like.

The first gets you a sound. The second gets you a sonic identity — a coherent system of sounds that work together to make a product recognizable, navigable, and approachable. The difference is the same as between picking a font and designing a visual identity.

Three questions that change everything

Before a single sound is produced, three questions need answers:

What does your product communicate acoustically right now? Listen to it. Record it. Play it back. The motor noise, the fan, the relay clicks, the silence during processing. That's your current sonic personality. It exists whether you planned it or not.

What should it communicate? Reliability? Warmth? Precision? Playfulness? Intelligence? This can't be the same answer for every product — and it can't be "all of the above." A surgical robot and a home assistant need fundamentally different sonic characters, even if both need to feel trustworthy.

What happens in the silence? What does your product feel like when it's idle? When it's waiting? That acoustic space is part of the personality too.

The invisible advantage

Think about the products you genuinely enjoy using. Not just tolerate — enjoy. The ones where you'd say "it just feels right." There's a good chance those products have a designed acoustic layer. You don't notice it consciously. But you'd notice immediately if it were gone.

This is the invisible competitive advantage of designed sound: the product simply feels like it was made by people who cared about every detail. Not louder, not flashier — just more considered. From the warehouse robot that announces itself before rounding a corner, to the medical device that confirms a completed scan with a tone that feels reassuring rather than clinical.

Your product already has a personality. The only question is whether you're going to design it — or leave it to chance.