Home » “Best” 10 Design Mistakes To Avoid

“Best” 10 Design Mistakes To Avoid

Product design mistakes to avoid

Avoid these product design mistakes for a lot of troubles: some product features or technologies are tempting at first, but may, with or without additional factors or errors, be your next ticking time bomb or your disaster waiting to happen, leading to a lot of user dissatisfaction, quality complains, or even legal issues or market recalls.

We have divided here below these questionable mistakes into “user features”, or at least pretending to be for the user’s benefit, and “technical design choices”.

Of course, there may be good reasons to implement these as not being design mistakes, but do some Risk Analyses while implementing any of the below features or technology.

Do also have the long-term in mind, all the Life-Cycle steps of your future product or process, and not only your direct cost, assembly, or solution-finding to meet tomorrow’s project deadline.

The following two posts can be complementary readings on avoiding design mistakes:

 

Questionable Product Features Design Mistakes

in general,

avoid any product feature … that is not a user feature!

Non-user features may come much more frequently than desirable as specs are written, or the project develops.

Home-calling Device or App

Home-calling device or app: if there is no response … is your product working with fewer features? or maybe stops functioning completely? This is usually closely related to Licence and Subscription but can be for maintenance or other data mining reasons. Mind that, of course, the user’s location may be without connection, your infrastructure may be down, some countries have network restrictions or surveillance, and so on. Not to mention that your company or service provider may disappear or your IP address change … 

Tip on Tip: the above “feature” could become very close to the concept of planned obsolescence, depending on how this has been implemented and/or could have been avoided. Think twice

New Special Electrical Connector

Rare but standard electrical connector
Rare but standard electrical connector

Do not design a new electrical connector while OEM component catalogs have tons of them … Think twice before paying ten times more than an off-the-shelf solution, add CAPEX and brick walling your customer and your production by designing a new electrical connector.

And if your product needs an original number of connections, maybe taking the version above, with more wires, may permit future feature upgrades.

De facto standard water connector
De facto standard water connector

Do challenge your marketing if they want to brick wall your customer or want to sell accessories at a high price.

Keep in mind that for some industries, devices, and countries this is becoming illegal to power some home appliances with original connectors.

Note: this also applies to many fluid connectors

Device With Separate Software To Configure

Connected watch with remote software
Connected watch with remote software

The most underestimated flaw we observe these days, thus the highlight.

If your hardware device is intended to be configured remotely via a desktop app or a phone app … what about this nice user feature when their OS is upgraded or the computer or phone becomes obsolete? Will your device not lose all its versatility or even all its features? Examples include:

    • most connected watches
    • connected home appliances or home automation accessories
    • electronic music instruments
    • electric bicycles

… and generally, all small devices that, to gain cost or size, the designers and marketers have decided not to include their own buttons and screen and rely on a remote third party.

As for the battery advice below, of course, if your market approach is only a short-term sell and product life … you may not have the problem … yet. And, of course, this is not the approach we recommend here for value-added and ecological products.

The Million Dollar Tip: we strongly recommend having a clear view of the software upgrades that you will maintain -or not-, and have accounted for this, even long after you do not sell the main product anymore. And to avoid potential legal actions (highly probable if you have a high runner product), do communicate on this since day one (yes, at least the small prints on the box or IFU …)

Complex screw patterns already existing
Complex screw patterns already existing

Original Screw Pattern

With a specific pattern on both the screw and counterpart. If you really -we already challenge that- need something special (high torque, extremely small or big, user-limited access …), tons of unique patterns already exist.

Note: to some extent, this also applies to any specially designed tool.

 

Software Driven Shut Off

No physical on/off switch, but a fully software-driven on/off having no main switch permits a leaner design, may reduce the cost or size, or avoid some water sealings, but if that function is handled only by software, do ensure that it is robust before implementation to avoid one day having to tell your users:

Wait until the battery depletes completely” :(

or “Unplug the main power cable“, and even in these cases, think twice if the hot/cold boot mode will solve the problem or crash even more.

Tip on Tip: your device does have a physical on/off switch, but it is on the back of the equipment, and the equipment is frequently, or intended to be, fix-mounted…

No Remote Software Upgrade Possibility

via bootloader or equivalent system for micro-controller based or full software install for bigger operating system-based products, the possibility of upgrading the system is a 99% must. Of course, some critical safety, data protection, minimal code or hardware size, or other valuable reasons may forbid that, but would you guarantee that your product is entirely bug-free?

And would you like to tell your users or sales channels in advance that they will never have some feature improvement without repurchasing it or returning it to the factory because the design did not take that into account?

Over-necessity of Explanations or Labeling

If to use your product,  you feel the need to explain in the IFU, on the stickers, on the...

Innovation.world community

Login or Register (100% free)

View the rest of this article and all members-only content and tools.

Only real engineers, manufacturers, designers, marketers professionals.
No bot, no hater, no spammer.

Table of Contents
    Ajoutez un en-tête pour commencer à générer la table des matières

    DESIGN or PROJECT CHALLENGE?
    Mechanical Engineer, Project or R&D Manager
    Effective product development

    Available for a new challenge on short notice in France & Swiss.
    Contact me on LinkedIn
    Plastic & metal products, Design-to-cost, Ergonomics, Medium to high-volume, Regulated industries, CE & FDA, CAD, Solidworks, Lean Sigma Black Belt, medical ISO 13485 Class II & III

    We are looking for a new sponsor

     

    Your company or institution is into technique, science or research ?
    > send us a message <

    Receive all new articles
    Free, no spam, email not distributed nor resold

    or you can get your full membership -for free- to access all restricted content >here<

    Topics covered: design mistakes, user features, technical design choices, risk analyses, product life-cycle, planned obsolescence, electrical connector, de facto standard, software configuration, connected devices, user dissatisfaction, quality complaints, legal issues, market recalls, maintenance, data mining, and software upgrades..

    1. Alek Schinner

      It’s a reminder that designing with longevity and user experience in mind is essential to avoid not just technological obsolescence, but also potential legal and customer satisfaction issues.

    2. toney rolfson

      This article highlights crucial considerations for product design, emphasizing the importance of user-friendly interfaces, robust software integration, and thoughtful feature grouping.

    3. Neva Block

      This article hits the nail on the head by emphasizing the importance of avoiding design decisions that prioritize short-term gains over long-term usability and customer satisfaction. It’s crucial for companies to consider the entire product lifecycle and potential pitfalls, such as reliance on proprietary connectors or separate configuration software, to ensure they don’t alienate users or face legal challenges down the road.

    Leave a Comment

    Your email address will not be published. Required fields are marked *

    Related Posts

    Scroll to Top

    You May Also Like