Physical product development often becomes expensive long before manufacturing starts. The problem is not always poor engineering or poor execution. In many cases, the programme begins without a sufficiently clear definition of what is actually being developed, who it is for, what it needs to achieve and what commercial constraints it must satisfy.
Product definition addresses those questions before significant development resources are committed.
What is product definition?
Product definition is the process of turning an opportunity, requirement or early idea into a clear development brief. It sits between the initial business opportunity and detailed product development.
At this stage, the objective is not to resolve every component or immediately begin detailed CAD. The objective is to establish enough clarity around the product for the development team to make informed decisions about what should be developed and how the programme should proceed.
A strong product definition considers the intended customer, the use case, the problem being addressed, required features and performance, product positioning, target pricing, manufacturing constraints, technical risks and the broader scope of the development programme.
Together, these considerations create the foundation for concept development, engineering and manufacturing.
Why starting with CAD can create problems
There is often pressure to move quickly into visible development. A concept model, prototype or render feels like progress, but beginning detailed design before the underlying requirements are agreed can create significant rework later.
A team may spend weeks developing a product before discovering that its manufacturing cost exceeds the viable target, an important customer requirement has been missed, the selected architecture creates unnecessary production complexity or the product cannot accommodate a critical system or component.
Commercial issues can emerge as well. The proposed feature set may not support the intended selling price, or the product may not be sufficiently differentiated from existing alternatives.
When those discoveries are made late in the programme, changes become more expensive because they affect work that has already been completed.
Product definition aims to resolve the highest-level decisions while the cost of changing direction is still relatively low.
Start with the customer and the use case
A strong development brief should explain who the product is intended for and how it will actually be used.
This sounds straightforward, but the development priorities can change considerably depending on the customer and application.
A product intended for a professional operator may prioritise durability, serviceability and operating cost. A premium consumer product may place greater emphasis on materials, user experience, aesthetics and brand perception. An industrial product may need to prioritise installation time, reliability and integration with existing equipment.
Understanding the intended use case helps the development team distinguish between features that genuinely contribute to the product proposition and features that simply add cost or complexity.
Define the commercial boundaries
Physical products have to work commercially as well as technically, which means commercial constraints should influence the programme from the beginning.
The development team should have an understanding of what the product can realistically sell for, what manufacturing cost that selling price allows, the expected production volume, likely tooling investment, supplier requirements and the margin the business needs to achieve.
These figures do not need to be perfectly accurate at the beginning of the programme. Their purpose is to establish realistic boundaries within which the product can be developed.
A technically impressive product that cannot be manufactured or sold at the required economics is unlikely to become a successful commercial product.
Turn expectations into requirements
One of the most useful outcomes of product definition is a preliminary product specification.
Broad statements such as “lightweight”, “premium”, “easy to manufacture” or “high performance” are difficult for a development team to design against. Product definition begins translating these expectations into measurable requirements.
That may mean defining a target weight, operating range, maximum dimensions, target manufacturing cost, environmental requirements, service intervals, expected production volume or required interfaces.
Not every requirement will be known at the beginning. The important point is to identify the requirements that materially influence the product and give the development team a basis against which concepts can be evaluated.
Separate requirements from preferences
Not every desirable feature should become a mandatory requirement.
Some characteristics are fundamental to the success of the product, while others are desirable but can be reconsidered if they introduce excessive cost, weight, complexity or programme risk.
Establishing these priorities early becomes increasingly valuable as development progresses.
When difficult decisions eventually arise, the team can assess them against an agreed set of priorities rather than relying on individual preferences or making decisions in isolation.
This also helps protect the product from unnecessary scope growth as more stakeholders become involved.
Consider manufacturing early
Manufacturing should influence product definition long before production drawings are created.
Expected production volume, available manufacturing processes, supplier capability, tooling budgets and assembly requirements can all affect the most appropriate product architecture.
A low-volume specialist product may justify one manufacturing approach, while a product intended for hundreds or thousands of units may require a completely different strategy.
Considering these constraints early helps prevent a common development problem: designing the product first and attempting to determine how it will be manufactured afterwards.
Manufacturing should be part of the product development conversation from the beginning, not something introduced once the design is considered complete.
Product definition creates a decision point
A successful definition phase should ultimately lead to a development decision.
The business should have enough information to decide whether to progress into concept development, modify the proposition, undertake further market or technical validation, change the scope, pause the programme or stop development entirely.
Stopping or redirecting a weak opportunity at this stage can be a successful outcome.
The cost of discovering that a product should not proceed during Product Definition is significantly lower than discovering the same thing after detailed engineering, tooling or manufacturing investment has already begun.
The purpose of product definition is therefore not to justify proceeding with every idea. It is to improve the quality of the decision.
Creating a stronger foundation for development
Product development rarely follows a perfectly straight line. Requirements change, technical problems appear and new information becomes available as the programme progresses.
A clear product definition does not eliminate those challenges, but it provides the development team with a reference point when they occur.
When a new feature is proposed, it can be assessed against the original product objectives. When manufacturing cost increases, decisions can be made against the commercial case. When engineering compromises become necessary, the team can understand which requirements matter most.
That discipline becomes increasingly valuable as more people, suppliers and capital become involved in the programme.
Ultimately, Product Definition is about answering one fundamental question before significant development begins:
Are we clear about what we are building, why we are building it and what it needs to achieve?
Getting that answer right creates a much stronger foundation for everything that follows.
Developing a new physical product?
Frankie Sterling Studio helps businesses turn early opportunities into clearly defined product development programmes, establishing the commercial and technical foundations before major investment begins.