By Fatskills Exam Guides Team — the exam nerds behind 28,500+ quizzes and 2.1M practice questions across 500+ global exams.
Decision-making models explain how individuals and organizations choose between alternatives. These models matter because managers must balance speed, accuracy, and stakeholder buy-in—poor decisions can waste resources, demotivate teams, or derail strategy. For example, Netflix’s shift from DVD rentals to streaming was a high-stakes decision: a purely rational analysis (data on declining DVD sales) combined with intuitive leaps (betting on broadband growth) and bounded rationality (limited foresight about piracy or competition from Disney+).
Rational Decision-Making Model (Herbert Simon, 1947): A prescriptive model assuming decision-makers are fully informed, objective, and logical. Steps: (1) Define the problem, (2) Identify criteria, (3) Weight criteria, (4) Generate alternatives, (5) Evaluate alternatives, (6) Select the best option. Practical implication: Useful for structured problems (e.g., Amazon’s warehouse automation—data-driven cost-benefit analysis of robotics vs. human labor). Limitation: Rarely achievable in real-world complexity.
Bounded Rationality (Simon, 1957): Decision-makers satisfice (accept "good enough") due to cognitive limits, time constraints, and incomplete information. They use heuristics (mental shortcuts) to simplify choices. Practical implication: Explains why managers might pick the first viable option (e.g., Zappos’ early hiring decisions—Tony Hsieh admitted to hiring fast based on cultural fit, not exhaustive analysis). Tool: Use "pre-mortems" (imagining failure before deciding) to counter overconfidence.
Intuitive Decision Making (Klein, 1998): Unconscious, pattern-based decisions relying on expertise and tacit knowledge. Often used in high-pressure or ambiguous situations (e.g., firefighters, ER doctors). Practical implication: Effective when data is scarce or time is critical (e.g., Southwest Airlines’ rapid gate turnarounds—pilots and crews rely on intuition honed by experience). Risk: Bias if intuition isn’t grounded in real expertise (e.g., a manager promoting a "gut feeling" hire who later fails).
Prospect Theory (Kahneman & Tversky, 1979): People evaluate decisions based on gains/losses relative to a reference point, not absolute outcomes. They’re risk-averse for gains but risk-seeking for losses (e.g., preferring a sure $50 over a 50% chance of $100, but taking a 50% chance to lose $100 over a sure $50 loss). Practical implication: Framing matters—Google’s "20% time" policy (sold as a gain: "innovate freely") was more motivating than "lose 20% of your work time."
Garbage Can Model (Cohen, March, & Olsen, 1972): Decisions emerge from chaotic interactions of problems, solutions, participants, and opportunities—often in organizations with unclear goals (e.g., universities, startups). Practical implication: Explains why Twitter’s (X) chaotic product changes (e.g., removing headlines from links) seem reactive—decisions are driven by shifting priorities, not strategic planning.
Vroom-Yetton-Jago Decision Model (1973): A contingency model prescribing how much participation to use based on decision quality, team expertise, and time. Options: Autocratic (AI/AII), Consultative (CI/CII), or Group (GII). Practical implication: Patagonia’s environmental policies—Yvon Chouinard often used consultative (CI) or group (GII) decisions for sustainability initiatives to ensure buy-in.
How to choose the right decision-making model for a problem:
Unstructured (ambiguous, novel)-Intuitive or Bounded Rationality (e.g., Apple’s iPhone launch—limited market data, high uncertainty).
Evaluate time pressure:
Low-Rational Model (e.g., Walmart’s supply chain optimization).
Check for cognitive biases:
Example: Google’s "Project Aristotle" (studying team effectiveness) used data to debias intuitive assumptions about "ideal" team composition.
Determine stakeholder involvement:
Low need-Autocratic (e.g., Elon Musk’s "hardcore" work culture mandate at Twitter/X).
Pilot or prototype:
For high-risk decisions, test alternatives (e.g., Amazon’s A/B testing for website changes).
Reflect and learn:
Misconception: The rational model is always best for organizations. Correction: It’s ideal for structured problems but impractical for complex, ambiguous, or time-sensitive decisions. Example: Blockbuster’s failure—a rational analysis might have shown declining DVD rentals, but bounded rationality (ignoring streaming) and intuition (dismissing Netflix as a "niche") led to bankruptcy.
Misconception: Intuition is just guessing. Correction: Expert intuition is pattern recognition (e.g., Chesley "Sully" Sullenberger’s Hudson River landing—decades of experience enabled split-second decision-making). Novices relying on intuition, however, often fall prey to bias (e.g., a manager promoting a "charismatic" employee without performance data).
Misconception: Bounded rationality means laziness. Correction: It’s a cognitive limitation, not a choice. Example: Zappos’ holacracy experiment—Tony Hsieh’s bounded rationality (limited understanding of self-management’s complexity) led to a costly, failed reorganization.
Misconception: More data always improves decisions. Correction: Data overload can paralyze (analysis paralysis) or confirm bias. Example: Kodak’s digital camera failure—despite inventing the technology, they over-relied on film sales data and ignored market shifts.
Misconception: Group decisions are always better than individual ones. Correction: Groups can suffer from groupthink (e.g., NASA’s Challenger disaster—engineers’ concerns were suppressed) or groupshift (e.g., Reddit’s WallStreetBets—collective risk-taking led to extreme trades). Use nominal group technique (silent idea generation + voting) to mitigate.
Intuitive questions involve expertise or crisis (e.g., "A cyberattack is underway—how does the CISO respond?").
Compare and contrast:
Intuition vs. Rationality: "When should a leader trust their gut?"-High expertise + time pressure (e.g., Steve Jobs’ iPhone design—no market research, just intuition).
Avoid the "either/or" trap:
Real-world decisions often blend models. Example: Netflix’s content strategy—rational (data on viewer habits) + bounded (limited foresight on competitors) + intuitive (Reed Hastings’ bet on original content).
Link to other OB concepts:
Scenario 1: Your team is debating whether to launch a new product feature. The data is mixed—some users love it, others hate it. The CEO wants a decision by tomorrow. Which decision-making model(s) should you use, and why?
Answer: Use bounded rationality (satisfice due to time pressure) + intuitive (if the team has domain expertise). Example: Spotify’s "Discover Weekly"—limited data on user preferences led to a "good enough" algorithm tweak, refined later.
Scenario 2: A hospital administrator must decide whether to invest in a new MRI machine. The budget is tight, but patient wait times are increasing. Which model is most appropriate, and what steps should they take?
Answer: Use the rational model (structured problem, high stakes). Steps: (1) Define criteria (cost, patient outcomes, ROI), (2) Weight criteria, (3) Generate alternatives (lease vs. buy, different vendors), (4) Evaluate, (5) Decide. Example: Mayo Clinic’s data-driven equipment purchases.
Join 4M+ learners. Unlock unlimited quizzes, wrong-answer tracking, flashcards + reminders, study guides, and 1-on-1 challenges.