Self-Determination Theory

What is Self-Determination Theory?

Self-Determination Theory, often shortened to SDT, is a theory of human motivation. It explains how people become more motivated, engaged, and satisfied when three basic psychological needs are supported: autonomy, competence, and relatedness.

In simple terms, people are more likely to stay motivated when they feel:

• Autonomy: “I have meaningful choice.”
• Competence: “I can do this and improve.”
• Relatedness: “I feel connected to other people.”

Self-Determination Theory is used in psychology, education, healthcare, work, product design, and user experience. For product teams, SDT is useful because it gives designers and product managers a practical way to think about motivation beyond rewards, badges, points, or reminders.

A product that supports autonomy, competence, and relatedness is more likely to help users feel in control, capable, and connected.

Self-Determination Theory definition

Self-Determination Theory is a motivation theory that explains how human behavior is shaped by the fulfillment of three basic psychological needs: autonomy, competence, and relatedness.

The theory was developed by psychologists Edward L. Deci and Richard M. Ryan. It argues that people are not only motivated by external rewards or punishments. People are also motivated by interest, growth, meaning, connection, and the desire to become more capable.

In SDT, motivation is not just a question of how much motivation someone has. It is also a question of what kind of motivation they have.

For example:

• A user may complete a task because they enjoy it.
• A learner may continue because they feel progress.
• An employee may contribute because the work feels meaningful.
• A customer may return because the product helps them feel capable or connected.

These are different from motivation based only on pressure, fear, rewards, or obligation.

What does SDT stand for?

SDT stands for Self-Determination Theory.

The abbreviation is often used in psychology, motivation research, education, workplace motivation, and UX design.

The terms SDT, SDT theory, Self Determination Theory, and Self-Determination Theory usually refer to the same framework.

The Self-Determination Theory model

The Self-Determination Theory model is built around three psychological needs:

SDT need	Meaning	Product-design question
Autonomy	Feeling that you have meaningful choice and control	How can users make meaningful choices?
Competence	Feeling capable, effective, and able to improve	How can users feel progress and mastery?
Relatedness	Feeling connected, included, or understood	How can users feel part of something or supported by others?

When these needs are supported, people are more likely to experience intrinsic motivation, engagement, persistence, and well-being. When these needs are blocked, people may become disengaged, frustrated, or dependent on external pressure.

The three needs in Self-Determination Theory

Self-Determination Theory is best known for its three basic psychological needs: autonomy, competence, and relatedness.

These needs are not the same as preferences. In SDT, they are treated as basic conditions that support motivation and well-being.

1. Autonomy

Autonomy is the need to feel that your actions are self-directed. It does not mean total independence or unlimited choice. It means people feel that they have agency, control, and meaningful participation in what they are doing.

In product design, autonomy is supported when users can make choices that matter.

Examples of autonomy in UX:

• Letting users choose notification preferences.
• Allowing users to customize their experience.
• Giving users control over privacy settings.
• Explaining why a step is required.
• Making it easy to opt out, skip, edit, or undo.
• Avoiding forced flows when a lighter path would work.
• Letting users choose goals, topics, filters, or difficulty.

Autonomy can be harmed when users feel forced, manipulated, trapped, or over-controlled.

Examples that reduce autonomy:

• Dark patterns.
• Forced account creation too early.
• Hidden cancellation paths.
• Unclear consent.
• Overly rigid onboarding.
• Too many mandatory steps.
• Defaults that are hard to change.

For product teams, a useful autonomy question is:

How can we give users meaningful control without overwhelming them?

Design patterns that support autonomy

Product teams can support autonomy through:

• Meaningful choice: Give users options that affect their experience.
• Customization: Let users adjust settings, layouts, preferences, or goals.
• Clear defaults: Provide helpful defaults while keeping them editable.
• Transparent explanations: Explain why information or actions are needed.
• Undo and edit options: Help users feel safe making choices.
• Progressive disclosure: Reveal complexity only when it becomes useful.

Autonomy is not about adding more options everywhere. Too many choices can create decision fatigue. The goal is to give users the right choices at the right time.

2. Competence

Competence is the need to feel capable and effective. People feel competent when they understand what to do, can make progress, and can improve through action.

