Expectancy Theory: An S-Tier Behavioral Designer’s Guide to Vroom’s Motivation Formula

In 1964, a thirty-two-year-old organizational psychologist at Carnegie Tech named Victor Vroom published a book that would quietly rewire how managers, economists, and later product designers thought about why people do things. The book was called Work and Motivation, and the core idea was a single equation: motivation equals the product of three beliefs — the belief that effort will produce performance, the belief that performance will produce an outcome, and the value the person places on that outcome. Multiply the three. If any of them is zero, motivation is zero. A paycheck the employee does not believe is achievable multiplies by zero. A promotion the employee does not believe the paycheck will unlock multiplies by zero. A promotion the employee does not actually want multiplies by zero. Three knobs, one multiplication, and the most honest answer to the question “why is this person not moving?” that organizational psychology had yet produced.

Expectancy Theory sits alongside the other motivation models in the Behavioral Framework Library, Yu-kai Chou’s curated index of the behavioral science behind world-class motivation and engagement design.

Most theories of motivation up to that point — Maslow’s hierarchy, Herzberg’s two-factor theory, McClelland’s needs — were content theories. They described what humans want. Vroom did something different. He built a process theory that described how humans calculate whether they will pursue any particular thing. The calculation happens in the head, usually below conscious awareness: in the seconds between reading a pitch and deciding whether to click, in the weeks between being handed a stretch goal and deciding whether to take it seriously, in the months between hearing “if you hit this quota, you make partner” and deciding whether to sprint or coast. Vroom gave that calculation a name (expectancy theory) and a shape (M = E × I × V) that survived six decades of field tests, meta-analyses, cross-cultural replications, and the biggest honest critiques behavioral science can throw.

I’ve spent nearly two decades designing behavioral systems through the Octalysis Framework, and in every engagement design review I’ve run — from LEGO education to Huawei enterprise dashboards to government citizen-service rollouts — Vroom’s equation is the crispest diagnostic for a stalled user I know. Users do not refuse to engage because your product is boring. They refuse to engage because one of the three terms in their private expectancy calculation is sitting at zero, and nothing else you layer on top will compensate for a zero. The gift of Vroom’s theory is that it tells you exactly which of three places the zero is hiding.

This is the S-tier designer’s guide to Expectancy Theory. I’m going to walk you through the three variables, the economics Vroom inherited and the psychology he invented, the evidence base that has accumulated since 1964, the critiques that have stuck, the neuroscience underneath, and — critically — how to translate the formula into actual product mechanics using Octalysis. If you take one idea with you, let it be this: every engagement problem is a multiplication with at least one hidden zero. Find the zero, fix the zero, and the multiplication starts paying off automatically.

⚡ Speed Run Notes

