How to write hardware product requirements your whole team will sign
"The product shall be quiet." Most engineers have seen a line like this in a requirements document. It sounds reasonable, everyone nods, and three months later engineering, quality and sales discover they each understood something different. A requirement that can be read three ways is not a requirement. It's a future argument.
This guide shows how to write hardware requirements that engineering can design to, quality can test and sales can explain.

Keep three levels apart
Many teams mix customer needs, product requirements and technical specifications in one long list. That makes it impossible to see why anything is there. Keep three levels separate, and link each to the one above it:
Customer need: the outcome in the customer's words. "Changing the filter should take less than five minutes, without tools."
Product requirement: what the product must do, measurable and solution-free. "The filter shall be replaceable by the user in under 5 minutes, without tools, in 9 out of 10 attempts by first-time users."
Technical specification: how engineering will meet it. "Quarter-turn bayonet housing, maximum 2 Nm opening torque."
The product manager owns levels 1 and 2. Engineering owns level 3. When engineers propose a specification, the PM checks that it meets the requirement and leaves the design choice to them.
Five tests for a good requirement
Measurable: a number and a unit, or a clear pass and fail test.
Verifiable: you know how it will be tested, and by whom.
Solution-free: it describes the result, not the design.
Traceable: it links back to a customer need, a regulation or a business goal.
Prioritised: must have, should have or nice to have.
Before and after
Weak: "The product shall be quiet."
Strong: "Sound power level shall not exceed 45 dB(A) in normal operating mode, measured according to the applicable product standard. Source: top-3 complaint in customer reviews."
Weak: "The housing shall be robust."
Strong: "The product shall show no functional damage after a 1 m drop onto concrete on each of its six faces. Source: service data shows drop damage in transport and installation."
The strong versions tell engineering exactly what success looks like, tell quality how to test it and tell sales why it matters.
Don't forget the requirements no customer asks for
Hardware has requirements that never appear in a customer interview but can stop a launch:
Safety, EMC and other certification requirements for each target market
Target unit cost and target margin
Manufacturing and serviceability constraints
Environmental and material requirements
Write these down early. Discovering a certification requirement after tooling has been ordered is one of the most expensive surprises in hardware.
Write what you will not do
The most underrated section of any requirements document is "out of scope". Listing what the product will deliberately not do, and getting it signed, protects the schedule. When a new feature request arrives mid-project, you can point to a decision instead of an opinion. The request can still be accepted, but now it's a conscious trade-off with a cost and a date attached.
Getting it signed
Sending a finished document for approval rarely works. People find problems at the last moment and it stalls. A better sequence:
Share the problem statement first and agree on it.
Review requirements one-to-one with engineering, quality, sales and operations.
Log every comment and how you handled it.
Hold one sign-off meeting where there are no surprises left.