Softpanorama

May the source be with you, but remember the KISS principle ;-)
Contents Bulletin Scripting in shell and Perl Network troubleshooting History Humor

Demeaning

News

Tactful communication Recommended Books Recommended Links Checklist Diplomatic Communication
Negative Politeness Five Points Verbal Response Test Rules of Verbal Self Defense Socratic Questions Never complain about your boss in office Minimize office gossip
Dealing With Negative Criticism Surviving a Bad Performance Review Six ways to say 'No' and mean it The Art of Positive Criticism Psychopaths in Movies Fighting direct verbal abuse
Communication with Corporate Psychopaths Communication with Micromanagers Seven Typical Corporate Email Errors The Eleventh Commandment Humor Etc

Q&A: How to cope with jerks at work

Thomas Hoffman

December 12, 2006 | Computerworld

 We've all worked with them at one time or another: people who are disruptive, abusive or otherwise demeaning or mean-spirited. In short, they're jerks. Incendiary co-workers are more than a workplace distraction, however. Indeed, a growing body of research is being conducted in the U.S. and Europe that examines the impact bullies have on productivity and financial performance.

Computerworld's Thomas Hoffman spoke yesterday with Robert Sutton, the author of The No Asshole Rule: Building a Civilized Workplace and Surviving One That Isn't, which is scheduled to be published by Warner Business Books on Feb. 22, about his inspiration for the book and some of the lessons that managers can draw from it. Excerpts from that interview follow:

What inspired you to write this book? It's partly the result of the endless parade of [jerks] that I've had to deal with in my life. But it primarily stems from a department I used to work in here at Stanford and how invoking the rule helped promote a better workplace. Also, I wrote a Harvard Business Review article on the topic that produced hundreds of e-mails, whereas previous articles I've written for them might have generated 10 or 15 e-mails each.

Is it harder to get away with being a jerk in today's politically correct work environment? Or are jerks learning how to adapt? I think you can make the argument that it's more socially acceptable than it used to be because we're putting people under an enormous amount of pressure at work, such as holding them to performance requirements. Increasingly, law firms track their profits per partner -- it doesn't matter how much of an a--hole you are.

At one law firm where I was asked to speak, the CEO called me and yelled at me about my airfare, even though it had been agreed to earlier. The first thing a senior partner said to me when I walked into the auditorium before my presentation was this: "Our law firm used to be a balance of humanity and economics. Now it's all about economics." It may be getting better in terms of political correctness, but people are more skilled in many ways. It's probably not against the law to be an equal opportunity a--hole.

You mention in the book that companies such as Southwest Airlines and Intel have instituted "no a--hole rules." What are these, and how are managers able to apply them? At Intel, they have this constructive confrontation norm where you can fight but you can't be too nasty.

My favorite one is about a company called SuccessFactors, an enterprise software firm in San Mateo. They've been around for almost seven years. Lars Dalgaard is the founder. For the first six and a half years of their existence, they said they had a "no a--hole rule" and had employees sign an agreement that they wouldn't be a--holes. Lars recently came up with a list of the company's accomplishments, including not having hired any a--holes in the first six and a half years. Then they changed the wording from "a--holes" to "jerks" because some of the customers didn't like the language. I'm going to visit them next week and have more information about it on my blog.

You also mention a lot of high-profile people in the book by name, including former Sunbeam CEO Al "Chainsaw" Dunlap and outgoing U.S. ambassador to the U.N. John Bolton. Any concerns about legal retribution? Anybody can sue anybody. I was very careful. The way I defined a--holes was someone who was consistently demeaning. I'm very careful to say things in my opinion and to cite other sources. Who knows, I may get sued, but I was very careful about how I labeled people to protect myself. I quoted a Wired magazine story about some people who have worked with him [who] have their "Steve-Jobs-the-a--hole" story.

For some organizations, the "no a--hole rule" is used to help prevent disruptive people from joining your organization in the first place. But what if your department already has a pre-existing jerk? What steps can managers take to either keep this person in check or flush them out of the organization? The first thing is what's going down with the person right in front of you. If you demean people in public, you can face a lawsuit. The second thing is to bring up a performance evaluation. Some organizations don't have the guts to demote people who are consistently demeaning. Other organizations have demoted people who are disruptive and demeaning and have lowered their pay.

At one Fortune 100 company, a new CEO took over and assembled an a--hole hit list. The CEO wanted to get rid of these people immediately, but their lawyers told them they'd have a bunch of lawsuits on their hands so they had to do it more systematically.

