New product introduction on the line: getting a design into serial production without wrecking the schedule

Pilot builds belong on production equipment with production people

A prototype assembled by engineers on a bench proves the design works; it proves nothing about whether the plant can build it. Pilot builds must run on the intended equipment, with the intended tooling, following the drafted work instructions, staffed by operators who will do the job — and the engineers should watch rather than help. What surfaces is the practical detail no drawing captures: the fixture that fouls, the fastener that cannot be reached, the two components that look identical, the test that takes far longer than the cycle allows. Every problem found here costs a fraction of what it costs after launch.

A readiness check with the authority to say no

Before the first scheduled order, someone has to confirm and sign that tooling and fixtures are on site and proven, gauges exist and are calibrated, the bill of material and routing are loaded and correct, materials are available with approved suppliers, work instructions are issued at the correct revision, operators are trained and recorded as such, the test or inspection method is defined and capable, and packaging is specified and available. The list is unremarkable; what matters is that the check has teeth. A readiness review that cannot delay a launch is a formality, and the plant will discover the gaps during the first production week instead.

Plan the ramp rather than assuming the standard rate

New products do not start at the rate the costing assumed. Early output is limited by operator familiarity, by process settings still being refined, by higher scrap and by interventions that will not exist later. Schedule the ramp explicitly — reduced rate for the first period, a defined step up, and criteria for each step — and tell the commercial side what that means for early deliveries. Planning at the eventual standard rate produces the standard sequence: shortfall in the first weeks, expediting, overtime, and pressure that pushes the plant to skip exactly the process verification the launch needed.

Learning curve, training and the resource nobody costed

Operators get faster and more accurate with repetition, and the improvement is steep at first, which means early builds absorb far more labour hours than the standard suggests. That extra labour has to come from somewhere, and it usually comes from the shift that was already building existing products. Budget it. Train ahead of the first order rather than during it, record who is competent on what, and accept that a launch running on a small number of trained people is fragile — one absence and the line either stops or gets staffed by someone learning on customer product.

Cutover, run-out and the period when both products exist

Where the new item replaces an existing one, the transition needs its own plan: how much old product and old component stock to run out, when the changeover happens for each customer, what to do with residual material, and how both variants will be kept physically apart while both are in the building. Mixing them is the standard error — a shared bin, a common label, a pallet of the wrong revision shipped in the final week. Set an effectivity point, mark the stock unambiguously, and decide in advance who authorises the switch, because the pressure to slide it will start almost immediately.

Frequently asked questions

How early should production get involved in a new product?

Early enough to change the design, which in practice means while the concept is still fluid rather than after drawings are released. Manufacturing input at that point is cheap and influential: a tolerance relaxed, a feature reoriented, a fastener standardised, an assembly sequence simplified. Once tooling is committed, production's role shrinks to absorbing whatever was decided. The cost of the same change rises steeply at each stage, which is the single strongest argument for putting a manufacturing engineer in the design review from the start.

Who should own a launch, engineering or production?

Production should own the readiness decision and engineering should own the design and process definition, with one named person accountable for the whole introduction end to end. Splitting accountability produces the familiar handover argument where engineering considers the job done at drawing release and production considers it undone until the line runs at rate. Naming a single owner who answers for both sides, with authority to hold the launch, resolves most of the disputes before they become schedule problems.

What is the most common reason a launch slips on the shop floor?

Tooling and fixtures arriving late or arriving and not working, followed closely by material with long lead times ordered after the design settled. Both are lead-time problems disguised as engineering problems, and both are visible months ahead if somebody maintains a launch plan that tracks physical items rather than design milestones. The second most common is discovering during the first production run that the inspection method cannot actually measure the characteristic the drawing demands.