Blog · Behavioral Analysis Work with Yu-kai
Self-Efficacy Theory: An S-Tier Behavioral Designer’s Guide to Bandura’s Belief in Ability
Behavioral Analysis

Self-Efficacy Theory: An S-Tier Behavioral Designer’s Guide to Bandura’s Belief in Ability

Albert Bandura's Self-Efficacy Theory in plain English: the four sources of belief, the brain underneath, the critiques, and how Octalysis turns the theory into design.

Short answer: Self-efficacy is a person’s belief that they can perform a specific task, and Albert Bandura introduced it at Stanford in 1977.

It is domain-specific and task-specific: the same person can hold high self-efficacy for public speaking and low self-efficacy for programming, and each belief predicts behavior in its own domain independently.

Bandura named four sources, ranked by their power to build efficacy beliefs: mastery experiences (performing the behavior and succeeding), vicarious experiences (watching similar others succeed), verbal persuasion, and physiological and affective states.

Mastery is the strongest of the four, and physiological state is the weakest.

In 1977, a small group of adults who were terrified of snakes walked into Albert Bandura’s lab at Stanford. Some had avoided basements, gardens, even certain aisles of the zoo for decades. Bandura didn’t treat their fear with pills or analysis. He ran them through a structured sequence of tiny, successful exposures — first watching him handle a boa, then wearing gloves to touch one, then letting one slide across their lap. Within three hours of guided mastery, most of the group could do things with a snake they had sworn, the week before, were impossible. The phobia collapsed. The part that stunned Bandura was what else collapsed with it: in follow-ups six months later, those same people reported being better at public speaking, demanding raises, confronting difficult colleagues, and holding the course on diets. Curing the snake had changed their behavior in rooms the snake had never been in.

Self-Efficacy Theory is one of the frameworks catalogued in the Behavioral Framework Library, Yu-kai Chou’s curated index of the behavioral science behind world-class motivation and engagement design.

That result — now known as the generalization effect — is the reason Albert Bandura spent the rest of his career arguing that the single most consequential belief a human being carries around is not self-esteem, not optimism, not even intelligence. It is the belief, in a specific domain, that I can do this. Bandura gave that belief a name — self-efficacy — and built a forty-year research program showing that it predicts effort, persistence, career choice, academic performance, recovery from illness, athletic outcomes, and the odds that a person will even try something difficult in the first place.

I’ve spent nearly two decades designing behavioral systems through the Octalysis Framework, and in every product team I’ve worked with — from LEGO to Huawei to governments rolling out citizen services — self-efficacy is the variable that quietly decides whether your design survives contact with a real user. You can give someone every incentive the spreadsheet allows; if they don’t believe they can pull it off, they will quietly disengage and blame the interface. Bandura’s theory, stripped of the academic scaffolding, is the answer to the question every designer eventually has to ask: “why did the user, who clearly wanted this outcome, fail to even begin?”

This is the S-tier designer’s guide to Self-Efficacy Theory. I’m going to walk you through the four sources Bandura identified, the evidence base that earned him a place as one of the most-cited psychologists in history, the critiques that have accumulated since 1977, and — critically — how to translate his theory into actual product mechanics using Octalysis. If you take one idea with you, let it be this: every engagement problem is, somewhere underneath, a self-efficacy problem. Solve that, and half your design decisions write themselves.

⚡ Speed Run Notes

  • Self-Efficacy Theory (Bandura, 1977) says that a person’s belief in their ability to succeed at a specific task is the single best predictor of whether they will try, how hard they will work, and how long they will persist when it gets hard. Not global confidence.
  • Self-efficacy is built from four sources, ranked by power: mastery experiences (doing it and succeeding), vicarious experiences (watching someone like you succeed), verbal persuasion (being told credibly you can do it), and physiological/affective states (reading your own arousal — heart rate, sweat, trembling — as evidence about your ability).
  • The effect sizes are large and stable across four decades of replication. Multon, Brown, and Lent’s 1991 meta-analysis of academic performance found self-efficacy accounting for roughly 14% of variance in achievement — larger than almost any other single psychological variable.
  • Bandura’s most counterintuitive insight is that self-efficacy is domain-specific. A world-class surgeon can have catastrophic self-efficacy on a dating app.
  • Efficacy beliefs shape four things in measurable, causal sequence. Choice of activities, effort invested, persistence under difficulty, and emotional reaction to obstacles.
  • Self-efficacy is NOT the same as outcome expectations. “I can run a marathon” (efficacy) and “running a marathon will impress people” (outcome) are different beliefs.

Table of Contents

Author Credibility: Yu-kai Chou

Yu-kai Chou — creator of the Octalysis Framework

Yu-kai Chou created the Octalysis Framework after studying gamification since 2003 — years before the term entered mainstream vocabulary. As a Human-Systems Architect & Behavioral Designer, his framework has been applied by LEGO, Microsoft, Porsche, Coca-Cola, Salesforce, and MrBeast, impacting over 1.5 Billion Users.

Chou has taught the Octalysis methodology at Harvard, Stanford, Yale, Tesla, Google, BCG, and IDEO.

His work has been cited by Harvard, Stanford, MIT, Forbes, Wall Street Journal, Wired, US Department of Energy, NIST, NSF, NCBI, US Department of Education, ClinicalTrials.gov, and Google Scholar — with 3,700+ more academic publications. Explore his books here.

What Is Self-Efficacy Theory?

Self-Efficacy Theory is a social-cognitive theory developed by Canadian-American psychologist Albert Bandura, first formally articulated in his 1977 Psychological Review paper “Self-efficacy: Toward a unifying theory of behavioral change.” The theory’s central claim is that a person’s perceived ability to execute a specific course of action — not their actual ability, not their general self-esteem, not their outcome expectations — is the single strongest domain-specific predictor of whether they will initiate the action, how much effort they will sustain, and how long they will persist in the face of obstacles.

The formal definition Bandura offered in his 1986 book Social Foundations of Thought and Action is tight: “Perceived self-efficacy is defined as people’s judgments of their capabilities to organize and execute courses of action required to attain designated types of performances.” Three clauses, each load-bearing. Perceived rules out objective ability; it is the belief that matters. Organize and execute means efficacy covers both planning and doing, beyond execution. Designated types of performances is where Bandura plants his flag: self-efficacy is always about something specific, never a global trait.