In UX and product design, competence is supported when users can complete tasks with confidence.

Examples of competence in UX:

• Clear onboarding.
• Immediate feedback.
• Helpful error messages.
• Progress indicators.
• Milestones and achievements.
• Good empty states.
• Tutorials that appear when needed.
• Tasks that match the user’s current skill level.
• A clear path from beginner to advanced use.

Competence can be harmed when the product is confusing, inconsistent, too difficult, or gives poor feedback.

Examples that reduce competence:

• Unclear labels.
• Jargon-heavy interfaces.
• Errors without explanations.
• Hidden progress.
• No confirmation after important actions.
• Tasks that are too complex too early.
• Interfaces that make users feel like they failed.

A useful competence question is:

How can we help users feel capable, successful, and able to improve?

Design patterns that support competence

Product teams can support competence through:

• Feedback: Show users what happened after they act.
• Progress indicators: Make progress visible.
• Appropriate challenges: Match task difficulty to user skill.
• Guided workflows: Break complex tasks into manageable steps.
• Helpful constraints: Prevent errors before they happen.
• Recognition: Acknowledge meaningful progress.
• Learning loops: Help users understand, act, receive feedback, and improve.

Competence is especially important in products that require learning, behavior change, productivity, or long-term engagement.

3. Relatedness

Relatedness is the need to feel connected to other people. It includes belonging, care, recognition, and meaningful social connection.

In product design, relatedness is supported when users feel seen, supported, or connected to a community.

Examples of relatedness in UX:

• Collaboration features.
• Comments and replies.
• Groups and communities.
• Shared goals.
• Peer support.
• Team spaces.
• Recommendations from people with similar needs.
• Social recognition.
• Human support at important moments.

Relatedness can be harmed when users feel isolated, ignored, judged, or treated as interchangeable.

Examples that reduce relatedness:

• Empty communities.
• Toxic social features.
• Unhelpful automated support.
• No visible human presence.
• Generic messaging that does not match the user’s situation.
• Social comparison that creates pressure instead of connection.

A useful relatedness question is:

How can we help users feel connected, supported, or understood?

Design patterns that support relatedness

Product teams can support relatedness through:

• Community spaces: Help users connect around shared goals.
• Collaboration: Let users work together.
• Social proof: Show that others have faced similar situations.
• Human support: Provide access to help when it matters.
• Shared progress: Let people see team or group progress.
• Recognition: Help users feel noticed in meaningful ways.
• Belonging cues: Use language and examples that reflect the user’s context.

Relatedness does not mean every product needs a social network. In many products, relatedness can be supported through tone, support, shared context, or thoughtful communication.

Self-Determination Theory and motivation

Self-Determination Theory explains motivation as a continuum. This continuum ranges from amotivation to extrinsic motivation to intrinsic motivation.

The important idea is that motivation can become more or less self-determined.

At one end, people may feel no motivation at all. At the other end, people act because they find the activity interesting, meaningful, or satisfying.

The Self-Determination Theory continuum

The Self-Determination Theory continuum describes different types of motivation.

Type of motivation	Meaning	Example
Amotivation	No intention or motivation to act	A user abandons onboarding because they do not see the point
External regulation	Acting for rewards or to avoid punishment	A user completes a task only to earn a coupon
Introjected regulation	Acting from pressure, guilt, or ego	A user continues because they feel bad about stopping
Identified regulation	Acting because the goal feels personally important	A user tracks spending because financial control matters to them
Integrated regulation	Acting because the behavior fits personal values and identity	A user exercises because health is part of how they see themselves
Intrinsic motivation	Acting because the activity itself is interesting or satisfying	A user learns a language because they enjoy the learning process

This continuum is useful for product teams because it shows that external rewards are not the only way to motivate behavior.

A product can help users move toward more self-determined motivation by supporting autonomy, competence, and relatedness.

Intrinsic vs. extrinsic motivation in SDT

Self-Determination Theory distinguishes between intrinsic motivation and extrinsic motivation.

Intrinsic motivation

Intrinsic motivation means doing something because the activity itself is interesting, satisfying, or enjoyable.

Examples:

