A System Diagram is worth 1,000 words - or maybe 10,000

This one’s for the products that are systems - sensors, actuators, controllers, pumps, etc.

How easy is it for you to describe your system’s operation to someone new? 

If it’s easy, I bet you’ve got a good system diagram to use as a reference. 

If you don’t have one… how many words do you think you would save if you did?

This level of the design record is often overlooked by the inventors, since the design is already in their head. But even if you never have to show it to someone new, you’d be surprised how valuable it can be to have all your high-level functionality laid out in front of you at once. 

It might only take an hour or two to create, but I bet it will pay dividends for years to come.

-Brian Schoolcraft

The importance of data logging

For some simple product categories, logging performance data can be informative. 

For complex systems, it’s essential.

When does it matter?

-If you have more than one controller communicating on a common bus

-If you don’t deeply understand the real world use case and loading

-If your product relies on sensor data to perform correctly

-If your product has a warranty that’s based on how much (and how hard) it’s used

-If you’re working on the next generation product, and want to optimize

-If you’re still working through early stage reliability issues

If you build your product with logging in mind from day one, you’ll know when the problems happen. And you’ll have the information to fix them.

Record it. Organize it. Analyze it. Improve it.

-Brian Schoolcraft

Prototyping with production in mind

Every step in the product development process requires decisions, and every decision is a choice between some version of:

-Do it fast

or 

-Do it right

Recognizing that you’re making that decision is the first step. Making it correctly is the next.

If I’m too careful, I don’t learn anything, and run out of time or money before I make it to market.

If I run too fast, I might get to market in record time, only to realize I’m selling unvalidated prototypes with sky high service and warranty costs.

The key is to move quickly, with an eye to the future. Attack the highest risks in your design with a rigorous, detailed approach (do it right). Leave the small risks for later, or ignore them completely (do it fast). 

Next time you’re faced with a decision, think about the immediate impact, but think of the future too. You’ll be in production before you know it!

-Brian Schoolcraft