That specificity is the most commonly missed aspect of the theory. When a popular-press article says “boost your self-efficacy” the way a self-help book might say “boost your confidence,” it has already misread Bandura. In his system, asking “what is this person’s self-efficacy?” is as meaningful as asking “what is this person’s temperature?” without specifying which part of the body. Bandura’s research instruments — the Children’s Self-Efficacy Scale, the Teacher Self-Efficacy Scale, the Exercise Self-Efficacy Scale — are domain-specific for a reason. A person’s self-efficacy for public speaking, for math, for quitting smoking, and for conducting difficult conversations are four different beliefs that rise and fall on different evidence.

The theory sits inside a broader framework Bandura called Social Cognitive Theory, which in turn replaced the earlier Social Learning Theory he had developed in the 1960s through the famous Bobo doll experiments. In Social Cognitive Theory, human behavior is the product of a three-way reciprocal interaction — what Bandura called triadic reciprocal determinism — between the person (their cognitions, including self-efficacy), the behavior, and the environment. Self-efficacy is the cognitive node in that triangle; it is the belief that converts environmental cues and prior behavior into future action.

Finally, a distinction most readers gloss over. Bandura insisted that efficacy expectations (can I do this?) are different from outcome expectations (if I do this, will it work?). Both matter. But they fail in different ways. A person with high outcome expectations but low efficacy says “exercise would work, I just can’t stick with it.” A person with high efficacy but low outcome expectations says “I can definitely do this, but I don’t think it will help.” Bandura argued — and a lot of subsequent evidence has supported — that efficacy is the more powerful and the more modifiable of the two. It is the one designers have real leverage over.

The Core Findings of Albert Bandura

Most treatments of Self-Efficacy Theory list the four sources and stop. That’s like saying a car runs on fuel and stopping. The theory’s real power is in the specific predictions each source generates, the order of their potency, and the feedback loops that turn small efficacy gains into compounding behavior change. Here are the six findings that actually matter.

1. Mastery Experiences Are the Most Powerful Source

In Bandura’s ranking — and every subsequent meta-analysis has replicated it — direct, successful performance of the target behavior is the most potent builder of self-efficacy. Bandura called these performance accomplishments in his 1977 paper and mastery experiences from the mid-1980s onward. The mechanism is obvious once stated: nothing persuades a person that they can do a thing like having just done it.

The engineering implication is less obvious. For a mastery experience to build efficacy, it must be non-trivial (a trivial success teaches nothing), attributed to the user’s own effort (luck and external help don’t count), and progressively more difficult over time. A tutorial that hands the user a win is not a mastery experience. A tutorial that stages five slightly harder challenges and lets the user solve each one — while making clear that they did the work — is.

2. Vicarious Experiences Work Through Similarity

Watching someone successfully perform the behavior, Bandura found, is the second most powerful builder — but only when the observer sees the model as similar to themselves. A user watching a celebrity do the task gets an inspirational buzz and little efficacy. A user watching someone who looks like them, comes from the same background, and started at the same skill level gets a direct efficacy boost.

Bandura’s 1982 research showed that similarity cues can be manipulated with surprising subtlety. Matching the model’s gender, age, or even name to the observer’s raised efficacy gains by 20-30% over a non-matched but objectively identical model. This is why modern fitness apps display testimonials by body type, why coding bootcamps feature student profiles by prior career, and why a good onboarding flow shows you progress from users with your same starting conditions, not from the “top 1%” banner that hurts more than it helps.

3. Verbal Persuasion Is the Weakest but Cheapest Source

Being told credibly that you can do something builds efficacy — weakly, but reliably, and at almost zero cost. Bandura was careful about the word credible. Persuasion from a source with expertise, a track record, and personal knowledge of the user’s context works. Generic encouragement (“you’ve got this!”) has near-zero measurable effect, and repeated empty reassurance can actively corrode efficacy because the user starts reading the pattern as social politeness.

The design lesson is brutal: the cheapest feedback is usually the least effective. A simple “great job!” after every action is noise. A specific, contextual note — “you hit that plateau most users stall on, and you pushed past it” — is signal. Signal builds efficacy; noise erodes it.

4. Physiological and Affective States Are Read

Bandura’s fourth source is the one most designers under-use. Humans read their own physiological arousal — heart rate, sweat, trembling, racing thoughts — as evidence about their efficacy. The same body state read as “I’m excited” builds efficacy; read as “I’m scared” erodes it. The interpretation — more than the sensation — is what does the work.

This insight has spawned an entire subfield called arousal reappraisal. Alison Wood Brooks’s 2014 Harvard Business School experiments showed that teaching people to label pre-performance anxiety as excitement — three words, “I am excited” — produced measurable improvements in public speaking, math performance, and karaoke scores. The body state was identical. The label changed the efficacy judgment. The efficacy judgment changed the performance.

5. Efficacy Predicts Four Downstream Behaviors

Once self-efficacy is set, Bandura showed, it shapes behavior along four specific dimensions. Choice of activities: high-efficacy users select more ambitious tasks. Effort: high-efficacy users invest more cognitive and physical resources per attempt. Persistence: high-efficacy users hold on longer when obstacles appear. Emotional reaction: high-efficacy users experience difficulty as a challenge to be solved; low-efficacy users experience the same difficulty as confirmation of their inadequacy.

Every engagement metric a product team tracks — opt-in rates, session length, retry frequency, drop-off at friction points — is a downstream manifestation of one of these four. The implication is that when an engagement metric is broken, the causal lever is usually upstream of the metric itself, in the user’s efficacy belief about the behavior the metric is measuring.

6. Collective Efficacy Scales the Individual Version

In his later career, Bandura extended the theory to groups: collective efficacy is a team’s or community’s shared belief in their joint capability to execute a course of action. Collective efficacy is not the average of individual efficacies; it is a separable construct that predicts group performance above and beyond the sum of its members.

This is why team rituals, shared progress trackers, and public commitments work. They don’t just boost individual efficacy; they build a parallel collective belief that the group, acting together, can accomplish the target. In product terms, this is the reason a leaderboard works differently from a solo progress tracker, and why a community-driven challenge produces different behavior than the same challenge run individually.

Put these six findings together and you have the complete Bandura operating system. Four sources, ranked. Four downstream behaviors. One collective extension. Every application of Self-Efficacy Theory — in clinics, classrooms, boardrooms, and product roadmaps — is a recombination of these six.

What Bandura Got Right

