Early in the quarter, a product team picks up a rumor that the launch will probably slip. Nobody says it in a meeting. It travels through hallway conversations and side-channel messages. By week six, people are padding estimates, avoiding bold decisions, and quietly preparing explanations. The launch slips. Everyone nods. They saw it coming.

The sociologist Robert Merton called this a self-fulfilling prophecy: a belief that is false at first but triggers behavior that makes it come true. Merton used the example of bank runs. A rumor that a bank is insolvent causes the mass withdrawals that sink a bank that was actually sound. Teams do the same thing, only more quietly.

Groups make this pattern especially hard to shake because their expectations are shared. One person's pessimism is a mood. A whole team's pessimism becomes a plan. Learning how this happens, and how to catch it early, is one of the most useful skills a leader can build. The problems a team predicts are often the ones it ends up creating.

Self-fulfilling prophecies in teams rarely involve anyone deciding to fail. They work through small adjustments that each look reasonable. Suppose a team expects a stakeholder to reject its proposal. So it prepares a cautious, hedged version. The hedged version is less compelling, and the stakeholder rejects it. The expectation shaped the effort, and the effort shaped the result.

Research on the Pygmalion effect shows the same loop running through leaders. In a well-known study by Dov Eden and Abraham Shani, instructors in an Israeli military training program were told that certain trainees had high potential. Those trainees went on to outperform their peers, even though they had been chosen at random. Without realizing it, the instructors had given them more attention, clearer feedback, and harder challenges. The reverse, sometimes called the Golem effect, is just as real. Low expectations quietly reduce the support people receive.

At the group level, the mechanism scales through what psychologists call collective efficacy, a team's shared belief about what it can accomplish together. Albert Bandura found that this belief affects how much effort groups invest, how long they persist after setbacks, and which goals they choose in the first place. A team that doubts itself sets safer targets and gives up earlier. It also reads ambiguous feedback as proof of its limits.

Selective attention makes things worse. Once a team has a story about itself, members start noticing evidence that fits and filtering out what doesn't. The story might be we're always behind, the other department never cooperates, or leadership doesn't listen. Either way, it doesn't just predict the future. It edits the past, making the prophecy seem more accurate than it ever was. Each confirmed prediction then strengthens the belief that produced it.

Takeaway

Expectations aren't neutral predictions. They are instructions the team follows without realizing it. Before asking whether a belief is accurate, ask what behavior it is quietly prescribing.

The hardest part of a self-fulfilling cycle is that, from the inside, it looks like realism. Teams don't think they're being pessimistic. They think they're being experienced. They've seen this movie before, and they're simply acting on what they've learned. So recognizing a cycle starts with spotting patterns, not with debating whether any single belief is true.

One reliable signal is defensive preparation. Watch for a team that spends more energy building explanations for failure than plans for success. It might document who said what, lower commitments in advance, or call goals aspirational so that missing them won't count. That team is often preparing for an outcome it has already accepted. Another signal is predictable repetition. If the team reliably forecasts that the same problem will come back, and it does, that deserves investigation rather than acceptance.

Jean-François Manzoni and Jean-Louis Barsoux described a version of this between managers and employees, which they called the set-up-to-fail syndrome. A manager senses an employee is struggling and starts supervising more closely. The employee reads the extra scrutiny as distrust, withdraws, and takes less initiative. The manager sees the withdrawal as confirmation. Both are responding sensibly to what they observe, and the relationship spirals anyway. Teams fall into the same trap with other teams, with clients, and with their own leadership.

A useful diagnostic question is: What are we doing differently because we believe this? If the honest answer involves less effort, less candor, or less risk-taking, the belief is no longer just describing the situation. It's taking part in it. Also listen for the language of fixed identity, such as 'that's just how this team is.' It signals that the story has hardened into something no one thinks to question anymore.

Takeaway

A negative cycle feels like accurate perception from the inside. The real test is not whether the prediction comes true, but whether the team changed its behavior in ways that made it more likely.

Self-fulfilling prophecies run on behavior, so changing behavior usually breaks them faster than persuasion does. Telling a discouraged team to think positively rarely works, because the belief has too much evidence piled up behind it. A better approach is to create conditions where a different outcome becomes possible, then make sure people see that outcome.

Start with small, visible wins. Karl Weick argued that big problems tend to paralyze people, while smaller, concrete ones invite action. A team convinced it can't ship on time might commit to one tightly scoped deliverable and hit it. A single result doesn't prove much statistically, but it cracks the story. Collective efficacy grows the same way individual confidence does: through real experiences of success, not pep talks.

Next, make the expectation explicit. Prophecies thrive when they stay unspoken. Naming the belief in a meeting turns an invisible force into something the group can examine. You might say, 'We all seem to assume the client will push back, so how is that shaping our proposal?' Irving Janis's work on groupthink is useful here. He recommended assigning someone to argue the opposing case. In this setting, a designated challenger can ask what the team would do differently if the pessimistic assumption were false.

Finally, leaders should check their own expectations. Manzoni and Barsoux found that the set-up-to-fail cycle usually breaks only when the manager starts a candid conversation, acknowledges their own part in it, and resets the terms. Leaders set the emotional weather for a team. Small signals teach a group what is expected of it. Those signals include who gets stretch assignments, whose ideas get follow-up questions, and which risks get forgiven.

Takeaway

You can't argue a team out of a belief its experience keeps confirming. Change the experience first, and the belief will often follow.

Self-fulfilling prophecies aren't a sign of a bad team. They're a sign of a normal one: people trying to make sense of uncertainty and acting on their best guess. The trouble is that in groups, best guesses tend to become shared plans.

The practical move is to treat team expectations as variables rather than facts. In your next planning session, try asking one question: What are we assuming will go wrong, and how is that assumption shaping what we're about to do?

You won't catch every cycle. But catching even one changes what a team believes is possible. And that belief, it turns out, has a way of coming true too.