Worst Practices

The mythology about best practices is that they universally improve every organization. The truth is more likely that organizations are so idiosyncratic that any practice born elsewhere probably needs tailoring before it can be imported. My old shoes are very comfortable for me, but they probably aren't for you.

Worst practices are different — they're almost universally disastrous. We know this because, sadly, nearly everyone tries them. Here's a short list of some worst practices.

• Provide only outdated equipment. Even better: make people share outdated equipment.
• For security, lock all portable computers to desks
• Never, ever train anybody
• Use training as a reward. Provide it only to those who need it least.
• To increase productivity, increase pressure
• Let acrimony persist until it's truly injurious
• Leave in place people who are clearly incapable of doing much of anything
• Assign blame
• Spend time defending yourself in case someone, someday decides to assign blame
• Take credit for work done by subordinates or colleagues
• Give credit to one person for what was a team effort, ignoring everyone else's contributions
• Kill the messenger: punish people who deliver bad news
• Kill the nonmessenger: after you get bad news, punish those who knew about it but didn't tell you because you have a reputation for killing the messenger
• Force consensus by shaming or punishing those few souls foolish enough to disagree with the "correct" position
• Force consensus without allowing time for sufficient discussion
• Make decisions autocratically even when there's time for consensus
• Have favorite subordinates who can do no wrong
• The worst thing about
  worst practices isn't their
  consequences; it's that we
  keep using them despite
  their consequencesHave troubled subordinates who can do no right, even when they do right
• As team owner, publicly castigate team members
• Publicly overrule a subordinate manager, citing information obtained from one of his or her subordinates
• "Sit in" on a subordinate's meeting unannounced
• Make the problem excessively complicated by raising herds of ancillary minor issues
• Angrily say things that hurt people, damaging the group's ability to collaborate
• Add new people to the team. Even better: do it in a way that raises questions about the abilities of incumbents
• "Temporarily" transfer some team member(s) to another effort
• Conduct "emergency" project reviews regularly
• Increase the budget without warning
• Decrease the budget
• Circulate rumors that maybe we'll be cutting the budget
• Tighten project scope to maintain schedule
• Use (faked) schedule urgency as a way of managing spending
• Remove or relax some requirements
• After work is well underway, add new requirements or tighten existing requirements
• Reassign some work from one team member to another
• Assign the same work to two people (or teams) without their knowing it
• Assign to one person work already completed by another
• Assign work to two people, together, without designating either one as lead

Count how many of these you've seen. Even scarier: count how many you've done.  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!

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 Workplace Politics:

Using Indirectness at Work

Although many of us value directness, indirectness does have its place. At times, conveying information indirectly can be a safe way — sometimes the only safe way — to preserve or restore well-being and comity within the organization.

What Do You Need?

When working issues jointly with others, especially with one other, we sometimes hear, "What do you need to make this work?" Your answers can doom your effort — or make it a smashing success.

Workplace Politics and Type III Errors

Most job descriptions contain few references to political effectiveness, beyond the fairly standard collaborate-to-achieve-results kinds of requirements. But because true achievement often requires political sophistication, understanding the political content of our jobs is important.

High Falutin' Goofy Talk: III

Workplace speech and writing sometimes strays into the land of pretentious but overused business phrases, which I like to call "high falutin' goofy talk." We use these phrases with perhaps less thought than they deserve, because they can be trite or can evoke indecorous images. Here's Part III of a collection of phrases and images to avoid.

The Politics of Forming Joint Leadership Teams

Some teams, business units, or enterprises are led not by individuals, but by joint leadership teams of two or more. They face special risks that arise from both the politics of the joint leadership team and the politics of the organization hosting it.

See also Workplace Politics and Workplace Politics for more related articles.

Forthcoming issues of Point Lookout

Coming April 23: On Planning in Plan-Hostile Environments: I

In most organizations, most of the time, the plans we make run into little obstacles. When that happens, we find workarounds. We adapt. We flex. We innovate. But there are times when whatever fix we try, in whatever way we replan, we just can't make it work. We're working in a plan-hostile environment. Available here and by RSS on April 23.

And on April 30: On Planning in Plan-Hostile Environments: II

When we finally execute plans, we encounter obstacles. So we find workarounds or adjust the plans. But there are times when nothing we try gets us back on track. When this happens for nearly every plan, we might be working in a plan-hostile environment. Available here and by RSS on April 30.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenfHlRlTgqCIXkUHBTner@ChacrEuHRQPYVKkOucGfoCanyon.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