Introduction to Product Requirements Documentation for New Hardware Products
This post was originally published on Predictable Designs, the original article can be found here
What does a practical, hands-on product developer or maker dislike the most? In my experience, I would say spending time writing documentation instead of designing interesting stuff.
Usually, when a product developer has a clear understanding about the function of the device, he/she jumps straight into the design.
This is great, as there’s nothing better than having an early proof of concept prototype to show stakeholders you can make it.
However, after the proof of concept stage issues can arise if the engineer starts picking components and designing the schematics without first having formalized the functions, behavior, operating parameters and the expected performance of the device.
Always focus on the big picture before you dig down into all of the little details.