A Product Design Specification (PDS) is the brief for the whole development process. It defines what a product must do, who it's for, and the constraints the design has to work within, before any CAD model or prototype exists. This guide covers what a PDS includes, how to write one, why it often matters more than the idea itself, and how much to leave open for the designer.
A Product Design Specification, or PDS, is one of the most important documents in early-stage product development. It defines what a product must do, who it is for, and the constraints the design has to work within. Unlike a manufacturing specification or technical pack, which come later to tell a factory how to build the product, the design specification guides the design team before any CAD model or prototypes exist.
It is, in effect, the brief for the whole development process. It keeps designers, engineers and stakeholders aligned from the start, sets clear goals, reduces the risk of costly changes later, and sets the direction for a commercially viable product. This guide explains what a design specification includes, how to write one, and why it matters more than most people expect.
What a product design specification is
A product design specification is a structured document that sets out exactly what a new product must do, how it should perform, and the constraints that shape its development. It works as a design brief, guiding decisions through the early concept and engineering phases.
The distinction from a manufacturing specification matters. A manufacturing specification is created later, to communicate with factories, and it locks down materials, tolerances and processes. A design specification comes first, before any of this information is available. It sets out the foundations of the project, including the target users, performance goals, safety considerations, environmental constraints and cost targets, while leaving the design team free to explore how best to meet them. It defines the problem and the objectives, without prescribing the solution.
Why a product design specification matters more than the idea itself
There are two ways to understand the value of a design specification, and the first is not obvious.
A well-made design specification lets us genuinely understand a project: its trajectory, its requirements, its opportunities, and whether the parties involved are ready to move forward knowing what they are moving into. In most start-ups and innovation ventures, the strategy and outline captured in the design specification is a better indication of the route to success than the idea itself. A strong idea with a vague, unconsidered specification is a warning sign. A clear, well-reasoned design specification shows we are working with a project that has genuine substance behind it. If questions can be answered about target markets, and core function and indicative price points have been defined, it gives a strong foundation to the project and ensures alignment between the designer and the client.
The second way is more practical. A well-defined design specification results in a much smoother development process, with fewer surprises and fewer unplanned costs. It makes the whole process more efficient, and it keeps deviation from the plan to a minimum. Where a design specification is weak, the opposite happens. Every stage has to be approached with caution, milestones and decisions laid down step by step, with the project scope effectively defined on the way. That means course corrections, sometimes redoing concept development, a slower approach, and the need to change direction along the way. A good PDS is the difference between a project that runs to plan and one that has to be fragmented and approached cautiously.
A word on "AI developed" design specifications
There is a growing problem worth highlighting, and that is AI developed design specifications. Increasingly, the critical details in these documents are generated with AI support rather than genuine input from the person behind the product. The result is often vague or unfeasible, and it has the potential to cause real damage: detours, delays and blurry definitions. Current AI models cannot fully grasp the intent behind a new idea, and they tend to define outputs by reference to similar existing products, which by its very nature is problematic when you are developing an innovative new product. A design specification needs genuine reasoning, often between the client and the designer. It is the one document where borrowed thinking shows. It also makes the client's real level of knowledge unclear, making them look as though they understand more than they do about materials, prototyping and production. AI can't replace a candid, detailed conversation about the project between all parties. If AI tools are used, it's important to interrogate the output thoroughly together, and refine and clarify it.
A worked example: the Equerry shoe care device
Equerry is a handheld electric shoe polisher that shines shoes quickly and cleanly, using a built-in polish dispenser and motorised brush. Before any CAD design or prototyping began, we created a design specification to define exactly what the product needed to do and the boundaries for its development.
The design specification covered the function, that it must polish evenly and quickly with no mess; the target user, time-poor professionals who value well-kept shoes; the key performance requirement, enough motor torque to turn the brush effectively without damaging the shoe; the form factor, small enough to hold comfortably in one hand; the cost constraint, a premium gift positioned under £100 retail; battery life, at least ten full polishing cycles per charge; and the aesthetic direction, a sleek satin finish suitable for gifting.
Only later, once the design was finalised, did we develop the manufacturing specification. That document detailed the brush bristle material, motor torque values, gearbox ratio, component materials, surface textures and packaging. The design specification guided the design team to develop the right concept; the manufacturing spec helped the factory build it correctly. Jump straight to the technical detail too early, and you risk boxing in the design and inflating costs for no reason, or worse, developing a product that doesn't meet the needs of the target market and won't sell.
Why you should leave room for the designer
This is the point most often missed by anyone unfamiliar with how a design agency works. If you over-define a design specification, writing down every dimension and every technical detail you think you want, you are no longer looking for a designer. You are looking for a draftsman to execute a design you have already fixed.
If instead you want design solutions, options for how to make your product succeed in the market, you have to leave the designer room to think, evaluate and reason. This does not mean there are no constraints. Every project has constraints, and they all need to be fully defined. But that definition should happen through the design process, not be locked down before it begins. If the constraints and details are fixed from the start, you limit the design possibilities and lose the very input you engaged a designer for. Insist on carrying fixed specifications forward without good reason, and if something goes wrong, you may find yourself back at the drawing board.
Keeping a product design specification commercially grounded
A design specification should be commercially grounded and as realistic as the market data allows, because understanding the current value in the market is one of the most important things in product development. Your product may well be better, more efficient or more economical than what is already out there, but the market price still controls every output of the design.
Retail price is the key indicator. From the requested retail price, and your planned operational costs as a whole, we estimate the cost of goods manufactured, and that tells us how the product needs to be designed: how many parts, what materials, what level of detail. It affects everything. If the numbers show you are working to a tight and critical threshold, the design team will look to simplify the design, keeping the cost of manufacture as low as possible. If the product is creating a new level and needs premium, well-considered detail to justify its position, we make sure the right materials and details are there to deliver it.
How firm should a design specification be?
The best design specification is written and finalised with feedback from all parties, so that no grey areas remain. The logical way to start is with a single party setting it down as honestly and clearly as they can, then sharing it so that everyone else can bring their own expertise, challenge the terms, and define it further.
Having said that, through the design process reality will always force some change. Nothing can be fixed permanently in a world where technology moves as quickly as it does, and as designs evolve and prototypes are developed, there are inevitably some changes to the specification. The discipline is to keep the core idea and the approach steady, while accepting that the details will evolve over time.
Safety and compliance: easy to neglect, costly to miss
Safety and compliance are the two things most often neglected in the excitement of testing something new. The costs of meeting them are usually straightforward to calculate. The harder part is identifying the right regulations to follow in the first place. A design specification should flag the potential safety and compliance requirements early, with a proper review carried out after concept development or the initial prototypes, so that every detail is considered before it becomes expensive to address. Finding a designer who has experience developing products that need to meet regulatory requirements is vital, so that you can be sure the design is considering them from the outset.
What to include in a product design specification
A strong design specification captures the essential requirements without over-defining the solution. The key sections are the product's purpose and use, the target market and user, the core functions in priority order, the performance requirements, the constraints and limitations, safety and compliance, aesthetic considerations, environmental factors, and any known plans for future versions. It is also worth including a few "nice to have" elements. They might not be viable, or may be better suited to later generations of the product, but they can drive innovation and creativity throughout the process.
When to write it
A product design specification should be created early, after the initial idea is formed but before concept generation or CAD work begins. In practice, that means after market research has confirmed there is demand, before engaging a design team or starting CAD, and often as a key output of an early discovery or feasibility stage. Write it too late and you are reacting to design constraints instead of shaping them. Write it too early, without enough insight, and you risk developing a product on flawed assumptions.
How D2M helps
The design specification is usually made after our first conversation with a client, unless they arrive with one already written, in which case we go through it in detail and refine it together. Sometimes an idea arrives with strong reasoning already behind it, and we can quickly see the use, the opportunity and the scope, which lets us reflect it accurately in a proposal. More often, clients have defined parts of the specification themselves and need support both to complete it and to realise the full value of the idea behind it.
For that, we have established two custom stages. Our Discovery stage lets us look at a project from a fresh perspective and evaluate every step before committing to concept development. Our Product Viability Assessment evaluates the product across several metrics, including market feasibility, idea feasibility and commercial viability.
The first thing we ask when developing a design specification is always the use case. What is the product for? Who will use it, and where? Everything begins with understanding the context and the intended use, because that is what lets us offer design solutions to realise the product.
What we bring beyond that is the design, manufacturing and commercial knowledge a founder may not have: years of experience across a wide range of product sectors, a clear view of the market metrics, and a sense of how a product will be positioned once it launches. These are the inputs that turn a specification from a wish list into a working foundation for a successful product.
In summary
A clear, well-written design specification is one of the most valuable tools in early-stage product development. It defines what your product must do, sets realistic constraints, and aligns everyone involved. It reduces costly mistakes, shortens development, and lays the groundwork for prototyping, manufacture and certification. Most of all, a good one shows that the thinking behind a product is as sound as the idea itself.
Related guides: Designing a Product: A Step by Step Guide · The Importance of a Clear Project Brief · Manufacturing Specification
FAQ
What's the difference between a design specification and a manufacturing specification? The design specification comes first and defines the problem and objectives, what the product must do, for whom, within what constraints, while leaving the solution open. The manufacturing specification comes later and tells the factory how to build it, locking down materials, tolerances and processes.
When should I write a product design specification? Early, after the idea is formed and market research has confirmed demand, but before concept generation or CAD begins. Often it's the key output of a discovery or feasibility stage.
Should I specify every detail? No. Over-defining turns a designer into a draftsman executing a design you've already fixed. Define the constraints fully, but leave room for the designer to reason and offer solutions.
Can I use AI to write my PDS? AI can assist, but it can't replace the genuine reasoning between client and designer. AI-generated specs tend to be vague or defined by reference to existing products, which is a problem for an innovative product. If used, interrogate and refine the output together.
