Self-Efficacy Theory

What is Self-Efficacy Theory/

Self-efficacy theory asks a fairly narrow question: how much does a person believe they can actually do the thing in front of them? Not whether they’re a confident person in general, and not whether they’re smart or skilled in some broad sense. Just: do they believe, right now, that they can pull off this particular task?

The theory comes from the psychologist Albert Bandura, who introduced it in a 1977 paper. His early work grew out of studying how people overcame phobias, watching what changed in someone’s behavior once they believed they could handle the thing that used to terrify them. From there the idea spread across education, sport, health, and eventually management, because belief in your own capability predicts a lot about how you perform, not just how you feel.

We need to be careful with the term from the start, because it gets confused with two other ideas. Self-efficacy is not the same as self-esteem (how much you generally value yourself as a person), and it’s not the same as actual ability. You can be highly skilled at something and still doubt you can do it under pressure, and you can be mediocre at something and still walk in believing you’ll manage fine. Self-efficacy sits specifically at the belief-about-this-task level, which is exactly what makes it useful for managers: it’s something you can actually influence, task by task, rather than trying to rewire someone’s whole personality.

Where Does Self-Efficacy Actually Come From?

Bandura identified four main sources. As you can probably guess, they don’t all carry equal weight.

Mastery Experience

This is the big one: actually doing the task and succeeding at it. Nothing convinces someone they can do a job like having already done it, even in a small way. A new sales associate who successfully talks one customer through a return builds more genuine self-efficacy from that single win than from a week of being told “you’ve got this.”

It’s also why flight and surgical training start on simulators and easy cases before anyone gets near a real emergency. Easy wins first, harder ones once the earlier ones have landed.

Watching Other People Succeed

Second is vicarious experience, watching someone else do the task, especially someone we see as similar to us. If a new hire watches an experienced colleague handle an angry customer calmly and it works, that tells the new hire something about what’s possible.

It matters who the model is, though. Watching a star performer who seems to operate on a different level doesn’t help much, because the new hire can quietly write it off as “well, they’re just naturally good at this.” Watching a peer at a similar starting point tends to work better.

What People Tell Us

Third is social persuasion, basically verbal encouragement from other people. This one is weaker than the first two, and it’s also the one managers reach for most by default, because it’s cheap and quick. “You can do this” said in passing doesn’t do a lot on its own. Specific feedback tied to something the person actually did (“the way you handled that customer’s complaint”) carries more weight, because it’s tied to real evidence rather than a generic pep talk.

How We Feel in the Moment

Fourth is our physiological and emotional state. A racing heart, sweaty palms, a dry mouth before a presentation, these get interpreted by us as evidence about whether we’re going to succeed. Someone who reads their own nerves as “I’m not ready for this” will have lower self-efficacy walking into the room than someone who reads the exact same sensations as normal pre-performance adrenaline.

This is part of why coaching around presentations often focuses on reframing nerves rather than trying to eliminate them, since eliminating them usually isn’t realistic anyway.

How Does Belief Actually Change Performance?

So why does any of this matter for how someone actually performs, rather than just how they feel walking in? A few mechanisms are worth naming.

People with higher self-efficacy for a task tend to set themselves higher goals for it. This connects directly to goal-setting theory: someone who believes they can hit a demanding target is more willing to accept one, while someone who doubts themselves will quietly negotiate it down, or avoid committing to one at all.

They also persist longer when things get difficult. A salesperson with strong self-efficacy who gets three rejections in a row is more likely to read that as “this particular batch of calls didn’t land” rather than “I’m bad at this,” and that reading determines whether they pick up the phone for the fourth call with the same energy as the first, or start to disengage.

And self-efficacy shapes how people respond to setbacks generally. Low self-efficacy after a failure tends to produce something close to learned helplessness (the belief that effort won’t change the outcome, so why bother trying as hard next time). High self-efficacy after the same failure is more likely to produce troubleshooting instead: what went wrong, what do I adjust.

What Happens When Self-Efficacy Gets It Wrong?

None of this means high self-efficacy is automatically good and low self-efficacy is automatically bad. Both can be miscalibrated, and that creates real problems for a manager.

An employee whose self-efficacy is inflated relative to their actual skill can be hard to manage. They resist coaching because, from where they sit, they don’t need it, and they take on tasks they’re not ready for without asking for help until something has already gone wrong. Because confidence often reads as competence to the people around them, at least at first, it can take a while for anyone to notice the gap.

On the other end, an employee whose self-efficacy is too low will avoid stretch assignments and undersell their own work, not because they lack the ability but because they don’t believe they have it, a common and frustrating situation for a manager to watch. The manager’s job in both cases isn’t to hand out more or less praise. It’s to close the gap between what the person believes and what’s actually true, using real evidence rather than reassurance alone.

Does This Apply to Teams as Well as Individuals?

Bandura also wrote about collective efficacy, the same idea applied to a group: does the team believe it can pull off what’s being asked of it together, not just as individuals. A team full of individually confident people can still have low collective efficacy if they don’t trust that they’ll coordinate well as a unit.

Sports teams show this constantly, a roster of talented individuals underperforming because the group doesn’t believe in itself as a group. The same thing shows up on project teams and cross-functional groups at work, and it’s worth a manager watching for separately from how any one team member is doing.

What Should a Manager Actually Do With This?

As highlighted above, mastery experience is the strongest of the four sources, which means the practical implication for a manager is mostly about sequencing. Don’t hand a new employee the hardest version of a task first and hope encouragement carries them through it.

Structure the early weeks so that early wins are genuinely achievable, then build from there. A retail chain training a new associate might start them on straightforward transactions before ever putting them in front of an angry customer with a complicated return. That isn’t coddling the new hire. It’s building a track record of real success to draw on later, when the harder situations show up.

We also need to think carefully about who we pair people with for modeling. Pairing a nervous new hire with the single best performer in the building can backfire, for the reason mentioned earlier: it’s too easy for the new hire to write off that performance as talent rather than as something learnable. A peer who is only slightly ahead of them is often a better model.

Feedback matters here too, and it needs to be specific rather than generic. “Great job today” is pleasant but does very little for someone’s self-efficacy going forward, because there’s nothing in it they can point to and repeat. Telling them exactly what they did that worked gives them something concrete to draw on next time. We also have to watch our own expectations, because these leak out in tone, in how much rope we give someone, in whether we hover or step back. An employee who senses their manager doesn’t expect much from them will often come to expect less of themselves too.

There’s a real trade-off worth sitting with as well. Stretch assignments build self-efficacy over time, but a badly timed one, given before any mastery experience has built up underneath it, can just as easily damage it, and a single bad failure early on can undo weeks of careful sequencing.

The timing of a challenge matters almost as much as the challenge itself, and that’s a judgment call based on where a specific person actually is, rather than a fixed onboarding schedule that treats every new hire the same way.


Key Points to Take Away

  1. Self-efficacy is task-specific belief in one’s own capability, not general confidence, self-esteem, or actual skill.
  2. Mastery experience (actually succeeding at the task) builds self-efficacy more reliably than encouragement alone, which is why sequencing tasks from easy to hard matters.
  3. Watching a similar peer succeed helps more than watching a star performer, because it feels achievable rather than exceptional.
  4. Specific feedback tied to real evidence builds belief better than generic praise.
  5. Both inflated and deflated self-efficacy create management problems, and the fix is closing the gap between belief and actual skill, not simply adding more praise or criticism.
  6. Collective efficacy, a team’s belief in itself as a group, is a separate thing worth watching alongside individual confidence.
Scroll to Top