Disruptive solutions process: Difference between revisions

Revision as of 10:31, 17 June 2021

Latest revision as of 19:38, 9 March 2025

(9 intermediate revisions by 8 users not shown)

Line 1:

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

[[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 formdecision-making ofprocess iterative,used low-cost,by first-to-marketthe development[[United States Air Force]] and [[Air National Guard]]. It was created in 2005 by [[fighter pilot]] and [[United States Air Force]]/[[Air National Guard]] [[Colonel (United States)|Colonel]] Edward Vaughan and is iterative, low-cost, and first-to-market in nature.<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]] to prevent mishaps during the [[combat operations process]].

==Overview==

The typical defense industry bureaucratic approach to problem-solving involves long [[Leadlead time|lead times]]s and relative inflexibility. Long development cycles and lead times results in solutions that are no longer relevant.<ref>[{{cite web |url=http://www.nationaldefensemagazine.org/blog/lists/posts/post.aspx?ID=661 |title=DoD Procurement Chief: Acquisition Programs Stuck in Cycle of Failure - Blog |website=www.nationaldefensemagazine.org |access-date=27 January 2022 |archive-url=https://archive.today/20140503132704/http://www.nationaldefensemagazine.org/blog/lists/posts/post.aspx?ID=661] |archive-date=3 May 2014 |url-status=dead}}</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] {{Dead link|date=February 2022}}</ref> Conversely, when resources are constrained, bureaucratic staff adopt continuous process improvement, similar to [[kaizen]], [[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 [[Creative disruption|disruptive]], [[Iterative and incremental development|iterative approach]] that may not be appropriate in hardware-focused programs, such as aircraft production.

To address the cultural issues associated with mishap prevention in a large bureaucracy, the [[Air National Guard]] safety directorate used Boyd's [[OODA Loop|Observe, Orient, Decide, Act Loop]] to assess the effectiveness of the process. This was the origin of DSP.

DSP is persistent and adaptive:<blockquote>"Persistence is about refusing to give up even in the face of adversity. Adaptation is about shortening the time to success through ingenuity and flexibility. 'Adaptive persistence' entails alternating between anticipation, changing course, and sticking with it, deftly navigating that paradox with aplomb."<ref>[http://blogs.harvardbusiness.org/gergen-vanourek/2009/04/fending-off-the-recession-with.html Adaptive Persistence article from HBR]</ref></blockquote>

{{blockquote|Persistence is about refusing to give up even in the face of adversity. Adaptation is about shortening the time to success through ingenuity and flexibility. "Adaptive persistence" entails alternating between anticipation, changing course, and sticking with it, deftly navigating that paradox with aplomb.}}

==Basic process==

DSP is a six-step process that focuses on projecting future market needs by looking at front-line problem solving activity and scaling those solutions up. Although the full algorithm has not been publicly published as of January 2024, the following process has been made public:

1. POLL FIELD—IDEA MINING: Use network of professionals at the field unit level to identify best practice mishap prevention, education, mishap investigation, procurement, and other tools. Look for full and partial solutions.

2. CONSOLIDATE / RACK AND STACK: Sort list of ideas into groups based on resource requirements, proven record, technology leveraging, mission accomplishment, and identified needs. Rank order all projects based on overall value to the force using DSP assessment algorithm.

3. ELIMINATE BAD FITS: Scrub the list for those items requiring major hardware, Air Force Major Command level funding, or other special, difficult to acquire funding or processes. Also remove from consideration solutions that duplicate or compete directly with future programmed or existing military programs unless the cost savings is significant, as well as those programs that are not scalable in scope.

4. SELECT AND DEM/VAL: Consider resource requirements and rapidly source field unit funding or headquarters seed monies in the sub-$50K range to perform a limited demonstration and validation (DEM/VAL) of concept. Use rapid contracting mechanisms through government contracting office, primarily employing SBA set-asides, blanket purchase agreements, or previously procured assets that may be re-roled into current use.

5. ITERATE FOR RESULTS: Establish definition of success that are measurable and reportable. Then, demonstrate measurable results within six months. Meanwhile, seek further external and scalable funding from sources such as DARPA, Defense Safety Oversight Council (DSOC), other services, other government agencies, etc.

6. LEAD AND MARKET: Market the solution intensely and seek buy in by returning the solution to same experts that initially proposed it. Identify capable project leaders to run with the project.

This is a form of the more well known [[OODA loop]]. Step 1 is Observe, steps 2 and 3 are Orient, steps 4 and 5 are Decide, and step 6 is Act.

==History==

The disruptive solutions process was first used 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]]s 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]] and [[USAF|the United States Air Force]] to field mishap prevention programs:

