MENU

 

15-Aug-2017

Simplexity’s 7 Steps to Simplification©

By Dorota Shortell (Chief Executive Officer)

 

Simplexity’s brand promise is to deliver simple solutions to complex engineering challenges. As many in the field know, it’s actually harder to develop elegant solutions with fewer parts and components. Adding parts, cost, and complexity to solve issues is often much easier than taking things away. At Simplexity, we’ve formalized our process into the 7 Steps to Simplification©.

1. Ask questions

The most important part of the process is at the very beginning: asking questions. A large quantity of questions, but more importantly the right type of questions. Questions that are open-ended and challenge the status quo of how products have typically been designed rather than questions with one right answer. My favorite question is “why?”

Why does a product need to be designed a certain way? Why do you need that feature? Why have other products been designed a certain way? Why does the customer need this product? Why are other solutions on the market not as compelling? The goal of this step is to open the design space and break down pre-conceived assumptions. Done well, this step often teases out hidden needs and opportunities.

2. Write down the specifications

The next step is to write down the specifications, specifically a document with all the requirements. Many clients who come to Simplexity are under tremendous schedule pressures. The ones who successfully develop the simplest and most elegant solutions are the ones who, even with the need to start designing right away, understand the need to write down all the requirements in a specification document. Teams often think they know what they want to design, but when you write down the requirements, it often reveals conflicting assumptions or needs.

A good requirement has two aspects. First, it must be specific and testable. For example, a poor requirement for battery life would be “must have long battery life.” “Long” could mean different things in different contexts. What does “long” mean for this product? How do you test to make sure a battery lasts a “long” time? A better requirement specification would be “this battery must last three days between charges when used 10 hours per day.”

The second aspect to a good requirement is that it states a requirement, not a design. Returning to the battery example, the requirement should not be “battery must have a capacity of 1000 mAh.” This is too specific. It forces the hand of the design team, and precludes other features that could require more power. It’s important that the requirements specification not restrict the design space unnecessarily or bring in assumptions about how a system will be designed too early.

3. Brainstorm from a systems perspective

We believe in brainstorming from a systems perspective since it has successfully yielded tremendous simplification results. For a few examples, read my earlier blog post, “If I Could Only Do 3 Things to Simplify a Design, What Should They Be?” Challenge assumptions about which engineering disciplines are responsible for which functions. Having the whole team involved and drawing on the diversity of their opinions and experience in the brainstorming process leads to unexpected combinations and solutions. These combinations yield a simpler product architecture, and often deliver product cost savings and reliability improvements.

4. Design with the end in mind

Step 4 is to design with the end in mind. This step focuses on risk. Figure out what the riskiest subsystems are likely to be in your product and design those subsystems first. By considering how users will interact with the product, how it will be manufactured and assembled, and what the possible error areas could be, you start to understand where the most design focus should be applied.

If, for example, the biggest risk to the product is that it’ll be used in wet and humid environments, you want to design for that up front. You get a simpler design by understanding that additional seals and methods for keeping water away from sensitive electronics should be incorporated into the core design, rather than adding those parts at the end. For more details on how we mitigate risk, readDoug Harriman’s two-part blog post on risk mitigation.

5. Do the math

One distinguishing aspect of Simplexity’s hiring process is that we require our engineers to be able to solve complex analytical design problems during the technical interview. The best designs require that they use those skills. For example, it’s not enough to have a mechanical engineering degree if you don’t know how to draw a free body diagram to represent a system and solve for what forces each component would experience. Doing the math and performing critical calculations — such as for strength, tolerance stackup, and fatigue life — can save expensive build and test cycles. For a detailed example of this, read Gabriel Aldaz’s blog post, “Why Engineering Still Matters in Product Development.”

6. Prototype and test

The next step is to prototype and test the highest risk subsystems. Targeted proof-of-concept prototypes help you dial in the critical design areas. This step ties back to Step 2, about writing down the requirements specification. When writing the requirements, you must also have an agreed-upon plan for how each can be verified and tested by the engineering team. This also ties into Step 4, designing with the end in mind, since you use early prototypes to prove out the parts of the design you’re most worried about. We don’t want to spend time and money creating a beautiful housing for a device if the core technology has not yet been prototyped and shown to work.

