Designing a Hit Product
Most products that "hit" aren't the result of one clever idea — they're the result of getting a handful of unglamorous decisions right, in the right order.
Every founder we talk to has a version of the same hope: that the product they're holding is the one that breaks through. Most of the time, what separates the ones that actually do from the ones that quietly disappear isn't a single flash of brilliance. It's a set of decisions — some of them made long before the product ever looks finished — that most people never think to name.
Here's what those decisions usually look like.
It solves one problem clearly, not several problems vaguely
The products that break through tend to have an almost boring clarity about what they're for. Not "a smarter way to organize your life" — something specific enough that a stranger could repeat it back correctly after hearing it once.
Vague products try to be useful to everyone a little bit. Sharp products are useful to someone specific a lot. The second kind is much easier to design, market, and manufacture — and much harder to resist watering down along the way, especially once a team starts collecting feature requests.
It's obviously different, not just slightly better
"Better" is a hard case to make to someone scrolling past your product in three seconds. "Different" isn't. A product that looks, feels, or behaves in a way nothing else on the shelf does gets noticed before anyone reads a single spec.
This is a design decision as much as a positioning one. Differentiation usually shows up in form, material, or interaction — the things a person registers before they've consciously decided to pay attention. Category-defining products are rarely the most feature-complete option. They're the most legible one.
The price matches what it feels like in your hand
Perceived value is set by the senses before it's set by the spec sheet. A product can have excellent internals and still feel cheap the moment someone picks it up — a hollow-sounding button, a seam that doesn't quite align, a material that looks right in a photo and wrong in person.
The reverse is also true, and more useful: thoughtful material choices, weighting, and finish can make a modestly-specced product feel worth more than its price, before a customer has read a single feature. This is one of the highest-leverage design decisions a team can make, and one of the easiest to underinvest in when budget gets tight.
It was designed to be built, not just designed to look good
This is the decision that gets skipped most often, and it's the one we see cause the most damage after the fact. A design that looks right in a rendering isn't automatically a design a factory can build consistently, at cost, five hundred times in a row.
Designing for manufacturability isn't a constraint bolted onto a finished design — it's a parallel conversation that should be happening from the first sketch. Tolerances, assembly sequence, and material behavior at scale all shape what "good design" can actually mean for a given product. Teams that treat this as a later-stage problem tend to discover it's a much more expensive one to solve after tooling is already committed.
The details nobody consciously notices, notice anyway
Color, material, and finish (what the industry calls CMF) rarely get the attention they deserve relative to how much they influence a first impression. Neither does the sound a button makes, the resistance of a hinge, or how a product sits in the hand versus on a desk.
None of these show up on a spec sheet, and all of them shape whether a product feels considered or accidental. For products sold through unboxing-heavy channels — crowdfunding campaigns, DTC brands relying on organic social content — this extends to the packaging itself, which is often the first physical interaction a customer has with the brand at all.
Knowing when to stop iterating
There's no fixed number of design rounds that guarantees a good outcome, but there is a pattern worth watching for: early iterations tend to change the product meaningfully, and later ones tend to change it marginally. When a round of feedback starts producing small, aesthetic-only adjustments rather than functional ones, that's usually a signal the design has converged — and that further delay is costing more than it's improving.
The harder version of this problem is knowing when a design that looks finished still hasn't been tested against how a factory will actually build it. That's a different kind of "done," and it's worth treating separately.
None of this happens by accident, and very little of it happens by design talent alone — it happens because design and manufacturability were treated as one conversation from the start, not two conversations handed off at the end. That's the approach we take with every product that comes through Rlzed's Shanghai design team, whether it's headed for a Kickstarter campaign or an Amazon FBA listing.
If you're working through some of these decisions on a current product, we're happy to look at where it stands. Get in touch, or read more on how we take a product from prototype to production.
Frequently asked questions
How many design iterations does a good product actually need? There's no universal number — what matters more is the pattern. Early rounds should meaningfully change the product; once feedback is only producing small, cosmetic adjustments, the design has likely converged.
What's the difference between a good design and a manufacturable one? A good design solves the right problem and feels right in someone's hands. A manufacturable design can also be built consistently, at cost, across hundreds or thousands of units — which depends on tolerances, materials, and assembly decisions made early, not adjustments made after tooling.
Does CMF (color, material, finish) really matter that much? Yes, disproportionately so. Perceived value is set by touch and first impression before anyone reads a spec sheet, and CMF decisions are usually where that impression is won or lost.