User:Prazan/Decision Engineering

From Wikipedia, the free encyclopedia
Jump to: navigation, search
Decision engineering framework

Decision Engineering is a framework that unifies a number of best practices for organizational decision making. It is based on the recognition that, in many organizations, decision making could be improved if a more structured approach were used. Decision engineering seeks to overcome a decision making "complexity ceiling", which is characterized by a mismatch between the sophistication of organizational decision making practices and the complexity of situations in which those decisions must be made.

Despite the availability of advanced process, technical, and organizational decision making tools, decision engineering proponents believe that many organizations continue to make poor decisions. In response, decision engineering seeks to unify a number of decision making best practices, creating a shared discipline and language for decision making that crosses multiple industries, both public and private organizations, and that is used worldwide.[1]

To accomplish this ambitious goal, decision engineering applies an engineering approach, building on the insight that it is possible to design the decision itself using many principles previously used for designing more tangible objects like bridges and buildings. This insight was previously applied to the engineering of software—another kind of intangible engineered artifact—with significant benefits.[2]

As in previous engineering disciplines, the use of a visual design language representing decisions is emerging as an important element of decision engineering, since it provides an intuitive common language readily understood by all decision participants. Furthermore, a visual metaphor[3] improves the ability to reason about complex systems as well as to enhance collaboration.

In addition to visual decision design, there are two other aspects of engineering disciplines that aid mass adoption. These are 1) the creation of a shared language of design elements and 2) the use of a common methodology or process, as illustrated in the diagram above.


The need for a unifying methodology of decision making is driven by a number of factors that organizations face as they make difficult decisions in a complex internal and external environment. These include the fact that the world is increasingly interconnected, contains a growing number of actors (whether state entities, private competitors, or non-state actors) and technology advances that increase information flow and the speed with which decisions must be made.

Recognition of the broad-based inability of current methods to solve decision making issues in practice comes from several sources, including the US intelligence community,[4] and specific industries such as telecommunciations, media, and pharmaceuticals.

Transferring engineering principles[edit]

Unlike other decision making tools and methodologies, decision engineering seeks to bring to bear a number of engineering practices to the process of creating a decision. These include requirements analysis, specification, scenario planning, quality assurance, security, and the use of design principles as described above. During the decision execution phase, outputs produced during the design phase can be used in a number of ways; monitoring approaches like business dashboards and assumption based planning are used to track the outcome of a decision and to trigger replanning as appropriate. One view of how some of these elements combine is shown in the diagram at the start of this article.

Like related engineering disciplines before it, decision engineering promises improvements in the quality of decisions made, the ability to make them more quickly, the ability to align organizational resources more effectively around a change in decisions, and lowers the risks associated with decisions. Furthermore, a designed decision can be reused and modified as new information is obtained.


It is interesting to note that, despite decades of development of decision support systems and methodologies, these are still less popular than spreadsheets as primary tools for decision making. Decision engineering seeks to bridge this gap, creating a critical mass of users of a common methodology and language for the core entities included in a decision, such as assumptions, external values, facts, data, and conclusions. If a pattern from previous industries holds, such a methodology will also facilitate technology adoption, by clarifying common maturity models and road maps that can be shared from one organization to another.

The decision engineering approach is multidisciplinary, unifying findings on cognitive bias and decision making, situational awareness, critical and creative thinking, collaboration and organizational design, with engineering technologies.

Decision engineering is considered an improvement upon current organizational decision making practices, which include the use of spreadsheets (difficult to QA, hard to collaborate and discuss), text (sequential in nature, so is not a good fit for how information flows through a decision structure), and verbal argument. The movement from these largely informal structures to one in which a decision is documented in a well understood, visual language, echoes the creation of common blueprint methodologies in construction, with promise of similar benefits.

Decision engineering is both a very new and also a very old discipline. Many of its elements—such as the language of assessing assumptions, using logic to support an argument, the necessity of critical thinking to evaluate a decision, and understanding the impacts of bias—are ancient. Yet the realization that these elements can form a coherent whole that provides significant benefits to orgnizations by focusing on a common methodology is relatively new.

Visual decision design[edit]

Because it makes visible the otherwise invisible reasoning structures used in complex decisions, the design aspect of decision engineering draws from other conceptual representation technologies like mind mapping, conceptual graphs, and semantic networks. The basic idea is that a visual metaphor enhances intuitive thinking, inductive reasoning, and pattern recognition—important cognitive skills usually less accessible in a verbal or text discussion. A business decision map can be seen as one approach to a formal decision language to support decision engineering.


  • Amos Tversky's seminal work on cognitive bias and the irrationality of human economic choices.
  • Nobel Laureate Daniel Kahneman, who continues to study the impact of associative cognitive bias on decision making.
  • The term "Decision engineering" is used in several industries with more specific meaning than the framework described here. For instance, the Australian Software Research Centre has an IT evaluation approach called Decision Engineering; Idea focuses on emergency management under the heading of "Decision Engineering Analysis"; and the National University of Singapore includes an organization called the Decision Engineering Group. Each of these has a meaning that is distinct from what is discussed in the present article.
  • Cost engineering applies engineering principles to measure the costs associated with engineering projects. Cost engineering is sometimes grouped into the broader context of other engineering decisions, such as product engineering and design optimization, in which context it is sometimes referred to as "Decision Engineering". This can be distinguished from the broader framework of this article, which goes beyond the arena of engineering decisions to all decisions faced by organizations.[5]
  • Operations research is a largely quantitative approach to decision making that attempts to identify optimal or near-optimal solutions to decision making problems.

See Also[edit]