Disruptive solutions process: Difference between revisions

Revision as of 10:24, 17 June 2021

Revision as of 10:28, 17 June 2021

Line 2:

{{Use mdy dates|date=September 2012}}

{{abbreviations|date=April 2011}}

[[File:Air National Guard - Flickr - The National Guard (1).jpg|thumb|The [[Air National Guard]] is the primary user of DSP.]]

The '''disruptive solutions process''' ('''DSP''') is a form of iterative, low-cost, first-to-market development created in 2005 by [[fighter pilot]] and the [[United States Air Force]]/[[Air National Guard]] [[Colonel (United States)|Colonel]] Edward Vaughan.<ref>[http://www.defenselink.mil/news/newsarticle.aspx?id=53044 Face of Defense: Air Guardsman Entrepreneurial Approach..]</ref> It is primarily used by the [[Air National Guard]] at the [[military tactics|tactical]] or operational level to prevent mishaps during the [[combat operations process]]. However, it has been used successfully in other government agencies and the private sector. The term 'disruptive' was borrowed from the marketing term [[disruptive technologies]].

==Overview==

The typical defense industry bureaucratic approach to problem-solving involves long [[Lead time|lead times]] and relative inflexibility. Long development cycles and lead times results in solutions that are no longer relevant.<ref>[https://archive.today/20140503132704/http://www.nationaldefensemagazine.org/blog/lists/posts/post.aspx?ID=661]</ref>

Recent attempts to resolve inefficiencies include overwhelming the problem with funding, resources, and manpower—for example, major weapon systems development, such as a new fighter jet or IT system.<ref>[http://www.armytimes.com/article/20140403/NEWS/304030061/Lawmakers-scold-DoD-medical-records-failure]</ref> Conversely, when resources are constrained, bureaucratic staff adopt continuous process improvement, similar to [[Kaizenkaizen]], [[total quality management]], and [[Lean Six Sigma]]. This perpetuates low-value programs that should be eliminated, rather than "improved".

Because most preventable safety mishaps are caused by human factors,<ref>Catalog of Air Force Statistics by Aircraft Type, considered typical for US Military [http://www.afsc.af.mil/organizations/aviation/aircraftstatistics/index.asp] {{Webarchive|url=https://web.archive.org/web/20081205120401/http://www.afsc.af.mil/organizations/aviation/aircraftstatistics/index.asp |date=December 5, 2008 }}</ref> safety should apply a disruptive, iterative approach that may not be appropriate in hardware-focused programs, such as aircraft production.

Line 19 ⟶ 20:

{{Unreferenced-section|date=May 2021}}

{{How to|section|date=May 2021}}

}}Essentially DSP is a six-step process that runs counter to the military mantra of being "requirements-driven", instead focusingfocuses on projecting future market needs. This is accomplished by looking at front-line problem solving activity and scaling thesethose solutions up. These six steps, when applied rapidly, can get ahead of recognition, providing viable solutions at the point and time of need:

1. IDEA MINING: use professionals at the field unit level to identify best practices for mishap prevention. Project unpublished requirements by including end-use customers in the idea mining process.

Line 34 ⟶ 35:

==History==

DSP was initiated in 2004, when a joint team led by Vaughan created Project ''Black Mountain''. The project evolved from a combined requirement to share real-time tactical data among ground and air forces, as well as avoid [[mid-air collision|mid-air collisions]] within the [[area of responsibility]]. The term 'disruptive' was borrowed from the marketing term [[disruptive technologies]].

More recently, DSP has been used in the [[Air National Guard|ANG]] and [[USAF]] to field mishap prevention programs: