Lieut. E. Shackleton, Capt. R.F. Scott and Dr. E.A. Wilson, of the British Antarctic Expedition, before starting south in Spring 1902. They eventually set a Furthest South record at 82 degrees south latitude that stood until Shackleton's expedition of 1907. On this journey, all three fell ill with scurvy, but Shackleton was the worst afflicted, and became the "injured teammate." However, he and Scott had by that point had interpersonal difficulties, and Scott's management of the situation created by Shackleton's illness, letting his personal feelings dominate his leadership, was a model of what not to do. Scott humiliated Shackleton in various ways, by word and deed, with respect to his illness. When the party of three returned to base, Scott sent Shackleton home early, a year before the rest of the party, using Shackleton's illness as an excuse. Read the story in detail in Roland Huntford's biography of Shackleton, Shackleton. (Order from Amazon.com) Photo courtesy Wikimedia Commons.
You're leading a team of some kind, and one of the team members has been severely injured 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
Would you like to see your comments posted here? rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.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 Emotions at Work:
Email Happens- Email is a wonderful medium for some communications, and extremely dangerous for others. What are its
limitations? How can we use email safely?
Irrational Self-Interest- When we try to influence others, especially large groups or entire companies, we sometimes create packages
of incentives and disincentives that are intended to affect behavior. These strategies usually assume
that people make choices on rational grounds. Is this assumption valid?
A Review of Performance Reviews: Blindsiding- Ever learn of a complaint about you for the first time at your performance review? If so, you were blindsided.
Reviews can be painful. Here are some guidelines for making them a little fairer.
Managing Hindsight Bias Risk- Performance appraisal practices and project retrospectives both rely on evaluating performance after
outcomes are known. Unfortunately, a well-known bias — hindsight bias — can limit the effectiveness
of many organizational processes, including both performance appraisal and project retrospectives.
Not Really Part of the Team: I- Some team members hang back. They show little initiative and have little social contact with other team
members. How does this come about?
See also Emotions at Work for more related articles.
Forthcoming issues of Point Lookout
Coming October 1: On the Risks of Obscuring Ignorance- A common dilemma in knowledge-based organizations: ask for an explanation, or "fake it" until you can somehow figure it out. The choice between admitting your own ignorance or obscuring it can be a difficult one. It has consequences for both the choice-maker and the organization. Available here and by RSS on October 1.
And on October 8: Responding to Workplace Bullying- Effective responses to bullying sometimes include "pushback tactics" that can deter perpetrators from further bullying. Because perpetrators use some of these same tactics, some people have difficulty employing them. But the need is real. Pushing back works. Available here and by RSS on October 8.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.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
rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed
My 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!
