InteractiveMap of Operations Research
Back to Modern OR Practice
TheoryApplied06.11
Modern OR Practice

Behavioral OR & Human Decisions

Account for how people actually use, resist, and adapt to models.

Overview

Behavioral OR & Human Decisions focuses on account for how people actually use, resist, and adapt to models. In the map of OR, it connects Bias, Trust, Incentives to decisions that must be modeled, solved, explained, and revised as evidence changes.

Behavioral OR studies judgment, incentives, trust, cognitive bias, strategic response, and organizational adoption when analytical recommendations meet human decision-makers. The practical use case is clearest in Policy design, Workforce planning, Healthcare, Pricing, Operations change, where the method helps turn constraints and tradeoffs into a decision artifact someone can inspect.

Core ideas

Bias

Bias is a core checkpoint for Behavioral OR & Human Decisions: define it concretely, attach units or rules where possible, and test whether stakeholders interpret it the same way.

Trust

Trust is a core checkpoint for Behavioral OR & Human Decisions: define it concretely, attach units or rules where possible, and test whether stakeholders interpret it the same way.

Incentives

Incentives is a core checkpoint for Behavioral OR & Human Decisions: define it concretely, attach units or rules where possible, and test whether stakeholders interpret it the same way.

Adoption

Adoption is a core checkpoint for Behavioral OR & Human Decisions: define it concretely, attach units or rules where possible, and test whether stakeholders interpret it the same way.

Human-in-the-loop decisions

Human-in-the-loop decisions is a core checkpoint for Behavioral OR & Human Decisions: define it concretely, attach units or rules where possible, and test whether stakeholders interpret it the same way.

How to use it

  1. 1Start with Policy design: write the decision, time horizon, actors, and objective in operational language.
  2. 2Translate the problem into Bias, Trust, and Incentives; define units and data sources for each one.
  3. 3Build a small instance of Behavioral OR & Human Decisions that can be solved or simulated by hand inspection before using full production data.
  4. 4Compare the recommendation against a baseline policy, not just against mathematical optimality.
  5. 5Document assumptions, sensitivity results, and the conditions under which the recommendation should be revisited.

Applications

Policy designWorkforce planningHealthcarePricingOperations change
  • Policy design: compare feasible policies, quantify the operating tradeoffs, and make the assumptions behind the recommendation visible.
  • Workforce planning: compare feasible policies, quantify the operating tradeoffs, and make the assumptions behind the recommendation visible.
  • Healthcare: compare feasible policies, quantify the operating tradeoffs, and make the assumptions behind the recommendation visible.
  • Pricing: compare feasible policies, quantify the operating tradeoffs, and make the assumptions behind the recommendation visible.
  • Operations change: compare feasible policies, quantify the operating tradeoffs, and make the assumptions behind the recommendation visible.

Common pitfalls

  • Applying Behavioral OR & Human Decisions because the label sounds appropriate while leaving the actual decision boundary vague.
  • Treating Bias as a technical detail instead of a modeling choice that affects the recommendation.
  • Reporting one answer without showing sensitivity to demand, capacity, costs, or behavioral assumptions.
  • Ignoring implementation details such as data quality, explainability, ownership, and how users will override bad recommendations.

Resources