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 non-messenger: 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.

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:

Devious Political Tactics: Divide and Conquer, Part I

While most leaders try to achieve organizational unity, some do use divisive tactics to maintain control, or to elevate performance by fostering competition. Understanding the risks of these tactics can motivate you to find another way.

The Risky Role of Hands-On Project Manager

The hands-on project manager manages the project and performs some of the work, too. There are lots of excellent hands-on project managers, but the job is inherently risky, and it's loaded with potential conflicts of interest.

On Advice and Responsibility

Being asked for advice can be an affirming experience, but actually giving advice can sometimes entail risk. How can this happen, and what choices do we have?

Before You Blow the Whistle: I

When organizations know that they've done something they shouldn't have, or they haven't done something they should have, they often try to conceal the bad news. When dealing with whistleblowers, they can be especially ruthless.

Holding Back: I

When members of teams or groups hold back their efforts toward achieving group goals, schedule and budget problems can arise, along with frustration and destructive intra-group conflict. What causes this behavior?

See also Workplace Politics for more related articles.

Forthcoming issues of Point Lookout

Coming October 23: Power Distance and Teams

One of the attributes of team cultures is something called power distance, which is a measure of the overall comfort people have with inequality in the distribution of power. Power distance can determine how well a team performs when executing high-risk projects. Available here and by RSS on October 23.

And on October 30: Power Distance and Risk

Managing or responding to project risks is much easier when team culture encourages people to report problems and question any plans they have reason to doubt. Here are five examples that show how such encouragement helps to manage risk. Available here and by RSS on October 30.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.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 words in your inbox in one hour. License any article from this Web site. More info

Public seminars

The Race to the South Pole: Lessons in Leadership

On 14 December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough. But to organizational leaders, business analysts, project sponsors, and project managers, the story is fascinating. We'll use the history of this event to explore lessons in leadership and its application to organizational efforts. A fascinating and refreshing look at leadership from the vantage point of history. Read more about this program.

Here's a date for this program:

• Baldwin-Wallace University, 275 Eastland Road, Berea, Ohio 44017: November 7, Kerzner Lecture Series/International Project Management Day, sponsored by Baldwin Wallace University and the Northeast Ohio Chapter of the Project Management Institute. Register now.
   

The Power Affect: How We Express Our Personal Power

Many people who possess real organizational power have a characteristic demeanor. It's the way they project their presence. I call this the power affect. Some people — call them power pretenders — adopt the power affect well before they attain significant organizational power. Unfortunately for their colleagues, and for their organizations, power pretenders can attain organizational power out of proportion to their merit or abilities. Understanding the power affect is therefore important for anyone who aims to attain power, or anyone who works with power pretenders. Read more about this program.

• A recording of a program presented June 29, 2017, Monthly Webinar, sponsored by Technobility Webinar Series. PMI members can earn 1.0 Category 'A' PDU by viewing this program. View this program now.