SCRUM MASTER RESOURCE

Learned Helplessness in Agile Teams

Why capable teams stop trying—and how leaders and Scrum Masters can help restore agency.

01 / THE PROBLEM

When silence is learned

Illustration from presentation slide 1: The problem

What if some of your team’s silence isn’t apathy, but a rational response to their history?

Capable people can stop raising concerns, challenging decisions, and proposing improvements when experience has taught them that speaking up makes no difference—or makes things worse.

Understanding that history changes the question a Scrum Master asks: rather than “Why won’t this team take initiative?”, we can ask “What has this team learned happens when it tries?”

02 / THE ORIGIN

When yesterday’s constraint becomes today’s belief

Illustration from presentation slide 2: The origin

In the late 1960s, psychologists studied how exposure to uncontrollable unpleasant experiences could affect later behavior. In experiments involving dogs, some animals that had previously been unable to escape discomfort subsequently failed to attempt escape even when it became possible.

The central lesson was that repeated experiences of having no control can teach an expectation that one’s actions will not change the outcome.

The familiar elephant-and-rope story illustrates this idea: a young elephant cannot break a tether, so it eventually stops pulling. Later, even when strong enough to break it, the animal does not try because it has learned the restraint is immovable.

The elephant story is a metaphor, rather than evidence from Seligman’s experiments. Its point is memorable: a past constraint may no longer describe the present reality.

The rope is no longer the physical constraint. The belief has become the constraint.
03 / THE DEFINITION

Rituals continue. Agency disappears.

Illustration from presentation slide 3: The definition

Learned helplessness describes a pattern in which people stop trying to affect outcomes even after change becomes possible. Within an Agile team, repeated experiences of ignored feedback, punished failure, and performative leadership can create a similar pattern of withdrawal.

Retrospectives still happen. Plans are made. Work is delivered. But the willingness to challenge, improve, and experiment slowly fades.

“If you treat people like cogs in a machine, don’t be surprised when they act like cogs.”

The behavior may look like an attitude problem, but the conditions that reinforce it can be systemic. Delivery can continue while ownership, innovation, and adaptability decline.

04 / THE SIGNALS

How it shows up in Agile teams

Illustration from presentation slide 4: The signals

It can start with recurring experiences: velocity used as punishment, escalated impediments that never get resolved, or priorities that constantly shift regardless of the team’s input.

The team adapts. People go quiet when risks are obvious. Improvements are dismissed with “That won’t get approved anyway.” Retrospectives become low-energy rituals rather than opportunities to change the way work gets done.

Repeated eventsMetric-driven punishment
Unresolved escalations
Chronic priority churn
Visible reactionsSilence around risks
“That won’t get approved”
Low-energy retrospectives
Possible outcomesEroded psychological safety
Minimal experimentation
Disengagement

These signals do not prove learned helplessness in any individual team. They are reasons to investigate the team’s experiences and the organizational response to its efforts.

05 / THE BLIND SPOT

When leaders mistake withdrawal for a lack of accountability

Illustration from presentation slide 5: The blind spot

Managers say they want self-managing teams: people who make decisions, take ownership, and act with accountability. Then they grant more freedom and find that nobody moves. Decisions are deferred. People wait for instructions.

The tempting conclusion is: “This is why I can’t trust them.” But that interpretation overlooks what may have come before.

Years of micromanagement, approval gates, being told to “stay in your lane,” and punishment for trying something new can teach people that initiative is risky. When leaders then ask for autonomy, the team may continue behaving according to the old rules.

If effort has repeatedly produced negative consequences, withdrawal can become a rational adaptation to the environment.

A change in leadership expectations alone may not be enough. People need evidence that the rules have actually changed.

06 / THE RESPONSE

How a Scrum Master helps break the rope

Illustration from presentation slide 6: The response

The Scrum Master’s work is not simply to motivate the team. It is to help change the feedback loops that have taught people their efforts do not matter.

Start by making small successes possible and visible. Show when an impediment has actually been removed. Escalate repeated patterns with evidence instead of treating each occurrence as an isolated frustration. Help leaders see how their decisions and responses shape team behavior.

Give the team meaningful, low-risk choices: select the format of the next Sprint Review, choose one improvement to try this Sprint, or redesign one small workflow within their authority.

Then close the loop. Help people experience: “I made a decision. I wasn’t punished. It helped.” Repeated experiences of action leading to meaningful results can rebuild agency, trust, and momentum.

Small wins → restored agency → momentum.
07 / PUT IT INTO PRACTICE

A facilitation exercise: test the rope

Illustration from presentation slide 7: Put it into practice

Use a retrospective or team discussion to identify one area where the team may have stopped trying. Keep the scope narrow enough to test an assumption safely within a Sprint.

  1. Ask where the team has stopped trying.Invite specific examples of ideas, decisions, or improvements people no longer attempt.
  2. Identify one assumption that might no longer be true.What constraint are we treating as permanent? When did we last check whether it still exists?
  3. Design one small, safe experiment.Agree what the team will try next Sprint and what observable result would count as useful learning.
  4. Close the loop next Sprint.Show what changed because the team acted, whether the experiment succeeded or revealed another obstacle.
The goal is not dramatic transformation.
The goal is testing the rope.