Self-Determination Theory: The Three Things Every Brain Needs to Stay Motivated

In the late 1970s, Edward Deci was running experiments at the University of Rochester that made his colleagues uncomfortable. The prevailing wisdom in psychology, and in virtually every management textbook, was simple: if you want people to do something, reward them. Pay more, get more. Incentivize the behavior you want and punish the behavior you don't. The entire architecture of corporate compensation, from sales commissions to stock options, rested on this assumption.

Deci's experiments kept producing the opposite result.

In one of his early studies, published in 1971 in the Journal of Personality and Social Psychology, Deci gave college students a set of Soma puzzles, interlocking plastic cubes that can be assembled into various configurations. During a "free choice" period, when participants were told the experiment was paused and they could do whatever they wanted, Deci measured whether they continued playing with the puzzles voluntarily. The group that had been paid to solve puzzles during the experimental phase spent significantly less time playing with them during the free period than the group that had never been paid. Paying people to do something they already enjoyed made them enjoy it less.

Over the next two decades, Deci and his colleague Richard Ryan built these findings into a comprehensive framework they called Self-Determination Theory, or SDT. Published across hundreds of papers and formalized in their 2000 article in American Psychologist, the theory identified three fundamental psychological needs that, when satisfied, produce sustained intrinsic motivation, well-being, and high performance. When thwarted, the same three needs produce disengagement, burnout, and the quiet deterioration that kills startups from the inside. The three needs are autonomy, competence, and relatedness. And if you're running a company, they explain more about your team's performance, your customers' loyalty, and your own founder burnout trajectory than any compensation structure ever will.

Autonomy Is Not Independence

The most misunderstood need in Self-Determination Theory is autonomy, because most people confuse it with independence. Autonomy doesn't mean working alone, making all your own decisions, or being free from oversight. In Deci and Ryan's framework, autonomy means experiencing your actions as volitional. You feel autonomous when you believe your behavior reflects your own values and choices, not when you're free from other people, but when you're free from coercion.

The distinction matters enormously for how you build a company.

A 2005 meta-analysis by Marylène Gagné and Edward Deci, published in the Journal of Organizational Behavior, synthesized decades of workplace motivation research through the SDT lens. The findings were consistent across industries and cultures: employees who experienced autonomy support from managers, meaning their managers acknowledged their perspectives, offered choices within constraints, and provided rationale for decisions rather than simply issuing directives, showed higher job satisfaction, stronger organizational commitment, better psychological well-being, and superior performance. The size of the effect was not trivial. Autonomy support predicted performance outcomes more strongly than pay level in multiple studies.

Google's famous "20% time" policy, which allowed engineers to spend one day per week on projects of their own choosing, was a direct autonomy intervention. Gmail, Google News, and AdSense all emerged from 20% time projects. The policy didn't give engineers independence. They still worked within Google's infrastructure, used Google's tools, and operated under Google's broader strategic direction. What it gave them was volition: the experience that a significant portion of their professional life was self-directed.

Atlassian ran a similar experiment they called "ShipIt Days" (originally "FedEx Days," because participants had to deliver something overnight). Engineers got twenty-four hours to work on any project they wanted, with the only requirement being a demo at the end. The company reported that the feature ideas generated during ShipIt Days outperformed those generated through their standard product planning process. The mechanism wasn't that engineers worked harder without management direction. It was that autonomy activated a motivational system that management direction suppresses.

For founders, the autonomy finding creates an uncomfortable tension. Startups move fast. Resources are thin. The instinct to centralize decisions, to maintain control over every product detail and every strategic choice, is strong and often justified. But the research is unambiguous: every decision you make for your team that they could have made for themselves is an autonomy withdrawal. Make enough of those withdrawals and the motivational account runs dry, regardless of how much you're paying them.

Competence: The Mastery Loop

The second need in SDT is competence: the experience of being effective, of growing in capability, of mastering challenges that are neither too easy nor too hard.

Deci and Ryan drew heavily on the earlier work of Robert White, a Harvard psychologist who published a landmark paper in 1959 in Psychological Review arguing that humans have an innate drive toward "effectance," the desire to produce effects on the environment and to experience oneself as capable. White's insight was that this drive was independent of basic biological needs. Rats explore new environments even when they're not hungry. Children manipulate objects for the sheer pleasure of seeing them respond. The motivation to master the environment isn't a means to an end. It's an end in itself.

