← Latest papers
📈 economics

Optimal Use of Preferences in Artificial Intelligence Algorithms

This paper establishes that separating preference-free training from post-processing is theoretically optimal for maximizing welfare across diverse decision problems by preserving information value, though embedding preferences directly into training can be superior when users face cognitive constraints that hinder optimal downstream decision-making.

Original authors: Joshua S. Gans

Published 2026-01-27
📖 6 min read🧠 Deep dive

Original authors: Joshua S. Gans

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are building a smart assistant to help you make important decisions, like deciding whether to approve a loan, hire a candidate, or diagnose a medical condition. The core question this paper asks is: When should you teach the AI your specific rules and preferences while you are training it, versus teaching it just the raw facts and letting you apply your rules after it gives you an answer?

The author, Joshua Gans, argues that in most cases, it is better to keep the AI "neutral" during training and apply your preferences later. Here is the breakdown using simple analogies.

The Two Approaches

1. The "Embedded" Approach (Teaching the AI your bias)
Imagine you are training a chef to make soup. You tell the chef, "I hate salt, so whenever you taste the soup, add extra pepper to compensate." You bake your specific preference (less salt, more pepper) directly into the chef's training.

  • The Risk: The chef stops learning what the soup actually tastes like. They only learn how to make "your version" of the soup. If tomorrow you decide you actually want a salty soup, this chef is useless because they never learned the true flavor profile. They have forgotten the raw truth to focus on your specific rule.

2. The "Separated" Approach (The Modular Pipeline)
Instead, you train the chef to be a master of tasting. You teach them to identify exactly how salty, sour, or sweet the soup is, without telling them what to do with that information. They give you a precise report: "This soup is 80% salty."

  • The Benefit: Once you have that accurate report, you decide what to do. If you want it less salty, you add water. If you want it spicier, you add pepper. If your tastes change next week, you don't need to retrain the chef; you just change your recipe.

The Core Discovery: Why "Neutrality" Wins

The paper uses math to prove that the Separated Approach is almost always better. Here is the logic in plain English:

The "Flattening" Effect
When you force an AI to learn your specific preferences (like "false alarms are worse than missed opportunities") during training, it changes how the AI learns. It effectively "flattens" the AI's ability to distinguish between different scenarios.

  • Analogy: Imagine a map. A good map shows clear differences between a mountain and a valley. If you tell the map-maker, "I only care about valleys, ignore mountains," the map-maker might blur the lines between the two to make the valleys look more prominent. Suddenly, the map is less useful because it can't clearly tell the difference between a high peak and a low hill anymore.
  • The Result: The AI becomes less informative. It gives you a "muddy" signal. Once the AI has lost that clarity, you can't get it back later, no matter how smart your decision rules are.

The "Option Value"
By keeping the AI neutral (training it to give you the most accurate probability possible), you preserve option value. You keep all your choices open. You can use the same AI for a strict safety policy today and a lenient efficiency policy tomorrow. If you bake the strict policy into the AI, you lose the ability to be lenient later without retraining the whole system.

When Does the "Embedded" Approach Win?

The paper admits there is one specific situation where baking your preferences into the AI is better: When the user is tired, confused, or overwhelmed.

  • The Analogy: Imagine you are a doctor. The AI gives you a complex, 50-page report with probabilities for every possible disease. You are exhausted and have 5 minutes to see the next patient. Reading and interpreting that complex report is too hard (cognitively expensive).
  • The Solution: In this case, it is better to have the AI do the hard work for you. You train the AI to say, "Give this patient the antibiotic," rather than "There is a 72% chance of infection." The AI "compresses" the information into a simple action, saving your brain power.
  • The Trade-off: You lose some precision (the AI might be slightly less accurate), but you gain speed and simplicity. If the user cannot handle the complex data, the "Embedded" approach wins.

Real-World Examples Mentioned in the Paper

The paper applies these ideas to two main areas:

  1. Standard AI Pipelines (like hiring or lending):

    • Advice: Train the AI to be a perfect "calculator" of probabilities (e.g., "This applicant has a 65% chance of success"). Do not train it to decide who to hire. Let a human or a separate rule decide who to hire based on that 65%. This allows you to change hiring rules without retraining the AI.
  2. Large Language Models (like Chatbots):

    • The Problem: We often use a technique called RLHF (Reinforcement Learning from Human Feedback) to teach AI what is "helpful" or "harmless." This is like baking the "helpful" rule directly into the AI's brain.
    • The Warning: If we bake in a specific definition of "helpful" today, the AI might become bad at being "harmless" or "truthful" tomorrow if those priorities shift. It's like training a chef to only make spicy food; they will fail if you ask for a mild dish.
    • The Fix: The paper suggests keeping the AI's base knowledge broad and neutral, and using "post-processing" (like filters or rules) to decide what to show the user. This keeps the AI flexible.

The Bottom Line

The Golden Rule:
Unless your users are too overwhelmed to understand complex data, do not bake your preferences into the training.

  • Train the AI to tell the truth (give accurate probabilities).
  • Let the humans (or simple rules) decide what to do with that truth.

This keeps your AI flexible, accurate, and ready for whatever rules or goals you might have in the future. Only "bake in" the preferences if you absolutely need to simplify the decision for a tired or confused user.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →