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
- 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.
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!
- 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? rbrenSHFKAjWwgJCDXvhqner@ChacXdltRwavOtnZDcupoCanyon.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 Personal, Team, and Organizational Effectiveness:
- Take Any Seat: I
- When you attend a meeting, how do you choose your seat? Whether you chair or not, where you sit helps
to determine your effectiveness and your stature during the meeting. Here are some tips for choosing
your seat strategically.
- Knowing Where You're Going
- Groups that can't even agree on what to do can often find themselves debating about how
to do it. Here are some simple things to remember to help you focus on defining the goal.
- On Virtual Relationships
- Whether or not you work as part of a virtual team, you probably work with some people you rarely meet
face-to-face. And there are some people you've never met, and probably never will. What does it take
to maintain good working relationships with people you rarely meet?
- The Reification Error and Performance Management
- Just as real concrete objects have attributes, so do abstract concepts, or constructs. But attempting
to measure the attributes of constructs as if they were the attributes of real objects is an example
of the reification error. In performance management, committing this error leads to unexpected and unwanted
- Unnecessary Boring Work: II
- Workplace boredom can result from poor choices by the person who's bored. More often boredom comes from
the design of the job itself. Here's Part II of our little catalog of causes of workplace boredom.
See also Personal, Team, and Organizational Effectiveness for more related articles.
Forthcoming issues of Point Lookout
- Coming March 28: Four Overlooked Email Risks: II
- Email exchanges are notorious for exposing groups to battles that would never occur in face-to-face conversation. But email has other limitations, less-often discussed, that make managing dialog very difficult. Here's Part II of an exploration of some of those risks. Available here and by RSS on March 28.
- And on April 4: Narcissistic Behavior at Work: III
- People who behave narcissistically tend to regard themselves as special. They systematically place their own interests and welfare ahead of anyone or anything else. In this part of the series we consider how this claimed specialness affects the organization and its people. Available here and by RSS on April 4.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenCgIiunfuXjihXeUBner@ChacjPpwPIAMoHCUlpuyoCanyon.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.
- Your stuff is brilliant! Thank you!
- You and Scott Adams both secretly work here, right?
- I really enjoy my weekly newsletters. I appreciate the quick read.
- A sort of Dr. Phil for Management!
- …extremely accurate, inspiring and applicable to day-to-day … invaluable.