Redesigning an existing product is worth doing when a specific, measurable problem cannot be solved any other way — unit cost that blocks a price point, a failure rate that is eating your margin in warranty claims, a component that has gone end-of-life, a certification that no longer applies, or a design that has visibly aged next to newer competitors. Redesign is not worth doing because the product feels dated to the people who built it. This guide separates the triggers that justify opening a working product from the ones that only cost money.

Triggers that genuinely justify a redesign

  • Cost. Unit cost prevents you from reaching a price the market will pay, or from funding the channel margins distribution requires.
  • Reliability. Returns and warranty repairs cluster around a known weak point. Field data pointing at one subassembly is the cleanest possible redesign brief.
  • Obsolescence. A microcontroller, sensor, display, or connector has gone end-of-life. This is the most common forced redesign in electronics, and it usually arrives with a deadline attached.
  • Manufacturing change. Volume has grown enough to justify a different process, or you are moving suppliers and the current design does not suit the new one.
  • Regulatory change. A standard has been revised, or you are entering a market with different requirements.
  • Competitive pressure. Competitors offer meaningfully more capability, better ergonomics, or a lower price and you are losing deals for a nameable reason.
  • New use or new market. The same product needs to survive outdoors, run on a battery, or be used by non-specialists.

What does not justify it: internal boredom, a new designer's preferences, or a vague sense that the product should be "modernized." If you cannot state the problem as a number — dollars of unit cost, percent of returns, units lost per quarter — you are not ready to spend on a redesign.

Three levels of depth, three very different budgets

Level one: cosmetic and surface refresh

Colors, textures, finishes, graphics, labeling, and packaging, with no change to internal geometry. Sometimes a new mold texture or a different paint process is all that is required. Cheap by redesign standards — often the low five figures for a modest product — and fast, because tooling is modified rather than replaced. The vocabulary for this level is in CMF design.

Level two: re-engineering inside a familiar shell

New circuit board, new firmware, a substituted motor or sensor, revised internal ribs and mounting bosses, while the external form and user experience stay recognizable. This is the most common redesign in practice and the best value for money, because you keep brand recognition, most documentation, and often much of the tooling. Budgets commonly run in the mid five figures upward depending on how much electronics work is involved.

Level three: ground-up redesign

New architecture, new form, new tooling, new certification. Effectively a new product development program that happens to have an existing product as its reference — and it should be planned and funded like one, following the same development process steps as a first product.

Choosing the level honestly is the most valuable decision in the project. Most disappointing redesigns are level-three problems funded as level-two projects.

Cost reduction: the most common brief we receive

When the driver is unit cost, the discipline is value engineering: reducing cost without reducing what the customer values. The usual sources of savings, roughly in order of return on effort:

  • Part count. Combining several molded parts into one, or replacing screws with snap features, cuts both piece price and assembly labor.
  • Tolerances and finishes. Tight tolerances and cosmetic finishes on surfaces nobody sees are pure cost. Reviewing the drawings against design-for-manufacturing rules routinely finds double-digit percentage savings.
  • Materials. A grade chosen conservatively years ago is often above requirement today.
  • Electronics consolidation. Integrating functions, removing unused circuitry, and replacing a module with components.
  • Process change with volume. Machining to casting, fabricated to molded, or a different molding strategy as quantities grow — see choosing a process by volume.
  • Assembly time. Often a larger cost line than any single component, and improved by designing for assembly rather than by pressing the factory.

Where to start when documentation is missing

Older products frequently exist only as physical objects: drawings lost, the original engineer gone, source files in a format nobody can open. In that case the redesign starts with reconstruction — measuring and modeling the existing part into current CAD, as described in reverse engineering a part. It feels like overhead. It is the only way to make a controlled change rather than a guess, and it produces the documentation you should have had all along.

How not to break what already works

A shipping product carries accumulated, undocumented knowledge: a rib added after a field failure, a tolerance tightened for a reason nobody wrote down, a firmware delay that prevents a rare fault. Redesigns fail when that knowledge is discarded.

  • Investigate before you change. Collect warranty data, service reports, and complaints, and interview the people who repair the product. They know where it breaks.
  • Change deliberately and in stages, using a real engineering change order process so every modification has a reason on record.
  • Retest as a system. A redesigned unit is a new configuration for safety, emissions, and durability purposes — assume reliability testing and applicable certification must be repeated, and budget it from the start.
  • Protect interfaces. If accessories, mounts, or consumables exist, changing a dimension can obsolete your customers' equipment and your own inventory.
  • Preserve the existing design until the new one is proven, and keep the old configuration buildable during the transition.

Getting an outside assessment

The most useful first step is usually a short, paid engineering review rather than a full program: a fresh team looks at the current design, the field data, and the cost breakdown, and reports what can be improved at each level of depth with an estimate attached. That report lets you decide whether to spend on a refresh, a re-engineering, or nothing at all.

Projects House performs this kind of review regularly on products already in the market. If you have a product that costs too much, fails too often, or has fallen behind, tell us about it through the contact form and we will tell you where the realistic gains are.