Self-Efficacy Theory has been tested, replicated, critiqued, and extended for almost fifty years. Most of the original claims have held. The ones that failed have failed informatively. Here are the three things Bandura got right that every design practitioner should internalize before they touch a user flow.

1. He moved the lever from “ability” to “belief”

Before 1977, the dominant assumption in behavioral science was that if you wanted a person to do a hard thing, you taught them how to do it. The model was a skills-deficit model: inability to perform equals lack of technical competence. Bandura’s contribution — shown in experiment after experiment — was that even people with the objective skill often fail to deploy it because they do not believe they can. The limiting variable was not skill. It was the belief about the skill.

This shifted the design problem. A user who fails to do something is not necessarily a user who lacks the capability. They may be a user whose efficacy belief has not caught up to their actual capability. The intervention is not more training; it is structured efficacy-building. Every modern learning system that emphasizes “confidence before complexity” — the scaffolded progression you see in Duolingo, in Khan Academy, in Codecademy — inherits this insight directly from Bandura.

2. He made efficacy measurable and modifiable

Bandura’s second contribution was methodological. He turned a vague concept — belief in one’s ability — into a measurable, modifiable variable. His team developed domain-specific self-efficacy scales (exercise, academic, parenting, smoking cessation, public speaking) that could be administered in minutes and that predicted behavior with useful precision.

The methodological rigor matters because it let subsequent researchers run interventions, measure the efficacy change, and then observe the behavior change that followed. That chain of evidence — intervention → efficacy increase → behavior change — is what separates self-efficacy from fuzzier siblings like self-esteem and self-concept, which have much weaker evidence trails. It is also the reason a design team can build an efficacy strategy, measure it with a five-item survey, and know within a sprint whether it is working.

3. He identified the four sources in the right order

The ranking of the four sources — mastery beats vicarious beats verbal beats physiological — has been tested in hundreds of follow-up studies across cultures, domains, and populations. The ordering holds. Small variations appear: vicarious beats mastery for first-time learners whose prior mastery experience base is zero; verbal persuasion does better than usual when delivered by a same-identity peer rather than an authority figure. But the broad ranking is stable.

For designers, that stability is gold. It means you can prioritize. If you have time and budget for only one efficacy intervention, engineer the mastery experience. If you have two, add the vicarious layer. Add verbal persuasion third, and build physiological reappraisal last. The theory gives you both a menu and a sequence, which is rare in behavioral science.

Where Self-Efficacy Theory Falls Apart

Forty-plus years of testing have surfaced real scars on the theory. Three of them matter enough that any serious designer should internalize them before building on Bandura’s foundation. Ignoring these is how you end up shipping a system that works for two weeks and then inexplicably stops.

Critique 1: Measurement Inconsistency Is Rampant

Bandura insisted that self-efficacy measurement be domain-specific and aligned tightly to the target behavior. In practice, a large fraction of published self-efficacy research uses general, global, or only loosely specific instruments. The consequence is that effect sizes reported in meta-analyses are a mix of well-measured domain-specific efficacy (large and reliable effects) and vaguely measured general efficacy (small and noisy effects).

Sitzmann and Ely’s 2011 meta-analysis of self-regulated learning flagged this directly: studies using domain-specific measures produced effect sizes roughly twice as large as those using general measures of the same construct. The practical implication is that when you read a claim like “self-efficacy explains 14% of performance variance,” the underlying studies may have been measuring four different things. A cautious designer reads the primary literature carefully and treats the broad meta-claims with a grain of salt.

Critique 2: The Construct Overlaps Its Neighbors

Self-efficacy, self-concept, self-esteem, perceived control, and internal locus of control are supposed to be distinct constructs. In practice, they correlate at 0.5 to 0.7 with each other, which is high enough that critics — Marsh, Martin, Cheng, and colleagues in particular — have argued that self-efficacy measures often capture generalized competence beliefs rather than the precise task-specific construct Bandura defined.

This is not a fatal objection, but it should discipline design practice. When you measure efficacy, measure it narrowly. When you intervene on efficacy, intervene narrowly. A “general self-efficacy boost” program — of the kind pitched by some corporate training vendors — either does not exist or is actually a self-esteem program under a different name. The theory’s utility comes from its specificity; the moment you blur the specificity, you blur the utility.

Critique 3: The Theory Is Demonstrably Culturally Specific

Self-Efficacy Theory was developed in the United States in the 1970s and carries individualist assumptions about agency, causality, and self. Subsequent cross-cultural research — Klassen’s 2004 review is the cleanest — found that in collectivist cultures, efficacy beliefs predict behavior less strongly than in individualist cultures, and collective efficacy predicts more strongly. The lever is still the belief; but which belief is the dominant lever depends on the cultural substrate.

The implication for international design is concrete: a feature that builds individual efficacy beautifully in a U.S. or Northern European market may underperform in East Asian, Latin American, or sub-Saharan African markets without a matching collective-efficacy scaffold. Product teams shipping globally need both rails; teams shipping locally need to audit their cultural context before deciding which rail to emphasize.

There is a fourth critique that deserves a line: the chicken-and-egg problem. If self-efficacy requires mastery experiences and mastery requires some initial self-efficacy to even attempt the behavior, how does the cycle get started? Bandura’s answer was that vicarious experience and verbal persuasion bootstrap the cycle — they build the seed efficacy that allows the first attempt, which allows the first mastery, which then runs on its own. Fair answer; still a reminder that the theory, taken alone, does not explain behavior initiation from total efficacy zero. That requires pairing with Prospect Theory’s framing, BJ Fogg’s ability reduction, or the sort of Octalysis onboarding choreography I’ll describe below.

The Brain on Self-Efficacy: The Neuroscience Underneath

Bandura built the theory on behavioral and self-report data. But the three decades of neuroscience since have given us a reasonably clear picture of what’s happening in the brain when self-efficacy rises and falls, and the picture has direct implications for what designers should and should not do.

Self-efficacy judgments recruit the medial prefrontal cortex (mPFC), particularly the ventromedial region — the same network involved in self-referential thinking, future simulation, and the integration of value and self-relevance. When a user asks themselves, consciously or not, “can I do this?” the mPFC is running the query. High-efficacy answers activate reward-prediction regions (the ventral striatum) as if anticipating a successful outcome. Low-efficacy answers activate the amygdala and insula, signaling threat and aversion to the very task the user is being asked to start.