• Expectancy Theory (Vroom, 1964) says motivation is the product of three beliefs: M = E × I × V. Expectancy is the belief that effort will lead to performance.
• The multiplicative form is the entire design insight. A single zero collapses motivation to zero.
• Expectancy Theory is a process theory more than a content one. Maslow, Herzberg, and McClelland describe what humans want.
• The three variables correspond to three distinct psychological questions. “Can I do this?” is expectancy.
• Valence can be negative. This is the variable every casual summary of the theory misses.
• The effect sizes are real and stable across six decades of replication. Van Eerde and Thierry’s 1996 meta-analysis of 77 studies found expectancy-theory variables correlating with work performance, effort, choice, and satisfaction at magnitudes that match or exceed most Table of Contents
  • What Is Expectancy Theory?
  • The Core Findings of Victor Vroom
  • What Vroom Got Right
  • Where Expectancy Theory Falls Apart
  • The Brain on Expectancy Theory
  • Expectancy Theory vs Other Theories
  • Expectancy Theory in the Real World
  • The Elephant in the Room
  • How to Apply Expectancy Theory with the Octalysis Framework
  • Practical Steps to Apply Expectancy Theory
  • Frequently Asked Questions

  Author Credibility: Yu-kai Chou

  

  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.

  TEDxLausanne · Gamification to Improve Our World17 min

  What Is Expectancy Theory?

  Expectancy Theory is a cognitive process theory of motivation developed by Canadian-American organizational psychologist Victor H. Vroom, first formally articulated in his 1964 book Work and Motivation. The theory’s central claim is that human beings choose among alternative courses of action by anticipating the consequences of each and selecting whichever one their private calculation tells them is most likely to produce outcomes they value. The calculation is the product of three terms: expectancy, instrumentality, and valence, usually written M = E × I × V.

  The formal definitions Vroom offered in Work and Motivation are worth stating precisely. Expectancy is the subjective probability, from 0 to 1, that a given level of effort will produce a given level of performance — the honest answer the person gives themselves when they ask “can I actually pull this off?” Instrumentality is the subjective probability, from 0 to 1, that the performance, once achieved, will produce a specific outcome — “if I hit this number, will the system actually give me what it promised?” Valence is the affective value, positive or negative, the person places on that outcome — “do I even want the thing on offer?” Multiply the three, and you have the motivational force acting on the person for that particular alternative.

  The equation is deceptively simple. What gives it teeth is the multiplicative form. If any single term is zero, the whole product is zero. A sales representative who does not believe the quota is hittable has E = 0, and no bonus — however attractive — will move them. A sales representative who believes the quota is hittable but does not trust the company to pay out the promised bonus has I = 0, and the same paralysis sets in. A sales representative who believes the quota is hittable and trusts the payout, but does not personally value the bonus — because they already have enough money, or because the bonus is structured in a way they experience as insulting — has V = 0. Three different failure modes, three different interventions, one equation that tells you which is which.

  Vroom was building, in 1964, on a trail of ideas that stretched back to Kurt Lewin’s field-theory work in the 1930s (which would mature into force-field analysis by the mid-1940s), Edward Tolman’s expectancy-value learning models in the 1950s, and the broader cognitive-behaviorist revolution in American psychology. What Vroom contributed that his predecessors had not was a rigorous operational specification: three variables, each independently measurable, bound by a mathematical relationship that generated testable predictions. That was the piece that turned a philosophical claim about rational action into an empirical research program.

  A distinction that is critical for applied design: Expectancy Theory is a process theory more than a content one. Content theories — Maslow, Herzberg, McClelland — tell you what people want (safety, esteem, affiliation, achievement). Process theories tell you how people decide whether any given course of action will deliver what they want. Content theories make local cultural assumptions; process theories generalize across cultures, industries, and time periods more cleanly. Vroom’s equation does not commit on whether the user values money, meaning, or mastery. It only commits on how the user weighs whatever they value against the perceived odds of getting it.

  One last precision point before we move on. Vroom’s framework was designed for what behavioral economists now call “second-level outcomes.” The performance itself (hitting the quota, finishing the marathon, submitting the proposal) is a first-level outcome. The reward that performance unlocks (the bonus, the medal, the promotion) is a second-level outcome. Instrumentality is the link between them. Most sloppy applications of Expectancy Theory collapse the two levels, which makes the diagnostic useless. The whole point of separating them is that a person can be totally confident in their ability to produce the first-level outcome and still skeptical that the second-level outcome will follow.

  The Core Findings of Victor Vroom

  Most treatments of Expectancy Theory list the three variables and stop. That’s like saying a car runs on an internal combustion engine and stopping. The theory’s real power is in the specific predictions each variable generates, the interactions between them, the way Porter and Lawler extended the model four years later, and the feedback loops that make today’s motivation the evidence for tomorrow’s expectancy. Here are the six findings that actually matter.

  1. Motivation Is Multiplicative

  The multiplicative form is the argument. Vroom’s rivals at the time — the content theorists in particular — implicitly assumed motivation was additive: incentives add up, intrinsic meaning adds up, satisfaction adds up. If a reward scheme is not working, pile more rewards on top. Vroom’s equation formalizes the opposite claim: a ten on one variable and a zero on another produces zero, never ten. You cannot add your way out of a multiplicative zero.

  The engineering implication is that the first diagnostic move, when a user is not moving, is to locate the zero — not to introduce new features. A stalled sales rep does not need a bigger bonus; they need whichever of E, I, or V is secretly at zero to be moved off zero. A stalled student does not need a more exciting curriculum; they need whichever of the three variables is zero to be patched. Every product team that keeps adding rewards to a system that is not engaging users is committing the additive fallacy. Fix the zero first.

  2. Expectancy Is Built

  Of the three variables, expectancy is the most engineerable. Vroom defined it as the subjective probability that effort will produce performance — exactly the territory Bandura would later map with his theory of self-efficacy. A user’s expectancy is not a fixed personality trait. It is a belief built from prior experience in the domain, the visibility of the path to performance, and the early-session evidence the product gives them about what is possible.

  The design implication is that expectancy can be raised through four specific levers, in roughly descending order of effect size: visible progress paths, small early wins, models of similar users succeeding, and credible verbal coaching. Notice that three of the four match Bandura’s four sources of self-efficacy precisely — Vroom and Bandura arrived at the same engineering conclusions from different sides of the behavioral-theory river.

  3. Instrumentality Is a Trust Variable

  Instrumentality is where most organizations quietly break their own motivation systems. The variable measures whether the user believes that, if they achieve the performance the system asks of them, the system will in fact deliver the promised outcome. Every broken promise in the user’s history with the platform — or with platforms like it — erodes this variable.

  Vroom’s research, replicated many times since, showed that instrumentality is a function of the consistency and transparency of the reward logic. A system in which the reward schedule is publicly known, applied uniformly, and survives contact with edge cases will build high instrumentality over time. A system in which the reward logic is opaque, arbitrarily modified, or subject to “performance review” politics will erode instrumentality even when the nominal rewards are generous. This is why the highest-engagement reward programs in practice are those where the user can predict exactly what reward each action produces, never those with the most generous possible payout.

  4. Valence Is Personal, Sometimes Negative, and Rarely What Designers Assume

  Valence is the third variable and the most commonly mis-assumed. Designers assume users value money, status, power, or whatever their own reference class values, and then cannot understand why the reward program falls flat. Vroom’s insistence that valence is measured from the user’s private frame — not from the designer’s frame — is the intellectual antidote.

  The stakes of this point are easy to underestimate. Valence can be negative, meaning the user actively prefers not to receive the outcome. A reward of a team lunch is positive valence for one employee and negative valence for the colleague with social anxiety. A reward of travel is positive for the single employee in their twenties and negative for the parent of a newborn. An outcome of being publicly recognized at an all-hands is positive for the extrovert and deeply negative for the introvert. When the designer’s assumed valence is wildly off, the multiplication’s third term goes negative and motivation flips — the user avoids the performance to avoid the reward.

  The darker half of valence, which Vroom did not model directly, is that valence moves over time. Pay me to do something I already love and, if you pay me enough and then pay me less and less, at some point I will refuse to do it even for free. The external reward has overwritten the internal one. Self-Determination Theory names this the over-justification effect; in Vroom’s language it is V collapsing after the paycheck trained the user to stop accessing their own intrinsic reason. Any incentive system designed to run for more than a few quarters without accounting for this will find, around year three, that V has quietly drifted toward zero and the team has no diagnostic for why. The Vroom audit still works because you will detect the V = 0 reading, but you will mistake the cause for “the reward is too small” and double it, which accelerates the decay. The right move is to restore whatever intrinsic reason the user had before the extrinsic system arrived, rather than to raise the extrinsic lever further.

  5. The Porter-Lawler Extension Adds the Feedback Loop

  In 1968, Lyman Porter and Edward Lawler extended Vroom’s equation to include ability, role perceptions, perceived equity of reward, and the crucial observation that today’s satisfaction becomes tomorrow’s valence input. The extended Porter-Lawler model looks more like a cycle than a single multiplication: effort produces performance (moderated by ability and role clarity), performance produces reward (moderated by perceived equity), reward produces satisfaction, and satisfaction feeds forward into the next round’s valence and expectancy.

  The feedback-loop framing is important because it explains why Expectancy Theory predicts both initial engagement and also retention curves. Each cycle the user runs through either confirms or disconfirms the three variables. A user whose first cycle delivers the promised reward has a second-cycle expectancy and instrumentality that are higher than the first. A user whose first cycle fails — because the performance was not hittable, or the reward did not arrive, or the reward was not what they wanted — enters the second cycle with lower variables and a much harder design problem to solve.

  6. The Three Variables Interact

  The equation is written as a simple multiplication, but subsequent research has shown the three variables interact in ways the bare formula does not capture. Expectancy influences valence, because a person’s sense of what is achievable shapes what they allow themselves to want. Instrumentality influences expectancy, because a system the user does not trust makes effort feel pointless regardless of objective capability. Valence influences both, because a strongly wanted outcome motivates the kind of information-seeking that builds expectancy and instrumentality over time.

  The design implication of the interactions is subtle. Raising any single variable raises the product directly via multiplication. But raising any single variable also creates pressure on the other two through the interactions, so the product compounds faster than the bare equation suggests. This is why Expectancy Theory interventions that target only one variable — the most common design mistake — underperform interventions that target all three in sequence.

  Put these six findings together and you have the complete Vroom operating system. Three variables, multiplied. Four levers for building expectancy. Trust as the infrastructure of instrumentality. Personal, sometimes negative valence. A Porter-Lawler feedback cycle running underneath. And interaction effects that reward sequenced, multi-variable design over single-variable brute force.

  What Vroom Got Right

  Expectancy Theory has been tested, replicated, critiqued, and extended for six decades. Most of the original claims have held. Here are the three things Vroom got right that every design practitioner should internalize before they touch a user flow.

  1. He moved motivation from content to process

  Before 1964, the dominant question in motivation research was “what do humans want?” Maslow had a hierarchy. Herzberg had a two-factor theory. McClelland had three needs. Each was a content taxonomy. Vroom’s contribution was to ignore the content question and focus on the process: given whatever a human wants, how do they decide which of several available actions will actually deliver it?

  The shift was enormous. A process theory does not care whether the user values money or meaning, status or service, safety or self-actualization. It only cares whether the user’s current belief state will translate any particular motivator into action. That universality is why Vroom’s formula survives across industries, cultures, and decades while content theories drift out of fashion as the cultural context around them shifts. Every modern design system that emphasizes user-centered motivation over assumption-driven reward engineering inherits this shift directly from Vroom.

  2. He made motivation measurable in the wild

  Vroom’s second contribution was methodological. He turned motivation from a feeling to be described into a variable to be measured. His three terms are each independently surveyable — users can rate their expectancy, instrumentality, and valence for a given alternative on numeric scales that have acceptable reliability. The product of the three ratings predicts action in the laboratory and in the field at effect sizes competitive with anything behavioral science has produced.

  The methodological rigor let organizational psychology run a serious evidence program. Managers could survey their teams, identify the variable that was dragging down motivation, intervene on that variable specifically, re-survey, and measure whether the intervention moved the needle. That chain of evidence — diagnose → intervene → remeasure — is what separates actionable behavioral theories from inspirational ones. It is also the reason an Expectancy-Theory audit is one of the fastest diagnostics a product team or a management consultant can run on a stalled team or a plateauing engagement metric.

  3. He respected the subjectivity of the user

  Vroom was insistent that all three terms are the user’s subjective judgments, never objective properties of the environment. Expectancy is not “can you really do this?” — it is “do you believe you can do this?” Instrumentality is not “will the reward really arrive?” — it is “do you believe it will?” Valence is not “is this reward really valuable?” — it is “do you value it?” The user’s private calculation is what drives behavior, not the designer’s spreadsheet.

  This subjectivity principle is what prevents the common design failure of building reward systems on assumed user preferences. The assumption-driven reward program is the one where HR hands out points that can be redeemed for office supplies the employees could just expense, or where product teams build elaborate leveling systems for users who do not care about levels. Vroom’s subjectivity insistence is the corrective: measure the user’s actual valence before you design for it, because the valence your spreadsheet assumes is almost always wrong at the margins, and the margins are where engagement lives or dies.

  Where Expectancy Theory Falls Apart

  Sixty-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 Vroom’s foundation. Ignoring these is how you end up shipping an elegantly specified motivation system that somehow, inexplicably, fails to move users.

  Critique 1: The Rationality Assumption Is Strong

  Vroom’s equation assumes the user performs — or at least behaves as if they perform — a multiplication of three subjective probabilities. The assumption is cousin to the rational-actor assumption in classical microeconomics, and it has taken the same beating from behavioral economics that the economic version has. Kahneman and Tversky’s work on heuristics and biases, Thaler’s extensions of Herbert Simon’s bounded-rationality program into behavioral economics, and the entire behavioral economics revolution of the 1980s onward have made clear that humans do not reliably compute subjective probabilities, do not consistently multiply when they should, and are subject to systematic biases that distort all three Vroom variables.

  Loss aversion in particular — the finding that losses feel roughly twice as large as gains of the same magnitude — means the valence term is asymmetric in ways Vroom did not specify. Framing effects mean the same objective outcome can have wildly different subjective valence depending on whether it is presented as a gain or a loss. Availability heuristics mean expectancy judgments are biased toward recent, salient experiences rather than base rates. The cumulative effect is that the equation as written is a clean specification of a process that humans run much messier versions of in practice. The formula is still useful as a diagnostic; it is not useful as a precise predictor of individual decisions in the moment.

  The cleanest one-sentence demonstration that Vroom’s multiplication understates real human motivation is a thought experiment I use in every Octalysis workshop. Imagine pressing a button for four hours straight, guaranteed to receive a paycheck at the end. That is factory work, and people endure it rather than enjoy it. Now imagine pressing a button for four hours straight, uncertain whether you will receive a paycheck, lose money, or break even. That is casino gambling, and people pay for the privilege. A straight M = E × I × V reading predicts the casino should be empty because expected value is negative. The casino is not empty. The variance itself is motivating in a way the equation does not carry a term for. Vroom’s math captures three levers; it misses the separate additive charge that uncertainty contributes to perceived valence, which is the Core Drive 7 (Unpredictability & Curiosity) machinery the Octalysis Framework models explicitly.

  Critique 2: Self-Report of Subjective Probabilities Is Noisy

  The theory depends on being able to measure expectancy, instrumentality, and valence — which in practice means asking users to rate them. Self-report of subjective probabilities is famously unreliable. Users do not introspect accurately on what they think will happen. They rationalize their ratings in light of the behavior they have already committed to. They adjust their ratings to match what they think the researcher wants to hear. They shift their ratings depending on the reference point made salient by the question wording.

  The empirical consequence is that the correlation between measured Vroom variables and actual behavior is lower than the theoretical correlation would be if measurement were clean. Van Eerde and Thierry’s 1996 meta-analysis flagged this directly: within-subject research designs (where the same user rates multiple alternatives) produce much stronger support for the theory than between-subject designs (where different users are compared), which is exactly the pattern you would expect if the measurement instrument is noisy but the underlying process is real. A practical designer reads the theory not as a precise prediction engine but as a diagnostic framework whose resolution is limited by the resolution of the self-report instruments that feed it.

  Critique 3: The Theory Has Individualist Cultural Assumptions

  Expectancy Theory was developed in the American workplace of the 1960s and carries individualist assumptions about agency, choice, and reward. The user is modeled as an autonomous decision-maker selecting among alternatives based on their own private valuation. Cross-cultural research — Eylon and Au in 1999, Sparrow and Wu in the 2000s, Gelfand and colleagues more broadly — has shown that in more collectivist cultures, motivation is often more accurately modeled as a function of group expectations, role obligations, and face considerations that sit outside Vroom’s three variables.

  The implication for international design is concrete. Expectancy Theory travels well as a diagnostic in North American and Northern European workplaces; it travels less well in East Asian, Latin American, and sub-Saharan African contexts where motivation is more socially distributed. Product teams shipping globally should either supplement the Vroom diagnostic with a collectivist-motivation framework (collective efficacy, role expectations, relational obligations) or apply the Vroom diagnostic at the group level rather than the individual level. A fourth unspecified critique is worth a line: the theory, as written, does not account for unconscious motivation. Psychodynamic, affective, and automatic-processing research has all shown that humans are driven by forces they cannot accurately report on. Vroom’s survey instruments are blind to these forces by design. The gap is real, and a designer who treats Expectancy Theory as the only motivation lens will miss the portion of behavior that runs below the conscious calculation it specifies.

  The Brain on Expectancy Theory: The Neuroscience Underneath

  Vroom built the theory on survey and behavioral data. The three decades of cognitive neuroscience since have given us a reasonably clear picture of what the brain is doing when it computes expectancy, instrumentality, and valence, and the picture has direct implications for what designers should and should not do.

  The valence computation maps most cleanly onto the brain’s reward-valuation circuitry. When a user considers an outcome, the ventromedial prefrontal cortex (vmPFC) and the ventral striatum, particularly the nucleus accumbens, generate a subjective value signal that integrates the expected payoff with the user’s personal preferences, current deprivation state, and contextual framing. Single-cell recordings in primates and human functional imaging both show that these regions encode value on a common currency scale — euros, chocolate, social approval, and novelty all converge into the same neural signal that the decision-making circuitry can compare.

  The expectancy computation — can I do this? — recruits a different network. Three regions carry most of the Vroom load. The medial prefrontal cortex handles self-referential simulation of the action. The anterior cingulate cortex (ACC) encodes the expected difficulty and the effort cost. The dorsolateral prefrontal cortex integrates the action simulation with memory of prior attempts to produce a capability estimate. When the network’s output is a high capability estimate, expected-reward signaling in the ventral striatum ramps up accordingly. When the output is a low capability estimate, the same striatal signal flattens, and the user’s body registers the task as effortful-and-probably-futile.

  The instrumentality computation — will the system actually pay out? — is a trust judgment, and the brain treats it as such. The right temporoparietal junction and the dorsomedial prefrontal cortex, two regions heavily involved in theory-of-mind and social inference, are active when users assess whether an institution will follow through on its promises. Prior research on economic trust games shows that these regions encode a running estimate of counterparty reliability that updates with each observed interaction. A company that pays out the promised bonus produces a trust signal that raises instrumentality for the next cycle. A company that misses payout once produces a trust-violation signal whose half-life is months, and whose recovery requires several honored cycles in a row.

  The three networks converge in the decision-making circuitry of the lateral prefrontal cortex and the basal ganglia, which integrate the valence signal with the expectancy and instrumentality signals to produce a go/no-go output. This is where the multiplication in Vroom’s formula happens in biological hardware — not as a literal multiplication, but as a nonlinear integration where any near-zero input collapses the output toward no-action. The collapse is why the multiplicative form of the formula matches the neural reality better than an additive form would.

  The most important neural finding for designers is the role of dopamine. Dopaminergic neurons in the ventral tegmental area encode reward prediction errors — the difference between the outcome the user expected and the outcome they received. When an outcome exceeds expectation, dopamine spikes and future expectancy is revised upward. When an outcome falls short, dopamine dips and future expectancy is revised downward. This is the neural substrate of the Porter-Lawler feedback loop: today’s outcomes are tomorrow’s expectancy through the prediction-error learning signal.

  The design takeaway from the neuroscience is concrete. Interventions that hit valence, expectancy, and instrumentality simultaneously produce compounding effects because they activate three different neural networks in a coordinated way. Interventions that only hit one — the most common design mistake — run into the bottleneck of whichever other network is at its floor. The neural evidence endorses exactly the interaction-aware, multi-variable design posture the behavioral data also supports.

  Expectancy Theory vs Other Theories

  Expectancy 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.

  Framework	Type	What it tells you	Best for
  Expectancy Theory (Vroom, 1964)	Process	Whether motivation will translate into action: M = E × I × V	Diagnosing why engagement is not happening
  Maslow’s Hierarchy (1943)	Content	What humans want, arranged in levels	Generating the menu of possible rewards
  Self-Determination Theory (Ryan & Deci, 1985)	Content + Process	How autonomy, competence, relatedness drive intrinsic motivation	Designing for engagement that lasts
  Self-Efficacy Theory (Bandura, 1977)	Process (deep dive on E)	The four sources that build perceived capability	Moving the expectancy variable specifically
  Fogg Behavior Model (B = MAP)	Process	Behavior = Motivation × Ability × Prompt	Pre-flight checklist for any single action

  Expectancy Theory vs Maslow’s Hierarchy of Needs: Maslow is a content theory: it specifies what humans want, arranged in a hierarchy. Vroom is a process theory: it specifies how humans decide whether any given course of action will deliver what they want. Maslow tells you that the user might value belonging, esteem, or self-actualization. Vroom tells you whether the user currently believes your product will help them get any of those things, and which of the three variables is stopping them from trying. The two are complementary: use Maslow to generate the menu of possible rewards; use Vroom to diagnose why the user is not engaging with the one you chose.

  Expectancy Theory vs Self-Determination Theory (SDT): SDT specifies the three innate psychological needs — autonomy, competence, relatedness — whose satisfaction produces intrinsic motivation. Expectancy Theory specifies the calculation that translates any motivator, intrinsic or extrinsic, into action. SDT’s competence need maps onto Vroom’s expectancy variable. SDT’s relatedness need influences Vroom’s valence when the outcome is social. SDT is stronger when you care about why engagement endures (intrinsic motivation lasts; extrinsic does not). Vroom is stronger when you need a crisp diagnostic for why engagement is not happening at all in the first place.

  Expectancy Theory vs Self-Efficacy Theory (Bandura): Bandura’s self-efficacy construct is a deep dive into Vroom’s expectancy variable. Both are domain-specific subjective probabilities that effort will produce performance; Bandura added the specification of the four sources (mastery, vicarious, verbal, physiological) that build the belief. The frameworks are not competitors — they are complementary at different levels of resolution. Vroom gives you the three-variable diagnostic; Bandura gives you the deep engineering spec for moving the expectancy variable specifically.

  Expectancy Theory vs BJ Fogg’s Behavior Model (B=MAP): Fogg’s model says behavior happens when motivation, ability, and a prompt converge. Vroom’s expectancy maps onto Fogg’s ability variable (perceived). Vroom’s valence × instrumentality maps onto Fogg’s motivation variable. Fogg is operationally crisper as a design checklist — three factors, prompt-triggered, build for the moment. Vroom is more precise as a diagnostic — three variables, multiplied, reveal the specific zero. Use Fogg when you’re designing the moment; use Vroom when you’re diagnosing why the moment is not producing the behavior.

  Expectancy Theory vs Goal-Setting Theory (Locke & Latham): Locke and Latham’s Goal-Setting Theory specifies that specific, difficult goals produce higher performance than vague or easy goals. Expectancy Theory specifies that the goal only produces performance when the user’s expectancy, instrumentality, and valence are all non-zero. The two frameworks are compatible: Goal-Setting tells you what kind of goal to write; Expectancy Theory tells you when the user will actually pursue the goal you wrote. A well-written goal that the user does not believe is achievable (E = 0) produces exactly nothing; Goal-Setting alone does not flag this failure mode, but Vroom does.

  Expectancy Theory vs Porter-Lawler Extended Model: The Porter-Lawler extension is not a competitor; it is the theory’s natural evolution. Porter and Lawler added ability and role clarity as moderators on the effort-performance link, perceived equity as a moderator on the reward-satisfaction link, and explicit separation of intrinsic and extrinsic rewards. The extension is more precise for workplace application; the core Vroom formula is more portable for design diagnostic. In practice, use the Vroom core for initial diagnosis and the Porter-Lawler extension when you need to specify implementation in a formal organizational context.

  Expectancy Theory 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 a user would engage at all — which of eight Core Drives your design is activating, and how. Expectancy Theory is the economic diagnostic that tells you whether the Core Drives you are activating will translate into action given the user’s current belief state. Every Octalysis-designed system uses Vroom implicitly. The systems that last use it explicitly — running expectancy-instrumentality-valence diagnostics on each Core Drive they are relying on, finding the zeros, and patching them before the Core Drive can compound. That’s what I’ll unpack below.

  Expectancy Theory in the Real World: Four Domains

  Expectancy Theory’s real value shows up when you see the same three variables applied across wildly different contexts. I’ll walk through four — workplace compensation, education, healthcare, and consumer product — because each domain tells you something different about what Vroom’s formula can and cannot do.

  Workplace Compensation: The Sales Quota Autopsy

  The cleanest domain to see Vroom at work is sales compensation. Every year, thousands of companies design bonus plans meant to motivate their sales teams. A large fraction of those plans underperform their designers’ expectations. When you run an Expectancy Theory autopsy on the failures, the pattern is almost always the same: one of the three variables is secretly at zero.

  The E = 0 failure shows up when the quota is set aspirationally — management picked a target that looks good in the board deck but that the reps know, from the territory data, cannot be hit with any reasonable level of effort. The reps do not protest; they simply stop trying. The I = 0 failure shows up when the compensation plan has a history of being modified mid-year, or when territory assignments shift in ways that redistribute credit, or when the accounting process for crediting sales is opaque. The reps hit the number and wait to see if the bonus actually lands. The V = 0 failure shows up when the bonus is structured in a way the rep does not value — non-cash rewards a top performer would rather just have as money, or public recognition for an introverted top performer who experiences it as exposing.

  The research supports the pattern. Meta-analyses by Jenkins, Mitra, Gupta, and Shaw in 1998 and 2000 show that financial incentives improve performance when all three expectancy-theory conditions are met — and fail to improve performance, or actively backfire, when any one of them is at zero. The literature on pay-for-performance is littered with negative findings that became positive once the design team fixed the hidden zero. Vroom’s formula gives you the diagnostic vocabulary to find the zero in the first place.

  Education: Why Grades Don’t Always Motivate

  Expectancy Theory explains one of the most persistent puzzles in educational design: why grade-based incentives produce dramatically different effort curves across students. Students who believe they can earn a high grade with reasonable effort (E = high) and believe the system will grade fairly (I = high) and value the high grade (V = high) study. Students with any of the three at zero do not, regardless of the nominal size of the grade differential.

  The practical consequence shows up in tracking and ability-grouping research. Students placed in classes where the average grade is an A and they are performing at C level often have E = 0 because the relative performance needed for a high grade is out of reach. Students in schools where grade assignment is perceived as arbitrary or teacher-biased have I = 0. Students whose cultural reference group does not value school performance — whose peer reality runs on a different status currency — have V = 0 on grades specifically. Interventions that raise grades without addressing the underlying variable produce marginal improvements; interventions that diagnose and patch the zero produce step-change improvements in the kind of gains documented in high-quality meta-analyses of college-performance interventions.

  Healthcare: Chronic Disease Management and Adherence

  In chronic disease management, Expectancy Theory gives clinicians a clean diagnostic for non-adherence. A patient who does not take their diabetes medication, does not exercise despite cardiac-rehab orders, or does not show up for follow-up appointments is usually not being irrational — they are acting on a Vroom calculation the clinician has not inspected. The E-zero patient does not believe they can sustain the regimen. The I-zero patient does not believe that sustaining the regimen will produce the health outcome. The V-zero patient does not value the health outcome enough to motivate the effort.

  Each of the three has a distinct clinical intervention. E = 0 calls for graduated mastery (start with a smaller adherence target the patient can hit, then escalate). I = 0 calls for evidence — showing the patient data from similar patients whose adherence produced the outcome. V = 0 calls for a conversation about what the patient actually wants from their life and reframing the adherence as instrumental to that goal rather than to the clinician’s goal. The literature on Motivational Interviewing, developed by William Miller and Stephen Rollnick in the 1980s, is in effect a structured way to run an Expectancy Theory diagnostic on a patient and intervene on whichever variable is zero.

  Consumer Product: Onboarding and Retention

  The fourth domain is where I spend most of my advisory time. Every consumer-product onboarding is an Expectancy Theory test bench. The user arrives with a fragile calculation: can I get meaningful value from this product (E), will the product actually deliver what it promises (I), is the value something I actually want (V)? The product has roughly one session — sometimes three — to move all three variables off zero, or the user disengages.

  Duolingo’s onboarding is a near-perfect Vroom implementation. The first lesson is short and winnable (E rises immediately). The streak and XP systems are predictable and transparent (I stays high). The lesson content is selected to produce a phrase the user can speak aloud — a tangible immediate payoff — at the end of lesson one (V is concretized, never left abstract). Headspace’s onboarding is the same pattern with different content: a three-minute guided meditation the user can finish (E), a progress tracker that reliably shows up (I), and an immediate felt-sense of calmness or focus as the reward (V). Both apps are effectively running the Vroom equation in the first session and ending with all three terms well above zero, which is why their retention curves look the way they do.

  The Duolingo streak, once you look at it through Vroom, is not really a Core Drive 2 progress bar. It is an Instrumentality amplifier. Every +1 to the streak number is the cleanest, most transparent, most immediate payout any app ships: you did the thing, the counter moved, the system honored the promise. Ninety days in, the streak number has stopped being a claim about Spanish fluency. It is the record of a commitment kept. By day 247, the thing the user is protecting is not their progress in a language; it is the accumulated evidence that this system, unlike most systems in their life, pays out. That is why people open Duolingo on Christmas Eve at 11:58 pm. The language goal has long since been overtaken by the trust relationship.

  The cautionary note: teams often optimize one variable and leave the others at zero. A flashy rewards program (high V) bolted onto a product the user does not believe they can succeed at (E = 0) produces no engagement lift. A frictionless onboarding flow (high E) bolted onto a reward system the user does not trust (I = 0) produces no engagement lift. Vroom’s formula is unsentimental: you have to fix all three, beyond the one you know how to fix.

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

  You cannot teach Expectancy Theory honestly without acknowledging its shadow. The same three variables that can be engineered to produce genuine, valued action can be engineered to produce action that serves the designer’s goals at the expense of the user’s. The line between the White-Hat and Black-Hat versions of Vroom is thinner than most designers admit.

  The classic failure mode is the manufactured-expectancy trap — engineering the user’s belief that an outcome is achievable when in fact the base rate of success is much lower than the onboarding implies. Gambling products, certain multi-level marketing schemes, and some trading platforms have built entire business models on this pattern. The onboarding flows are engineered to produce high-E judgments through carefully selected early experiences (a small initial win, a testimonial from a survivor) that do not reflect the population-level base rate of outcomes. The user’s Vroom calculation tilts toward action; the downstream reality is that most users will not achieve the outcome; the high E was a designed illusion.

  The second failure mode is the instrumentality bait-and-switch — building trust in the reward system through a string of honored promises, then modifying the rules after the user is committed. Loyalty programs that change redemption thresholds, employers who redefine “performance” mid-cycle, and software platforms that change pricing after a user has built workflow dependencies all deploy this pattern. The I variable was built honestly and then exploited. The user’s discovery that the rules changed is what produces the characteristic user-rage response — not the rule change itself, but the violation of the trust the user extended to the reward system when they committed to it.

  The third failure mode, and in some ways the most insidious, is valence substitution. A system that surveys its users, learns what they actually value, and then nudges them to pursue a different outcome the system values by packaging it with the valenced outcome the user expressed. Engagement-optimized recommendation systems are notorious for this: users report wanting connection with friends; the system delivers connection-flavored engagement that actually optimizes advertising dwell time. The valence the user expressed is not the valence the system is actually delivering against. The mismatch is not transparent to the user, and the trust violation, once caught, is corrosive.

  The dividing line I teach is the honest-Vroom test. Would the user, reading a full spec of your expectancy, instrumentality, and valence design decisions, still choose to engage? If yes, your design is White Hat. If you depend on the user not understanding what you are actually optimizing, you have built a manipulative Vroom machine, and regulators, journalists, and the user base will eventually catch it. The Octalysis ethical frame applies here exactly as it does elsewhere: short-term engagement through manufactured belief will always give way to long-term resentment. Build a Vroom calculation you would let the user audit, or do not use the diagnostic at all.

  How to Apply Expectancy Theory with the Octalysis Framework

  This is where the theory becomes architecture. Expectancy Theory gives you three variables. The Octalysis Framework tells you where each variable lives inside the eight-dimensional motivation map, which Core Drive each one touches, and how to sequence them across the four Experience Phases. Without Octalysis, Vroom’s formula is a diagnostic; with Octalysis, it is an engineering spec.

  

  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.

  Expectancy Theory sits as the economic counterpart to the Core Drives. In fact, the cleanest way to see the relationship is this: the Core Drives are the sources of valence, expectancy, and instrumentality in the human motivational system; Vroom’s formula is the calculus that determines whether any particular Core Drive’s activation will translate into action in a given user at a given moment. Without the formula, Octalysis is a map. Without Octalysis, the formula is an equation with three variables and no idea what is filling them.

  Here is the mapping from Vroom’s three variables to the eight Core Drives that most design teams miss:

  • Expectancy → CD2 (Development & Accomplishment) primary, CD3 (Empowerment of Creativity & Feedback) secondary. Every perceived-capability judgment is a CD2 computation. When the perceived path also gives the user meaningful choice in how they achieve the outcome, CD3 layers on top. The design pattern is clear: scaffolded challenge (CD2) with open-ended solution paths (CD3) produces the densest expectancy-building architecture behavioral science has documented. This is the same conclusion Bandura reached for self-efficacy; Vroom’s expectancy variable is Bandura’s self-efficacy in economic clothes.
  • Instrumentality → CD4 (Ownership & Possession) primary, CD5 (Social Influence & Relatedness) secondary. Instrumentality is a trust variable. CD4 is the Core Drive that builds over time as the user accumulates points, badges, streaks, and status — each of which becomes evidence that the system pays out reliably. CD5 supports instrumentality when peers visibly receive the promised rewards, which provides social evidence that the system works. The Octalysis Game Technique for instrumentality-building is Points (GT#1) and Progress Bar (GT#4) done with enough transparency that the user can predict exactly what payoff each action produces.
  • Valence (positive) → CD1 (Epic Meaning & Calling) and CD5 (Social Influence & Relatedness) primary, CD3 (Empowerment) secondary. The outcomes users value most are the ones tied to meaning (CD1), to the people they care about (CD5), and to their own creative expression (CD3). Valence-rich design finds the specific intersection of those three for the specific user population. Valence is the Core-Drive variable that varies most across users; a one-size-fits-all valence design will always underperform a segmented valence design.
  • Valence (negative) → CD8 (Loss & Avoidance) and CD6 (Scarcity & Impatience). When the “reward” a system offers is actually experienced by the user as a loss — lost time, lost face, lost flexibility — the valence term goes negative. CD8 and CD6 are the Core Drives that specifically fire on avoidance and urgency; a design that accidentally activates them when targeting CD1 or CD2 will produce avoidance behavior that looks like disengagement but is actually active flight.

  

  

  The design rule that falls out of this mapping is the one I teach in every Octalysis workshop: Vroom diagnoses; Octalysis intervenes. When a Core Drive is not producing the engagement the design called for, you do not need a new Core Drive — you need a Vroom audit of the Core Drive you already chose. Is the user’s expectancy for the CD2 challenge at zero? Raise it with mastery scaffolding. Is the user’s instrumentality for the CD4 reward at zero? Raise it with transparency and honored commitments. Is the user’s valence for the CD5 social outcome actually zero or negative? Discover the real valence through research and redesign the social reward to match.

  In the Octalysis Level 2 framework, which maps motivation across the four Experience Phases (Discovery, Onboarding, Scaffolding, Endgame), Vroom’s diagnostic is heaviest in Discovery and Onboarding. Discovery is where the user forms their first E, I, and V estimates, mostly from the product’s copy, screenshots, and onboarding preview. Onboarding is where those estimates are either confirmed by concrete experience or collapse. Scaffolding is where the Porter-Lawler feedback loop takes over, each successful cycle raising the next cycle’s expectancy and instrumentality. By Endgame, the three variables are either well-established (and the user’s engagement is being carried by intrinsic motivation) or they were never resolved (and the user has churned). Running a Vroom audit on each Experience Phase separately — rather than on the product as a whole — is the highest-resolution diagnostic I know.

  Go deeper

  The Expectancy-to-Octalysis mapping is one view of the framework. The full Octalysis Framework gives you all 8 Core Drives, 4 Experience Phases, and the Game Techniques that move each variable.

  Read the Complete Octalysis Framework →

  Practical Steps to Apply Expectancy Theory

  Everything above is theory. Here’s the playbook I walk product teams, coaches, and organizational leaders through when they bring a real motivation problem and ask for the Expectancy Theory version of the answer.

  Step 1: Name the target behavior in one concrete sentence

  Not “engagement.” Not “motivation.” “By the end of week one, the user has completed three lesson sessions and invited one friend.” “By the end of the quarter, the rep has submitted five qualified opportunities to the pipeline.” The target sentence anchors the Vroom diagnostic. Without a concrete behavior, expectancy and instrumentality are abstract; with one, each becomes a specific question you can ask a real user.

  Step 2: Ask five users to rate E, I, and V on a 1-10 scale

  For a representative sample of five users who are in the position to perform the target behavior, ask three questions in plain language. Expectancy: “on a 1-10 scale, how confident are you that you can actually do this?” Instrumentality: “on a 1-10 scale, how confident are you that if you do it, the system will deliver what it promised?” Valence: “on a 1-10 scale, how much do you actually want the promised outcome?” Critical: also ask why after each rating. The why is where the design decisions live; the numbers alone are not enough.

  Step 3: Find the zero (or the lowest variable)

  Across your five users, identify the variable with the lowest average rating and, more importantly, the variable that has the most zeros or near-zeros. This is where your intervention will have the largest effect, because the multiplicative form means moving a 2 to a 6 is vastly more valuable than moving an 8 to a 10. The lowest variable is the bottleneck; fix it first, then move to the next lowest.

  Step 4: Raise expectancy with visible paths and small wins

  If expectancy is the lowest variable, the intervention is mastery scaffolding. Redesign the path from first interaction to first meaningful win so the user encounters non-trivial, attributable, progressively harder successes in their first session. Show the full path to the target behavior so users can see the staircase, beyond the destination. Surface peer examples of users who started at the new user’s skill level and completed the path. These interventions are the Bandura-esque application of Vroom’s expectancy variable, and they are among the highest-leverage design moves available.

  Step 5: Raise instrumentality with transparency and consistency

  If instrumentality is the lowest variable, the intervention is trust-building. Publish the reward logic in language the user understands. Apply it uniformly, and especially apply it at the edge cases — the edge cases are where trust is made or broken. Honor the logic even when the user is not watching, because users compare notes. Show a running ledger where the user can see exactly what actions produced what rewards across all past cycles. Instrumentality is built the way trust is always built: slowly, by honoring small commitments, with zero tolerance for exceptions that serve the platform at the user’s expense.

  Step 6: Raise valence by discovering what the user actually wants

  If valence is the lowest variable, the intervention is research. Stop assuming the user wants what your spreadsheet says they want. Five user interviews with an open-ended “what do you want out of this domain of your life, in your own words?” will usually produce three to five valence themes you did not have in your design deck. Redesign the reward to deliver against those themes specifically. The most common finding is that users value outcomes that are cheaper to deliver than the ones the platform was building toward — a source of insight, a moment of autonomy, a small social recognition — all of which can be designed into the product for a fraction of the cost of the financial reward the platform assumed was needed.

  Step 7: Sequence the interventions by Experience Phase

  Discovery gets valence clarity (the promise is honest and matches what users actually want). Onboarding gets expectancy scaffolding (early mastery experiences that confirm “I can do this”). Early Scaffolding gets instrumentality confirmation (the first rewards arrive as promised, on time, in the form described). Mid-Scaffolding gets all three in tight feedback loops. Endgame releases the scaffolding and lets intrinsic motivation carry the load. A roadmap that tries to raise all three variables simultaneously at peak intensity will feel heavy-handed; a sequenced roadmap will feel, to the user, like the system is proving itself in layers.

  Step 8: Measure the variables over time, beyond the behavior

  Most product teams measure the downstream behavior and stop there. The Vroom-aware team measures E, I, and V through a three-item survey at onboarding, at 30 days, and at 90 days. If behavior is improving without the variables improving, your engagement is fragile and built on something other than honest motivation. If the variables are rising ahead of behavior, you are early in a compounding curve and the behavior will follow. The three-item survey is the leading indicator most teams never track, and it is the single cheapest instrument for distinguishing durable engagement from a sugar rush.

  Closing Thoughts: The Economic Counterpart to Every Core Drive

  If you have read this far, you know more about Expectancy Theory than almost every manager, educator, and product designer who will cite Vroom this year. You know the three variables — expectancy, instrumentality, valence — and the multiplicative form that makes any single zero catastrophic. You know the four levers for raising expectancy, the trust infrastructure behind instrumentality, and the personal, sometimes negative nature of valence. You know the three serious critiques — rationality, measurement, cultural specificity. You know how each variable maps onto Octalysis Core Drives and which Experience Phase each variable is heaviest in. That is enough scaffolding to diagnose a stalled user, a plateauing engagement metric, or a reward program that is not producing the behavior its designers expected.

  The last lesson is the one that takes the longest to internalize. Vroom’s gift is not the formula. Many motivation theories have formulas. The gift is the discipline the formula imposes on the designer: that motivation is a multiplication, that a single hidden zero kills the multiplication, and that the design job is not to add more features but to locate the zero and patch it. The team that internalizes this stops building new reward programs as the first response to disengagement and starts running Expectancy Theory diagnostics instead. The diagnostic is cheap. The new reward program is expensive. The diagnostic wins roughly every time.

  Vroom’s real contribution, sixty years on, was not the three variables in isolation. Psychologists had pieces of each of them before 1964. His contribution was to bind them together in a relationship that survived empirical testing, generated specific interventions, and gave practitioners a vocabulary for the calculation every human runs before deciding whether to bother. Six decades later, that vocabulary is still the most reliable diagnostic instrument we have for turning a user who could engage into a user who actually does. Use it carefully. Hunt for the hidden zeros. And remember that the multiplication rewards honest design, because the user is running it too, and their version of the calculation is the one that actually drives their behavior.

  Put Vroom to work

  You’ve got the diagnostic. Now go hunt the hidden zeros.

  Two ways to take this further:

  • Bookmark the framework — the full Octalysis Framework is where every Vroom variable gets an engineering spec.
  • Read the book — Actionable Gamification walks through 180+ behavioral design patterns that move Expectancy, Instrumentality, and Valence in real products.

  No email wall. No gated download. Just the resources, in the order that builds the skill fastest.

  Frequently Asked Questions About Expectancy Theory

  What is Expectancy Theory in simple terms?

  Expectancy Theory is a process theory of motivation that says a person’s motivation to pursue any particular course of action is the product of three beliefs: that effort will lead to performance (expectancy), that performance will lead to an outcome (instrumentality), and that the outcome is something they value (valence). The three beliefs multiply. If any one of them is zero, motivation is zero. Victor Vroom introduced the theory in his 1964 book Work and Motivation.

  Who created Expectancy Theory?

  Expectancy Theory was developed by Canadian-American organizational psychologist Victor H. Vroom, then at Carnegie Tech and later at Yale School of Management. Vroom published the theory in his 1964 book Work and Motivation. Lyman Porter and Edward Lawler extended the model in 1968 to include abilities, role clarity, perceived equity, and the distinction between intrinsic and extrinsic rewards.

  What is the Expectancy Theory formula?

  The formula is M = E × I × V, where M is motivational force, E is expectancy (the belief that effort will produce performance, scaled 0 to 1), I is instrumentality (the belief that performance will produce the outcome, scaled 0 to 1), and V is valence (the subjective value of the outcome, positive or negative). The terms are multiplied, never added, which means any single zero collapses the whole product to zero.

  What is the difference between expectancy and instrumentality?

  Expectancy is the belief that your effort will lead to performance — the honest answer to “can I do this?” Instrumentality is the belief that the performance, once achieved, will lead to the promised outcome — the honest answer to “will the system actually pay out if I do?” They fail in different ways and require different interventions. A user with low expectancy needs mastery scaffolding; a user with low instrumentality needs trust-building through transparent, consistent reward logic.

  Can valence be negative?

  Yes, and this is the point designers most often miss. Valence is how much the user values the outcome, which can be positive (they want it), zero (indifferent), or negative (they actively do not want it). A “reward” the user experiences as a punishment — public recognition for an introvert, travel for a new parent, a team lunch for someone with social anxiety — produces negative valence and motivates avoidance of the performance that would unlock it.

  How does Expectancy Theory differ from Maslow’s Hierarchy?

  Maslow’s Hierarchy is a content theory: it specifies what humans want, arranged in a five-level pyramid from physiological needs to self-actualization. Expectancy Theory is a process theory: it specifies how humans decide whether any given action will deliver what they want. Maslow tells you what rewards might matter; Vroom tells you whether the user currently believes your product will produce any of those rewards, and if not, which variable is at zero.

  Is Expectancy Theory still relevant in 2026?

  Yes. Six decades of empirical work have consistently supported the core multiplicative form. Van Eerde and Thierry’s 1996 meta-analysis of 77 studies found expectancy-theory variables correlating with work performance, effort, choice, and satisfaction at effect sizes comparable to any competing motivation framework. The theory travels well across industries, cultures, and time periods because it specifies the motivational process without committing on the content — a portability that most content theories cannot match.

  How does Expectancy Theory relate to Self-Efficacy Theory?

  Bandura’s self-efficacy construct is a deep specification of Vroom’s expectancy variable. Both describe the domain-specific subjective probability that effort will produce performance. Bandura added the four sources — mastery experiences, vicarious experiences, verbal persuasion, and physiological reappraisal — that build the belief. Use Vroom’s three-variable formula as the diagnostic, and use Bandura’s four sources as the engineering spec for raising the expectancy term specifically.

  How does Expectancy Theory relate to Octalysis?

  Expectancy Theory is the economic diagnostic inside the eight Octalysis Core Drives. The Core Drives specify what a user is motivated by; Vroom’s formula specifies whether the user’s current belief state will translate any given Core Drive into action. Expectancy maps onto CD2 (Development & Accomplishment). Instrumentality maps onto CD4 (Ownership & Possession) and CD5 (Social Influence). Valence maps onto CD1 (Epic Meaning) and CD5, with negative valence activating CD6 and CD8.

  What are the main limitations of Expectancy Theory?

  Three serious limits have emerged. First, the rationality assumption — the theory assumes users perform a multiplication they may not actually run consciously, which misses the systematic biases that behavioral economics has documented. Second, measurement reliability — self-report of subjective probabilities is noisy, which limits the precision of the theory’s predictions. Third, cultural specificity — the theory was developed in individualist American workplaces and predicts individual behavior more strongly in individualist than collectivist cultures, so applications in collective settings need a group-level supplement.

  References

  1. Vroom, V. H. (1964). Work and Motivation. John Wiley & Sons.
  2. Porter, L. W., & Lawler, E. E. (1968). Managerial Attitudes and Performance. Richard D. Irwin.
  3. Van Eerde, W., & Thierry, H. (1996). Vroom’s expectancy models and work-related criteria: A meta-analysis. Journal of Applied Psychology, 81(5), 575-586.
  4. Lawler, E. E. (1973). Motivation in Work Organizations. Brooks/Cole.
  5. Mitchell, T. R. (1974). Expectancy models of job satisfaction, occupational preference, and effort: A theoretical, methodological, and empirical appraisal. Psychological Bulletin, 81(12), 1053-1077.
  6. Pinder, C. C. (1998). Work Motivation in Organizational Behavior. Prentice Hall.
  7. Jenkins, G. D., Mitra, A., Gupta, N., & Shaw, J. D. (1998). Are financial incentives related to performance? A meta-analytic review of empirical research. Journal of Applied Psychology, 83(5), 777-787.
  8. Eylon, D., & Au, K. Y. (1999). Exploring empowerment cross-cultural differences along the power distance dimension. International Journal of Intercultural Relations, 23(3), 373-385.
  9. Tolman, E. C. (1932). Purposive Behavior in Animals and Men. Century.
  10. Lewin, K. (1938). The Conceptual Representation and the Measurement of Psychological Forces. Duke University Press.
  11. Atkinson, J. W. (1964). An Introduction to Motivation. Van Nostrand.
  12. Kanfer, R. (1990). Motivation theory and industrial and organizational psychology. In M. D. Dunnette & L. M. Hough (Eds.), Handbook of Industrial and Organizational Psychology (Vol. 1, pp. 75-170). Consulting Psychologists Press.
  13. Mitchell, T. R., & Daniels, D. (2003). Motivation. In W. C. Borman, D. R. Ilgen, & R. J. Klimoski (Eds.), Handbook of Psychology: Industrial and Organizational Psychology (Vol. 12, pp. 225-254). John Wiley & Sons.
  14. Locke, E. A., & Latham, G. P. (2004). What should we do about motivation theory? Six recommendations for the twenty-first century. Academy of Management Review, 29(3), 388-403.
  15. Schunk, D. H., & DiBenedetto, M. K. (2020). Motivation and social cognitive theory. Contemporary Educational Psychology, 60, 101832.

  Related Reading on yukaichou.com

  Five posts that extend the Expectancy Theory diagnostic into adjacent frameworks. Each one deepens a specific variable in the Vroom equation.

  • The Octalysis Complete Gamification Framework — the full 8 Core Drives map that gives every expectancy, instrumentality, and valence mechanic its underlying motivation architecture.
  • Self-Efficacy Theory: Bandura’s Belief in Ability — the deep specification of what Vroom called expectancy, with four sources for engineering the variable.
  • Goal-Setting Theory: Locke & Latham’s SMART Goals — the companion theory that tells you what kind of goal to write once Vroom tells you whether the user will pursue it.
  • Self-Determination Theory: Autonomy, Competence, Relatedness — the intrinsic-motivation framework that complements Vroom’s extrinsic diagnostic.
  • Prospect Theory: An S-Tier Behavioral Designer’s Guide to Loss Aversion — the framework that makes Vroom’s valence term asymmetric in the way real users actually experience it.

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

  Yukaichou.com Main Contact Form

  Δ

  Notify

  Name

  Email

  Organization

  Subject

  Your Message

  Ok, Let’s Do It. SEND!