The Injured Teammate: II

You're leading a team of some kind, and one of the team members has been severely injured or or has been stricken with a serious illness. I'll call him Andy. The team doesn't know about it yet, but, everyone knows him personally and when they find out, everyone will feel loss or worry.

In Part I, we explored what to do to prepare before you talk to the team. In this Part II, we look at what to say and how to say it.

Tell the team what you can about Andy's near future

Whatever you say must respect organizational policy and Andy's personal preferences. You might know his condition, and you might know his location and whether he's receiving visitors (he probably isn't yet). If you can, provide an address (or tell them when you will) for those who wish to send cards or good wishes.

You probably don't know when or whether he'll be returning. It's best to say this as, "I don't yet know when Andy will be back." Telling people that you don't know whether he'll be back is probably unhelpful.

Offer team members what they might need

Some team members might benefit from counseling, though this is rare in the case of injury or illness. It probably isn't necessary to offer counseling to everyone, but be attentive to special cases.

Beware: the event might have exposed previously hidden factors. For instance, Andy might be involved in an affair with another team member, who could be severely upset, and who might also be unwilling or unable to visit Andy because of privacy concerns. Private counseling might be desirable for both. Sensitivity on your part is a valuable asset.

Beware the complexity of virtual relationships

Some team members might have close virtual relationships with Andy. They might be thousands of miles away, and perhaps they have never met, but the emotional impact of the event can be every bit as painful and disruptive as if they were co-located.

Contact remote or traveling team members in advance by telephone, and give them the news privately. Don't leave anything in voicemail other than a request for a return call. Ask for confidentiality until you talk to the rest of the team.

It isn't necessary to have a new
plan immediately. Indeed, if you
do, you risk appearing over-eager
to replace the one stricken

Announce that you'll be re-planning the work

It isn't necessary to have a new plan immediately. Indeed, if you do, you risk appearing over-eager to replace Andy. Announce that some assignments might change, and that you might introduce new resources. Estimate a date by which you expect changes, and ask for their patience.

Beware asking for input from the team generally, because resource allocation and scheduling is your job. Consulting some team members is fine, but do so with discretion.

Most important, leave space for team members to talk to the team and to each other. Not everyone will want to, but space is important for those who do.  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

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 Emotions at Work:

The Fallacy of the False Cause

Although we sometimes make decisions with incomplete information, we do the best we can, given what we know. Sometimes, we make wrong decisions not because we have incomplete information, but because we make mistakes in how we reason about the information we do have.

Never, Ever, Kill the Messenger

If you're a manager in a project-oriented organization, you need to know the full, unvarnished Truth. When you kill a messenger, you deliver a message of your own: Tell me the Truth at your peril. Killing messengers has such predictable results that you have to question any report you receive — good news or bad.

Can You Hear Me Now?

Not feeling heard can feel like an attack, even when there was no attack, and then conversation can quickly turn to war. Here are some tips for hearing your conversation partner and for conveying the message that you actually did hear.

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.

Compulsive Talkers at Work: Peers II

Our exploration of approaches for dealing with compulsive talkers now concludes, with Part II of a set of suggestions for what to do when peers who talk compulsively interfere with your work.

See also Emotions at Work and Project Management for more related articles.

Forthcoming issues of Point Lookout

Coming June 14: Pseudo-Collaborations

Most workplace collaborations produce results of value. But some collaborations — pseudo-collaborations — are inherently incapable of producing value, due to performance management systems, or lack of authority, or lack of access to information. Available here and by RSS on June 14.

And on June 21: Asking Burning Questions

When we suddenly realize that an important question needs answering, directly asking that question in a meeting might not be an effective way to focus the attention of the group. There are risks. Fortunately, there are also ways to manage those risks. Available here and by RSS on June 21.

Coaching services

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