The anterior cingulate cortex (ACC) plays a second critical role. ACC encodes effort-value judgments — how much cognitive and physical cost a person is willing to pay for an expected reward. High self-efficacy calibrates the ACC to accept higher effort costs because the expected payoff is perceived as more achievable. Low self-efficacy biases the ACC toward the default: avoid the task, because the cost is high and the perceived likelihood of success is low.

Mastery experiences produce a specific neural signature: dopaminergic reward signaling in the ventral tegmental area and nucleus accumbens, coupled with hippocampal encoding of the episodic memory. That coupling is important because it means a mastery experience doesn’t just feel good in the moment; it lays down a memory trace tagged with the reward signal, which is later retrieved the next time the user considers attempting a similar task. This is the neural substrate of what Bandura called the generalization effect — one mastery experience echoes forward in time.

Vicarious experiences activate the mirror neuron system (the inferior parietal lobule and premotor cortex) alongside the mPFC. Watching someone similar to you perform the task produces a faint motor simulation in your own brain, which feeds back into efficacy judgments the same way direct experience does — just more weakly. This is the mechanism that explains why the similarity cue matters: the mirror simulation is stronger when the observer and model share physical, demographic, or contextual features.

Verbal persuasion activates the lateral prefrontal cortex, which handles language and social inference, but — critically — does not directly produce reward signaling or motor simulation. This is why verbal persuasion is the weakest source: it reaches the cognitive-control network but never quite plugs into the reward and motor circuits that mastery and vicarious experiences do. It is real, and it is measurable; it is just not where the heavy lifting happens.

Physiological state reappraisal works through top-down modulation of the amygdala by the ventrolateral prefrontal cortex. Teaching a user to label arousal as excitement rather than threat recruits the regulatory network that dampens amygdala output and preserves cognitive capacity for the task. The user’s heart still races; the interpretation of the racing changes, and with it the efficacy judgment.

The design takeaway from the neuroscience is concrete: interventions that hit multiple neural circuits at once — mastery plus vicarious plus verbal — compound nonlinearly, because they activate the reward, motor simulation, and regulatory networks in a coordinated way. Interventions that hit only the language network, however well-intended, plateau quickly. This is why “motivational messaging” as a standalone strategy consistently underperforms; the language network alone is not where efficacy lives.

Bring this into your product, beyond your reading list.

Self-efficacy is the quiet variable behind retention curves. The Octalysis Framework is the instrument that lets you design for it deliberately — 8 Core Drives, dozens of Game Techniques, sequenced by Experience Phase.

Read the full Octalysis Framework →

Self-Efficacy Theory vs Other Theories

Self-Efficacy Theory at a glance, next to the four frameworks it most often gets confused with:

FrameworkCentral belief / variableWho coined itEfficacy-specific slot
Self-Efficacy TheoryPerceived domain-specific capabilityBandura, 1977Is the theory
Self-Determination TheoryAutonomy, competence, relatednessDeci & Ryan, 1985Competence need ≈ efficacy
Expectancy TheoryE × I × V (expectancy × instrumentality × valence)Vroom, 1964Expectancy term = efficacy
Dweck Mindset TheoryGrowth vs fixed belief about abilityDweck, 2006Growth mindset feeds efficacy
BJ Fogg B=MAPBehavior = Motivation × Ability × PromptFogg, 2009Ability axis subsumes efficacy

Self-Efficacy Theory sits inside a crowded neighborhood of motivation and behavior-change frameworks. Here’s how it stacks up against the others a designer actually has to choose between.

Self-Efficacy vs Maslow’s Hierarchy of Needs: Maslow describes what humans want; Bandura describes whether they believe they can get it. Maslow is the destination map; self-efficacy is the fuel gauge for the journey. A user can sit atop Maslow’s esteem level and still have zero self-efficacy for a specific esteem-building behavior, which is why Maslow-only design feels grand but inert. The two are complementary, never competing.

Self-Efficacy vs Self-Determination Theory (SDT): SDT’s three innate needs — autonomy, competence, relatedness — include competence, which overlaps heavily with self-efficacy. The difference is scope and grain. SDT treats competence as a basic psychological need that, when met, produces intrinsic motivation across domains. Self-Efficacy Theory drills into the specific belief-building mechanics within one domain. Use SDT to decide whether you are feeding the right psychological needs; use Self-Efficacy Theory to engineer the exact sequence that builds competence beliefs for a specific behavior.

Self-Efficacy vs BJ Fogg’s Behavior Model (B=MAP): Fogg’s model says behavior happens when motivation, ability, and a prompt converge. Self-efficacy is an input into Fogg’s ability variable — a user’s perceived ability, which for Fogg’s purposes is often more important than their objective ability. Fogg’s practical advice to reduce friction is operationally equivalent to raising perceived ability, which is operationally equivalent to building momentary self-efficacy. The two frameworks are compatible; Fogg is crisper as a checklist, Bandura is deeper as a theory of the underlying belief.

Self-Efficacy vs Dweck’s Growth Mindset: Dweck’s construct is about beliefs regarding the malleability of ability (“I can improve”), while Bandura’s is about beliefs regarding current capability (“I can do this now”). They are related but distinct. A growth mindset makes self-efficacy more responsive to feedback and mastery experiences; a fixed mindset makes self-efficacy brittle and context-dependent. In practice, you want both: a growth mindset as the receptivity layer and self-efficacy as the action layer.

Self-Efficacy vs Outcome Expectations: This is Bandura’s own distinction and it is the one most designers collapse in practice. Efficacy is “can I?” and outcome is “will it work?” A user can rate a feature 10/10 on outcome (“this would change my life”) and 2/10 on efficacy (“I can’t pull it off”). They will not engage. Most conversion-rate experiments that fail are failures of efficacy despite glowing outcome surveys; “it’s a great idea, I just can’t” is a signal worth taking seriously.

Self-Efficacy vs the Octalysis Framework: This is the comparison most of my readers care about. Octalysis is the eight-dimensional motivation map that tells you why the user would engage at all. Self-Efficacy Theory is the precision instrument inside Core Drive 2 (Development & Accomplishment) that tells you whether the user will believe they can make the engagement pay off. Every Octalysis-designed system uses self-efficacy implicitly; the systems that last use it explicitly, engineering mastery moments, peer progress, credible feedback, and reframed arousal into the architecture. That’s what I’ll unpack below.

Self-Efficacy in the Real World: Four Domains

