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
Would you like to see your comments posted here? rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.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 Workplace Politics:
- When It's Just Not Your Job
- Has your job become frustrating because the organization has lost its way? Is circumventing the craziness
making you crazy too? How can you recover your perspective despite the situation?
- On Noticing
- What we fail to notice about any situation — and what we do notice that isn't really there —
can be the difference between the outcomes we fear, the outcomes we seek, and the outcomes that exceed
our dreams. How can we improve our ability to notice?
- Columbo Tactics: I
- When the less powerful must deal with the more powerful, or the much more powerful, the less powerful
can gain important advantages by adapting the strategy and tactics of the TV detective Lt. Columbo.
Here's Part I of a collection of his tactics.
- Grace Under Fire: III
- When someone at work seems intent on making your work life a painful agony, you might experience fear,
anxiety, or stress that can lead to a loss of emotional control. Retaining composure is in that case
the key to survival.
- The Risks of Humor at Work
- Humor at work can be useful for strengthening relationships, making connections, and defusing tension.
And it can be risky, too. Some risks: irrelevance to the here and now, leaving out the funny, or ambiguous
sarcasm. Read this post for five more risks.
See also Workplace Politics and Workplace Politics for more related articles.
Forthcoming issues of Point Lookout
- Coming December 11: White Water Rafting as a Metaphor for Group Development
- Tuckman's model of small group development, best known as "Forming-Storming-Norming-Performing," applies better to development of some groups than to others. We can use a metaphor to explore how the model applies to Storming in task-oriented work groups. Available here and by RSS on December 11.
- And on December 18: Subgrouping and Conway's Law
- When task-oriented work groups address complex tasks, they might form subgroups to address subtasks. The structure of the subgroups and the order in which they form depend on the structure of the group's task and the sequencing of the subtasks. Available here and by RSS on December 18.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.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
rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed
Beware any resource that speaks of "winning" at workplace politics or "defeating" it. You can benefit or not, but there is no score-keeping, and it isn't a game.
- Wikipedia has a nice article with a list of additional resources
- Some public libraries offer collections. Here's an example from Saskatoon.
- Check my own links collection
- LinkedIn's Office Politics discussion group