The Technology Valley of Death, Another Viewpoint
Robert Herron
Delivering Strategic Engineering Leadership to drive excellence in sustainability and scalability to organizational growth. Engineering Operational Management | Product Research & Development (R&D) | Program Management
Let’s chat about the technology “Valley of Death”. ?There are many comments and articles on the topic lamenting about the “Valley of Death” and its causes. ?Everyone is frustrated about the lack of technology implementation and innovation across all types, levels, and domains of technology.? Many point a finger at causes such as “not willing to take risks” or “overburdensome requirements”.? So, the typical demand is to loosen requirements.? I want to present an alternative view for your consideration.
In a September 15, 2024 post, I referenced two reports released by independent review boards of two major innovation leading government organizations, the DoD and NASA.? The two reports I highlight are:
?
Each study board found evidence supporting the prevalent rationale that contribute to the manifestation of the “Valley of Death”. ?Supporting statements in each reports include:
?
But let us not be satisfied with evidence that appear to support our confirmation bias around the contributing factors for the “Valley of Death”, instead let’s explore further.?
?
The NASA report highlights another little discussed issue that I believe may be a larger contributor. ?The National Academies NASA study states the following:
?
I summarize these two findings as:
领英推荐
?
Now let’s determine if these two findings are applicable to the DoD.? The DIB report sheds some light on the DoD’s approach to maturing technologies for acquisitions.? The DIB found, “…while programs [technology development] with Technology Readiness Levels (TRLs) in stages 6-7 are vital in establishing military viability and paving the way for emergent technology—they receive less than 10% of total RDT&E dollars… “.? But we must look beyond the DIB report to shed any light on the impact of this reported finding on acquisition planning and outcomes as the DIB did share any deeper insights into the impact.
?
The Government Accountability Office (GAO) has conducted annual weapon systems assessment on DoD’s major acquisition programs at least since 2016.? Reviewing GAO’s assessments, you will find for the past 20 years, on average, DoD acquisition programs experience 40% cost overruns during the technology development phase of the acquisition. ?For reference, an ACAT 1 program has an estimated RDT&E threshold of more than $525 million1. ?Therefore, using $525 million as a baseline, a 40% overrun is $210 million per program. Extrapolated over 20 programs, it is equivalent to $4,200 million or $4.2 billion in cost overruns across the DoD. ?Worse yet, technology development cost and schedule overruns do not generally translate into manufacturing or operational cost savings.
?
Consider the following potential impacts because of the DoD investing “less than 10% of total RDT&E dollars” to mature technologies:
?
Point 1: ?Consider that “not willing to take risks” is not the contributor to the “Valley of Death” that many make it out to be.? Instead, consider that the information may suggest Program Managers are taking technology risk in the acquisitions they manage equivalent to a $250 million financial risk, on average.
?
Point 2: ?I suggest that the information indicates a contributor the technology implementation of the “Valley of Death” is a lack of available resources resulting from technology risks. ?When acquisition programs exceed their budgets by $250 million during the initial phases of an acquisition, it likely depletes planned resources for requirements such as reliability and maintainability, much less freeing up funding for other technology insertions. ?As noted in the example above, a $4,200 million cost overrun is equivalent to funding the $525 million technology development budgets for 8 new ACAT I acquisition programs.
Point 3: Consider the question, "Does the underfunding of technology maturity contribute to poor acquisition planning and execution resulting in cost and schedule overruns?"
?
While I do not discount the common complaints and contributors to the technology “Valley of Death”, I hope this brief discussion provides a broader picture on other and potentially more relevant contributors.
?
Mechanical Design Engineer for Naval Systems
4 个月I think part of the issue is lack of filtering capability and "pull" on the government side due to the relatively low priority for transition of an organization's core competency technical knowledge to technical workforce and the lack of INTERNAL technical learning and development opportunities being created and offered. It is all external with STEM and Talent pipeline -Good, but what about the existing workforce? Look at the Senior Leadership training- The same 24 competencies, books, and emphasis on management and generic leadership. For organizations with a significant technical mission, where are technical leadership opportunities? How about: Enterprise-Level Use of AI to Improve Intellectual Capital; Creating a Continuous Technical Learning Environment; Managing Technical Knowledge and Human Intellectual Capital in the 21st Century; Stewarding Critical Intellectual Capital in National Defense Organizations;Using a Khanmigo-Style Learning Assistant to Track Technical Capabilities; Motivating Intellectual Curiosity in a Technical Workforce for Purpose-Filled Careers; Enterprise level Technical Capability Metrics and assessments; PPBE of Workforce Development or Enterprise integration of Technical Mission strategic objectives ?