Attribution Theory of Leadership: How Followers Judge Leaders

By Tara Minh · Updated Oct 10, 2026

The attribution theory of leadership says that people explain outcomes by assigning causes, and those explanations shape how they judge and treat each other. Leaders decide whether a subordinate's poor result came from the person or the situation. Followers decide how much credit or blame a leader deserves for what the organization achieved.

That makes it a theory about judgment, not about traits or styles. It asks a plainer question: when something goes well or badly, who do we say caused it, and what do we do next because of that answer?

Where the theory comes from

Attribution theory started in social psychology, not management. Fritz Heider laid the groundwork in his 1958 book The Psychology of Interpersonal Relations, published by Wiley. Researchers writing in the Journal of Organizational Behavior summarize his premise this way: people have an innate desire to understand the causes of important outcomes, and the explanations they land on influence how they respond. Typical explanations are ability, effort, the nature of the task, and luck.

Harold Kelley turned that idea into something testable. In a 1973 paper, "The processes of causal attribution" in American Psychologist, he described how people use covariation information to decide whether a behavior points to the person or to the circumstances. The three cues are consensus (do others behave the same way?), distinctiveness (does this person act this way in other situations?), and consistency (does this person act this way over time?).

Leadership researchers picked the idea up in the late 1970s and split it in two directions:

• Leader as attributor. Stephen Green and Terence Mitchell's 1979 paper "Attributional processes of leaders in leader-member interactions", published in Organizational Behavior and Human Performance, treated the supervisor as an information processor who works out the cause of a subordinate's behavior and then acts on that conclusion.
• Follower as attributor. James Meindl, Sanford Ehrlich and Janet Dukerich's 1985 paper "The Romance of Leadership" in Administrative Science Quarterly argued that observers tend to credit or blame leaders for organizational outcomes, whatever the leaders actually did.

Key Facts

Key Facts

• Fritz Heider's The Psychology of Interpersonal Relations (Wiley, 1958) is the starting point for attribution theory.
• Harold Kelley's covariation model (1973) uses consensus, distinctiveness and consistency to separate person causes from situation causes.
• Green and Mitchell (1979) applied attribution to supervisors judging subordinates; later studies by Ashkanasy and colleagues essentially validated the model, per a review in the Journal of Organizational Behavior.
• Meindl, Ehrlich and Dukerich (1985) named the "romance of leadership": a romanticized, heroic view of leaders as the main force behind organizational events.
• The fundamental attribution error, a term usually credited to Lee Ross (1977), is the tendency to overweight personal factors and underweight situational ones.
• It is a theory of perception and judgment. It doesn't prescribe a leadership style.

How leaders explain their people's performance

This is the direction that matters most for managers, because it drives what you do on a Monday morning.

According to a Sage encyclopedia entry on the attribution model of leadership, leaders judge whether poor performance reflects the employee or the situation using the same three cues Kelley described. An employee who consistently struggles with a task that others handle well (low consensus, high consistency, low distinctiveness) points toward an internal cause such as ability. Because that analysis takes effort, leaders often shortcut to four causes: ability (internal, stable), effort (internal, unstable), task difficulty (external, stable), and luck (external, unstable).

The consequences follow directly. The same entry says internal attributions lead leaders to aim corrective action at the employee and to punish poor performance more often than external attributions do. Stable causes make leaders expect the problem to continue. And effort attributions provoke particularly strong reactions, because effort feels controllable.

Here's a generic example. A sales manager sees a rep miss quota three quarters in a row. If she concludes "low effort," she'll push for activity numbers and a performance plan. If she concludes "the territory was cut in half and the product changed," she'll look at coverage and enablement. Same data, different story, very different intervention. Neither story is automatically right. The point of the theory is that the manager should know which one she's telling.

Why the leader's story is often wrong

Two well-known biases push leaders toward the person-blaming story.

The fundamental attribution error. Ross, in a 1977 chapter in Advances in Experimental Social Psychology, described a general tendency to overestimate the importance of personal or dispositional factors relative to environmental ones. Sabini, Siepmann and Stein quote that passage and note it's the source of the term. They also argue the classic evidence for the error is weaker than its reputation, so treat it as a strong tendency to watch for, not a law.

Self-serving bias. People often credit themselves for success and point to outside factors for failure. Miller and Ross's 1975 paper "Self-serving biases in the attribution of causality: Fact or fiction?" in Psychological Bulletin is the classic examination of whether that pattern is real and why it happens. The practical version: in a review conversation, the manager may see the employee's miss as the employee's fault, while the employee sees it as the territory's fault. Both can be partly right, and both are probably leaning toward the explanation that protects them.

How followers explain their leader's results

The follower direction runs the other way. Instead of one manager judging one report, many people judge a leader from a distance, usually from outcomes they can see: revenue, a product launch, a layoff.

