Projects

Three rules for faster product development

Mohit Saini · 27 Jul 2026 · 4 min read

Three rules for faster product development

Customers today are spoilt for choice in almost every category: cars, phones, appliances, clothes, even coffee. Each company launches new features; competitors respond with their own; and the cycle speeds up. Product development teams are under pressure to deliver more products, faster, often with a high failure rate for new launches.

In most development organisations, the people and skills haven’t grown as fast as the workload. Add the uncertainty of developing something new and a heavy dependence on outside suppliers for parts and tooling, and you get the familiar symptoms: rework, delays, unstable production after launch, late launches, and exhausted engineers.

Why it is especially hard in engineered products

Developing a vehicle, an appliance or an industrial product is complex for two reasons:

  • Design interdependence. Mating parts are designed by different teams. A change in one part ripples into several others.
  • Supplier dependence. Many components and their tooling are developed by different vendors.

Some iterations are unavoidable in the early stages. But when designers also switch between several projects, they keep producing new versions of the same drawing to absorb the latest change from someone else. Time slips, and the pressure to start tooling grows.

The usual remedies, and why they fail

More people. Managers on the ground see a capacity problem and ask either for more people or for fewer projects. Top management wants more projects, not fewer. Experienced experts are hard to hire, and fresh graduates add numbers but not much real capacity. “Work harder” doesn’t help either.

More visibility. Top management sees a visibility problem: issues surface late, it is hard to pin delays on any one department, and requests for more resources aren’t backed by data. So they invest in tools with detailed task and resource schedules. In an environment of constant rework and scope changes, those schedules are out of date within days. Plans end up being revised to match what already happened, rather than guiding what happens next.

More fast-tracking. Under time pressure, departments hand over work early without waiting for critical inputs, hoping to gain time. This is “concurrent engineering” done badly, and it backfires.

Two kinds of rework

It helps to distinguish two kinds of iteration:

  • Valuable iteration: a test or simulation shows that a design doesn’t work, generating new knowledge. This leads to a better product.
  • Wasteful rework: work handed over before the information it depends on was ready. This creates rework later, at much higher cost.

The goal isn’t zero iteration. It is eliminating the wasteful kind.

The hidden cause: no limit on work in progress

On a shop floor, excess work in progress is visible. It clutters the floor and shows up in the balance sheet. So factories develop mechanisms to control it.

In product development, work in progress is invisible. Drawings sit on hard disks. Components are scattered across vendors. There is always room to open one more project. Nothing in the accounts shows it. So nobody limits it, and every resource group has a long, shifting list of tasks across projects and phases. Each project sponsor pushes his project with aggressive deadlines, which delays all the others, which makes their sponsors push harder.

It is like trying to drive faster by pressing the accelerator harder while keeping a foot on the brake.

Rule 1: Limit work in progress

Think of a doctor’s clinic that runs on tokens. Nobody knows in advance how long each patient will take, or when the next one will walk in, so the clinic doesn’t make a timed schedule. It simply sees one patient at a time, in token order, and calls the next only when the current one is done. When the queue grows, it looks for ways to move faster, but it never sees two patients at once.

Product development can work the same way:

  • Define work in modules with clear completion criteria.
  • Set a work-in-progress limit for each critical group, often around half of today’s level, and freeze the rest.
  • A new module enters only when one is completed: one in, one out.
  • Agree a single priority order across all projects, so every group pulls from the queue in the same sequence.

Freezing work feels frightening, especially when everything is already late. But fewer open tasks means less switching, faster closures and released capacity.

Rule 2: Full kit before starting

Development should start on a module only when the full kit of inputs it depends on is complete and checked: interacting designs, specifications, approvals, customer inputs. No more handing over half-finished work “to save time”.

Teams usually accept the logic of gates but break them under time pressure. Rule 1 makes Rule 2 possible: once design lead times shrink, there is time to honour the gate.

Rule 3: Plan with buffers, manage daily

Instead of deadlines for every task (which hide safety time in each task, only to waste it), plan each project with realistic touch times and a shared project buffer at the end. Then:

  • Watch the flow of work daily, not only near milestones, and step in when a task is interrupted, reworked or expanding.
  • Use the rate of buffer consumption compared with progress as the early-warning signal and the priority signal across projects.
  • Give top management visibility of which projects and which groups are burning buffer fastest.

Companies that apply these three rules (full kit, controlled work in progress, buffer-based planning and execution) often cut development lead times by half or more while significantly increasing the number of projects completed.

Development teams don’t need to start more projects. They need to finish the ones they have started.

Mohit Saini

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