• Learning because the topic is interesting.
• Exercising because movement feels good.
• Designing because solving the problem is satisfying.
• Using a creative tool because the process is engaging.

Intrinsic motivation is often associated with persistence, creativity, and deeper engagement.

Extrinsic motivation

Extrinsic motivation means doing something because of an outcome separate from the activity itself.

Examples:

• Completing a course to earn a certificate.
• Using an app to receive a discount.
• Finishing a task to avoid a penalty.
• Posting content to gain recognition.

Extrinsic motivation is not always bad. It can help users get started, complete necessary tasks, or build habits. The risk is over-reliance on external rewards.

If a product depends only on points, badges, streaks, or discounts, users may stop when the reward disappears.

Balancing intrinsic and extrinsic motivation

Product teams should use extrinsic rewards carefully.

Good extrinsic motivators support autonomy and competence. Poor extrinsic motivators can make users feel controlled.

For example:

• A badge that recognizes real progress can support competence.
• A forced streak that makes users feel guilty can reduce autonomy.
• A reward that helps users choose their next goal can support autonomy.
• A reward that distracts from the real value of the product can weaken intrinsic motivation.

A useful product question is:

Are our rewards supporting user motivation, or replacing it?

Amotivation in Self-Determination Theory

Amotivation is a state where a person has little or no intention to act. The person may not see value in the activity, may not feel capable, or may not believe the action will lead to a useful outcome.

In product design, amotivation often appears as abandonment, low activation, low engagement, or churn.

Common causes of amotivation include:

• The user does not understand the value of the product.
• The product does not match the user’s goal.
• The first experience is too hard.
• The interface is confusing.
• Progress is invisible.
• Feedback is missing.
• The user feels forced into steps they do not understand.
• The product uses too much jargon.
• The user does not trust how their data will be used.
• The product asks for too much before giving value.

To reduce amotivation, product teams should make the value clear, reduce unnecessary effort, show progress, and help users experience early success.

Applying Self-Determination Theory in product design

Self-Determination Theory can help product teams design products that support better motivation and engagement.

Instead of asking only, “How do we get users to do this?”, SDT encourages teams to ask:

• How can we support autonomy?
• How can we help users feel competent?
• How can we create relatedness?
• Are we relying too much on external rewards?
• Are we making users feel controlled?
• Are we helping users connect the product to their own goals?

Designing for autonomy

To support autonomy, give users meaningful control.

Practical ways to design for autonomy:

• Let users set preferences.
• Let users choose goals.
• Allow users to skip or delay nonessential steps.
• Explain why a task matters.
• Make consent clear.
• Avoid manipulative defaults.
• Let users undo or revise important actions.
• Give users control over notifications.
• Avoid locking users into one path too early.

Example: A music app that lets users create playlists, choose discovery settings, and adjust recommendations supports autonomy because users can shape their own experience.

Designing for competence

To support competence, help users feel capable.

Practical ways to design for competence:

• Use clear labels.
• Give immediate feedback.
• Show progress.
• Break complex tasks into steps.
• Provide examples.
• Use helpful error messages.
• Let users practice safely.
• Give users tasks that match their current ability.
• Celebrate meaningful progress without making the product feel childish.

Example: A language learning app that gives immediate feedback, tracks progress, and increases difficulty gradually supports competence.

Designing for relatedness

To support relatedness, help users feel connected or understood.

Practical ways to design for relatedness:

• Provide human support when users are stuck.
• Show examples from people like the user.
• Create spaces for collaboration or peer feedback.
• Let users share progress when appropriate.
• Use inclusive language.
• Help teams work together.
• Build community features only when they serve a real user need.
• Avoid social comparison that creates pressure.

Example: A professional network supports relatedness when it helps users connect with peers, join relevant groups, and receive useful recognition.

Real-world examples of Self-Determination Theory

Self-Determination Theory can be seen in many everyday products.

Slack supports autonomy

Slack supports autonomy by letting users create channels, manage notification preferences, use threads, integrate tools, and choose how they communicate.

These choices help users adapt the product to the way their team works.

Duolingo supports competence

Duolingo supports competence through short lessons, clear progression, immediate feedback, and increasing difficulty.

