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.
- 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
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? rbrenUhjqOfEXkDCdTUpqner@ChacrThiDJeDdbVzfRjVoCanyon.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:
- Films Not About Project Teams: II
- Here's Part II of a list of films and videos about project teams that weren't necessarily meant to be
about project teams. Most are available to borrow from the public library, and all are great fun.
- TINOs: Teams in Name Only
- Perhaps the most significant difference between face-to-face teams and virtual or distributed teams
is their potential to develop from workgroups into true teams — an area in which virtual or distributed
teams are at a decided disadvantage. Often, virtual and distributed teams are teams in name only.
- How to Reject Expert Opinion: I
- When groups of decision-makers confront complex problems, they sometimes choose not to consult experts
or to reject their advice. How do groups come to make these choices?
- The Retrospective Funding Problem
- If your organization regularly conducts project retrospectives, you're among the very fortunate. Many
organizations don't. But even among those that do, retrospectives are often underfunded, conducted by
amateurs, or too short. Often, key people "couldn't make it." We can do better than this.
What's stopping us?
- Holding Back: II
- Members of high-performing teams rarely hold back effort. But truly high performance is rare in teams.
Here is Part II of our exploration of mechanisms that account for team members' holding back effort
they could contribute.
See also Personal, Team, and Organizational Effectiveness for more related articles.
Forthcoming issues of Point Lookout
- Coming May 31: Unresponsive Suppliers: III
- When suppliers have a customer orientation, we can usually depend on them. But government suppliers are a special case. Available here and by RSS on May 31.
- And on June 7: The Knowledge One-Upmanship Game
- The Knowledge One-Upmanship Game is a pattern of group behavior in the form of a contest to determine which player knows the most arcane fact. It can seem like innocent fun, but it can disrupt a team's ability to collaborate. Available here and by RSS on June 7.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenbJkMrwfqsFkyywvUner@ChacJKVdRmmgogVPQdnJoCanyon.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
- Creating High Performance Virtual Teams
- Many people experience virtual teams as awkward, slow, and sometimes
frustrating. Even when most team members hail from the same nation or culture, and even when they all
speak the same language, geographic dispersion or the presence of employees from multiple enterprises
is often enough to exclude all possibility of high performance. The problem is that we lead, manage,
and support virtual teams in ways that are too much like the way we lead, manage, and support co-located
teams. In this program, Rick Brenner shows you how to change your approach to leading, managing, and
supporting virtual teams to achieve high performance using Simons' Four Spans model of high performance.
Read more about this program. Here's an upcoming date
for this program:
- Baci Grill, 134 Berlin
Road, Berlin, CT 06416: September 19,
Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- Baci Grill, 134 Berlin Road, Berlin, CT 06416: September 19, Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- The Race to the South Pole: Ten Lessons for Project Managers
- On 14 December 1911, four men led by Roald
Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen
had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished.
As historical drama, why this happened is interesting enough, but to organizational leaders, business
analysts, project sponsors, and project managers, the story is fascinating. Lessons abound. Read
more about this program. Here's an upcoming date for this program:
- CTCPA, 716 Brook Street,
Rocky Hill, CT 06067: September 20,
Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.
- CTCPA, 716 Brook Street, Rocky Hill, CT 06067: September 20, Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.
- 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.