Authority Bias
One-Line Definition
People tend to over-trust the judgments of authority figures or institutions.
Core Concept
It helps you identify blind spots, biases, and oversimplifications in thinking.
More specifically, Authority Bias is suitable for answering questions like: Is what I’m seeing a fact, an assumption, or a habitual practice? To make a better choice, which variable, path, or constraint should I examine first?
When to Use
- When the problem becomes complex and intuitive judgment is not reliable.
- When the team disagrees on next steps and needs a common analytical framework.
- When you need to turn abstract judgments into concrete actions, checklists, or experiments.
- When existing methods are declining in effectiveness and you need to re-examine the underlying logic.
When NOT to Use
- The problem is simple, and direct execution is more important than analysis.
- Basic facts are missing, leading to conceptual spinning without substance.
- Using a model only to justify an existing conclusion rather than help correct judgment.
- The cost is extremely high and trial-and-error is not possible, without additional verification methods.
How to Apply
- Write down the current problem: Describe the issue you want to judge or solve in one sentence.
- List existing assumptions: Distinguish facts, opinions, experiences, emotions, and default answers given by others.
- Identify key variables: Find the 1-3 factors that most influence the outcome.
- Form alternative actions: Based on key variables, propose several different approaches.
- Define a minimum verification: Use a low-cost action to test which judgment is closer to reality.
Example
Suppose a team finds that new user conversion rate has dropped. When using “Authority Bias,” instead of immediately asking a designer to change a button or a marketing person to increase budget, first break down: where users come from, what information they see, at which step they hesitate, what they lose when they give up, and whether there is a stronger alternative. After decomposition, the team may find the real problem is not insufficient traffic, but that users don’t understand what problem the product solves on the first screen. So the minimum action is not to redo the entire product, but to first test a clearer value proposition.