In my last post, I discussed writing product requirements from a software perspective. In this post, I will focus on writing product requirements for hardware.
Like software, a product requirements document for hardware is essential for product development optimization. The outcome of the product requirements document is a more defined technical specification document for each engineering discipline which then results in a Bill of Materials (BOM). The Bill of Materials (BOM) is a list of raw materials and assemblies which are needed for the end-to-end manufacture of the product. The PRD sets clear requirements and performance targets that influence which components the engineering team chooses as well as the cost of goods for the product.
A hardware product I use daily is my Philips Sonicare DiamondClean Electric Toothbrush. Every time I use it, I can’t help but think of ways to improve its user experience. Currently to get the full experience of this device, I need to have my phone nearby during usage. Via bluetooth, the device connects to your phone thereby tracking daily usage and giving real-time guidance during brushing. While this is great, it assumes that we all have our phones with us at all times. I don’t have my phone with me when i’m brushing my teeth in the mornings and evenings; as such, I rarely utilize the full capabilities of the Philips App. Side note: the app could use lots of improvements but that’s a topic for another day.
Anyway, If I were the PM for this product, I would include a smart mirror that one can easily stick unto an existing bathroom mirror or a wall. This way, I won’t have to carry my phone when brushing my teeth.
I’ve written an example of what that PRD might look like. PRD: Smart Mirror for Electric Rechargeable Power Toothbrush
Note: This PRD is an example and not exhaustive and I am definitely missing additional requirements.
After a draft of the PRD is written, the product manager should socialize it with various cross-functional teams as a next step. This will result in several iterations of the PRD as teams ask clarifying questions and express concerns. As such, priorities might change and requirements may be added/removed. However, the goal of the product should always be clear.
A more detailed technical specifications documents will result from the PRD. These can be separate documents or can be included under the Technical/Engineering Specifications column as I’ve included in the example.
The Product Manager finalize the Product Requirements Document (PRD) before the Design Phase of Hardware Product Development.
For additional guidance on writing hardware product requirements documents, see https://blog.bolt.io/product-requirements/
Liked the post and think someone else will? Please share 😃