Decision Making
The Decision-Making Process
Decision Making
The logical process of identifying a problem or opportunity, generating alternatives, and choosing the optimal course of action based on the values, preferences, and available data of the decision-maker.
Engineering managers are essentially paid to make decisions. The quality of a manager's decisions directly dictates the success or failure of their team and projects. A rational decision-making process involves these sequential steps:
Procedure
- Identify the Problem: Recognize that a discrepancy exists between the current state of affairs and the desired state. Define the root cause, not just the symptoms.
- Establish Decision Criteria: Determine what factors are relevant in making the decision (e.g., cost, time, safety, quality).
- Allocate Weights to Criteria: Prioritize the criteria. Not all factors are equally important (e.g., safety might be weighted heavily, while aesthetics might be weighted lower).
- Generate Alternatives: Brainstorm and list all viable solutions or courses of action.
- Evaluate Alternatives: Critically assess the pros and cons of each alternative against the weighted criteria established in steps 2 and 3.
- Select the Best Alternative: Choose the alternative that scores the highest and best resolves the problem.
- Implement the Decision: Put the chosen alternative into action and communicate it to relevant stakeholders.
- Evaluate the Decision Effectiveness: Review the results after implementation. Did it solve the original problem? If not, the process must begin again.
Bounded Rationality and Heuristics
While the rational decision-making process is ideal, human beings rarely make perfectly rational choices due to cognitive limitations and time constraints, a concept known as Bounded Rationality.
Heuristics and Biases
Managers often rely on heuristics (mental shortcuts or "rules of thumb") to quickly process complex information. However, these shortcuts can lead to cognitive biases:
- Availability Heuristic: Basing decisions entirely on information that is readily available in memory (e.g., heavily weighting the risk of a recent, highly publicized bridge collapse, even if statistically rare).
- Confirmation Bias: The tendency to seek out only information that explicitly supports one's pre-existing beliefs while ignoring completely contradictory data.
- Sunk Cost Fallacy: Continuing to invest heavy capital into a failing engineering project simply because a massive amount of money has already been spent, rather than cutting losses based on future utility.
Group Decision Making
Engineering problems are often too complex for one individual, requiring collective expertise. Group decision-making leverages diverse perspectives but must be managed carefully to avoid "groupthink."
Checklist
- Brainstorming: A highly interactive technique to generate an enormous volume of creative alternatives in a short period. Criticism of ideas is strictly forbidden during the generation phase to encourage wild, "out-of-the-box" thinking.
- Nominal Group Technique (NGT): A highly structured variation of brainstorming where individuals silently write down ideas first, then systematically present and rank them, ensuring that powerful personalities do not dominate the quiet introverts.
- Delphi Technique: An anonymous, iterative process using written questionnaires administered by an external facilitator to a geographically dispersed panel of experts. It completely eliminates interpersonal conflict and groupthink.
Types of Decisions
Managers face a spectrum of decisions, categorized broadly by their frequency and complexity.
Programmed vs. Non-Programmed Decisions
- Programmed Decisions: Routine, repetitive, and highly structured decisions. Procedures, rules, or policies are already in place to handle them. The information needed is readily available.
Example: Approving standard employee leave requests or reordering raw materials when inventory hits a specific par level. - Non-Programmed Decisions: Unique, one-shot, and completely unstructured decisions. Information is often ambiguous or incomplete, requiring custom-tailored solutions and high-level judgment.
Example: Deciding whether to acquire a competing engineering firm or selecting a site for a new, first-of-its-kind manufacturing plant.
Decision-Making Conditions
The level of information available to the manager dictates the condition under which the decision is made.
Checklist
- Certainty: The ideal condition. The manager knows exactly what the outcome of every alternative will be. (Rare in complex engineering management).
- Risk: The most common condition. The manager cannot guarantee outcomes, but they have enough historical data or expertise to assign accurate probabilities to different outcomes.
- Uncertainty: The manager has neither certainty about outcomes nor reasonable probability estimates. Decisions here rely heavily on intuition, experience, and psychological orientation (optimism vs. pessimism).
Quantitative Tools for Decision Making
When making decisions under conditions of risk or uncertainty, engineering managers utilize mathematical models to formalize the process and remove emotional bias.
Payoff Matrices
A Payoff Matrix is a table that displays the possible financial payoffs (profits or costs) for different alternatives under various unpredictable future events (called "states of nature").
When operating under strict Uncertainty (no probabilities known), managers use psychological strategies to pick an alternative from the matrix:
- Maximax (Optimist's Choice): The manager assumes the best possible state of nature will occur and chooses the alternative that yields the absolute highest maximum payoff.
- Maximin (Pessimist's Choice): The manager assumes the worst possible state of nature will occur. They look at the worst possible outcome for each alternative and choose the "best of the worst" to guarantee a minimum baseline outcome.
- Minimax Regret: The manager seeks to minimize the maximum "regret" (opportunity loss)—the difference between the actual payoff they received and the best possible payoff they could have received had they known the state of nature in advance.
Decision Trees and Expected Value
A Decision Tree is a chronological, graphical representation of a decision situation. It uses squares to represent decision points (where the manager chooses an alternative) and circles to represent chance nodes (states of nature with assigned probabilities). It is the premier tool for decisions involving sequential choices under conditions of Risk.
Expected Value (EV)
$$
EV = \sum_{i=1}^{n} (P_i \times X_i)
$$Expected Value Context
To solve a decision tree, managers calculate the Expected Value at each chance node. EV is the long-run average value of a decision, calculated by multiplying each possible financial outcome by its probability of occurring, and summing the results.
Decision Tree: Launch vs. Don't Launch
Market Conditions
(60%)
Prob. of Failure:40%
Payoffs
$
$
$
Expected Value (EV)
Launch:$52,000
No Action:$0
Rec: Launch Product
Decision
Market
EV: $52,000
END
Success
$100,000
END
Failure
$-20,000
END
Status Quo
$0
Key Takeaways
- The rational Decision-Making Process is a logical sequence: identify the problem, establish criteria, generate alternatives, evaluate, select, implement, and finally, evaluate the outcome's effectiveness.
- Managers handle routine, structured issues with Programmed Decisions (using rules and policies) and tackle unique, complex problems with Non-Programmed Decisions (requiring judgment and custom analysis).
- Decisions are categorized by the information available: Certainty (outcomes known), Risk (probabilities known), and Uncertainty (neither known).
- Under uncertainty, managers use strategies like Maximax (optimistic) or Maximin (pessimistic) on Payoff Matrices. Under risk, Decision Trees and the Expected Value (EV) calculation provide a statistical basis for choosing the most profitable long-term path.