Declaring Condition Red

A team emergency is an unforeseen situation that requires immediate, decisive action. It can arise from almost any sudden change, including the discovery of a serious design or manufacturing flaw; a reduction of budget or other resources; a competitive threat; or the loss of key personnel.

Usually, teams search for emergency responses using their normal, meeting-upon-endless-meeting work style. But since most emergencies demand immediate responses, team members can become frustrated, anxious, and fearful when their usual approach fails them. Interpersonal conflict erupts, people begin to attack or withdraw, and they might even hurt each other emotionally. In emergencies, permanent damage both to teams and to relationships is common.

Much of the conflict we see in teams originates during unacknowledged emergency situations. If we can learn to acknowledge emergencies, we can temporarily restructure our processes, and eliminate some sources of interpersonal conflict.

You'll do better if you have a plan. Here are some guidelines for preserving your high-performance team as it deals with emergencies.

Formally declare the emergency

Formally declaring "Condition Red" lets everyone know that the usual procedures are suspended, and emergency procedures are in effect. This protects you from long-term precedents that might otherwise persist after the emergency. When the emergency passes, formally declare its passing, too.

Choose an appropriate decision-making process

If you don't have a plan,
you can't follow it

Consensus usually produces the best decisions, but consensus takes time. In an emergency, use a more centralized process — perhaps one with a single authoritative decision maker. See "Decisions, Decisions: I," Point Lookout for November 17, 2004, for a catalog of decision-making processes.

Think short-term

In emergencies, long-term optimizations become irrelevant when compared with short-term survival. Shift to a shorter-term perspective. If you normally think about this quarter, think about this week. If you normally think about this week, think about today. Failing to think short-term is an important source of conflict and failure in emergencies.

Train and simulate

Train your team. In simulations, they can practice emergency procedures, and learn what emergencies feel like. Make emergencies familiar territory.

Delegate more deeply

To reduce frustration, temporarily delegate authority more deeply into the organization. In emergencies, raise spending authority thresholds and reduce the number of sign-offs required.

Relax cost controls

There's little point to saving $23k when $2.3 billion is at stake. If you normally don't feed or house your team, consider doing so. If you already do, upgrade what you do for them. Offer compensatory time off and combat pay.

Never cry wolf

Reserve your emergency plan for emergencies. A bone-headed project plan that fails miserably isn't an emergency — it's a bad plan. Take responsibility for it — don't shift the burden to the team by declaring an emergency.

After an emergency, when everyone has given 120% and saved the company, thank them in some way they will never forget. It will be the best investment you ever made.  Top    Next Issue

In a single day, you can witness the final hours of a brand that took ten years to build. Or you can see it re-emerge stronger than ever. From Tylenol to JetBlue — no brand is exempt. And the outcome depends not only on what you say to the public, but on how well you communicate internally — to each other. 101 Tips for Communication in Emergencies is filled with tips for sponsors of, leaders of, and participants in emergency management teams. It helps readers create an environment in which teams can work together, under pressure from outside stakeholders, in severely challenging circumstances, while still maintaining healthy relationships with each other. That's the key to effective communication in emergencies. It's an ebook, but it's about 15% larger than "Who Moved My Cheese?" Just . 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 Project Management:

Nine Project Management Fallacies: II

Some of what we "know" about managing projects just isn't so. Identifying the fallacies of project management reduces risk and enhances your ability to complete projects successfully.

Risk Management Risk: I

Risk Management Risk is the risk that a particular risk management plan is deficient. It's often overlooked, and therefore often unmitigated. We can reduce this risk by applying some simple procedures.

Seven Ways to Get Nowhere

Ever have the feeling that you're getting nowhere? You have the sense of movement, but you're making no real progress towards the goal. How does this happen? What can you do about it?

Nonlinear Work: When Superposition Fails

Much of the work we do is confounding, because we consistently underestimate the effort involved, the resources required, and the time required to get it done. The failure of superposition can be one reason why we get it wrong.

Power Distance and Teams

One of the attributes of team cultures is something called power distance, which is a measure of the overall comfort people have with inequality in the distribution of power. Power distance can determine how well a team performs when executing high-risk projects.

See also Project Management for more related articles.

Forthcoming issues of Point Lookout

Coming November 30: Avoiding Speed Bumps: II

Many of the difficulties we encounter when working together don't create long-term harm, but they do cause delays, confusion, and frustration. Here's Part II of a little catalog of tactics for avoiding speed bumps. Available here and by RSS on November 30.

And on December 7: Reaching Agreements in Technological Contexts

Reaching consensus in technological contexts presents special challenges. Problems can arise from interactions between the technological elements of the issue at hand, and the social dynamics of the group addressing that issue. Here are three examples. Available here and by RSS on December 7.

Coaching services

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