Alderfer's ERG Theory of Motivation: Existence, Relatedness, Growth

Turn this article into takeaways for your work.

Each assistant summarizes the article only for you and suggests best practices for your work.

Alderfer's ERG theory is a motivation framework that sorts human needs into three groups: existence (physical and material security), relatedness (relationships with other people), and growth (development and meaningful contribution). Unlike a strict ladder, the needs can be active at once, and a person blocked at a higher need may fall back to a lower one.

Most managers meet motivation theory as a list of categories to memorize. ERG is more useful than that, because it describes what people do when something gets in their way. Someone who can't grow in a role doesn't just sit there. They start caring more about pay, or about their coworkers, or about leaving. If you know which need is under pressure, you can respond to the real problem instead of the visible symptom.

What Is ERG Theory?

Key Facts

Clayton Alderfer, an American psychologist and organizational consultant, built ERG as a direct revision of Maslow. He kept the intuition that people have different kinds of needs and rebuilt the structure so it fit what he saw at work. The name is just the three categories: Existence, Relatedness, Growth.

The shift from five levels to three isn't only a simplification. Alderfer argued that the needs sit on a continuum from concrete to abstract rather than on rungs of a ladder. Existence is the most concrete. Growth is the most abstract, because it doesn't depend on anything physical (Penn State World Campus). That framing matters in practice: a person can pursue several of them in the same week, and the order can differ from one person to the next.

The Three Needs

Each category covers a different kind of workplace concern. The table maps them to Maslow's levels and to everyday signals a manager can observe.

ERG Need What It Covers Maslow Equivalent What It Looks Like at Work
Existence Pay, benefits, physical safety, job security, working conditions Physiological and safety Questions about compensation, workload that threatens health, anxiety after layoffs
Relatedness Relationships with peers, managers, customers, and friends Social Wanting to be heard, team belonging, conflict with a colleague, isolation when remote
Growth Developing skills, creative or productive contribution, self-direction Esteem (internal) and self-actualization Asking for stretch work, wanting a bigger scope, boredom with repetitive tasks

The mapping is approximate. The Penn State summary pairs existence with physiological and safety needs, relatedness with social needs, and growth with esteem and self-actualization (Penn State World Campus). In real teams the categories overlap. A raise is an existence matter, but it can also feel like recognition, which is relatedness and growth.

Existence. These are the needs that keep a person able to work at all: a living wage, a safe workplace, some confidence the job will exist next quarter. When existence is shaky, nothing else gets much attention.

Relatedness. People want to matter to the people around them. That includes respect from a boss, trust among teammates, and the sense that colleagues know who you are. It also covers relationships outside work that the job helps or harms, like time with family.

Growth. This is the desire to become more capable and to have an effect on the work and the people around you. It's the most personal of the three, since two people can read the same job description and want entirely different things from it.

How ERG Differs from Maslow's Hierarchy

Alderfer rejected the strict ladder. He argued that needs can operate at the same time and that their order can vary by culture or personal preference, and he criticized Maslow for treating all workers as alike (EBSCO Research Starters). That makes ERG more flexible, and it matches what most managers see: a well-paid person can still be starved for connection, and a poorly paid person can still chase growth.

The real addition is the regression idea, covered in the next section. Maslow described movement upward as needs are satisfied. ERG also describes movement downward when progress is blocked.

Frustration-Regression: What Happens When Growth Is Blocked

Frustration-regression is the part of ERG that makes it useful for diagnosis. The principle says that when a person can't satisfy a higher need, that frustration can increase the pull of a lower, more concrete need. The Penn State example is an employee with no chance to advance who looks for satisfaction in social contact with coworkers instead (Penn State World Campus). If that route is blocked too, they may fall back further.

The same source describes two exceptions to the pattern: unmet existence needs tend to intensify existence needs, and fulfilled growth needs tend to intensify growth needs. In other words, going hungry makes you think about food, and a taste of real development makes you want more of it.

Here's how the pattern tends to show up in a team. These are illustrative scenarios, not research findings.