7. Select proven manufacturers

The final step is to select proven manufacturers. Although this step shows up last, design is an iterative process, not a linear one. If we know that a certain design will be pushing the limits of traditional manufacturing, we will look for cutting-edge manufacturing technologies early in the design process. This allows the manufacturing experts to give feedback early in the design to keep the parts as simple as possible from both a design and manufacturing perspective.

For more on topics related to product design and testing, follow Simplexity’s product development blog.


Subscribe For More

To receive more articles like the one above in your inbox, sign-up to our newsletter below.

Blog Posts


Better Firmware Faster

19-Nov-2018

Demystifying What it Takes to be a CEO

18-Oct-2018

Considerations for Code Refactoring

24-Sep-2018

American Association for Clinical Chemistry Annual Meeting

30-Aug-2018

Simplexity's Answer to Growing Pains

09-Aug-2018

Consumer Electronics Show 2018 | Part Three | So, What is a Robot?

29-Jan-2018

Consumer Electronics Show 2018 | Part Two | CES 2018 and IoT

22-Jan-2018

Consumer Electronics Show 2018 | Part One

15-Jan-2018

Why on earth are heavy weights being suspended from this printer?

22-Dec-2017

10 Best Places to Buy Parts for Product Development

29-Nov-2017

Robust Firmware Stack Sizing

08-Nov-2017

Senaptec Strobe: A Study in Simplification

19-Oct-2017

Treatment, Prevention, and Medical Engineering Solutions

04-Oct-2017

Options in Product Development Models: Internal, CDM, or Design Specialist

20-Sep-2017

Designing Thermal Control Systems

30-Aug-2017

Simplexity’s 7 Steps to Simplification©

15-Aug-2017

Battle of the Buttons: UCSD vs. PSU

02-Aug-2017

Considerations For Medical and Biotech Designs

13-Jul-2017

Risk Mitigation in Product Design: Part 2

11-Jul-2017

Risk Mitigation in Product Design: Part 1

28-Jun-2017

San Diego's Biotech Consortium

09-Jun-2017

Appropriate Models for 3D Motion Analysis: Part 3

25-Apr-2017

University of Oregon’s Product Design Program Is One of a Kind

19-Apr-2017

Appropriate Models for 3D Motion Analysis: Part 2

14-Apr-2017

From Engineer to Leader: How Do You Get There?

12-Apr-2017

Appropriate Models for 3D Motion Analysis: Part 1

06-Apr-2017

Why Engineering Still Matters in Product Development

29-Mar-2017

How Mechatronics Improve Drone Technology

16-Feb-2017

Why You Need a Gyro to Measure Position

20-Jan-2017

Why I, As The CEO, Get The Same Bonus As All My Other Employees

13-Dec-2016

Mechatronics Aids In Embedded System Design

07-Dec-2016

Top 10 Tips for Designing Injection Molded Plastic Parts

22-Nov-2016

British school kids and car hackers: the widespread appeal of open source

14-Nov-2016

When should you consider designing custom gears?

07-Nov-2016

Conference Report: Open Source Hardware Summit

31-Oct-2016

What is a Motion Control System?

20-Oct-2016

The Top 10 Questions to ask a Product Development Firm

05-Oct-2016

The Potential of the Apple AirPods To Disrupt A Whole Industry

12-Sep-2016

How to Use Open Source Hardware in Product Development

01-Sep-2016

What is the mech in mechatronics?

16-Aug-2016

3 Tips for IoT Product Success

02-Aug-2016

When Should I Start Designing For High-Volume Manufacturing?

19-Jul-2016

Designing a 3D Printer for the Home

29-Jun-2016

It Turns Out That EMC Is Not Black Magic

22-Jun-2016

Selecting the correct motor type and size

06-Jun-2016

When brainstorming fails, throw an imaginary cat

18-May-2016

Five Tips for Mechatronic System Integration

09-May-2016

Three Tips for Designing High Volume Mechatronic Products

28-Apr-2016

What Is Mechatronics?

18-Apr-2016

If I could only do 3 things to simplify a design, what should they be?

06-Apr-2016