Product development / INSIGHTS
How long does product development take?
A straightforward non-electronic product might reach a first production run in 4–8 months. A novel mechanism or connected product can take 9–18 months or longer. These are planning windows, not promises. The schedule depends on what must be proved, how often it changes and when suppliers can actually work on it.
Name the milestone you are planning for
A prototype for fundraising, samples for buyer meetings and stock ready to ship are three different deadlines. Define the required material, functionality, finish and documentation for each. A presentation model can arrive months before a repeatable production process.
Work backwards from the real event, including the time needed for distribution or installation. If the deadline is fixed, decide which features and variants can move to a later release before development begins.
Map the work and the approval gates
For a simple physical product, the following ranges can help frame an initial discussion. They are illustrative stage durations, with potential overlap; they should not be summed into a guaranteed delivery date.
| Stage | Working allowance | Exit condition |
|---|---|---|
| Definition and feasibility | 2–4 weeks | Requirements and major risks agreed |
| Concept and design development | 3–6 weeks | One direction selected |
| Engineering and prototype rounds | 6–12 weeks | Key fit and function risks resolved |
| Tooling and production trials | 6–12 weeks | Production-intent parts approved |
| First batch and inspection | 4–8 weeks | Accepted stock ready for dispatch |
Find the critical dependency
A delayed finish sample may not stop mechanical engineering. An unresolved hinge interface can stop both technical drawings and tooling. List which decisions genuinely block other work, then protect those decisions from late changes.
For example, reserve a toolmaking slot provisionally while engineering progresses, but release cutting only after the part revision and critical interfaces are approved. Parallel work saves time only when the team understands the cost of reversing it.
Budget time for iteration and decisions
If a sample takes two weeks to arrive, one week to review and three weeks to revise, a second round adds about six weeks. A schedule that assumes every first sample will pass has no allowance for learning.
Set review dates, name the approver and consolidate feedback into one document. Waiting for three separate stakeholder opinions can consume as much calendar time as producing the sample. Include specialist testing, long-lead components, factory closures and shipping in the plan rather than hiding them inside “production”.
Use a schedule with evidence, owners and buffers
A useful timeline shows the deliverable, decision owner, supplier dependency and recovery option for each milestone. Track confidence separately from dates: “tool trial booked” is stronger evidence than “tool trial expected”.
- Establish a baseline after the initial feasibility review.
- Reserve a specific iteration allowance around unproven features.
- Check stock and lead times before freezing materials and components.
- Review the plan after each sample round and scope change.
- Keep a simpler first-release option if the launch date cannot move.
DESIGN IN PRACTICE
Explore our industrial design services, or see the eyewear, accessories and physical products in the MILOSSI portfolio.