Pygmalion Side Effects: Bowling a Strike

Many managers know of the Pygmalion Effect, in which our expectations not only influence how we see employee performance, but also influence the employee's performance. This happens because we telegraph our expectations through tiny cues that are out of our awareness. When people pick up these cues, their behavior tends toward our expectations, and our expectations become self-fulfilling prophecies.

You might know this from personal experience. Perhaps your supervisor expected the best of you, and you delivered, and felt great. Or perhaps you were expected to fail, and you did. It's difficult to excel when your supervisor thinks you're a loser.

But there's much more to it than the Pygmalion Effect — there are the Pygmalion Side Effects. Managers who leave in place employees whom they believe are poor performers risk lost productivity, higher turnover, and interpersonal conflict, not only among the poor performers, but among other employees, too.

For example, the people around Elise also pick up on Alton's low opinion of her, which influences their expectations and how they behave toward Elise. They're less accepting of her contributions, and they might come to distrust her and even dislike her. These Pygmalion Side Effects influence Elise's performance, perhaps even more than the original Pygmalion Effect.

And the team's Managers who leave poor
performers in place risk triggering
the Pygmalion Side Effects —
lost productivity among
other employeesperformance can degrade. With or without a spoken agreement, the team might isolate Elise, depriving itself of contributions she might have made. Team members might second-guess her work, or distrust her opinions, or they might even reject her valid contributions. Interpersonal conflict can erupt, and that can lead to defects and project delays.

The Pygmalion Side Effects are something like bowling a strike. The bowling ball itself knocks down some of the pins, but most of the pins are knocked down by other pins.

If you're a manager, what can you do about a poor performer?

Beware perceptions

Recognize that it's possible that you're seeing the performance as poorer than it is. You can clear this up only by greater first-person involvement with the work of your organization — the whole organization. Email and third-hand communications are not first-person involvement.

Change something — carefully

If there's a performance issue, your best options are training, reassignment, transfer, or termination. Leaving poor performers in place and hoping for the best isn't likely to work, and could threaten team performance.

Go for the root cause

In today's highly interconnected work teams, evaluating personal performance can be difficult. If someone isn't doing well, some of the rest of the team could be playing a role. If you terminate a "poor performer" when the root cause is actually elsewhere in the team, the team will likely produce a new "poor performer."

The next time you're thinking about someone's poor performance, try not to bowl a strike.  Top    Next Issue

Are your projects always (or almost always) late and over budget? Are your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around. Read 52 Tips for Leaders of Project-Oriented Organizations, filled with tips and techniques for organizational leaders. Order Now!

For a discussion of the connection between confirmation bias and the Pygmalion effect, see "Confirmation Bias: Workplace Consequences: II," Point Lookout for November 30, 2011.

For more on the Pygmalion Effect, see:

• J.S. Livingston, "Pygmalion in Management." Harvard Business Review, reprint #88509, in The Best of the Harvard Business Review, Harvard Business School Press, 1991.
• "Expectations May Alter Outcomes Far More Than We Realize," by Sharon Begley, in The Wall Street Journal, p. B1, November 7, 2003.

Your comments are welcome

About Point Lookout

Thank you for reading this article. I hope you enjoyed it and found it useful, and that you'll consider recommending it to a friend.

This article in its entirety was written by a human being. No machine intelligence was involved in any way.

Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.

Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.

Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.

Related articles

More articles on Personal, Team, and Organizational Effectiveness:

When We Need a Little Help

Sometimes we get in over our heads — too much work, work we don't understand, or even complex politics. We can ask for help, but we often forget that we can. Even when we remember, we sometimes hold back. Why is asking for help, or remembering that we can ask, so difficult? How can we make it easier?

Four Popular Ways to Mismanage Layoffs: I

When layoffs are necessary, the problems they are meant to address are sometimes exacerbated by mismanagement of the layoff itself. Here is Part I of a discussion of four common patterns of mismanagement, and some suggestions for those managers and other employees who recognize the patterns in their own companies.

Action Item Avoidance

In some teams, members feel so overloaded that they try to avoid any additional tasks. Here are some of the most popular patterns of action item avoidance.

Holding Back: II

Members of high-performing teams rarely hold back effort. But truly high performance is rare in teams. Here is Part II of our exploration of mechanisms that account for team members' holding back effort they could contribute.

Pseudo-Collaborations

Most workplace collaborations produce results of value. But some collaborations — pseudo-collaborations — are inherently incapable of producing value, due, in part, to performance management systems, lack of authority, or lack of access to information.

See also Personal, Team, and Organizational Effectiveness and Personal, Team, and Organizational Effectiveness for more related articles.

Forthcoming issues of Point Lookout

Coming January 22: Storming: Obstacle or Pathway?

The Storming stage of Tuckman's model of small group development is widely misunderstood. Fighting the storms, denying they exist, or bypassing them doesn't work. Letting them blow themselves out in a somewhat-controlled manner is the path to Norming and Performing. Available here and by RSS on January 22.

And on January 29: A Framework for Safe Storming

The Storming stage of Tuckman's development sequence for small groups is when the group explores its frustrations and degrees of disagreement about both structure and task. Only by understanding these misalignments is reaching alignment possible. Here is a framework for this exploration. Available here and by RSS on January 29.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.

Get the ebook!

Past issues of Point Lookout are available in six ebooks:

• Get 2001-2 in Geese Don't Land on Twigs (PDF, )
• Get 2003-4 in Why Dogs Wag (PDF, )
• Get 2005-6 in Loopy Things We Do (PDF, )
• Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
• Get 2009-10 in The Questions Not Asked (PDF, )
• Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )

Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500-1000 words in your inbox in one hour. License any article from this Web site. More info