What steps can someone take to deal with a boss who's a jerk without putting their own careers in jeopardy? The best thing you can do is not take the job in the first place. Empirical studies have shown that if you work for a boss that's a jerk, you start acting like them. But if you can't get out, there are three different things you can do. First, you've got to learn the power of indifference, learning not to [care] when you can't control the situation. The other two things are to focus on this notion of reframing things. If you can't leave, become more detached in other ways. Have shorter meetings or avoid them at meetings or contact them as much as possible by phone or e-mail. Even prisoners of war can find little ways of gaining control and exacting revenge.

A couple of weeks ago, this guy described to me how he was flying back to L.A. from New York. He had this abusive passenger seated in front of him and he said to the airline employee, "How can you take this kind of abuse?" The woman said with a straight face, "Mr. Smith is going to Los Angeles but his luggage is going to Nairobi." It's this little notion of taking control. If you look at the basic ways to cope with these situations, find the little nooks and crannies where you can exercise actual and perceived control.

How can employees fight back? HP has always taken its employee surveys very seriously, especially in the days when Lew Platt was running the company. There was a boss in the '80s there who was really nasty and tended to [rush] in and take credit when something good happened. On her evaluations from her employees she typically received ones [1 being bad and 5 being excellent].

I don't know if you've attempted to quantify this, but has there been a rise in the number or percentage of jerks in the workplace? Or has this remained a constant? I don't know the answer to this. But there has been a dawning awareness in U.S. academia to study abusiveness in the workplace. I'm confident in saying that in Europe, the U.K. and Scandinavian countries, there is a societal and legal movement against it. And we're starting to see this in the United States.

You write about a metric called TCA, or total cost of a--holes to an organization. How did you come up with this? How does it work? This is like an open-source book. A management consultant sent me a note about the TCA concept and how expensive they can be and what the hidden costs are. I asked if he would let me publish his name and he never got back to me.

If there's one message you'd like people to take away from this book, what would it be? The reason the book is important is not just because there's a business case for it, but the reason I wanted to write the book is that we only have so many days on this planet. So if you're experiencing a life that's filled with constant abuse, you end up having a terrible life. It's just not worth putting up with that kind of abuse.

Find out more about dealing with difficult co-workers -- or being one:

  •  How to survive a bad boss
  •  Managing Mavericks
  •  Are You a Scary Boss?

Don't miss Computerworld's best management advice of 2006.

Share your tales of jerks at work at the Sound Off blog



Etc

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available in our efforts to advance understanding of environmental, political, human rights, economic, democracy, scientific, and social justice issues, etc. We believe this constitutes a 'fair use' of any such copyrighted material as provided for in section 107 of the US Copyright Law. In accordance with Title 17 U.S.C. Section 107, the material on this site is distributed without profit exclusivly for research and educational purposes.   If you wish to use copyrighted material from this site for purposes of your own that go beyond 'fair use', you must obtain permission from the copyright owner. 

ABUSE: IPs or network segments from which we detect a stream of probes might be blocked for no less then 90 days. Multiple types of probes increase this period.  

Society

Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers :   Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism  : The Iron Law of Oligarchy : Libertarian Philosophy

Quotes

War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda  : SE quotes : Language Design and Programming Quotes : Random IT-related quotesSomerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose BierceBernard Shaw : Mark Twain Quotes

Bulletin:

Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 :  Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method  : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law

History:

Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds  : Larry Wall  : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOSProgramming Languages History : PL/1 : Simula 67 : C : History of GCC developmentScripting Languages : Perl history   : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history

Classic books:

The Peter Principle : Parkinson Law : 1984 : The Mythical Man-MonthHow to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Hater’s Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite

Most popular humor pages:

Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor

The Last but not Least


Copyright © 1996-2016 by Dr. Nikolai Bezroukov. www.softpanorama.org was created as a service to the UN Sustainable Development Networking Programme (SDNP) in the author free time. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License.

The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be tracked by Google please disable Javascript for this site. This site is perfectly usable without Javascript.

Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.

FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.

This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...

You can use PayPal to make a contribution, supporting development of this site and speed up access. In case softpanorama.org is down you can use the at softpanorama.info

Disclaimer:

The statements, views and opinions presented on this web page are those of the author (or referenced source) and are not endorsed by, nor do they necessarily reflect, the opinions of the author present and former employers, SDNP or any other organization the author may be associated with. We do not warrant the correctness of the information provided or its fitness for any purpose.

Last modified: October, 11, 2015