
The Scapegoat by William Holman Hunt (1827-1910), Oil on canvas, Lady Lever Art Gallery, Port Sunlight, Merseyside. Courtesy Wikipedia
Recognizing early signs of trouble — red flags — in collaborations can help us deal with trouble while it's still in early stages of its development. And red flags can warn us when it's time to change course and find a different collaboration to join. I'm thinking of collaboration here in the broad sense — a team, a project, an organization, or even an enterprise. In earlier posts, I examined red flags that included toxic conflict, turnover, and a few examples of dysfunctional communication patterns.
Another set of red flags provides even clearer warning of trouble ahead. These are the behaviors generally termed abuses of power. Following Fiske and Berdahl [Fiske 2007], I take the term power to mean one's degree of control over the ability of others to achieve outcomes they value. And powerholders abuse their power when they employ it to achieve outcomes other than those for which they were granted that power or permitted to continue exercising it.
One example of abusing power is using it to "adjust" the general understanding of the causes of failures in one's own areas of responsibility. For concreteness, here's a scenario:
But Frederick didn't want that narrative to become generally accepted, because it represented a threat to his career. So he devised a program of retrospectives, performance reviews, performance improvement plans, transfers, demotions, and terminations that created the impression that the under-estimates were entirely the fault of the estimators. Essentially, he used his legitimate authority over performance management processes and organizational learning processes to protect himself against criticism of his own performance.
In this example, instead of using his power in legitimate ways to prevent a recurrence of gross under-estimates, Frederick used it to shape a narrative that allocated full responsibility for the faulty estimates away from himself and onto others. That's an abuse of power in a pattern I call Misalignment-Between-Narrative-and-Reality.
Here are four other examples of red flags in the form of abuse of power.
- Scapegoating former staff
- One common Powerholders abuse their power
when they employ it to achieve
outcomes other than those for
which they were granted
that power or permitted to
continue exercising itvariant of the Misalignment-Between-Narrative-and-Reality pattern is Scapegoating-Former-Staff. In this pattern, the powerholder uses information that only he or she can verify to accuse former staff members of malfeasance, negligence, or other actions or inactions that account for whatever failure is in question at the moment. - This pattern is popular because of its unassailability. Since the former staff members are no longer part of the organization, they cannot dispute the powerholder's charges. Indeed, because they have moved on to positions elsewhere, the former staff members might not even be aware of any charges. And any current staff members who are aware of the charges and their speciousness tend not to dispute the charges against the former staff members, for fear of receiving similar treatment themselves.
- Designated heroes
- Perhaps the opposite of scapegoats are the designated heroes — people who can do no wrong, and who are consistently praised and recognized for both minor contributions and contributions generated by others. The existence of a designated hero is often an indicator that contributions by people other than the designated hero are unlikely to be recognized. And that means that ideas are valued not for their merits but according to their attributed authorship.
- When that happens, the organization can become committed to courses of action that might not have been subjected to fair testing and evaluation. And that exposes the organization to elevated risk of making wrong-headed choices.
- Bullying
- My definition of workplace bullying differs from some others. For me, workplace bullying is any aggressive behavior, associated with work, and primarily intended to cause physical or psychological harm to others. (See "What Is Workplace Bullying?," Point Lookout for March 3, 2010) Bullying need not involve a pattern of aggression repeatedly targeting the same individual or individuals. A single incident is enough. And organizational objectives play no role. A perpetrator might cite organizational objectives as a "justification," but that isn't the primary reason why bullies bully. Bullies bully because they seek to harm others.
- Perpetrators actually want bystanders to know that bullying is happening. Knowing that the bullies are harming their targets, and that no one is intervening, is part of the reward for the perpetrators. The fact that their superiors (if there are any) aren't intervening assures perpetrators that they can continue their nefarious activities unconcerned about adverse consequences for themselves. In most cases, a tacit agreement is in place: the perpetrator can continue bullying as long as production remains at acceptable levels.
- And that's why bullying is a red flag. If it's happening, filing a grievance is unlikely to bring about an intervention, because the perpetrator isn't the only conspirator. The perpetrator's superior is also involved, as is the superior's superior, and on up the chain to the very top. Even if you aren't a target at the moment, you will be soon, unless you have a special connection to someone powerful enough to bring an end to the bullying altogether.
- Denying risks
- Those who have authority over resources must often respond to requests for resources to mitigate risks. In a typical scenario, the resource seeker has identified a risk associated with a project or policy, and needs resources to reduce the consequences of that risk if it materializes, or to reduce the likelihood of that risk materializing. Usually, the business case is so clear that the powerholder must approve such requests. In other cases, no immediate outlay is required, but the resource seeker might instead request that a financial reserve be set aside to support a response if the risk event occurs.
- Risk denial is the pattern in which the powerholder declines to grant the resource seeker's request, or instead grants a scaled-down version of the request that's very likely inadequate.
- Risk denial is an abuse of power if the denier is gambling that the project can proceed, or the policy can remain in place, with unmitigated risk. In effect, the powerholder is seeking success out of proportion to costs by betting that the risk in question won't materialize. If the risk doesn't materialize, the powerholder intends to claim credit for great success at low cost. If the risk does materialize, the powerholder (usually) intends to cast blame in someone else's direction.
- That's why a pattern of risk denial is a red flag. Working in the organizational vicinity of a risk denier eventually exposes one to the risk of being blamed for the poor decisions of the risk denier. Even if one escapes blame, the organization must find a way to deal with the consequences of the risk event without having expended any resources to mitigate it, and without having reserved adequate resources to deal with its consequences. The organization is harmed, and might not recover. If it does recover, the price might be severe downsizing, which could affect almost anyone. Worse: risk denial is rarely a personal quirk. If one powerholder engages in risk denial, others probably do as well.
Abuse of power in its various forms can distort decision making, disrupt succession planning, and deflect strategic action in dangerous directions. Widespread or consistent abuse of power therefore tends to expose the organization to existential risk. First issue in this series
Top
Next Issue
Is every other day a tense, anxious, angry misery as you watch people around you, who couldn't even think their way through a game of Jacks, win at workplace politics and steal the credit and glory for just about everyone's best work including yours? Read 303 Secrets of Workplace Politics, filled with tips and techniques for succeeding in workplace politics. More info
Footnotes
Your comments are welcome
Would you like to see your comments posted here? rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.comSend me your comments by email, or by Web form.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 Cognitive Biases at Work:
Effects of Shared Information Bias: I
- Shared information bias is the tendency for group discussions to emphasize what everyone already knows.
It's widely believed to lead to bad decisions. But it can do much more damage than that.
Bullet Point Madness: I
- Decision makers in modern organizations commonly demand briefings in the form of bullet points or a
series of series of bullet points. But this form of presentation has limited value for complex decisions.
We need something more. We actually need to think.
Remote Hires: Inquiry
- When knowledge workers join organizations as remote hires, they must learn what's expected of them and
how it fits with what everyone else is doing. This can be difficult when everyone is remote. A systematic
knowledge-based inquiry procedure can help.
On Schedule Conflicts
- Schedule conflicts happen from time to time, even when the organization is healthy and all is well.
But when schedule conflicts are common, they might indicate that the organization is trying to do too
much with too few people.
Lessons Not Learned: I
- The planning fallacy is a cognitive bias that causes us to underestimate the cost and effort involved
in projects large and small. Mitigating its effects requires understanding how we go wrong when we plan
projects by referencing our own past experience.
See also Cognitive Biases at Work and Cognitive Biases at Work for more related articles.
Forthcoming issues of Point Lookout
Coming February 26: Devious Political Tactics: Bad Decisions
- When workplace politics influences the exchanges that lead to important organizational decisions, we sometimes make decisions for reasons other than the best interests of the organization. Recognizing these tactics can limit the risk of bad decisions. Available here and by RSS on February 26.
And on March 5: On Begging the Question
- Some of our most expensive wrong decisions have come about because we've tricked ourselves as we debated our options. The tricks sometimes arise from rhetorical fallacies that tangle our thinking. One of the trickiest is called Begging the Question. Available here and by RSS on March 5.
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
Follow Rick





Recommend this issue to a friend
Send an email message to a friend
rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed
