How to Set Cost Reduction Targets when Data is Limited

Before starting any cost reduction effort, you need to decide if it is worth funding. Cost reduction requires time, resources, and clear financial return expectations.

A cost target provides the foundation for that decision by defining expected savings and linking technical effort to financial outcomes. When combined with project costs such as engineering hours, validation and tooling, it allows you to calculate the ROI and compare opportunities directly. In most organizations, leadership is not evaluating a single project in isolation. They are reviewing several proposals at once, each competing for limited resources and management attention. Some projects offer lower risk with moderate returns, while others promise larger savings but carry more uncertainty and longer timelines. A well-defined cost target creates a consistent basis for comparison, making tradeoffs visible and enabling faster, more grounded decisions that align with business strategy.

Cost targets also influence how teams behave once a project is approved. Without a clear target, work tends to fragment into isolated improvements that do not add up to meaningful results. Teams focus on what is easy to change rather than what matters most. With a defined objective, the mindset shifts. Teams begin to focus on closing the gap between current cost and the target. This alignment drives better collaboration across engineering, procurement, operations, and sales because each function understands how its actions contribute to the outcome. It also changes how individuals approach problems. Instead of accepting constraints as fixed, they begin to question assumptions, revisit earlier design decisions, and explore areas that were previously ignored. That shift in behavior is often where the most valuable cost reduction opportunities are found.

The Challenge of Limited Data

Setting cost targets early introduces a fundamental challenge because the available data is incomplete and often inconsistent. At the beginning of a project, specific ideas for reducing cost may not exist or are very conceptual and engineering feasibility is still evolving as teams begin to explore options. Competitive benchmarks may exist, but they are often based on indirect comparisons or outdated information.

Despite these limitations, the business still needs a target to decide whether to invest. Waiting for complete data is not a practical option because it delays decisions and slows progress at the point where early direction is most valuable. Projects that stall at this stage often lose momentum and struggle to regain it later. Instead of waiting, you need to accept that uncertainty is part of the process and build a target that is strong enough to support a decision.

This means working with imperfect information in a structured way. Each input you use may be incomplete on its own, but together they can form a credible estimate. The objective is not to achieve precision at this stage, but to define a target that is grounded in reality and aligned with business needs. You are building a range of understanding rather than a single exact number, and that range is sufficient to move forward.

Building a Target from Multiple Inputs

The process begins with margin requirements. If the current cost structure does not support that expectation, the difference defines your baseline cost reduction target. This ensures that the effort is anchored in financial outcomes rather than technical preferences or isolated ideas.

From there, estimate what the product should cost using high-level methods. These may include comparisons to similar products in your portfolio, benchmarking against known competitors, or applying simple models such as cost per unit weight or cost per functional output. While these approaches lack precision, they provide a directional view that is often sufficient to identify whether your current cost is significantly out of alignment.

At the same time, you need to consider the savings ideas already identified by the team. Early in a project, these ideas are typically limited in scope and may only cover a portion of the eventual target. This is expected and should not be seen as a limitation. In fact, the relationship between identified savings and the cost reduction target is an important signal. If identified savings already meet or exceed the cost reduction target, it indicates that the target is too conservative and will not drive meaningful change. If identified savings fall short of the target, the gap creates tension that encourages the team to explore further and uncover additional opportunities.

Engineering input is critical in refining the target. Engineers bring practical experience and an understanding of system constraints that cannot be captured through models alone. They can assess whether a target is achievable based on known limitations, past efforts, and the complexity of the design. They can also identify areas of uncertainty where outcomes may vary, such as new materials, manufacturing processes, or supplier capabilities. This input helps you adjust the target to reflect both opportunity and risk.

Historical experience provides another layer of validation. Looking at past cost reduction efforts allows you to understand what has been achieved under similar conditions and what challenges were encountered. For example, if previous projects consistently delivered savings in the range of 12% to 18%, setting a cost reduction target of 25% requires further justification as to what will be different from previous efforts.

Testing and Strengthening the Target

Once a preliminary cost reduction target is defined, it needs to be tested against financial constraints to ensure that it supports a viable business case. One practical method is to determine the minimum level of savings required to justify the investment. This calculation includes project costs such as engineering time, testing, tooling, and implementation, as well as the expected duration of the project and the volume of production over which savings will be realized.

If your proposed cost reduction target is only slightly above this minimum threshold, the project carries a higher level of risk because there is little margin for error. Even a small shortfall in performance could eliminate the financial benefit and result in a negative outcome. If the target is significantly above the minimum, the project has more flexibility and a higher probability of delivering a positive return, even if actual results fall short of expectations.

