No Surprises

Beth looked at Philippe. Philippe looked at Jim. Jim looked at Beth. When they realized what they were doing, they all chuckled. "You. No you. No you," said Beth. "Seriously," she continued, "someone has to tell him."

Jim was more serious. "It's a suicide mission. You know how he always says 'no surprises' in all caps. I don't think I'll be the one."

Philippe had an idea. "There must be some way to spin this so it isn't so awful sounding," he said.

Beth, Jim, and Philippe are trying to figure out a way to break some bad news to somebody who evidently has a well advertised "no surprises" policy. They might find a way this time, but "no surprises" is a risky way to run things. Here's a little of what can go wrong with a "no surprises" policy.

Too broad a message

If your policy is "no surprises," then you're saying that you don't want any good surprises either. Probably you don't mean that.

It's an unattainable goal

Surprises are inevitable in projects. Operations and projects differ in that projects are unique and first-of-a-kind. Surprises are the essence of project work.

When a surprise does happen, you have a new problem

If your policy is "no surprises," and a surprise happens, you have two problems. Not only do you have to deal with the surprise, but you also have a violation of policy. Because policy violations usually require disciplinary action, the policy itself creates a problem.

People find workarounds

A "no surprises" policy
could create some
unpleasant surprises

Above, Philippe is about to suggest that they slant the truth to avoid the surprising bad news. Slanting the truth is almost always a bad idea.

Instead of "no surprises," why not ask for what you really need? Some possibilities:

No surprises — really

If this is what you need, then unique, first-of-a-kind projects aren't within your reach. Instead, move into an operational role, where everything you do is like something done before. Surprises are less common in operations.

Keep me so well informed that I know whatever you know

This would be nice, if it weren't micromanagement. It's so intrusive that it's irritating for everyone involved. And if two people in an organization know all the same things, one of them is redundant.

If it's a surprise to me, it should be a surprise to you, too

This is more reasonable, and it's what you probably need, too, provided you allow for the pace of events exceeding anyone's ability to keep you up to date. Allow a reasonable time lag between others' learning of the event and their passing it along to you.

There will always be surprises, and here's one: The trick for dealing with surprises is not to avoid them, but to get really good at recovering from them.  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!

Reader Comments

Alex S. Brown (www.alexsbrown.com)

At first read, I was surprised that your column was against a "No Surprises" policy. I often emphasize this point to my own staff.

The more I read, though, the better I understood. The column makes good points about overly controlling, impossible policies. When I need "no surprises" on a project, I mean something like the "if it's a surprise to me, it should be to you" version.

The way I explain it is, "If I am going to hear about something on your project and it will surprise me, I want to hear it from you first. If you are not sure whether I will be surprised or whether I will hear about it, err on the side of caution: tell me about it. If you are sure I will be surprised, tell me about it as soon as you can." People take a couple of weeks to figure out what is important and what is not, but it seems to build an open relationship quickly. Also, because it emphasizes "You tell me about it," people know that I want them to tell me about bad news and quickly.

I bet the fictional manager in your story also suffers from the "shoot the messenger" syndrome. No matter what official policies you have, people will never tell you bad news if you punish the people who bring the news. Personally, I just ask them for solutions, and give them help and support if they need it. So far, it has worked well for me.

Thanks for another thought-provoking column. — Alex

Your comments are welcome

Would you like to see your comments posted here? rbrenRHfEIzYHVWnFypbfner@ChacjNgncGaToRXnONcDoCanyon.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.

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 Personal, Team, and Organizational Effectiveness:

Enjoy Your Commute

You probably commute to work. On a good day, you spend anywhere from ten minutes to an hour or two — each way — commuting. What kind of experience are you having? Taking control of this part of your life can make a real difference.

First Aid for Painful Meetings

The foundation of any team meeting is its agenda. A crisply focused agenda can make the difference between a long, painful affair and finishing early. If you're the meeting organizer, develop and manage the agenda for maximum effectiveness.

Our Last Meeting Together

You can find lots of tips for making meetings more effective — many at my own Web site. Most are directed toward the chair, or the facilitator if you have one. Here are some suggestions for everybody.

The Deck Chairs of the Titanic: Strategy

Much of what we call work is about as effective and relevant as rearranging the deck chairs of the Titanic. We continue our exploration of futile and irrelevant work, this time emphasizing behaviors related to strategy.

Paradoxical Policies: I

Although most organizational policies are constructive, many are outdated or nonsensical, and some are actually counterproductive. Here's a collection of policies that would be funny if they weren't real.

See also Personal, Team, and Organizational Effectiveness for more related articles.

Forthcoming issues of Point Lookout

Coming February 27: Brainstorming and Speedstorming: II

Recent research into the effectiveness of brainstorming has raised some questions. Motivated to examine alternatives, I ran into speedstorming. Here's Part II of an exploration of the properties of speedstorming. Available here and by RSS on February 27.

And on March 6: A Pain Scale for Meetings

Most meetings could be shorter, less frequent, and more productive than they are. Part of the problem is that we don't realize how much we do to get in our own way. If we track the incidents of dysfunctional activity, we can use the data to spot trends and take corrective action. Available here and by RSS on March 6.

Coaching services

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

Public seminars

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.

• A recording of a program presented 6:00 PM June 29 (Eastern Time), Monthly Webinar, Technobility Webinar Series. You can earn 1.0 Category 'A' PDU by viewing this program. View this program now.