Users can see progress and build skill over time, which helps them feel capable.

LinkedIn supports relatedness

LinkedIn supports relatedness by helping people connect, join professional communities, share updates, and receive recognition.

The product is built around professional connection and belonging.

Fitbit combines autonomy, competence, and relatedness

Fitbit supports autonomy by letting users set personal goals. It supports competence by showing progress, activity trends, and achievements. It supports relatedness through challenges, sharing, and social features.

This combination can help users stay engaged with long-term behavior change.

Self-Determination Theory in UX research

SDT can also guide UX research.

When researching motivation, ask questions that reveal whether autonomy, competence, and relatedness are supported or blocked.

Questions about autonomy

• Do users feel in control?
• Do they understand why they are being asked to do something?
• Do they feel forced into a path?
• Do they have meaningful choices?
• Are defaults helpful or restrictive?

Questions about competence

• Do users understand what to do next?
• Do they know whether they are making progress?
• Do they feel capable of completing the task?
• Where do they feel confused or stuck?
• What feedback do they expect?

Questions about relatedness

• Do users feel supported?
• Do they feel understood by the product?
• Do they want help from peers, experts, or teammates?
• Does social interaction improve the experience or add pressure?
• Where would human support matter most?

These questions help product teams understand motivation beyond surface-level behavior.

Self-Determination Theory in product management

Product managers can use SDT to make better decisions about engagement, retention, onboarding, and feature prioritization.

Onboarding

A good onboarding experience should support autonomy and competence.

It should help users understand the value of the product, make meaningful choices, and reach an early success point.

Retention

Retention improves when users continue to experience value. SDT helps teams look beyond reminders and incentives by asking whether the product helps users feel capable, in control, and connected.

Feature prioritization

SDT can help product teams evaluate whether a feature supports real motivation.

Ask:

• Does this feature give users meaningful control?
• Does it help users become more capable?
• Does it help users feel connected or supported?
• Does it rely on pressure or manipulation?
• Does it support long-term engagement or only short-term activity?

Metrics

SDT can connect to product metrics such as:

• Activation rate
• Engagement rate
• Task completion rate
• Retention
• User satisfaction
• Feature adoption
• Community participation
• Churn
• Support requests

The point is not to measure autonomy, competence, and relatedness directly in every product. The point is to understand which user needs may be driving the metrics.

Self-Determination Theory limitations

Self-Determination Theory is useful, but it should not be applied too rigidly.

It can oversimplify motivation

Human motivation is complex. Autonomy, competence, and relatedness are important, but they are not the only factors that shape behavior.

Context, identity, culture, habits, incentives, constraints, and life circumstances also matter.

Autonomy can mean different things in different contexts

Some users want many choices. Others want guidance. Some cultures and work environments place more emphasis on group goals, duty, or shared responsibility.

Designers should not assume that autonomy always means more options.

Relatedness can be positive or negative

Social features can support belonging, but they can also create comparison, pressure, exclusion, or harmful behavior.

Not every product needs social features.

Extrinsic rewards can be useful

SDT often warns against over-reliance on external rewards, but rewards are not automatically bad.

Rewards can help users start, learn, or complete difficult tasks if they support autonomy and competence.

Measuring psychological needs is difficult

It can be hard to know whether a product truly supports autonomy, competence, or relatedness. Teams should combine SDT with user research, behavioral data, and product experiments.

Self-Determination Theory vs. Flow Theory

Self-Determination Theory and Flow Theory are related, but they focus on different things.

Self-Determination Theory explains motivation through autonomy, competence, and relatedness.

Flow Theory describes a state of deep focus and engagement when challenge and skill are well matched.

They often work together. A product that supports competence and provides appropriate challenge may make flow more likely.

For example, a learning product can use SDT to support motivation and Flow Theory to design tasks that are neither too easy nor too hard.

Self-Determination Theory vs. behaviorism

Self-Determination Theory differs from behaviorist approaches that focus mainly on rewards and punishments.

Behaviorism looks at how external reinforcement shapes behavior.

SDT looks at the quality of motivation and whether people feel autonomous, competent, and connected.

