The 70% Problem: Why Lifecycle Costs Are Locked in During Design

Source: Sanders and Klein (2012), adapted from the INCOSE Systems Engineering Handbook.

That finding comes from a Honeywell Aerospace study published through the Conference on Systems Engineering Research, drawing on data from the INCOSE Systems Engineering Handbook.

The researchers were investigating why aerospace and defense programs consistently blow past their budgets and timelines. Their conclusion was blunt: the problem almost always traces back to decisions made at the front end of development.

The Numbers Behind the Problem

The lifecycle cost curve is steep and unforgiving. By the time conceptual design wraps up, 70% of total costs are committed.
Finish the detailed design phase, and that number climbs to 85%. By the time you enter development, you have already determined 95% of what you are going to spend across the product’s entire life, often 10, 20, or 30 plus years.

What makes this worse is the cost of changing course. During design, a change runs 3 to 6 times more expensive than catching it during concept.
During development, that multiplier jumps to 20 to 100 times. Once you are in production, you are looking at 50 to 1,000 times the original cost to fix something that could have been addressed in the first months of the program.

This is why “we will fix it later” is the most expensive sentence in product development. Later costs exponentially more.

This Is Not a Theoretical Problem

The study pointed to real programs where this pattern played out at scale. A Government Accountability Office assessment of active defense acquisition programs found, on average,
42% growth in research and development costs beyond original estimates, and initial capability delivery running 22 months behind schedule.
Nearly half the programs also saw unit acquisition costs increase by 25% or more.

Commercial aerospace has not been immune. The Airbus A380 and A400M both ran years behind schedule and billions over budget.
The Boeing 787 Dreamliner saw its first flight delayed nearly two years.

In each case, the pattern was the same. Early decisions about architecture, materials, supply chain structure, and manufacturing approach created constraints that cascaded through the entire program lifecycle.
The financial costs were obvious, but the damage went further: eroded stakeholder confidence, strained partnerships, and delayed capabilities reaching the people who needed them.

Where Communication Fits In

The decisions made during that critical early window are not purely technical. They are shaped by conversations between engineers, executives, investors, and partners,
groups that often do not share a common language.

When technical complexity outpaces the audience’s ability to follow, decisions default to what feels safest.
And safe choices made from incomplete understanding are where cost overruns begin.

The core argument in the study is that producibility and affordability need to be part of the design conversation from day one, not bolted on after the architecture is set.
The same principle applies to how that architecture gets communicated to the people who greenlight it.

What This Means for Early Stage Programs and Newspace Startups

The lifecycle cost curve is not going to change. The physics of product development mean that early decisions will always carry disproportionate weight.
What can change is how well those decisions get communicated to everyone who has a hand in making them.

That means making technical innovations understandable to non technical decision makers before commitments are locked in, not after.
The programs that get this right build stronger stakeholder alignment earlier, and that alignment is what keeps funding, partnerships, and timelines on track.