Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 5, Issue 15;   April 13, 2005: Shining Some Light on "Going Dark"

Shining Some Light on "Going Dark"

by

If you're a project manager, and a team member "goes dark" — disappears or refuses to report how things are going — project risks escalate dramatically. Getting current status becomes a top priority problem. What can you do?
The Cone Nebula

The Cone Nebula as imaged by the ACS camera of the Hubble Space Telescope. Courtesy Space Telescope Science Institute.

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. Go to top Top  Next issue: Knowing Where You're Going  Next Issue

52 Tips for Leaders of Project-Oriented OrganizationsAre 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? rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.comSend me your comments by email, or by Web form.

About Point Lookout

This article in its entirety was written by a 
          human being. No machine intelligence was involved in any way.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:

FootprintsStatus Risk and Risk Status
One often-neglected project risk is the risk of inaccurately reported status. That shouldn't be surprising, because we often fail to report the status of the project's risks, as well. What can we do to better manage status risk and risk status?
A Strangler Fig in AustraliaProjects 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.
An A-10 Thunderbolt II over Afghanistan in 2011Down in the Weeds: I
When someone says, "I think we're down in the weeds," a common meaning is that we're focusing on inappropriate — and possibly irrelevant — details. How does this happen and what can we do about it?
A candleAnticipating Absence: Passings
In times more normal than ours, co-workers who pass on tend to do so one at a time. Disease or accidents rarely strike many co-workers in the same week, month, or year. There are exceptions — 9/11 was one such. This pandemic is another.
Opera house, Sydney, AustraliaLessons Not Learned: I
The planning fallacy is a cognitive bias that causes us to underestimate the cost and effort involved in projects large and small. Mitigating its effects requires understanding how we go wrong when we plan projects by referencing our own past experience.

See also Project Management, Effective Communication at Work and Conflict Management for more related articles.

Forthcoming issues of Point Lookout

Saturn during equinox — a composite of natural-color images from CassiniComing May 22: Rescheduling Collaborative Work
Rescheduling is what we do when the schedule we have now is so desperately unachievable that we must let go of it because when we look at it we can no longer decide whether to laugh or cry. The fear is that the new schedule might come to the same end. Available here and by RSS on May 22.
The Leonard P. Zakim Bunker Hill BridgeAnd on May 29: Rescheduling: Project Factors
Rescheduling is what we do when we can no longer honor the schedule we have now. Of all causes of rescheduling, the more controllable are those found at the project level. Attending to them in one project can limit their effects on other projects. Available here and by RSS on May 29.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.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:

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-1000 words in your inbox in one hour. License any article from this Web site. More info

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at X, or share a post Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
Technical Debt for Policymakers BlogMy blog, Technical Debt for Policymakers, offers resources, insights, and conversations of interest to policymakers who are concerned with managing technical debt within their organizations. Get the millstone of technical debt off the neck of your organization!
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
101 Tips for Managing ConflictFed up with tense, explosive meetings? Are you the target of a bully? Learn how to make peace with conflict.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.
If your teams don't yet consistently achieve state-of-the-art teamwork, check out this catalog. Help is just a few clicks/taps away!
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.