Meindl and colleagues called the resulting habit the romance of leadership. Per that overview, they argued that observers and participants in organizations may hold highly romanticized, heroic views of leadership, seeing it as the premier force behind organizational events. The same entry describes it as an attractive, if biased, account of success and failure that reflects faith in the efficacy of formal leaders.

Two things follow in practice:

• Credit and blame travel upward. A strong quarter gets read as proof of a great CEO. A weak one gets read as a leadership failure, even when the market, a competitor, or a supply problem did most of the damage.
• Leadership gets inferred from results. When people see good outcomes, they tend to conclude the leader must have been effective. That reasoning is circular: you can't use the result to prove the leadership and the leadership to explain the result.

This is also why attribution theory sits awkwardly next to charismatic leadership and great man theory. Both assume leadership qualities sit in the person. Attribution theory asks how much of "the leader is great" is really in the eye of the observer.

If you're a leader, the implication is uncomfortable but useful. Followers will judge you by outcomes you only partly control, and the stories they tell about you may have little to do with your actual decisions. Being open about the role of luck and circumstances, in good quarters as well as bad, is one way to keep those stories honest. It also fits with building psychological safety, where people can discuss what really caused a result without fearing the answer.

How it compares with other leadership theories

Most theories ask "what should a leader be or do?" Attribution theory asks "how is the leader being perceived and judged?" That makes it a useful companion to the others, not a replacement.

Attribution links most naturally to leader-member exchange, since Green and Mitchell's paper is about leader-member interactions. A manager who reads a report's miss as a personal failing is likely to treat that person as an out-group member, which then shapes the next round of evidence.

How to apply attribution thinking, step by step

Step 1: Notice your first explanation

When a result surprises you, write down your instant explanation in one sentence before you act. "She isn't trying" or "The market shifted." That sentence is the attribution.

Step 2: Run the three cues

Ask Kelley's questions. Consensus: are others in the same situation getting the same result? Distinctiveness: does this person do well on other tasks? Consistency: does this keep happening, or was it a one-off? If everyone is missing, look at the situation. If only one person misses, and always, look closer at the person.

Step 3: Check the four causes

Walk through ability, effort, task difficulty and luck. Ask what evidence supports each, and what evidence would change your mind.

Step 4: Ask the person

The subordinate has information you don't. Ask for their account before you decide. If it differs from yours, that gap is the real finding.

Step 5: Match the response to the cause

If the cause is skill, train. If it's effort or motivation, find out why. If it's the task or the environment, fix the task or environment. Punishing a situation problem doesn't fix it.

Step 6: Apply the same standard to yourself and to leaders above you

When you assess a senior leader's results, ask what part came from decisions and what part from conditions. Then do the same for your own wins.

Template: attribution check worksheet for performance reviews

Copy this into your review notes before a performance conversation. Fill in the left column from facts, then the right column with your honest reading.

If the "My reading" column says "internal" everywhere and you haven't filled in the employee's account, slow down. That's the pattern the fundamental attribution error produces.

Examples by business function

These are generic scenarios, written to show the pattern.

Sales. A regional manager sees one rep underperform while the rest of the team hits target. Low consensus and high consistency point toward the rep. But if the rep inherited the weakest accounts, the cause is the territory plan, and a performance plan won't help.

Operations. A warehouse supervisor blames a night-shift lead for repeated late dispatches. Checking the cues, every night team has the same delay, which points to a system bottleneck (consensus is high). The right fix is process, not discipline.

HR and people. An HR director reads a high turnover number as proof that one department head is a poor manager. Before concluding that, she compares exit reasons across departments. If pay bands are the common thread, the cause is external to the manager.

Product. A product launch misses its target, and the team's story is "engineering was slow." Engineering's story is "requirements kept changing." Both are self-serving. A shared timeline of decisions is a better basis for the retrospective than either account.

Executive team. A board credits the CEO for a record year driven mostly by a market upswing. Next year the market turns, and the same board blames the CEO. That's the romance of leadership working in both directions.

Do's and don'ts

Limits of the theory

Attribution theory describes how judgments tend to form. It doesn't tell you which judgment is correct in a given case, and it doesn't offer a leadership style to adopt.

Critics have also pushed on how much it explains. The review in the Journal of Organizational Behavior discusses two common criticisms: that attribution is overstated as an explanation of leader behavior compared with other predictors, and that people don't run attribution processes on every event because they're mentally demanding, saving them for significant or unusual ones. The authors argue the theory is still underused in organizational research. So use it as a prompt for better questions in important moments, not as a model that predicts every decision.

Putting it into practice

Pick one upcoming performance conversation. Before it, fill in the worksheet above, including the column where you imagine the result is your own. Then start the meeting by asking for the employee's explanation, and listen to the whole thing before you offer yours.

Most leadership mistakes about people aren't about lacking a framework. They're about being sure of a story too early. This theory won't make your judgments right. It will make you more likely to catch the moment when you're about to treat a situation problem as a character flaw.