Mihaly Csikszentmihalyi's research on flow states, published across several books beginning with Flow: The Psychology of Optimal Experience in 1990, mapped the conditions under which competence produces its most intense motivational effects. The key was the ratio between challenge and skill. When challenge exceeds skill by too much, the result is anxiety. When skill exceeds challenge by too much, the result is boredom. When the two are matched, with challenge slightly exceeding current capability, the person enters a flow state: deep concentration, loss of self-consciousness, distorted time perception, and intrinsic reward so strong it overrides external incentives.

The competence need explains a pattern that baffles many founders: why talented employees leave well-paying jobs at stable companies to join risky startups at lower salaries. The SDT framework predicts this. A stable company where your role is well-defined and your skills exceed the challenge creates competence deprivation. The employee isn't bored because the work is bad. They're bored because the work no longer stretches their capabilities. The risky startup, with its undefined roles and problems that exceed current skill, offers what the stable company can't: the competence loop of challenge, effort, growth, and mastery.

For the same reason, the competence need explains why micromanagement is so destructive beyond its effect on autonomy. When a manager prescribes not just what should be done but how it should be done, the employee's experience of competence is undermined. They're not mastering anything. They're executing instructions. The motivational distinction between "I figured out how to solve this" and "I was told how to solve this" is the difference between competence satisfaction and competence frustration, even when the outcome is identical.

Does Relatedness Explain Why Remote Teams Struggle?

The third need, relatedness, is the one most founders underestimate. Relatedness is the need to feel connected to others, to care and be cared for, to experience belonging within a group. It sounds soft. The research says it's structural.

In 2018, a Gallup meta-analysis of 339 research studies across 230 organizations found that the single strongest predictor of employee engagement wasn't compensation, career advancement, or job fit. It was having a "best friend at work." Employees who strongly agreed with the statement "I have a best friend at work" were seven times more likely to be engaged, had higher customer satisfaction scores, and were significantly less likely to leave. The phrase "best friend" sounds like a Hallmark card. The performance implications look like a strategic advantage.

Baumeister and Leary published a seminal 1995 paper in Psychological Bulletin titled "The Need to Belong," which argued that the need for interpersonal connection is as fundamental as the need for food. They reviewed evidence across cultural anthropology, developmental psychology, clinical research, and evolutionary biology, all pointing to the same conclusion: humans who are socially isolated show the same stress responses, cognitive declines, and health deteriorations as humans who are deprived of physical necessities. The brain treats social disconnection as a threat to survival, because for most of human evolutionary history, it was exactly that.

This is the neuroscience behind why fully remote teams face a motivation challenge that no amount of compensation or autonomy can solve. Remote work satisfies autonomy powerfully. It can satisfy competence if the work is challenging. But relatedness requires repeated, unstructured, emotionally resonant interaction, the kind that happens in hallways, at lunch, and during the conversations that have no agenda. Slack channels and Zoom calls transmit information. They transmit belonging poorly.

The SDT framework doesn't say remote work can't work. It says remote work creates a relatedness deficit that must be deliberately compensated for. The companies that thrive remotely, like GitLab and Automattic, invest heavily in in-person gatherings, social rituals, and structural practices designed to create the belonging that physical proximity provides automatically. They're not doing this because it's nice. They're doing it because Self-Determination Theory predicts that a team with high autonomy, high competence, and low relatedness will eventually burn out, disengage, or fracture.

The SDT Audit for Founders: Are You Running on All Three?

The most dangerous application of SDT isn't about your team. It's about you.

Founder burnout is typically discussed in terms of workload: too many hours, too much stress, too little sleep. SDT offers a different diagnosis. Burnout occurs when one or more of the three fundamental needs is chronically thwarted, regardless of workload. A founder who works eighty hours a week on problems they've chosen, that stretch their capabilities, alongside people they trust, may be exhausted but not burned out. A founder who works forty hours a week on tasks imposed by investors, that no longer challenge them, in isolation from meaningful relationships, will burn out no matter how reasonable the hours look on paper.

Deci and Ryan's research, extended by Maarten Vansteenkiste and colleagues in a 2007 paper in the Journal of Research in Personality, showed that pursuing goals that don't align with your fundamental psychological needs produces what the researchers called "ill-being" even when the goals are achieved. Founders who optimize for metrics they don't care about, who build products that don't interest them, or who maintain partnerships that drain rather than energize them, are building toward a burnout that has nothing to do with time management. The three needs framework offers a diagnostic: when motivation disappears, check which of the three is being starved.