3 Signs Your Product Development Process Is Costing You More Than You Think

It's vacation time. The phone is (almost) off, the coffee is still hot, and for once, you have time to think instead of react. Let's take advantage of it to talk about a subject there's never time for during the year: your product development process.

Let's start with some good news: in the vast majority of teams Merkur works with, the problem isn't talent. The engineers are skilled, the designers are creative, the managers work hard. And yet, projects drag on, budgets overrun, and time-to-market disappoints.

Why? Because in product development, it's not only what you do that counts — it's when you do it. The right decisions made at the wrong time cost almost as much as the wrong decisions. Here are three signs that the sequence of your process is working against you — and what it's really costing you.

Sign #1: The big decisions get made at the end of the project

Does this scenario sound familiar? The concept is chosen quickly, detailed design moves along at a good pace… then, a few weeks before production launch, everything starts to shift: the product cost is too high, assembly is more complicated than expected, a supplier can't deliver the part as drawn. You modify, redo drawings, rerun validations.

The problem is that the cost of a change explodes as a project moves forward. A decision that costs an hour of discussion in the concept phase can cost weeks of rework in the industrialization phase — not counting the tooling to modify and the delays that pile up. That's the whole difference between cost prevention (making the right choices before they're set in stone) and cost reduction (trying to recover what you can, after the fact). The first is by far the more profitable, but it requires one thing: that questions of manufacturability, assembly, and sourcing be asked at the start — not at the end.

Sign #2: Your engineering team has become the bottleneck

Second symptom, and probably the most common one: engineering is constantly being interrupted by production. Questions come from everywhere — “there's a dimension missing on the drawing,” “there's no way we can assemble it like that,” “what was the intent here?” — and while the team answers them, new projects don't move forward. The result: engineering becomes the bottleneck of the entire company.

The natural reflex is to blame the workload, when the real cause is upstream: manufacturing and assembly requirements aren't captured at design time. When you know from the start the plant's processes, the production team's pain points, and your suppliers' constraints, you design something that assembles right the first time — and the questions stop coming back.

That's exactly the role of activities like DFMA integrated directly into the development process: not a one-off exercise when a product “comes out wrong,” but a systematic reflex on every new project. The difference is enormous — on one side, you fix things product by product; on the other, your engineering team is freed up for good.

Sign #3: Every product starts from a blank page

“Us? Everything we do is custom.” We hear that phrase constantly — and nine times out of ten, it deserves to be challenged. Because when you look closely at the catalogue, you don't find thousands of different products: you find variations of the same family. And yet, every order starts from a blank page.

Think of a vehicle: the skeleton is shared, and options are grafted onto it. That's what modular design is — a common core of proven sub-assemblies, with a layer of customization on top. When it's missing, “custom” comes at a steep price: you redraw parts that already existed under another part number, you requalify suppliers for nearly identical components, you redo validations on solutions that had already proven themselves.

The cost of false custom doesn't show up on a quote — it's diluted across every project. But added up over a year, it often amounts to hundreds of engineering hours and an exploding parts inventory, to deliver products the customer perceives as… pretty much the same. Standardization and modularization are among the most profitable levers in a development process — and among the most neglected.

It's not a question of talent. It's a question of sequence.

If you recognized yourself in one of these three signs (or all three — it happens more often than you'd think!), remember this: none of it gets fixed by working harder. It gets fixed by working in the right order.

And let's be honest: most teams call us when the fire has already started. That's fine — it's actually the norm, and we're very good at putting out fires. But the real gain is the next step: once the fire is under control, embedding good practices directly into the development process so that this fire is the last one. We've supported teams who already knew these approaches, had applied them, then lost them through departures and reorganizations — re-embedding them durably into the process is what changes the trajectory.

Concretely, this diagnoses well. A structured look at your current process — how projects get started, how production requirements are captured, where time is really being lost — is usually enough to identify two or three levers that change the game: integrated DFMA, standardization, cost targets managed from the design stage onward (design-to-cost). From there, we define where you want to be in 12 months, measure the gap, and build a realistic action plan, with quick wins to create momentum.

That's exactly the kind of support we offer at Merkur: a diagnostic of your product development process, an honest gap analysis, a concrete action plan — and, if you wish, a team to help you implement it, or engineering reinforcement to keep delivering while you transform.

But for now, file it away in a corner of your mind. Enjoy your vacation. We'll talk again in the fall — and until then, if one of the three summer tests made you wince, you know where to find us. 

Merkur has been supporting manufacturing companies in their engineering and product development projects for over 30 years. Discover our product development services.