The Three Needs Behind the Experience of Work
Workplace autonomy becomes easier to judge when it is separated from two other experiences that shape motivation: feeling capable of doing the work and feeling connected to the people around it. This chapter focuses on autonomy, competence, and relatedness as three distinct psychological needs, and gives the reader a way to diagnose which part of a work situation is being supported or undermined. The distinction matters because the same management practice can create choice while withholding mastery, or provide training while leaving someone isolated.
Three distinct jobs a workplace must make possible
Autonomy is the experience of volition and ownership: a person can understand the purpose of an action, exercise legitimate judgment, and recognize the action as their own. Competence is the experience of mastery and effectiveness: a person can make progress, use their abilities, and develop the capacity to handle future tasks. Relatedness is the experience of meaningful connection: a person feels affiliated with others and treated as a participant in a human relationship rather than as a replaceable input.
These definitions are related, but they are not three names for engagement. Consider a new analyst asked to redesign a reporting process. If their manager permits them to choose the format and explain the trade-offs, autonomy may be supported. If the analyst lacks access to the underlying data, examples of good work, or feedback on early drafts, competence may be undermined. If the team treats every question as an interruption and withholds context that colleagues already share, relatedness may be weak. The employee could therefore describe the assignment as “mine” while still feeling unable to do it and unwelcome in the group.
The reverse combination is possible too. A tightly standardized process may help a novice build competence through clear demonstrations and timely feedback, but it can still be experienced as controlling if every deviation is treated as disobedience. A friendly team may satisfy relatedness while offering little authority or opportunity to learn. More discretion may improve autonomy while increasing anxiety if the person is expected to make decisions without tools, training, or a safe way to correct course. The needs interact, but one cannot be used as a substitute for another.
This gives the model an important interface. The work context supplies demands, resources, leadership behavior, and social signals. The employee interprets those conditions through the three needs. The resulting experience is not simply a property of the job description. It is what the person can do, choose, and share within that context. A policy that looks neutral on paper can have different effects depending on whether it clarifies decision rights, builds skill, or changes who is available to help.
The diagram is deliberately not a one-way pipeline. A work context can shape each need differently, and each need can relate to different outcomes. A leader who grants discretion but gives no feedback may be supporting autonomy less effectively than they think because competence is left to chance. A training program that increases skill without giving people any say in how to apply it may improve effectiveness while leaving the motivational problem untouched. A team-building event cannot repair a work design that prevents colleagues from sharing information during the work itself.
Consider a company that introduces flexible scheduling to give employees more control over when they work. The change may support autonomy for someone who can now arrange focused time around a demanding task. It may undermine competence if handoffs become unpredictable and the person cannot get timely answers. It may weaken relatedness if the team loses the informal contact needed to notice problems or include a newcomer. The policy is not intrinsically supportive or unsupportive. Its effect depends on the interfaces around it: whether responsibilities remain clear, whether collaboration has a reliable channel, and whether people have enough information to use the discretion well.
The same reasoning applies to a promotion. A new title can increase autonomy by widening decision rights, but it can also create competence strain if the person is given accountability without training or authority. A manager who responds only with motivational language may miss the actual need: clearer role boundaries, access to a more experienced colleague, or permission to learn through reversible decisions. Relatedness can matter here too, because a newly promoted person may need to remain connected to former peers while establishing a different responsibility. One visible organizational change can therefore move the three needs in different directions.
The needs also interact over time. A competence failure may make a person less willing to exercise autonomy; repeated exclusion may reduce the confidence needed to ask for feedback; a controlling interaction may make a person interpret later guidance as pressure. Conversely, an early success with useful feedback can make a difficult choice feel manageable, and a supportive relationship can make it safer to admit what one does not yet know. These are plausible dynamics suggested by the theory and the diary evidence, not a complete feedback loop established by the reviewed studies. They show why diagnosis should ask what condition came first and what resources are available for recovery.
This is also why a single “engagement” score has limited diagnostic value. A high score may conceal an employee who is socially connected but exhausted by impossible demands. A low score may reflect a temporary loss of competence after a role change rather than a general rejection of the organization. If a manager responds to every low score with more recognition or more social activity, they may improve the wrong condition. The three-needs model asks a more useful question: what is missing in the relationship between this person and this work?
Conditions move the needs differently
The diary evidence makes the distinction concrete because it compares fluctuations within people. Across the studies, changing job demands generally moved with changing need satisfaction in a negative direction, especially for autonomy and relatedness. But competence was less uniform. Physical demands, stress, and conflict could be associated with lower competence satisfaction, while some demands were unrelated or even positively associated. The implication is not that all pressure is harmful. It is that what a demand requires, how it is appraised, and what resources accompany it can change its meaning.
A demand becomes a hindrance when it blocks progress without offering a plausible route to the goal: unclear role conflict, repeated administrative friction, avoidable interruption, or a workload that consumes the capacity needed to do the work well. Such a condition can reduce a person’s room for judgment, make mastery feel impossible, and strain relationships. A challenge demand is still effortful, but it can be experienced as an opportunity to use or extend capability when the person has adequate resources and understands what success requires. The same difficult project may therefore stimulate competence in one setting and erode it in another.
That difference is why “remove pressure” is a poor universal prescription. A surgical team, emergency service, or customer-support operation may have to respond quickly. The relevant questions are whether the urgency is intelligible, whether the people closest to the work can surface problems, whether the tools and staffing match the standard, and whether the pressure is used to coordinate action or to threaten identity. A fixed requirement can coexist with autonomy and competence support; an apparently flexible environment can undermine all three needs through ambiguity and neglect.
Imagine a product team approaching a release deadline. The deadline may restrict autonomy because the date cannot move, but the restriction does not determine the whole experience. If the team can decide how to sequence the remaining work, raise a risk without retaliation, and understand why the date matters, some ownership remains. If the work is repeatedly redefined at the last minute, competence may suffer because people cannot tell which standard they are trying to meet. If managers respond to the resulting delay by identifying a culprit rather than coordinating a solution, relatedness may suffer as well. The same deadline can therefore expose three different problems, each requiring a different response.
This also explains why a resource cannot be judged only by its label. “Autonomy” in a job design may mean useful discretion, or it may mean that the employee is responsible for solving problems that the organization has refused to resource. “Feedback” may provide information for improvement, or it may be a stream of status judgments. “Team support” may create genuine access to knowledge, or it may consist of occasional social events while everyday collaboration remains blocked. The model asks what the resource makes possible in the actual flow of work.
Job resources generally showed the opposite pattern in the diary review. Skill utilization, positive feedback, work-family enrichment, work-life balance, autonomy, and breaks were positively associated with need satisfaction, usually with small-to-medium effects and some exceptions. Resources matter because they change what a person can do with the demands already present. A break can restore capacity; feedback can make improvement possible; access to skill can turn a routine assignment into an occasion for mastery; social support can make a difficult problem shareable rather than private.
Organizational resources were especially visible in the form of leader behavior. Autonomy support and transformational leadership were positively associated with need satisfaction in the reviewed diary studies, often at medium size, while controlling communication was negatively associated. This does not mean that a supportive conversation is a magic intervention. It means that leadership is part of the work environment experienced by employees, not merely a layer of communication placed on top of it. The way a manager explains a change, responds to a mistake, or invites input can alter the practical conditions of choice, mastery, and connection.
The review suggests that organizational resources, particularly supportive leader behavior, appeared more important for varying need satisfaction than negative demands or employee factors. That is a useful direction for attention, but not a settled ranking. The studies were few and diverse, and many measured demands, resources, and need satisfaction at the same time. A manager should therefore treat the conclusion as a reason to inspect the social and organizational context, not as proof that reducing workload is unimportant or that every leader-development program will outperform work redesign.
Employee states and actions also belong in the picture without becoming an excuse to individualize the problem. Daily proactive behavior, striving, morning energy, and positive affect were generally associated with higher need satisfaction, often in small-to-medium relationships. Negative affect, anxiety, and fatigue before work were often unrelated to later need satisfaction. This could mean that supportive work conditions compensate for a poor morning, or that the negative states are related more to need frustration than to low need satisfaction. It could also reflect the limits of concurrent measurement. The evidence does not let us decide that the employee caused the experience or that the experience caused the employee’s behavior.
The distinction between satisfaction and frustration is especially important. Low satisfaction means that a need is not being fully met. Frustration means that the environment is actively thwarting or obstructing the need. A person who receives no useful feedback may feel uncertain about competence. A person whose attempts to learn are mocked or deliberately blocked may experience competence frustration. A team that happens not to socialize much is not identical to a team that excludes someone from information and belonging. These conditions can have different antecedents and different consequences, so treating frustration as merely a low score loses information.
A practical diagnosis can therefore proceed by asking three different questions. Does this person have legitimate ownership over an intelligible part of the work? Can they develop and demonstrate effectiveness with the available tools, information, and feedback? Do they experience reliable connection, inclusion, and respect while doing it? The answers may diverge, and that divergence is useful. It tells a manager whether to clarify purpose and decision rights, repair the learning path and resources, or address the social relationship rather than applying a generic engagement solution.
The three needs do not turn workplace experience into a checklist. They identify different interfaces through which work conditions become motivation. Once those interfaces are visible, the next problem is to trace how need experiences relate to autonomous or controlled motivation and, from there, to outcomes such as engagement, well-being, performance, burnout, and turnover.