Self-Efficacy Theory’s real value shows up when you see the same four sources applied across wildly different contexts. I’ll walk through four — education, healthcare, workplace, and consumer product — because each domain tells you something different about what self-efficacy can and cannot do.

Education: The Multon-Brown-Lent Meta-Analysis Era

In 1991, Karen Multon, Steven Brown, and Robert Lent published what is still the most-cited meta-analysis in the self-efficacy literature. Across 36 studies, academic self-efficacy correlated with academic performance at r = 0.38 and with academic persistence at r = 0.34. The effect was largest for low-achieving and older students — the groups where the belief gap between “I can learn this” and “I can’t” was widest. For these students, the belief was the bottleneck, more than the material.

Modern edtech runs on this finding whether or not product teams name it. Khan Academy’s mastery-based progression, Duolingo’s streak-and-level structure, IXL’s question-by-question adaptive difficulty — all are attempts to engineer the four sources into a learning loop. The designs that work put mastery first (short, non-trivial wins), vicarious second (peer leaderboards with similar-skill comparisons), verbal third (specific, context-aware feedback), and physiological fourth (calm UX, reduced test anxiety through low-stakes retry loops).

The education lesson for designers outside the sector: every product that asks the user to learn something new — a new tool, a new workflow, a new framework — is subject to the same constraint. Efficacy is the ceiling on effort, effort is the ceiling on outcome, and mastery-first architecture is the most reliable way to raise the ceiling.

Healthcare: From Bandura’s Snake Phobia to Chronic Disease Management

Self-efficacy is arguably the single most validated variable in health-behavior research. A 2010 meta-analysis by Ashford, Edmunds, and French covering physical activity interventions found self-efficacy changes mediated nearly all intervention effects on actual exercise behavior. A 2015 meta-analysis on diabetes self-management found self-efficacy interventions produced HbA1c reductions equivalent to adding a moderate medication dose. In smoking cessation, self-efficacy at quit day is among the strongest predictors of long-term abstinence — stronger than nicotine dependence severity, stronger than social support.

The practical healthcare lesson is that chronic conditions are almost always efficacy conditions in disguise. Patients know they should take their medication, eat better, move more, monitor their symptoms. What they don’t always believe is that they can. Interventions that build efficacy — structured self-management programs like the Stanford Chronic Disease Self-Management Program, peer-led diabetes education, mastery-based exercise progression in cardiac rehab — outperform information-only interventions by a factor of two or more.

Workplace: Stajkovic & Luthans and the Productivity Link

In 1998, Alexander Stajkovic and Fred Luthans published a meta-analysis of 114 workplace studies covering 21,616 subjects. Self-efficacy correlated with work-related performance at a weighted average of r = 0.38, translating to a performance improvement of about 28% — larger than the effects of goal-setting, job satisfaction, organizational commitment, or most leadership interventions.

The workplace design implication is that efficacy-building is the highest-leverage activity a manager can run. Specifically: giving employees early, progressively harder wins that they clearly attribute to themselves (mastery); pairing newer employees with same-level peers who have just succeeded at a similar task (vicarious); providing credible, specific, context-aware feedback rather than generic praise (verbal); and building a workplace rhythm that frames stress as challenge rather than threat (physiological). Every modern high-performing team I’ve advised does at least three of the four, whether or not they would name them as Bandura’s sources.

Consumer Product: Efficacy-First Onboarding

The fourth domain is where I spend most of my advisory time. Every onboarding flow is an efficacy-building sequence or it is a churn machine. The teams that treat it as the former win.

Examples abound. Duolingo’s first lesson is deliberately ten seconds long and un-failable; that is a mastery experience by design. Headspace’s first meditation is three minutes and concludes with a specific verbal cue — “notice that you just did it” — that builds the attribution-to-self that mastery requires. Strava’s onboarding shows users comparable-pace runners on the same segment the new user just completed; that is the vicarious source, executed well. Apple’s Fitness rings, once closed for the day, use a celebratory animation that spikes the reward-signal circuit and reinforces the mastery attribution.

The cautionary note: efficacy-building onboarding is easy to fake and hard to do well. A tutorial that lets the user win by clicking a highlighted button is not mastery; it is theater, and users parse it accurately within a few sessions. Mastery requires actual challenge. Good onboarding is the narrow band where the first task is hard enough to be real, easy enough to be survivable, and framed clearly enough that the user attributes the win to their own action.

The Elephant in the Room: The Ethical Weight of Efficacy Design

You cannot teach Self-Efficacy Theory honestly without acknowledging its shadow. The same four sources that build genuine, lasting belief can be weaponized — and have been — to manufacture false confidence in the service of the designer’s goals rather than the user’s. The line between the White-Hat and Black-Hat versions is thinner than most designers admit.

The classic failure mode is the sandbox mastery experience — an onboarding task that is technically non-trivial but has been engineered so the user cannot lose. Day-trading apps and certain crypto platforms have built entire business models on this pattern. The user wins small, attributes the win to their own skill, builds efficacy for a behavior they have not actually mastered, and then deploys that manufactured efficacy against real stakes where they promptly lose money. The four-source ladder was executed faithfully. The mastery was false. The efficacy gain was real, and in a measurable number of cases, financially catastrophic.

The second failure mode is vicarious misrepresentation — showing the user testimonials from “people like them” where the similarity is stage-managed and the success stories are filtered for survivors. The fitness industry’s before-and-after photos are the obvious example. The vicarious mechanism fires; the efficacy rises; the base rate of success in the actual user population is much lower than the testimonial stream implies.

The third failure mode, and in some ways the most insidious, is verbal persuasion at scale. A system that tells every user “great job!” after every action degrades feedback into noise, as discussed earlier. A system that tells every user specifically why they did better than expected — when they did not — crosses into manipulation. Algorithmic recommendation systems have been caught doing this; engagement-optimized feedback loops that discover, through A/B testing, that inflated praise extends session length will deploy it, unless an ethical review catches it first.

The dividing line I teach is the transfer test. If the efficacy built inside your system transfers outward — if the user, on reflection six months later, is demonstrably more capable in the target domain, well beyond your product — your efficacy design is White Hat. If the efficacy evaporates when the user leaves your platform, or if it turns out to have been specific to sandbox conditions, you have built a manufactured-confidence machine, and regulators, journalists, and eventually the user base will catch it. The Octalysis ethical frame is the same here as it is everywhere: short-term engagement through manufactured belief will always give way to long-term resentment. Build real efficacy or don’t build efficacy at all.

