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
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 welcomeWould you like to see your comments posted here? rbrenlyqMwoeKYbGWXLJcner@ChacUPuGDKshVoQGKrOwoCanyon.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.
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.
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.
- Organizational Loss: Searching Behavior
- When organizations suffer painful losses, their responses can sometimes be destructive, further harming
the organization and its people. Here are some typical patterns of destructive responses to organizational
- Inappropriate Levels of Regard
- The regard we have for others as people is sometimes influenced by the regard we have for the work they
do. Confusing the two is a dangerous error.
- Preventing Spontaneous Collapse of Agreements
- Agreements between people at work are often the basis of resolving conflict or political differences.
Sometimes agreements collapse spontaneously. When they do, the consequences can be costly. An understanding
of the mechanisms of spontaneous collapse of agreements can help us craft more stable agreements.
- Projects as Proxy Targets: I
- Some projects have detractors so determined to prevent project success that there's very little they
won't do to create conditions for failure. Here's Part I of a catalog of tactics they use.
See also Workplace Politics for more related articles.
Forthcoming issues of Point Lookout
- Coming August 23: Look Where You Aren't Looking
- Being blindsided by an adverse event could indicate the event's sudden, unexpected development. It can also indicate a failure to anticipate what could have been reasonably anticipated. How can we improve our ability to prepare for adverse events? Available here and by RSS on August 23.
- And on August 30: They Just Don't Understand
- When we cannot resolve an issue in open debate, we sometimes try to explain the obstinacy of others. The explanations we favor can tell us more about ourselves than they do about others. Available here and by RSS on August 30.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenxFEbjcdIXqsJFwQyner@ChacReVWKSFHLfzVmSNeoCanyon.com or (617) 491-6289, 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, USD 11.95)
- Get 2003-4 in Why Dogs Wag (PDF, USD 11.95)
- Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
- Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 28.99)
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
- 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 organizational leaders, business
analysts, project sponsors, and project managers, the story is fascinating. Lessons abound. Read
more about this program. Here are some dates for this program:
- The Westin Virginia Beach Town Center, 4535 Commerce Street,
Virginia Beach, VA 23462: September 13,
Monthly Meeting, Hampton Roads Chapter of the Project Management Institute. Register now.
- CTCPA, 716 Brook Street,
Rocky Hill, CT 06067: September 20,
Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.
- The Westin Virginia Beach Town Center, 4535 Commerce Street, Virginia Beach, VA 23462: September 13, Monthly Meeting, Hampton Roads Chapter of the Project Management Institute. Register now.
- Creating High Performance Virtual Teams
- Many people experience virtual teams as awkward, slow, and sometimes
frustrating. Even when most team members hail from the same nation or culture, and even when they all
speak the same language, geographic dispersion or the presence of employees from multiple enterprises
is often enough to exclude all possibility of high performance. The problem is that we lead, manage,
and support virtual teams in ways that are too much like the way we lead, manage, and support co-located
teams. In this program, Rick Brenner shows you how to change your approach to leading, managing, and
supporting virtual teams to achieve high performance using Simons' Four Spans model of high performance.
Read more about this program. Here's a date for this
- Baci Grill, 134 Berlin
Road, Berlin, CT 06416: September 19,
Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- Baci Grill, 134 Berlin Road, Berlin, CT 06416: September 19, Monthly Meeting, Southern New England 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.
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.