After this validation step, the cost reduction target should be increased before it is shared with the team. A typical increase ranges from 25 to 50 percent depending on the level of uncertainty and opportunity. This adjustment serves two purposes. First, it creates a stronger challenge that encourages the team to look beyond obvious solutions. Second, it reduces the risk of underperformance by building in a buffer between expected and required results. Teams often deliver more than initially expected when they are pushed to do so.

At this stage, the target may feel unrealistic. There may be no clear path in achieving it, and the identified savings may still fall far short. This is a normal part of the process. Meaningful cost reduction rarely comes from a single idea that closes the entire gap. Instead, it emerges from a combination of improvements across design, sourcing, and manufacturing. A change in material specification may reduce cost in one area. A supplier negotiation may provide savings in another. An improvement in manufacturing may reduce labor or cycle time. Individually, these changes may appear small, but together they can produce substantial results.

In many cases, the largest savings are discovered in a subsystem that was not initially considered a major opportunity. Once that area is examined in detail, it can contribute a significant portion of the total reduction and change the trajectory of the project.

Structuring Targets Across Teams

For larger systems, the overall cost reduction target may need to be broken down into sub-targets aligned with team responsibilities. Multiple teams are typically responsible for different subsystems, and each needs a clear objective to guide its work. Without this structure, accountability becomes unclear and effort may not be directed effectively.

Each team should have one clear target tied to a defined scope.

Keeping the structure simple is important. One top-level target and one target per team is usually sufficient to provide clarity without adding unnecessary complexity. Introducing multiple layers of targets or overly detailed breakdowns increases administrative effort and can slow decision making without improving results.

When allocating sub-targets, you need to consider where the greatest opportunities are likely to exist. Some subsystems may offer significant potential for cost reduction due to use of custom fasteners, high material usage, or manufacturability. Others may already be optimized and offer limited room for improvement. Allocating more aggressive targets to high-opportunity areas helps focus effort where it is most likely to produce meaningful results.

This allocation is based on initial assumptions and should not be treated as fixed. As the project progresses and more information becomes available, these assumptions may change. One subsystem may deliver more savings than expected, while another may struggle to meet its target. In these cases, targets may need to be reallocated to reflect actual performance and maintain overall progress.

Managing Execution and Performance

Execution requires active management and frequent tracking of progress against the target.
Visibility of cost performance helps teams act quickly and maintain ownership of results.

Tracking estimated cost on a regular basis creates a feedback loop that allows teams to identify gaps early and take corrective action before they become difficult to recover. This requires consistent measurement and a clear understanding of how each decision impacts overall cost. When performance data is visible to the entire team, individuals can make informed decisions without waiting for direction. This increases responsiveness and improves the overall pace of execution.

Cost reduction targets should guide decisions at every level of the project. They influence which ideas are prioritized, where resources are allocated, and how tradeoffs are made during design and implementation. This reduces ambiguity and ensures that effort is focused on achieving measurable results rather than simply completing tasks.

At the same time, teams must remain disciplined in evaluating savings. Not all cost reductions are valid. Some ideas may reduce cost but fail to meet performance, quality, or regulatory requirements. These false savings must be identified early and either corrected or discarded. Allowing them to continue creates rework and delays that can undermine the entire effort.

Iteration and Continuous Improvement

Cost reduction is an iterative process that requires multiple cycles of evaluation, validation, and adjustment. Teams generate ideas, assess their impact, test their feasibility, and refine their approach based on what they learn. As the project progresses, some areas will exceed expectations while others will fall short.

This variation is normal and should be expected in complex systems.

Targets may need to be adjusted as new information becomes available, but these changes should be made in a coordinated way to maintain alignment across teams. Project leadership and team leads should agree on adjustments before they are implemented to avoid confusion and ensure that all teams continue to work toward a common objective.

Over time, results begin to accumulate from multiple sources. Smaller improvements add up, and areas that were initially overlooked can become major contributors once they are examined in detail. It is common for a single subsystem to deliver a disproportionate share of the total savings, which reinforces the importance of maintaining focus across the entire system.

With consistent execution and disciplined management, even aggressive targets can be achieved and often exceeded. The key is to set a target that challenges the team, manage it actively, and remain flexible as new information emerges. This approach allows you to make sound investment decisions and deliver meaningful cost reduction even when starting with limited data.