To achieve product success, design needs to inform engineering, and engineering needs to inform design. Period. But this can be challenging to achieve since designers and engineers serve distinct functions, often approach problems from opposite points of view, and usually have different requirements and goals.
What product designers want
Designers want to create concepts that draw users in and meet their latent and unmet needs. As such, their design choices are geared toward:
- Creating a positive and memorable user experience that sets your product apart from the competition.
- Incorporating your company’s brand into the product through thoughtful and consistent design choices (whether or not you have an official design language).
- Ensuring your product looks innovative and modern while feeling ergonomically pleasing.
- Generating “must-have” enthusiasm for your product.
However, if designers don’t intentionally think about your product’s engineering constraints, they could create a beautiful concept that looks great in theory but falls flat in practice.
For example, one client came to us for help developing a concept another firm designed. The design was beautiful and exciting — and it had already captured the attention and approval of the client’s CEO, the executive leadership team, and the marketing department.
There was just one problem. When we started engineering the solution, we found that the designers hadn’t considered the size of all the components the product required. They dove right into creating a cool concept without factoring in the limitations of the product’s casing. This required us to refine and modify the design to make it work — which was disappointing and embarrassing for the client since they had already shopped the concept around to their stakeholders.
What product engineers want
Engineers are more concerned with function than form. So generally speaking, they’re much more interested in:
- Ensuring your design is feasible and can stand up to the demands of mass production and manufacturing.
- Crossing every regulatory “t” and dotting every “i.”
- Choosing the right mix of COTS and custom parts to maximize your product’s functionality and longevity.
- Keeping your product’s total cost within budget.
When engineering or contract manufacturers focus solely on these objectives, they tend to strip the product design down to the lowest common denominator to simplify the development process.
For example, we’ve worked with clients who have engaged our services to conduct user research, create conceptual designs, and produce user-tested, proof-of-concept prototypes. But then, due to cost or internal politics, they take our design to a contract manufacturer (CM) or their internal team for development.
Unfortunately, what often happens is that the CM or internal team eliminates essential parts of the design — like removing custom surfacing in favor of a smooth cylinder — without realizing those design choices were made specifically in response to user feedback. Then, when the product reaches the market, they wonder why it doesn’t resonate with users the way our initial research showed it would. It’s a classic case of being penny-wise and pound-foolish.