How to Apply Self-Efficacy with the Octalysis Framework

This is where the theory becomes architecture. Self-Efficacy Theory gives you the four sources. The Octalysis Framework tells you where each source lives inside the motivation map, which Core Drive each one triggers, and how to sequence them across the four Experience Phases. Without Octalysis, Bandura’s theory is a checklist. With Octalysis, it is an engineering spec.

Octalysis Framework with Game Techniques around each Core Drive — Yu-kai Chou

The eight Core Drives of Octalysis are the human motivators every sustainable behavior rides on. Core Drive 1 (Epic Meaning & Calling), Core Drive 2 (Development & Accomplishment), Core Drive 3 (Empowerment of Creativity & Feedback), and Core Drive 5 (Social Influence & Relatedness) are the White-Hat drives — they produce sustained, endorsed engagement. Core Drive 6 (Scarcity & Impatience), Core Drive 7 (Unpredictability & Curiosity), and Core Drive 8 (Loss & Avoidance) are Black Hat — they drive behavior through urgency and fear. Core Drive 4 (Ownership & Possession) straddles the line.

Self-efficacy sits at the heart of Core Drive 2 (Development & Accomplishment). In fact, the cleanest way to say what CD2 is in operational terms is this: CD2 is the Core Drive that fires when the user believes they are making measurable progress toward meaningful mastery. Without self-efficacy, CD2 never activates. With it, CD2 does most of the heavy lifting in any White-Hat system, and the other Core Drives compound on top of it.

