Projects

How a late design cascades through a component supplier

Mohit Saini · 12 Jul 2026 · 4 min read

How a late design cascades through a component supplier

A generation ago, a car buyer in India had a choice of two or three models. Today there are well over a hundred, and two-wheelers and commercial vehicles have seen the same explosion. Each new model and feature prompts competitors to respond, so the pace of launches keeps rising, along with pressure to shorten development time.

But one part of the chain hasn’t become faster: suppliers of tooling and components. Their lead times and reliability, as vehicle makers experience them, have changed little. So vehicle makers try to win back time elsewhere, and the way they do it cascades down to their component suppliers.

Unplanned concurrency at the vehicle maker

To give tooling vendors enough time, vehicle makers push their teams to hand over designs as early as possible. Work starts before the previous stage gate is cleared:

  • tooling design for a component begins (sometimes castings are even ordered) before the full assembly has been integrated and checked;
  • assembly-line automation is designed before component designs are final.

This creates two kinds of rework:

  • Vertical rework: when a component design changes, the tools and machines designed for it must change too. Tooling vendors also ask for design changes to make parts manufacturable.
  • Horizontal rework: when one component changes, the components it fits against have to change, along with their vendors’ work.

There is another subtle problem. When a team hands over incomplete work to let the next team start, the pressure to complete the rest vanishes. The team moves on to other urgent work and forgets the remainder, until it becomes a crisis. Interference problems are found late; sometimes tools are rejected and development starts again.

Vehicle makers often contain this with dedicated cross-functional teams for each project. Component suppliers can’t afford that.

What the supplier experiences

A component supplier shares its designers, testers and vendor-development engineers across projects for several vehicle makers, each pushing its own priorities.

From the supplier’s side, a typical project unfolds like this:

  1. It submits a design proposal. Feedback might come the next day, or months later, depending on how the vehicle maker’s integration of dozens of components and cost targets is going.
  2. A request for prototypes might come immediately, or after a long gap.
  3. The prototype might need rework, again at an unpredictable time.
  4. The order for a pilot lot might follow quickly, or after months.

So the supplier keeps many projects open, each going dormant and then suddenly becoming urgent. When a dormant project wakes up, the vehicle maker usually still holds the original production start date, so urgency multiplies. The real priority rule becomes whoever shouts loudest, and designers switch tasks constantly.

Under that pressure, the supplier takes its own shortcuts: designs started without fully understanding the application; designs handed to development without checking manufacturability; incomplete designs sent to vendors. Parts arrive out of step, tests fail, work restarts on a fast track, and other projects slip. At the end, supplies start before production problems are solved. The plant loses capacity to an unstable part, and the supplier risks warranty costs.

What the supplier can’t control, and what it can

It can’t control the vehicle maker’s pace: the gaps between phases and the rework the vehicle maker’s own process generates. To stay in contention, the supplier must follow that pace.

It can control two things:

  1. how fast it completes each piece of work once it is active, and
  2. how much rework it generates itself.

Breaking work into packets

Split each component project into the independent work packets the supplier delivers. For example:

  • the design proposal,
  • prototype development,
  • the engineering release through tooling, sub-part development, production trials and approval, up to the first supply lot.

The objectives are to cut the lead time of each packet substantially and to keep the queue of waiting packets short, so that whenever a vehicle maker asks for something, it is done quickly. That requires more output from the same team, which means eliminating the waste of constant switching.

Two rules

1. One queue, limited work in progress. Put all open packets into one prioritised queue in front of each key group (design, vendor development). Limit how many are active at once; freeze the rest. A packet leaves the active list only when it is complete; then the next one enters. Packets in the queue can be reordered; active ones are finished first. A central coordinator keeps the queue, and everyone agrees not to send false urgency signals.

2. Full kit, with defined exit criteria. A packet starts only when everything needed to complete it is ready, and it is handed on only when its exit criteria are met. The two critical points for a supplier are the start of design (a full understanding of the application) and the handover from design to vendor development (a manufacturability check). Any concurrency is planned in advance, never improvised. A separate small team can prepare full kits for upcoming packets, using capacity released by rule 1.

With these two rules, output often rises sharply and the backlog shrinks. Requests from vehicle makers are handled quickly, and they start preferring this supplier, which brings more work. To avoid sliding back into chaos, the supplier must keep the waiting queue from growing again, and plan its next step up in capacity before it does.

A supplier can’t stop its customers’ plans from changing. It can stop those changes from turning into chaos inside its own walls.

Mohit Saini

Strategy, supply chain & sales transformation consultant. About · Book a discussion