4

Respecting employees can boost bottom line

Commentator Teresa Amabile says overbearing supervisors can sap worker creativity.

To view this content, Javascript must be enabled and Adobe Flash Player must be installed.

Get Adobe Flash player

Congratulations! You're the chief operating officer of a well-known consumer products company. Today, you're presiding over a big review of new products being developed. The room is packed with product teams, VPs, and other top brass.

You turn to the team presenting a new blender, but the team leader sheepishly admits the prototype isn't ready. There was a mistake somewhere in the development process, but he's confident the team will fix it soon.

As COO, do you:

A. Say nothing?
B. Say, "That's all right, as long as you can figure out what you did." Or
C. Say, "You've got your head up your [expletive]?"

This scenario really happened in a company we studied -- and the COO went with option C. His words, by the way. But for the good of the company, what he should have said was B.

That's the right answer because it fosters something called "psychological safety" -- an atmosphere where it's OK to admit errors because you're not going to get punished or dressed down for an honest mistake. Psychological safety allows people to dispassionately dissect shortcomings so they can learn and improve.

The opposite is an atmosphere of intimidation, where people avoid taking risks and stifle their creativity.

Unfortunately, my research team and I found that many business leaders undervalue respect. When faced with an employee's mistake, far too many rake the person over the coals.

A few leaders do get this right. They know that, if they respect the worker and focus on what went wrong in the work, their employees are far more likely to be innovative and productive. Research shows that respecting employees can help drive the bottom line upward. Doing the opposite can drive an enterprise into the ground.

About the author

Teresa Amabile is a professor at Harvard Business School and co-author of "The Progress Principle."
ChromeJob's picture
ChromeJob - Jul 5, 2012

There's an old, easy axiom that would've saved the COO's face and his subordinate's, um, pride. "Attack the ideas, not the person." Works well on USENET, Internet, business, social contexts.

Cdvallance's picture
Cdvallance - Jul 3, 2012

I agree that shaming staff is not the right answer but there is a larger problem here. How did it ever get to the point that the team lead did not tell the COO in advance of the meeting about the delay? Where was the dialogue that would have allowed problem solving together so the right message could have been conveyed at the meeting? What was missing before the meeting ever happened was the trust, mutual respect and openness that should form the baseline of the relationship between the two individuals.

Cyclist One's picture
Cyclist One - Jul 2, 2012

According to Payscale.com, the average CEO (sorry I couldn't find COO pay) to average worker is 213:1. I doubt very much if the 2 people in the "product roll out" scenario ever cross paths. I encourage more workers to start small companies, live simply, so other can simply live.

defina100's picture
defina100 - Jul 2, 2012

Thank You for this commentary. It is also a perfect description of how to raise creative and caring children.