What Gets Blocked What You Might Notice A Likely Regression Better Response
Growth (no path to a bigger role) A strong performer suddenly focuses on salary and title Toward existence or relatedness Talk about a development path before negotiating pay
Relatedness (a manager who doesn't listen) Rising demands about compensation and perks Toward existence Fix the relationship, not the pay band
Growth (work has become routine) More socializing, less initiative Toward relatedness Add scope or a new problem to solve
Existence (job insecurity) Narrow focus on protecting current status, little appetite for risk Existence intensifies Give straight information about the outlook

The practical lesson: a request for more money is not always a request for more money. Sometimes it's the visible edge of a growth need that has nowhere else to go. If you answer with a raise and the underlying problem stays, you'll hear the same request again in six months.

ERG vs Herzberg vs McClelland

ERG sits in a family of need-based theories. They answer different questions, so leaders get more from combining them than from picking a favorite.

Theory Core Claim What It Helps You Diagnose Weak Spot
ERG (Alderfer) Three needs, active at the same time, with regression when blocked What a blocked person is falling back on Hard to measure the needs precisely
Maslow's hierarchy Five needs satisfied in rising order Which category of need is missing Rigid order that people often don't follow
Herzberg's two-factor theory Hygiene factors prevent dissatisfaction; motivators create satisfaction Whether the issue is a problem to fix or an engagement to build Treats dissatisfaction and satisfaction as separate scales
McClelland's needs theory People differ in their drive for achievement, affiliation, and power Which stable motive fits which role Describes motive strength, not what to do when blocked

A useful shortcut: ERG tells you what happens when needs are thwarted, McClelland tells you who wants what, and Herzberg tells you which parts of the job to redesign. ERG's relatedness and growth categories line up loosely with McClelland's affiliation and achievement, though they aren't the same idea.

How to Apply ERG Theory: A Step-by-Step Process

You don't need a survey to use ERG. You need a few honest conversations and a habit of looking one level beneath the request.

  1. Notice the signal. Start with a change in behavior: a new focus on pay, withdrawal from the team, a drop in initiative, a stream of complaints about small things. Don't interpret yet.
  2. Ask open questions. "What would make the next six months feel worthwhile for you?" and "What's getting in the way?" reveal more than "Are you happy?" Listen for words about money and security (existence), people and recognition (relatedness), and skills and scope (growth).
  3. Name the likely active need. Write one line: "Primary need under pressure: growth. Currently expressing as: pay concerns." This step is where regression becomes visible.
  4. Check for a blocked higher need. Ask whether the person has a route to the next level of need. If growth looks closed, expect the lower needs to get louder.
  5. Pick a response that matches the need. Fix existence problems with fair pay and stable conditions. Address relatedness with real feedback, inclusion, and manager time. Address growth with stretch assignments, training, and decision rights.
  6. Remove the block, not just the symptom. If the cause is a stalled career path, a one-time bonus won't hold. Change the path.
  7. Follow up. Needs shift. Check again after a quarter, and after any reorganization, change of manager, or role change.

Template: ERG Needs Check-In

Copy this into your one-on-one notes. Fill it in after the conversation, not during it, so the person doesn't feel they're being scored.

Field Notes
Person and role
Date of conversation
Behavior change observed
Existence: how secure do pay, workload, and stability feel? (low / medium / high)
Relatedness: how connected do they feel to team and manager? (low / medium / high)
Growth: how much room do they see to develop? (low / medium / high)
Need under most pressure
Any sign of regression (what was blocked, what got louder)?
Agreed action and owner
Follow-up date

The ratings are your read of the conversation, not a score to put in a performance file. Treat them as a prompt for the next discussion.

Examples by Business Function

The same framework reads differently depending on the work. These examples are illustrative.

Function Need Under Pressure What It Might Look Like Response That Fits
Sales Growth blocked, existence rising A top rep with no path to team lead starts pushing hard on commission splits and territory Offer a defined route (mentor role, key-account track) alongside the pay discussion
Operations Existence Shift workers worried about schedule changes and safety on the floor Publish schedules earlier, fix the safety issue visibly, share plans honestly
HR Relatedness A new hire working remotely says the role is fine but feels invisible Assign a buddy, schedule regular check-ins, bring them into team rituals
Engineering Growth A senior engineer maintaining legacy code gets restless and withdrawn Rotate onto a new system, hand over an architecture decision, fund a conference
Customer success Relatedness, then growth A CSM handling escalations alone starts to disengage Pair on hard accounts, then give ownership of a playbook or onboarding redesign

In each case the manager's move is to read the need first, then choose the lever. Teams often default to money because it's the lever they control, and that's the risk ERG helps you see.

Strengths and Limitations

ERG's strengths are practical. It's simple enough to use in a one-on-one, it allows for individual differences, and the regression idea explains behavior that a strict hierarchy can't, like a high performer who becomes preoccupied with pay.

Its limits are just as real, and you should know them before you lean on it.

The evidence is mixed. Alderfer's own 1969 work supported the theory, but later tests found mixed support. In one study cited by Penn State, Wanous and Zwany (1977) found strong support for the growth category, moderate support for existence, and weak support for relatedness, with only partial support for the idea that satisfying one need changes the importance of another (Penn State World Campus). The same page describes ERG's research support as only modestly better than Maslow's.

The needs are hard to measure. The categories overlap, and two people can describe the same feeling in different words. Use ERG as a lens for conversation, not as a scorecard.

It's about motives, not method. ERG tells you which need is active. It doesn't tell you how to design a bonus plan or a role. For that, pair it with expectancy theory (will effort lead to a reward the person values?) or equity theory (does the exchange feel fair compared with peers?).

It can be over-read. Not every request for pay is a hidden growth issue. Sometimes the person simply needs more money. Ask before you assume.

Do's and Don'ts

Do Don't
Ask what the person wants before deciding which need is active Assume everyone on the team wants the same thing
Treat a sudden focus on pay or perks as a prompt for a conversation Answer every salary request with a bonus and move on
Offer growth paths early, before frustration builds Wait until a strong performer is already disengaged
Revisit needs after reorgs, role changes, and new managers Treat a single check-in as permanent
Combine ERG with other models when the picture is unclear Use any single motivation theory as the whole answer
Look at job design too, for example with the job characteristics model Blame attitude when the work itself offers no growth
Support autonomy and competence, as in self-determination theory Use rewards as a substitute for fixing a broken relationship

ERG theory earns its place because it explains something managers see all the time and misread: a person who is blocked on one front starts pushing on another. You don't have to treat the three categories as a science. Use them as a prompt to ask a better question the next time a good performer starts talking only about money, or goes quiet in meetings. For a fuller view of what drives effort, read how expectancy theory links effort to rewards, and how Herzberg's two-factor theory separates the factors that prevent frustration from the ones that create engagement.

About the author

Tara Minh

Tara Minh

Senior Operations & Growth Strategist

Tara Minh is Senior Operations & Growth Strategist at Rework, helping B2B SaaS leaders scale without breaking their teams. Tara turns messy workflows into systems people actually follow. Readers get practical frameworks they can use to cut waste, align teams, and grow on purpose.