Avoid Feature Creep: Write a Spec

Give me a pencil and paper, and let me sketch out this great idea. Scratch that — give me a laptop with a decent CAD tool — I’m ready to dive in. Here’s a PCB outline. It’ll need a power input connector, and a few USB ports too. An LED would be nice. Maybe an SSD for some onboard storage. Better add two mounting holes for a heatsink while we’re at it. And an Ethernet PHY, because — IoT! Shoot, we should have placed a cutout at the right edge to allow for cabling inside the enclosure. We can make room by removing half of the USB ports…

When designing hardware (and software), it’s tempting to dive into a project without sufficient planning. The designer in all of us likes the gratification that comes with engineering our next big idea. The closer we get to finishing the design, the closer it is to being in our hands, and the closer we are to applying power to it, debugging it, and sharing it with the world. Simple, right?

Wrong.

The problem with this method, is that without a plan, our ideas — and the entire scope of the project — will evolve while we are designing.

How much time is lost on an individual project when the scope changes? Did removing an extra USB port at the last minute result in a larger-than-necessary USB hub on the board, with more parts, more weight, higher cost and power consumption, and more points of failure? Were parts purchased that will now sit on the shelf because they will no longer be used on the design?

Parts aside — Was the reduction of a power supply overlooked with the last minute part removal, resulting in worse efficiency? Did a last minute change result in a careless connection error and another PCB spin? Is your customer disappointed to hear that the product won’t be available for two more months?

Take a deep breath.

Feature creep on a project is something we have all experienced. But it is something we can avoid by spending more time thinking through the form, fit, and function of our products before we design them. This is best accomplished with a design specification, a formal document that describes the “what”, “how”, and “where” of the design. What is the functionality of the product? How will the circuits be designed to achieve the desired functionality? And where will key components reside that are connecting to other pieces in the larger puzzle?

In essence, the specification is the map a team agrees to follow when the engineers begin their work. That’s why at the Engineering Design Group, specifications are the cornerstone for each of our projects. If you have a great idea, let’s work together to translate it into a specification. Because, with a map in hand, our team can engineer your next idea idea, and you can share your product with the world.

What are you waiting for?

Previous
Previous

Surface-Mount Component Packages - Which is best?

Next
Next

Design vs. Production Trade-offs through the Lens of Modularity