Worst Practices
by Rick Brenner
We hear a lot about best practices, but hardly anybody talks about worst practices. So as a public service, here are some of the best worst practices.
he 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.

Mustang stallions fighting. With tooth and hoof, stallions use these fights — most often — to settle differences of opinion about reproductive rights. The mares usually accept the result of these conflicts, though they do occasionally object. The social system of the wild horse functions to optimize the fitness of the next generation, because in Nature, there's little room for anything less than the best. Organizations can learn much from Nature's systems. Photo courtesy
U.S. Geological Survey.
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
Would you like to see your comments posted here?
Send 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.
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: Credit Appropriation
- Managers and supervisors who take credit for the work of subordinates or others who feel powerless are using a tactic I call Credit Appropriation. It's the mark of the unsophisticated political operator.
Devious Political Tactics: The Three-Legged Race
- The Three-Legged Race is a tactic that some managers use to avoid giving one person new authority. Some of the more cynical among us use it to sabotage projects or even careers. How can you survive a three-legged race?
Dealing with Org Chart Age Inversions
- What happens when you learn that your new boss is younger than you are? Or when the first two applicants you interview for a position reporting to you are ten years older than you are? Do you have a noticeable reaction to org chart age inversions?
When Power Attends the Meeting
- When the boss or supervisor of the chair of a regular meeting "sits in," disruption almost inevitably results, and it's usually invisible to the visitor. Here are some of the risks of sitting in on the meetings of your subordinates.
Devious Political Tactics: Cutouts
- Cutouts are people or procedures that enable political operators to communicate in safety. Using cutouts, operators can manipulate their environments while limiting their personal risk. How can you detect cutouts? And what can you do about them?
See also Workplace Politics for more related articles.
Coaching services
I offer email and telephone coaching at both corporate and individual rates.
Contact me for details at
rbrenner@ChacoCanyon.com
or (617) 491-6289, or toll-free in the continental US at (866) 378-5470.
Get the e-book!
Past issues of
Point Lookout are available in five e-books:
Reprinting this article
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
- Person-to-Person Communication for Project Managers
- When
we talk, listen, send or read emails, read or write memos, or when we leave or listen to voice mail messages, we're communicating person-to-person. And whenever we communicate person-to-person, we risk being misunderstood, offending others, feeling hurt, and being confused. There are so many ways for things to go wrong that we could never learn how to fix all the problems. A more effective approach avoids problems altogether, or at least minimizes their occurrence. In this very interactive program you'll learn a model of inter-personal communications that can help you stay out of the ditch. In those moments of intense involvement, when we're most likely to slip, you'll have a new tool to use to keep things constructive. Read more about this program. Here are some upcoming dates for this program:
Download to
your calendarThe Machine Shed, 11151 Hickman Road, Urbandale, IA 50322: February 16, Breakfast Meeting, Central Iowa Chapter of The Project Management Institute. Register now.
Download to
your calendarThe Hotel Fort Des Moines, 1000 Walnut Street, Des Moines, Iowa 50309: February 16, Lunch Meeting, Central Iowa Chapter of The Project Management Institute. Register now.
- Houston, Texas: May 8, Monthly Meeting, Houston Chapter of the Project Management Institute.
- Houston, Texas: May 9, Monthly Meeting, Houston Chapter of the Project Management Institute.
- The Race to the South Pole: The Power of Agile Development
- 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. Lessons abound. Among the more important lessons are those that demonstrate the power of the agile approach to project management and product development. Read more about this program. Here's an upcoming date for this program:
- Human-Centered Risk Management
- Most
of us can assess technological risks, but risks related to human behavior tend to resist our best efforts. This session provides a framework for evaluating risks related to the behavior of individuals, teams, organizations and people generally. Human-centered risk differs from technological or market risk, because objective evaluation requires acknowledging personal and organizational limitations and failures. Since some of those limitations and failures might apply to the people assessing the risks, or to their superiors, there's a tendency to deny them or to explain them away. Our approach examines capability, organization, context, risk mitigation, and workplace politics. It has tools for guiding the assessment and management of human-centered risk, and we show how to extend these tools to suit your situation. You'll learn how to identify sources of risk in human behavior; recognize systemic and individual barriers to acknowledging risk; assess the effects of organizational turbulence; determine the risk associated with inappropriate internal risk transfer; estimate the effects of team dysfunction, toxic conflict and turnover; and measure the impact of workplace politics. Read more about this program. Here's an upcoming date for this program:
- The Race to the South Pole: Ten Lessons for Project Managers
- 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 project managers, the story is fascinating. Lessons abound. Read more about this program. Here's an upcoming date for this program:
- Project Management in Fluid Environments
- Most
people now work in environments that can best be characterized as fluid, because they're subject to continual change. We never know what's coming next. In such environments, managing — teams, projects, groups, departments, or the enterprise — often entails moving from surprise to surprise while somehow staying almost on track. It's a nerve-wracking existence. This program provides numerous tools that help project managers who work in fluid environments. Read more about this program. Here's an upcoming date for this program:
- The Politics of Meetings for People Who Hate Politics
- There
's a lot more to running an effective meeting than having the right room, the right equipment, and the right people. With meetings, the whole really is more than the sum of its parts. How the parts interact with each other and with external elements is as important as the parts themselves. And those interactions are the essence of politics for meetings. This program explores techniques for leading meetings that are based on understanding political interactions, and using that knowledge effectively to meet organizational goals. Read more about this program. Here's an upcoming date for this program: