There's no excuse for going-dark behavior, of course, but in our frustration, trying to turn the lights back on, we often select tactics that are ineffective and can even be counterproductive. Avoid these:
- The Tweaking CC
- Something that rarely works: sending a query in email demanding information, accusing the recipient of failing to report, and including a CC to the recipient's boss, to the CEO and to the Master of the Universe. See "The Tweaking CC," Point Lookout for February 7, 2001.
- Public embarrassment
- Pillorying the offender in a general email to the team, or at a meeting — especially in his or her absence — is likely to arouse anger and resistance.
- Spreading poison
- Describing the problem to anyone who will listen will likely be seen as character assassination.
- Abuse
- Harassment and intimidation, in person or in other media, are always unethical and unacceptable. And they just plain don't work. See "When You're the Target of a Bully," Point Lookout for March 17, 2004.
- Suspending privileges or reassignment as punishment
- Indirect, threatening, or abusive
tactics are unlikely
to address the problem - The deterrence theory of punishment is questionable in any case, but in the team environment it's downright toxic.
- The nuclear option
- Waiting until the annual review period to then clobber the victim with a truly horrible report doesn't resolve the immediate problem.
Try the following steps instead. They're arranged in roughly increasing order of escalation.
- Email, voicemail, interdepartmental mail, fax, stopping by, and notes on the chair
- You probably already tried all of these. They haven't worked.
- Email with a return-receipt and high priority
- This probably won't work either, but you have to try.
- Call at odd hours
- Calling in the early morning, during lunch, late evenings, or weekends might work, if the subject is avoiding answering calls during business hours.
- Mask your caller ID
- If the subject is screening your calls using caller ID, mask your ID or call from an unusual number, such as a conference room, a friend's mobile, or a colleague's phone. Next level: call from the credit union, HR, or Security.
- Make a personal visit
- If you're remote, this isn't an easy option, but it might work.
- Ask for help
- Consult your boss for ideas, influence, and moral support. This is a last resort, but it usually works when all else has failed.
When you finally make contact, remember to remain calm. If the incident is a first-time offense, explain your concerns seriously and respectfully and demand respect in return. If the incident is part of a pattern, you've got a larger problem, and you need more information to figure out what that problem might be.
For instance, the "offender" might not be an offender at all — he or she might have been directed to go dark by someone up the management chain (I've seen this happen). Tread carefully.
In any case, work to repair and preserve the relationship first, and to resolve the problem second. Progress, when it comes, will require a sound and stable relationship. 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 Project Management:
- Project Improvisation and Risk Management
- When reality trips up our project plans, we improvise or we replan. When we do, we create new risks
and render our old risk plans obsolete. Here are some suggestions for managing risks when we improvise.
- Nonlinear Work: Internal Interactions
- In this part of our exploration of nonlinear work, we consider the effects of interactions between the
internal elements of an effort, as distinguished from the effects of external changes. Many of the surprises
we encounter in projects arise from internals.
- Why Scope Expands: II
- The scope of an effort underway tends to expand over time. Why do scopes not contract just as often?
One cause might be cognitive biases that make us more receptive to expansion than contraction.
- Ten Approaches to Managing Project Risks: III
- Project risk management strategies are numerous, but these ten strategies are among the most common.
Here are the last three of the ten strategies in this little catalog.
- Depth First or Breadth First?
- When investigating candidate solutions to a problem, we tend to focus first on what we believe is the
"best bet." But a more systematic approach can sometimes yield dramatic advantages by reducing
the cost of the investigation and the time it requires.
See also Project Management and Project Management 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