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
- 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.
- 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.
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? rbrenrLUIviROcPDwSYOmner@ChacBCdjqQQQExAYYiDHoCanyon.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 Project Management:
- Films Not About Project Teams: I
- Here's part one of a list of films and videos about project teams that weren't necessarily meant to
be about project teams. Most are available to borrow from the public library, and all are great fun.
- Project Improvisation Fundamentals
- Project plans are useful — to a point. Every plan I've ever seen eventually has problems when
it contacts reality. At that point, we replan or improvise. But improvisation is an art form. Here's
Part I of a set of tips for mastering project improvisation.
- Managing Non-Content Risks: II
- When we manage risk, we usually focus on those risks most closely associated with the tasks at hand
— content risks. But there are other risks, to which we pay less attention. Many of these are
outside our awareness. Here's Part II of an exploration of these non-content risks, emphasizing those
that relate to organizational politics.
- Down 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?
- How We Waste Time: I
- Time is the one workplace resource that's evenly distributed. Everyone gets exactly the same share,
but some use it more wisely than others. Here's Part I of a little catalog of ways we waste time.
Forthcoming issues of Point Lookout
- Coming June 28: Tackling Hard Problems: I
- Hard problems need not be big problems. Even when they're small, they can halt progress on any project. Here's Part I of an approach to working on hard problems by breaking them down into smaller steps. Available here and by RSS on June 28.
- And on July 5: Tackling Hard Problems: II
- In this Part II of our look at solving hard problems, we continue developing properties of the solution, and look at how we get from the beginning to the end. Available here and by RSS on July 5.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenYKmwuCqKoUAXzuQqner@ChacejzItZecxdBqbiatoCanyon.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 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. Here are some upcoming dates for this program:
- 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 an upcoming date
for this program:
- 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 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's an upcoming date for this program:
- CTCPA, 716 Brook Street,
Rocky Hill, CT 06067: September 20,
Full-day Workshop, Southern New England 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.