For product teams, this difference matters. A product can drive short-term behavior with external rewards, but long-term engagement often depends on whether users find the experience meaningful, useful, and satisfying.

How to use SDT as a product checklist

Use this checklist when designing or improving a product experience.

Autonomy checklist

• Can users make meaningful choices?
• Can users change preferences?
• Are users told why steps are required?
• Can users undo or edit important actions?
• Are defaults helpful and transparent?
• Are we avoiding manipulative patterns?

Competence checklist

• Is the next step clear?
• Do users get feedback after taking action?
• Is progress visible?
• Are tasks matched to user skill level?
• Are error messages helpful?
• Can users recover from mistakes?

Relatedness checklist

• Do users feel supported?
• Is help available when it matters?
• Does the tone feel human and respectful?
• Are social features useful rather than distracting?
• Can users connect with peers, teammates, or experts where relevant?
• Does the product help users feel understood?

Motivation checklist

• Are we relying too much on rewards, streaks, or pressure?
• Does the experience connect to the user’s own goals?
• Are users likely to feel progress?
• Are users likely to feel in control?
• Are users likely to return because the product is useful, not just because they were prompted?

Frequently asked questions about Self-Determination Theory

What is Self-Determination Theory?

Self-Determination Theory is a theory of motivation that explains how autonomy, competence, and relatedness influence behavior, engagement, well-being, and performance.

What does SDT stand for?

SDT stands for Self-Determination Theory.

What are the three needs in Self-Determination Theory?

The three basic psychological needs in Self-Determination Theory are autonomy, competence, and relatedness.

What is autonomy in Self-Determination Theory?

Autonomy is the need to feel that your actions are self-directed. In product design, autonomy can be supported through meaningful choice, control, transparency, and the ability to adjust the experience.

What is competence in Self-Determination Theory?

Competence is the need to feel capable and effective. In product design, competence can be supported through clear feedback, visible progress, helpful guidance, and tasks that match the user’s ability.

What is relatedness in Self-Determination Theory?

Relatedness is the need to feel connected to others. In product design, relatedness can be supported through collaboration, community, human support, shared progress, and respectful communication.

What is an example of Self-Determination Theory?

A language learning app can apply Self-Determination Theory by letting users choose goals, showing progress as they improve, and connecting them with other learners. This supports autonomy, competence, and relatedness.

What is the Self-Determination Theory continuum?

The Self-Determination Theory continuum describes motivation from amotivation to extrinsic motivation to intrinsic motivation. It shows how motivation can become more self-determined as people find value, meaning, or enjoyment in an activity.

What is the difference between intrinsic and extrinsic motivation in SDT?

Intrinsic motivation means doing something because the activity itself is satisfying. Extrinsic motivation means doing something for an external outcome, such as a reward, recognition, or avoiding a penalty.

How is Self-Determination Theory used in UX design?

UX designers use Self-Determination Theory to create experiences that support user autonomy, competence, and relatedness. This can improve onboarding, engagement, retention, and user satisfaction.

How is Self-Determination Theory used in product management?

Product managers can use SDT to evaluate whether features help users feel in control, capable, and connected. It can also guide decisions about onboarding, engagement, retention, and community features.

What are the strengths of Self-Determination Theory?

Self-Determination Theory is useful because it explains different types of motivation, not just the amount of motivation. It also gives teams a practical framework for supporting engagement through autonomy, competence, and relatedness.

What are the limitations of Self-Determination Theory?

Limitations include the risk of oversimplifying motivation, difficulty measuring psychological needs, and the need to account for culture, context, incentives, habits, and social conditions.

Is Self-Determination Theory the same as self-determination?

No. Self-determination can refer broadly to a person’s ability to make choices and control their own life. Self-Determination Theory is a specific psychological theory of motivation developed by Edward Deci and Richard Ryan.

Summary

Self-Determination Theory explains motivation through three basic psychological needs: autonomy, competence, and relatedness.

People are more likely to stay motivated when they feel they have meaningful choice, can make progress, and feel connected to others.

For product teams, SDT is useful because it helps explain why users engage, return, learn, contribute, or abandon a product. Instead of relying only on external rewards, teams can design experiences that help users feel in control, capable, and supported.