Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 5, Issue 13;   March 30, 2005: See No Evil

See No Evil

by

When teams share information among themselves, they have their best opportunity to reach peak performance. And when some information is withheld within an elite group, the team faces unique risks.

Mark clicked to the next slide and paused, waiting for the explosion. Everyone at the table seemed to be reading and re-reading his conclusion, but none of them were exploding. So he began.

Two infants exchanging secrets

Photo (cc) abardwell

"The Review Team's conclusion is simple. We don't believe that Marigold can make any date before July…even August is doubtful. To get to 95% confidence, we think we have to go out to November."

There. He'd said it.

Lambert, both elbows on the conference table, leaned forward. He seemed to make eye contact with everyone around the table at once. "Well," he began, "before we sort this out, I need one thing. What we've just heard is not to be repeated to the rest of the team. Or anyone. Clear?"

By choosing secrecy, Lambert might be guiding the group into a see-no-evil mode, which could jeopardize the project. It's a risky course.

When a team shares all team-relevant information, it's functioning as an open system. A team that intentionally confines some information within small subgroups is functioning as a closed system.

To function at their potential,
teams must share all
team-relevant information
Both systems can work, provided that all team members are aware of the reality. But in project teams that are closed, team members are often unaware that they're closed. That is, the fact that the team is a closed system is itself a secret. And that disparity between reality and perception can lead to trouble. Even when team members are aware, closed systems face special risks. Here are just a few.

Increased risk of bad decisions
If team members believe that they have access to all information relevant to their own activities, when they actually don't, they might believe that they're making correct decisions and trade-offs when they actually aren't.
Infringing the personal freedoms of team members
Some information is so significant that it can affect personal decisions. For instance, if a fatal flaw is discovered, some team members might choose to move on to a new assignment. If the flaw is concealed, they might stay, thinking that all is well when it isn't.
Re-inventing the wheel
In closed systems, when someone discovers a problem and finds a workaround, there's a temptation to implement the workaround without revealing the problem. If the root of the problem is deep within the system, failing to reveal it prevents resolution at the root. Several people might discover the problem independently, each one implementing a separate — and possibly different — workaround.
Management problems
When a team is closed, and it hasn't discussed the choice to be open or closed, and when its culture professes the values of openness, any team members who discover the brutal truth could begin resenting the team leadership. They might feel manipulated and alienated, and their behavior might lead to management problems.

It's tempting to contain problems until we have repairs underway. But the tactic can be misleading and disrespectful, creating problems even bigger than the ones we were trying to avoid. Leaders who conceal truth from others lead others to conceal truth from them. Go to top Top  Next issue: Email Ethics  Next Issue

303 Secrets of Workplace PoliticsIs every other day a tense, anxious, angry misery as you watch people around you, who couldn't even think their way through a game of Jacks, win at workplace politics and steal the credit and glory for just about everyone's best work including yours? Read 303 Secrets of Workplace Politics, filled with tips and techniques for succeeding in workplace politics. More info

Your comments are welcome

Would you like to see your comments posted here? rbrendBqnfBHLXoulqxzpner@ChaciBHKZLWyQBFMEhTxoCanyon.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 Project Management:

The Great Wall of China near MutianyuScope Creep and Confirmation Bias
As we've seen, some cognitive biases can contribute to the incidence of scope creep in projects and other efforts. Confirmation bias, which causes us to prefer evidence that bolsters our preconceptions, is one of these.
The Bloomingdale's store in Stamford, Connecticut in January 1955Why Scope Expands: I
Scope creep is depressingly familiar. Its anti-partner, spontaneous and stealthy scope contraction, has no accepted name, and is rarely seen. Why?
Illustrating the concept of local maximumFalse Summits: II
When climbers encounter "false summits," hope of an early end to the climb comes to an end. The psychological effects can threaten the morale and even the safety of the climbing party. So it is in project work.
An A-10 Thunderbolt II over Afghanistan in 2011Down in the Weeds: I
When someone says, "I think we're down in the weeds," a common meaning is that we're focusing on inappropriate — and possibly irrelevant — details. How does this happen and what can we do about it?
FlamesHow to Get Out of Firefighting Mode: II
We know we're in firefighting mode when a new urgent problem disrupts our work on another urgent problem, and the new problem makes it impossible to use the solution we thought we had for some third problem we were also working on. Here's Part II of a set of suggestions for getting out of firefighting mode.

See also Project Management, Effective Communication at Work and Conflict Management for more related articles.

Forthcoming issues of Point Lookout

Raquel Welch (left) and Gilda Radner (right) from a @Cite{Saturday Night Live rehearsal, April 24, 1976Coming December 20: Conceptual Mondegreens
When we disagree about abstractions, such as a problem solution, or a competitor's strategy, the cause can often be misunderstanding the abstraction. That misunderstanding can be a conceptual mondegreen. Available here and by RSS on December 20.
An engineer attending a meeting with 14 other engineersAnd on December 27: On Assigning Responsibility for Creating Trouble
When we assign responsibility for troubles that bedevil us, we often make mistakes. We can be misled by language, stereotypes, and the assumptions we make about others. Available here and by RSS on December 27.

Coaching services

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

Reprinting this article

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

Person-to-Person Communications: Models and Applications
When Person-to-Person Communications: Models and Applicationswe talk, listen, send or read emails, read or write memos, or when we leave or listen to voice mail messages, we're communicating person-to-person. And whenever we communicate person-to-person, we risk being misunderstood, offending others, feeling hurt, and being confused. There are so many ways for things to go wrong that we could never learn how to fix all the problems. A more effective approach avoids problems altogether, or at least minimizes their occurrence. In this very interactive program we'll explain — and show you how to use — a model of inter-personal communications that can help you stay out of the ditch. We'll place particular emphasis on a very tricky situation — expressing your personal power. In those moments of intense involvement, when we're most likely to slip, you'll have a new tool to use to keep things constructive. Read more about this program. Here's a date for this program:

Ten Project Management Fallacies: The Power of Avoiding Hazards
Most Ten Project Management Fallaciesof what we know about managing projects is useful and effective, but some of what we know "just ain't so." Identifying the fallacies of project management reduces risk and enhances your ability to complete projects successfully. Even more important, avoiding these traps can demonstrate the value and power of the project management profession in general, and your personal capabilities in particular. In this program we describe ten of these beliefs. There are almost certainly many more, but these ten are a good start. We'll explore the situations where these fallacies are most likely to expose projects to risk, and suggest techniques for avoiding them. Read more about this program. Here's a date for this program:

The Power Affect: How We Express Our Personal Power
Many The Power Affect: How We Express Personal Powerpeople 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.

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at Twitter, or share a tweet Follow me at Google+ or share a post Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
Technical Debt for Policymakers BlogMy 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!
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
101 Tips for Managing ConflictFed up with tense, explosive meetings? Are you the target of a bully? Learn how to make peace with conflict.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.