How Do You Reduce Product Development Lead Time When Every Sample Needs Another Round?
The question usually arrives in a Monday trading meeting or a range review: why is this hoodie still in development when the same silhouette was signed off last season, and which approval is actually holding the launch? To reduce product development lead time you rarely need a faster factory. You need fewer physical sample rounds, approvals that run side by side instead of in a queue, and feedback that reaches the factory once, complete and on time.
This guide is written for buyers, product developers and sourcing leads at established UK and European retailers and brands. It defines the measures, shows how to map the critical path from tech pack to sealed sample, and works through an illustrative comparison. Every number in the worked example is a hypothetical input chosen to show the arithmetic. None of it is a benchmark, a quote or a promise about any supplier.
Development lead time is also the cheapest lead time to recover. Production time is fixed by fabric, capacity and shipping, whereas development time is largely made of waiting, and waiting is a process problem. If you also need the production side, read our clothing production lead times guide next to this one.
What Counts as Development Lead Time? Three Measures to Define First
Before you try to reduce product development lead time, agree what you are measuring, because definitions vary between companies. Some teams start the clock at design sign-off, others at tech pack release; some stop at sealed sample, others at bulk fabric booking. Pick one definition, write it down, and apply it to every style so that season-on-season comparison means something.
The three development measures and how to calculate them
| Measure | Definition and formula | How to read it | Where definitions vary |
|---|---|---|---|
| Development days | Calendar days from tech pack release to sealed (approved) sample. Formula: sealed sample date minus tech pack release date. | A long number says the process is slow, but not why. Split it into build, courier and review days to find the waiting. | Some teams start at design brief; some stop at pre-production sample. State both dates. |
| Sample rounds | Number of physical samples submitted per style before it is sealed. Formula: count of submissions, tracked per style. | Each round adds build, courier and review time. Fewer rounds is usually the biggest single lever. | Decide whether a prototype or colour strike-off counts as a round. Be consistent. |
| First-time-right (FTR) % | Share of samples approved without rework at a given stage. Formula: samples approved on first submission divided by samples submitted at that stage, times 100. | Low FTR points to unclear specifications or late comments. Track by stage, supplier and category. | Some teams count approval with minor comments as right first time. Write the rule down. |
Definitions are working definitions for this guide. Confirm the definition your own organisation uses before comparing results across suppliers or seasons.
Two cautions apply. First, a number without its date range and its stopping rule cannot be compared. Second, averages hide the problem styles, so review the distribution as well as the mean.
Map the Critical Path From Tech Pack to Sealed Sample
The critical path is the longest chain of dependent steps between tech pack release and sealed sample. Anything on that chain delays the launch day for day; anything off it has slack. Mapping the path is the starting point if you want to reduce product development lead time on purpose. Mapping the path for one representative style per category usually reveals that a few long-lead items, rather than sewing time, set the date.
Five steps to map the critical path
- 1List every approvalFit, fabric, colour, trim, wash and decoration approvals, each with a named approver.
- 2Find the dependenciesMark which approvals need another to finish first, such as a colour before a decoration strike-off.
- 3Estimate each durationUse build, courier and review days from your own past samples, not guesses.
- 4Mark the longest chainAdd durations along each chain. The longest total is the critical path.
- 5Set dates backwardsWork back from the sealed-sample date and give each step a decision deadline.
The table below shows the items that most often sit on a garment critical path, whether they can run in parallel, and what evidence closes them. It is a template: durations and dependencies change with fabric, dye method, decoration and factory, so re-time it for each programme.
Critical path items from tech pack to sealed sample
| Item | Depends on | Can run in parallel? | Evidence that closes it |
|---|---|---|---|
| Tech pack complete and checked | Design sign-off, measurement chart, bill of materials | No, it starts the clock | Factory pre-sample review call with questions logged |
| Fabric swatch or sample-yardage approval | Fabric specification in the tech pack | Yes, alongside the first sample build | Signed swatch with composition, weight and finish noted |
| Colour approval (lab dip or strike-off) | Colour reference and dye method agreed | Yes, alongside fabric and fit work | Approved lab dip under the agreed light source |
| Trim and label approval | Trim list, artwork, placement | Yes | Approved trim card or physical trim samples |
| Decoration approval (print, embroidery, wash) | Colour and fabric, because both affect decoration | Partly; the strike-off needs approved fabric | Approved strike-off or wash standard on the right fabric |
| Fit sample approval | Fabric hand and weight close to production | Core path; the other approvals feed it | Measured sample against the chart with consolidated comments |
| Sealed sample | All of the above | No, it is the end point | Signed and dated sealed sample with measured points recorded |
Illustrative template only. Dependencies and durations vary by product, process and factory; each programme should re-time its own path.
A clear tech pack is the first item on this path because everything downstream is checked against it. For a full week-by-week view of a hoodie from fabric booking to shipment, see our hoodie critical path guide.
Separate Fit, Fabric and Decoration Approvals
The first structural way to reduce product development lead time is to stop bundling approvals. A common cause of repeated rounds is bundling every approval into one sample. A single garment is then asked to prove the fit, the fabric, the colour and the decoration at once, so one failed element sends the whole sample back, and fixes to one element often disturb another. Separating the approvals lets each one close on its own evidence and on its own clock.
Which approval proves what, and on which sample
| Approval | What it confirms | Best evidence | Typical owner |
|---|---|---|---|
| Fit | Measurements, proportion, drape and comfort on the body | Measured sample on a fit model or mannequin against the chart | Technical designer or garment technologist |
| Fabric | Composition, weight, hand-feel, structure and finish | Swatch or sample yardage with supplier test data where relevant | Fabric developer or buyer |
| Colour | Shade match to the reference | Lab dip or colour strike-off under the agreed light | Designer or colour specialist |
| Decoration | Print, embroidery or wash placement, size and appearance | Strike-off or wash standard on the approved fabric | Designer with technical sign-off |
| Trims and labels | Specification, placement and compliance content | Trim card and label proofs | Product developer |
A working split of responsibilities. Roles and names differ between organisations; the point is that each approval has one named owner.
Fit must be judged on a fabric close to the production fabric, because weight and stretch change how a pattern behaves. That is the one dependency that should not be relaxed. Fabric, colour, trim and decoration approvals can usually start together and finish before or during the first fit round, and a fit sample made in a proxy fabric can be accepted for pattern work only if everyone records that its hand-feel is not yet approved. For hoodies and fleece, our test-and-scale model is one way to keep approvals ahead of volume decisions.
Use Decision Deadlines and One Consolidated Feedback Owner
Most development days are not building days. They are the days a finished sample sits while four people on the buyer side form views, send them separately and sometimes disagree. The remedy is administrative: one person per style collects every comment, resolves conflicts, and sends a single numbered list with a date by which the factory will receive it.
Pair that with decision deadlines. A decision deadline is a stated date or elapsed time by which a named person must approve, reject with reasons, or escalate. Without one, silence behaves like a decision to wait.
What a consolidated feedback pack contains
- One numbered list of comments, each tied to a measured point, a photograph or a tech pack reference
- Conflicts between designer, technician and buyer already resolved by the feedback owner
- Each comment marked as must-fix, should-fix or note for the next stage
- A clear decision: approve, approve with comments, or resubmit
- The date the next sample or response is due and who owns it
A comment that cannot be measured or shown is usually a reason for another round. Rewrite it until the factory can act on it without asking.
Example decision deadlines and escalation rules (illustrative; set your own)
| Event | Suggested deadline | Owner | If missed |
|---|---|---|---|
| Sample arrives | Logged and photographed on the day of arrival | Product developer | Escalate to the product lead if not logged within one working day |
| Fit session held | Within two working days of arrival | Technical designer | Feedback owner books the next available slot and flags the date at risk |
| Consolidated feedback sent | Within one working day of the fit session | Feedback owner | Factory proceeds on the last confirmed instruction and the delay is recorded |
| Approval or resubmit decision | Same message as the feedback | Buyer | Product lead decides; the style moves to a defined fallback |
Deadlines shown are examples to adapt. Suitable timings depend on the category, location of the fit team and courier route.
Our guide to improving sample approval rate covers how to write specifications so that fewer comments are needed in the first place.
Worked Illustration: A Four-Round Process Against a Controlled Two-Round Process
The following comparison is a hypothetical single hoodie style, built to show how the arithmetic works. Every duration is an assumption, listed below, and the result is not a benchmark or a typical outcome. Your own data will differ, and the purpose is to show where the days go, not to promise a saving.
- Process A (four rounds): the prototype, two fit samples and a final pre-production sample are each submitted in turn. Approvals for fabric, colour and decoration are folded into the same samples and wait behind the fit comments.
- Process B (controlled two-round): a three-day alignment call on the tech pack, then one fit sample and one confirmation sample. Fabric, colour, trim and decoration approvals run in parallel during the first twenty days.
- Assumed build days: 10 for the first sample and 8 for later samples, in both processes. Assumed courier time: 4 days per round.
- Assumed review time: 7 days per round for Process A in the first three rounds and 3 days in the final one, because feedback arrives in pieces; 3 days in Process B round one and 2 days in round two, because there is one consolidated owner and a decision deadline.
Day-by-day arithmetic for both processes (hypothetical)
| Process | Stage | Build days | Courier days | Review days | Stage total | Cumulative day |
|---|---|---|---|---|---|---|
| A: four rounds | Round 1 prototype | 10 | 4 | 7 | 21 | 21 |
| A: four rounds | Round 2 fit sample | 8 | 4 | 7 | 19 | 40 |
| A: four rounds | Round 3 fit sample | 8 | 4 | 7 | 19 | 59 |
| A: four rounds | Round 4 pre-production sample | 8 | 4 | 3 | 15 | 74 |
| B: two rounds | Tech pack alignment call | 0 | 0 | 3 | 3 | 3 |
| B: two rounds | Round 1 fit sample | 10 | 4 | 3 | 17 | 20 |
| B: two rounds | Round 2 confirmation sample | 8 | 4 | 2 | 14 | 34 |
Hypothetical inputs for illustration only. Totals: Process A is 74 days, about 10.6 weeks; Process B is 34 days, about 4.9 weeks; difference 40 days.
Process A takes 74 days and Process B takes 34, a gap of 40 days. The chart below splits each total into building, courier, alignment and review days, so you can see that the gap comes from two fewer build-and-courier cycles and from shorter review windows rather than from anyone sewing faster.
Where the days go in each process (hypothetical, days)
Calendar days from tech pack release to sealed sample
Illustrative arithmetic from the table above, not market data. A: 34 plus 16 plus 24 equals 74. B: 3 plus 18 plus 8 plus 5 equals 34.
The two timelines that follow show the same story in sequence. They are illustrative templates; each programme should re-time them against its own fabric, colour and decoration lead times.
Process A: four rounds (illustrative)
- Day 0 to 21Tech pack released. Prototype built (10 days), couriered (4), reviewed in pieces over 7 days.
- Day 21 to 40Fit sample 2 built, couriered and reviewed. Comments from the first round are partly repeated because they were not consolidated.
- Day 40 to 59Fit sample 3. A hand-feel comment and a decoration placement comment surface for the first time.
- Day 59 to 74Pre-production sample built, couriered and signed on day 74.
Hypothetical durations. The review windows are the compressible part.
Process B: controlled two rounds (illustrative)
- Day 0 to 3Tech pack alignment call with the factory. Questions logged, measurement points confirmed, approval owners named.
- Day 3 to 20Fit sample built (10 days), couriered (4), reviewed within the 3-day decision deadline. Fabric, colour, trim and decoration approvals run in parallel and must close by day 20.
- Day 20 to 34Confirmation sample built (8), couriered (4), signed within 2 days. Sealed sample recorded on day 34.
Hypothetical durations. Process B only works if the parallel approvals really close on time and fabric for sampling is available; if either slips, a third round is likely.
The caution matters. Process B has no slack: it assumes the tech pack is complete, the fabric is available for sampling and the decisions arrive on time. Treat it as a target to design towards, not a forecast.
Why Samples Need Extra Rounds: Where to Look First
Before you try to reduce product development lead time, find out why your own samples fail. The table below ranks common causes by their indicative effect on the number of rounds. The ratings are a planning aid for discussion, not measured data, and your own sample log will give a better answer than any generic list.
Common causes of extra rounds
1 dot = low, 5 dots = high
| Likely to add a round | Easy to prevent upstream | |
|---|---|---|
| Unmeasurable comments ("make it feel better") | ●●●●● | ●●●●● |
| Feedback sent in several separate messages | ●●●●● | ●●●●● |
| Fabric not close to production hand-feel | ●●●●● | ●●●●● |
| Missing or ambiguous tech pack detail | ●●●●● | ●●●●● |
| Late change to colour or decoration after fit | ●●●●● | ●●●●● |
| Grade or size-range issues found late | ●●●●● | ●●●●● |
Indicative 1 to 5 ratings for discussion, based on common development practice. Replace with your own sample-log data when you have it.
A useful habit when you reduce product development lead time is to code every comment in the sample log by type: specification gap, factory execution, late change by the buyer, or conflicting feedback. After one season you will see which cause owns the most rounds, and the corrective action is different for each. Specification gaps point to the tech pack, execution points to supplier selection and pre-production alignment, and late changes point to your own decision gates.
Track First-Time-Right Sample Performance
First-time-right is the percentage of samples approved without rework, and it is the early warning for lead time. A style approved at the first submission saves a full round: build, courier and review days together. Track it by stage (prototype, fit, pre-production), by supplier and by category, and do not mix stages into one number.
The calculation is simple. Divide samples approved on first submission by samples submitted at that stage, and multiply by 100. State your rule for what counts as approved: with no comments, or with only minor comments that do not need a new sample. The table below applies the three measures to ten hypothetical styles, again for illustration.
Ten hypothetical styles under each process (illustrative sample log)
| Measure | Process A (four-round habit) | Process B (controlled) | How it is calculated |
|---|---|---|---|
| Rounds per style (styles 1 to 10) | 4, 3, 4, 2, 4, 3, 4, 3, 1, 4 | 1, 2, 2, 1, 2, 2, 3, 2, 1, 2 | Count of submissions until sealed |
| Total rounds | 32 | 18 | Sum of the ten values |
| Average sample rounds per style | 3.2 | 1.8 | Total rounds divided by 10 styles |
| First-time-right (sealed in round 1) | 1 of 10, or 10% | 3 of 10, or 30% | Styles with one round divided by styles, times 100 |
| Sealed within two rounds | 2 of 10, or 20% | 9 of 10, or 90% | Styles with two rounds or fewer divided by styles, times 100 |
Hypothetical data for illustration. They are not typical industry results or a forecast for any supplier or category.
Notice that the first-time-right figure alone looks modest in Process B at 30 per cent, but the share sealed within two rounds is much higher. A controlled process does not need every sample to be perfect first time; it needs a predictable maximum. Report both figures, and use the sample-round count to decide when to escalate to a supplier review.
Pick the measure that matches your current problem. If rounds are high, track first-time-right by stage. If rounds are fine but the days are long, track review days and courier days separately. Reviewing all three every week usually produces more charts and fewer decisions.
Decision: How to Reduce Product Development Lead Time Next Season
If you can only change one thing this season to reduce product development lead time, introduce the single feedback owner and the decision deadline, because it needs no new supplier and no new tooling. Start with the next five styles that enter development, log every sample in a shared sheet, and compare review days before and after.
Then move to parallel approvals. Release fabric, colour, trim and decoration approvals together at tech pack release, give each a named owner, and require that they close before the confirmation sample. Keep fit sequential, and keep the production-like fabric rule.
Decision guide: signal, likely cause and action
| Signal in your sample log | Likely cause | Action | Measure to watch |
|---|---|---|---|
| Many rounds, short review days | Specification gaps or factory execution | Tighten the tech pack and hold a pre-sample alignment call | Sample rounds, first-time-right by stage |
| Few rounds, long total days | Slow review or courier | Add decision deadlines; check courier routes and consolidate dispatches | Review days, courier days |
| Good fit approvals, late decoration | Decoration approved after fit rather than in parallel | Start strike-offs at tech pack release | Development days to sealed sample |
| One supplier is much slower than others | Capability or communication gap | Review with the supplier; consider a smaller test before more volume | First-time-right by supplier |
Illustrative decision rules. Confirm against your own sample log before changing suppliers or processes.
Evidence that should change your mind includes a style type, such as a complex wash or a new fabric, where extra rounds are justified because the risk is real, and a supplier whose first-time-right rate falls after you tighten the tech pack. For delivery risk after approval, our guide on how to prevent production delays picks up where this one stops.
So, for the next style in your range, which single approval is currently waiting on a person rather than on a process, and what date would you give them?
How Ruhrose Approaches Development Lead Time
Ruhrose develops hoodies, jersey, denim and woven casualwear for UK buyers, with development and production in Bangladesh. We sample before bulk, and we prefer to review a tech pack with you before the first sample is cut, so that missing measurements and unclear finish instructions are caught on a call rather than in round three. We do not quote development times in advance, because they depend on fabric, wash, decoration and how quickly feedback arrives. If it helps, our garment sampling process guide explains how we handle rounds, and you are welcome to send a tech pack for a plain second opinion.