* ''See and Avoid'': a web-based civilian-military midair collision avoidance program created by Vaughan and led by the [[Air National Guard]] Safety directorate from 2005 to 2009.<ref>[http://www.SeeAndAvoid.org See And Avoid] {{webarchive|url=https://web.archive.org/web/20061020000103/http://www.seeandavoid.org/ |date=October 20, 2006 }}</ref>

* ''WingmanDay.org'': provides tools for commanders, leaders, and care practitioners. In 2011, the program was relaunched as ''Wingman Day''. The Air Force Safety Center took the RealBase Toolkit concept and developed one-stop-shopping online tool kits hosted on the secure Air Force Portal.<ref>{{Cite web |url=http://www.wingmanday.org/ |title=Wingman Day |access-date=November 28, 2019 |archive-url=https://web.archive.org/web/20161202213017/http://wingmanday.org/ |archive-date=December 2, 2016 |url-status=dead }}</ref>

* ''FlyAwake'': a web-based fatigue risk management tool which returns quantitative fatigue analysis for a given flight schedule.<ref>[{{Cite web |url=http://www.Flyawakeflyawake.org/ |title=Fly Awake, User-Friendly Fatigue Assessment and Mitigation] |access-date=February 17, 2009 |archive-date=January 17, 2009 |archive-url=https://web.archive.org/web/20090117025735/http://www.flyawake.org/ |url-status=dead }}</ref>

* ''[[Wingman Project|''Wingman Project'']]'': a suicide intervention initiative that shows family and friends of distressed Airmen how to intervene to save a life, providing training in 54 U.S. states and territories.<ref>{{usurped|1=[https://web.archive.org/web/20091006181638/http://www.WingmanProjectwingmanproject.org/ The Wingman Project]}}</ref>

* ''FlyAwake'': a web-based fatigue risk management tool which returns quantitative fatigue analysis for a given flight schedule.<ref>[http://www.Flyawake.org Fly Awake, User-Friendly Fatigue Assessment and Mitigation]</ref>

* [[Wingman Project|''Wingman Project'']]: a suicide intervention initiative that shows family and friends of distressed Airmen how to intervene to save a life, providing training in 54 U.S. states and territories.<ref>[http://www.WingmanProject.org The Wingman Project]</ref>

* ''dBird bird mortality model'': tracks and predicts movements of pathogen-infected bird flocks using [[Bird strike|bird-aircraft-strike-hazard]] resources.<ref>{{Cite web |url=http://www.dbird.us/ |title=dBird, Bird Mortality Model |access-date=November 28, 2019 |archive-url=https://web.archive.org/web/20140102002503/http://dbird.us/ |archive-date=January 2, 2014 |url-status=dead }}</ref>

* ''Low Altitude Deconfliction Program'': an online scheduling function with [[FAA|the Federal Aviation Administration]]'s MADE program to avoid collisions for military aircraft operating in low-altitude environments.<ref>{{Cite web |url=http://www.deconflict.org/ |title=Low Level Deconfliction |access-date=July 26, 2019 |archive-url=https://web.archive.org/web/20110520002506/http://www.deconflict.org/ |archive-date=May 20, 2011 |url-status=dead }}</ref>

Line 52 ⟶ 70:

==External links==

* The Wingman Project: {{usurped|1=[https://archive.today/20091006181638/http://www.wingmanproject.org/ Suicide Intervention]}}

* See And Avoid: [https://web.archive.org/web/20061020000103/http://www.seeandavoid.org/ Civil/Military Mid-Air Collision Avoidance]

* Richards, Chet: [https://web.archive.org/web/20090227065603/http://www.d-n-i.net/boyd/boyds_ooda_loop.ppt OODA explained]. Seven-slide presentation explaining the OODA Loop

Line 59 ⟶ 77:

* Lockheed's Skunkworks: [https://web.archive.org/web/20090227060019/http://www.lockheedmartin.com/aeronautics/skunkworks/14rules.html Kelly's 14 Rules]

* Seamless Compassion, One-stop Automated Public Assistance: [https://web.archive.org/web/20110826220933/http://seamlesscompassion.org/ Seamless Compassion Link]

* FlyAwake: [http://www.flyawake.org Pilot Fatigue Mitigation] {{Webarchive|url=https://web.archive.org/web/20090117025735/http://www.flyawake.org/ |date=January 17, 2009 }}

[[Category:United States Air Force]]