Here is the mapping from Bandura’s four sources to the eight Core Drives that most design teams miss:

  • Mastery Experiences → CD2 (Development & Accomplishment) primary, CD3 (Empowerment of Creativity & Feedback) secondary. Every mastery experience is a CD2 event. When the mastery also required the user to make a meaningful choice — not just click a forced-path tutorial — it also fires CD3. The design pattern is obvious once you see it: scaffolded challenge (CD2) with open-ended solution paths (CD3) is the densest efficacy-building architecture humans have ever built.
  • Vicarious Experiences → CD5 (Social Influence & Relatedness) primary, CD2 secondary. Seeing a similar peer succeed is a CD5 social-proof event that cascades directly into a CD2 efficacy judgment. Leaderboards, community feeds, and “people like you” testimonials are the delivery mechanisms. The Octalysis insight is that these mechanisms only work when the similarity cue is tight — loose similarity triggers CD5 weakly and CD2 almost not at all.
  • Verbal Persuasion → CD3 (Empowerment of Creativity & Feedback) primary. Credible, specific, context-aware feedback is a CD3 event. Generic “great job” messages are not. The Octalysis Game Technique for this is Instant Feedback (GT#71) done with enough precision that the user reads the feedback as evidence about their own capability, rather than as system politeness.
  • Physiological State Reappraisal → CD1 (Epic Meaning & Calling) primary, CD2 secondary. Reframing arousal as excitement rather than threat is almost always a CD1 move — the user’s body-state interpretation rides on the story they are telling themselves about why the task matters. When the story is epic enough (CD1), the body’s racing heart reads as excitement. When the story is transactional, the same racing heart reads as anxiety.

The design rule that falls out of this mapping is the one I teach in every Octalysis workshop: efficacy is built in CD2 and deployed everywhere else. If you are running a CD5 social feature, it only builds efficacy if the similarity cue is tight. If you are running a CD3 feedback mechanic, it only builds efficacy if the feedback is specific and credible. If you are running a CD1 meaning-making intervention, it only builds efficacy if it reframes the user’s physiological state in the process. Every Core Drive is a potential efficacy builder or a potential efficacy destroyer, and the difference is whether the Bandura mechanism has been respected in the implementation details.

Which Octalysis Game Techniques actually move efficacy

The Core Drive map tells you which motivation channel each Bandura source fires. The Game Technique map tells you which concrete mechanic, inside that channel, actually moves the efficacy needle — and which neighbor mechanics, living under the same Core Drive, hurt efficacy when mis-deployed. Fifteen years of Octalysis field work keep pointing to the same short list.

  • Mastery → CD2: First Major Win State and Step-by-Step Onboarding are the two Game Techniques that build efficacy fastest. Badges on their own usually fail — badges awarded for showing up produce weak mastery evidence and can even lower efficacy by signalling that the domain is trivial. Pair badges with a visible difficulty curve or drop them.
  • Vicarious → CD5: Similar-Peer Leaderboards (with a similarity filter) and Mentorship / Protégé pairing build efficacy. Global leaderboards without a similarity slice are the classic efficacy-killer — the novice compares against the outlier and concludes the domain is not for them.
  • Verbal → CD3: Empowering Feedback tied to a specific visible effort builds efficacy. Generic praise notifications (“Great job!”) do not — Bandura specifically warned that verbal persuasion unlinked from credible evidence backfires.
  • Physiological / affective → CD1: Narrative Reappraisal and Calm-Down Cadence techniques move the Brooks (2014) “get excited” reappraisal into product form. The wrong move is Urgency Timers inside high-stakes first-use flows — they push pre-performance arousal in the exact direction that lowers efficacy.

Read across the bullets and the pattern is consistent: same Core Drive, opposite effects on efficacy depending on which Game Technique you choose. Efficacy design is a Game Technique problem more than a Core Drive one.

In the Octalysis Level 2 framework — the one that maps motivation across the four Experience Phases (Discovery, Onboarding, Scaffolding, Endgame) — self-efficacy work is heaviest in Onboarding and Scaffolding. Onboarding must deliver the first mastery experience within the first session, or Discovery momentum decays. Scaffolding is where the vicarious and verbal sources do their deepest compounding, as users accumulate credible evidence — from their own wins and from peers — that the harder challenges ahead are within reach. By Endgame, efficacy should be so well established that the user’s behavior is carried by intrinsic motivation (CD1, CD3, CD5); continuing to push efficacy work at that stage reads as patronizing.

Practical Steps to Apply Self-Efficacy Theory

Everything above is theory. Here’s the playbook I walk product teams, coaches, and education designers through when they bring a real behavior-change problem and ask for the self-efficacy version of the answer.

Step 1: Name the target behavior in one concrete sentence

Not “engagement.” Not “habit formation.” “By the end of week one, the user has completed three 10-minute guided meditations without skipping the end-of-session reflection.” “By the end of month three, the employee has submitted at least one proposal for a stretch project.” The target sentence is what determines which efficacy you need to build. If you cannot name the behavior in fewer than twenty words, the efficacy intervention has nowhere to land.

Step 2: Identify the current efficacy belief, explicitly

Ask five representative users, in plain language, to rate from 1 to 10 how confident they are that they could complete the target behavior right now, and — critically — ask them why. The “why” is where the design decisions live. Users who rate themselves low because they lack skill need different interventions than users who rate themselves low because they don’t believe their environment will let them succeed. The theory’s distinction between efficacy and outcome expectations matters here: make sure you are measuring efficacy, never outcome belief, in the five-user conversation.

Want the scale template? The ten-item domain-specific efficacy scale we use with client teams lives in the Octalysis Prime workbook — pair it with the eight Core Drives to know where to intervene first.

Step 3: Engineer the first mastery experience in onboarding

Bandura’s ranking says mastery is the top source, so lead with it. The onboarding task should be non-trivial (hard enough that completing it means something), attributable to user effort (not a forced-path click-through), and clearly framed as a success when completed. Most onboarding flows fail this test — they are demos or tutorials, never mastery sequences. A real mastery onboarding ends with the user thinking “I just did that, and I was a little surprised I could.”

Step 4: Add a vicarious layer with tight similarity

Once the first mastery fires, introduce peer evidence. The peers must feel like the user. Match on whatever similarity axis your audience actually uses for identification — skill level, demographic, starting point. Loose similarity (“other users like this”) underperforms tight similarity (“users who started at your skill level and completed their first month”) by a factor of two to three in most A/B tests I’ve seen run.

Step 5: Build credible verbal feedback

Verbal persuasion is the weakest source, but it is the cheapest to deploy well. The design bar is specificity and credibility. Specificity: feedback references what the user actually did, never generic encouragement. Credibility: the feedback source has demonstrated expertise or context-awareness. An automated message that reads “you just held your pace through the segment where 73% of runners slow down” meets both bars. A message that reads “great run!” meets neither.

Step 6: Design for physiological reappraisal

In any task involving visible performance (public speaking, competitive gaming, sales calls, athletic performance, test-taking), build a pre-task prompt that reframes arousal as excitement. The intervention can be as simple as a one-sentence card — “label what you’re feeling as excitement rather than anxiety” — surfaced in the thirty seconds before the high-arousal moment. The effect sizes in the published literature are small but reliable, and the cost to implement is near zero.

Step 7: Sequence by Experience Phase, rather than a flat roadmap

Onboarding gets mastery (CD2). Early Scaffolding gets vicarious evidence (CD5) and verbal feedback (CD3). Mid-Scaffolding adds physiological reappraisal (CD1). Endgame releases the efficacy scaffolding and lets intrinsic motivation carry the load. A roadmap that tries to deploy all four sources at the same intensity across all phases will feel heavy-handed; a roadmap that sequences them by phase will feel, to the user, like the system is growing up with them.

Step 8: Measure efficacy over behavior

Most product teams measure the downstream behavior — completion rates, session length, retention — and stop there. The efficacy-aware team also measures the belief, typically via a two-item domain-specific survey at onboarding and again at 30 days. If the behavior is improving without efficacy improving, your gains are probably fragile. If efficacy is rising ahead of behavior, you are early in a compounding curve and the behavior will follow. The two-item survey is the leading indicator that most teams never track.

Closing Thoughts: The Quiet Variable Behind Every Retention Curve

If you have read this far, you know more about Self-Efficacy Theory than almost every product manager, coach, and educator who will cite Bandura this year. You know the four sources in the right order — mastery, vicarious, verbal, physiological. You know the four downstream behaviors — choice, effort, persistence, emotional reaction. You know the three serious critiques — measurement inconsistency, construct overlap, and cultural specificity. You know how to map each of Bandura’s sources onto Octalysis Core Drives and which Experience Phase each source belongs in. That’s enough scaffolding to redesign most onboarding flows, chronic-behavior-change programs, and learning systems with evidence behind the decisions.

The last lesson is the one that takes the longest to internalize. Self-efficacy is the quiet variable. It almost never shows up in your product analytics because no dashboard measures it directly. It shows up in everything downstream of itself — completion rates, retention curves, feature adoption, churn — which is why product teams spend years optimizing symptoms without ever moving the root cause. The team that learns to measure efficacy, intervene on it, and sequence the four sources across the Experience Phases gets to watch the downstream metrics move in ways that feel almost unfair compared to teams stuck optimizing surface features.

Bandura’s real contribution was not the four sources. They existed before him, scattered across coaching manuals, religious practice, military training, and every teacher who ever got a struggling student over a threshold. His contribution was to measure them, rank them, prove they were causal, and give designers the vocabulary to engineer them on purpose. Four decades later, that vocabulary is still the most reliable lever we have for turning a user who wants a different future into a user who does the work to get there. Use it carefully. Build real mastery. And remember that the only efficacy worth engineering is the kind that survives leaving your product.

Frequently Asked Questions About Self-Efficacy Theory

What is self-efficacy in simple terms?

Self-efficacy is a person’s belief in their ability to successfully perform a specific task or behavior. It is not general confidence or self-esteem; it is domain-specific and task-specific. A person can have high self-efficacy for public speaking and low self-efficacy for programming, and those two beliefs will predict behavior in each domain independently. Albert Bandura introduced the concept in his 1977 paper “Self-efficacy: Toward a unifying theory of behavioral change.”

Who created Self-Efficacy Theory?

Self-Efficacy Theory was developed by Canadian-American psychologist Albert Bandura, a professor at Stanford University who spent most of his career there. He introduced the concept formally in 1977 and expanded it as part of his broader Social Cognitive Theory throughout the 1980s and 1990s. Bandura is one of the most-cited psychologists in history and was ranked the fourth most-eminent psychologist of the 20th century in a 2002 review of the field.

What are the four sources of self-efficacy?

Bandura identified four sources, ranked by their power to build efficacy beliefs: (1) mastery experiences — directly performing the behavior and succeeding; (2) vicarious experiences — watching similar others succeed; (3) verbal persuasion — being told credibly that you can do it; and (4) physiological and affective states — how you interpret your own bodily arousal. Mastery is the strongest source; physiological reappraisal is the weakest, but each contributes and they compound when deployed together.

Is self-efficacy the same as self-confidence?

No. Self-confidence is a broad, trait-like sense of general competence, while self-efficacy is a specific, task-bound belief. A person can be highly self-confident in general and still have near-zero self-efficacy for a specific new task. Bandura was explicit that self-efficacy’s power comes from its specificity — global measures of confidence are much weaker predictors of behavior than domain-specific efficacy measures.

Why is self-efficacy important in education?

Meta-analyses since Multon, Brown, and Lent’s 1991 synthesis have consistently shown that academic self-efficacy accounts for roughly 14% of the variance in academic achievement, which is larger than the effect of almost any other psychological variable. The effect is especially strong for low-achieving and older students, where the belief gap is often the bottleneck. Modern mastery-based learning systems like Khan Academy, Duolingo, and IXL are structured to build self-efficacy as a core design principle.

What is collective efficacy?

Collective efficacy is a group’s shared belief in their joint capability to execute a course of action. Bandura extended the theory to groups in his later career, showing that collective efficacy predicts team, organizational, and community outcomes above and beyond what individual efficacy alone predicts. It is especially important in collectivist cultures, where group-level beliefs often outweigh individual beliefs in predicting behavior.

What is the difference between self-efficacy and outcome expectations?

Efficacy expectations are “can I do this?” judgments. Outcome expectations are “if I do this, will it work?” judgments. Bandura insisted on keeping them separate because they fail in different ways. A user can believe a behavior will work yet doubt their ability to pull it off (high outcome, low efficacy) or believe they can do the behavior but doubt it will matter (high efficacy, low outcome). Designing for one without the other is one of the most common reasons behavior-change programs fail.

How does self-efficacy relate to Octalysis?

Self-efficacy is the trigger mechanism for Core Drive 2 (Development & Accomplishment) in the Octalysis Framework. Without self-efficacy, CD2 never activates, and the broader White-Hat engagement loop cannot sustain itself. Each of Bandura’s four sources maps onto specific Core Drives: mastery experiences to CD2 and CD3, vicarious experiences to CD5 and CD2, verbal persuasion to CD3, and physiological reappraisal to CD1 and CD2. Using Octalysis as the architecture and self-efficacy as the precision instrument gives designers a complete system.

Can self-efficacy be trained in adults?

Yes, and the evidence is strong. Bandura’s original snake-phobia intervention produced durable efficacy gains within hours, and those gains generalized to unrelated domains six months later. Workplace, healthcare, and educational interventions have all shown measurable efficacy gains from structured programs that deploy the four sources. The practical constraint is that efficacy is domain-specific; training needs to target the behavior you care about, more than a general “confidence” construct.

What are the limits of Self-Efficacy Theory?

Three serious limits have emerged in the literature. First, measurement inconsistency — studies using domain-specific efficacy measures produce much larger effects than those using global measures, which inflates noise in the broader literature. Second, construct overlap — self-efficacy correlates 0.5 to 0.7 with self-concept, self-esteem, and perceived control, raising concerns about whether it is always measuring what Bandura defined. Third, cultural specificity — the theory predicts behavior more strongly in individualist than collectivist cultures, so international applications need a collective-efficacy layer as well.

Design for efficacy on purpose.

If Bandura’s four sources are the science, Octalysis is the blueprint. Actionable Gamification is the book that connects them — the Core Drives, the Game Techniques, the Experience Phases — with the field examples that make them operational. This is the book Microsoft, LEGO, and the government of Ukraine have on their behavioral-design shelf.

Get the book → Or explore the framework

References

  1. Bandura, A. (1977). Self-efficacy: Toward a unifying theory of behavioral change. Psychological Review, 84(2), 191-215.
  2. Bandura, A. (1986). Social Foundations of Thought and Action: A Social Cognitive Theory. Prentice-Hall.
  3. Bandura, A. (1997). Self-efficacy: The Exercise of Control. W. H. Freeman.
  4. Bandura, A., & Adams, N. E. (1977). Analysis of self-efficacy theory of behavioral change. Cognitive Therapy and Research, 1(4), 287-310.
  5. Multon, K. D., Brown, S. D., & Lent, R. W. (1991). Relation of self-efficacy beliefs to academic outcomes: A meta-analytic investigation. Journal of Counseling Psychology, 38(1), 30-38.
  6. Stajkovic, A. D., & Luthans, F. (1998). Self-efficacy and work-related performance: A meta-analysis. Psychological Bulletin, 124(2), 240-261.
  7. Sitzmann, T., & Ely, K. (2011). A meta-analysis of self-regulated learning in work-related training and educational attainment. Psychological Bulletin, 137(3), 421-442.
  8. Ashford, S., Edmunds, J., & French, D. P. (2010). What is the best way to change self-efficacy to promote lifestyle and recreational physical activity? A systematic review with meta-analysis. British Journal of Health Psychology, 15(2), 265-288.
  9. Brooks, A. W. (2014). Get excited: Reappraising pre-performance anxiety as excitement. Journal of Experimental Psychology: General, 143(3), 1144-1158.
  10. Klassen, R. M. (2004). Optimism and realism: A review of self-efficacy from a cross-cultural perspective. International Journal of Psychology, 39(3), 205-230.
  11. Schunk, D. H. (1995). Self-efficacy, motivation, and performance. Journal of Applied Sport Psychology, 7(2), 112-137.
  12. Maddux, J. E. (2002). Self-efficacy: The power of believing you can. In C. R. Snyder & S. J. Lopez (Eds.), Handbook of Positive Psychology (pp. 277-287). Oxford University Press.
  13. Marsh, H. W., & Martin, A. J. (2011). Academic self-concept and academic achievement: Relations and causal ordering. British Journal of Educational Psychology, 81(1), 59-77.
  14. Pajares, F. (1996). Self-efficacy beliefs in academic settings. Review of Educational Research, 66(4), 543-578.
  15. Bandura, A. (2000). Exercise of human agency through collective efficacy. Current Directions in Psychological Science, 9(3), 75-78.

If this post was useful, these five cover the frameworks that live next door to Self-Efficacy Theory in a behavioral designer’s toolbox:

WOULD YOU LIKE YU-KAI CHOU TO WORK WITH YOUR ORGANIZATION?

Yukaichou.com Main Contact Form

Bring this to your organization

Yu-kai has applied the Octalysis Framework with 200+ organizations — from Google and LEGO to sovereign governments.

Continue your training

Every finished article levels you up. Now test what drives you — or pick a quest path.

Keep exploring

Related articles