Point Lookout An email newsletter from Chaco Canyon Consulting
Point Lookout, a free weekly email newsletter from Chaco Canyon Consulting
March 30, 2005 Volume 5, Issue 13
 
Recommend this issue to a friend
Join the Friends of Point Lookout
HTML to link to this article…
Archive: By Topic    By Date
Links to Related Articles
Sign Up for A Tip A Day!
Create a perpetual bookmark to the current issue Bookmark and Share
Tweet this! | Follow @RickBrenner Random Article

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"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
Bookmark and Share


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. Order Now!
Your comments are welcome
Would you like to see your comments posted here? Send 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:
Bottle of poisonToxic Projects
A toxic project is one that harms its organization, its people or its customers. We often think of toxic projects as projects that fail, but even a "successful" project can hurt people or damage the organization — sometimes irreparably.

Woman using binocularsScheduling as Risk Management
When we schedule a complex project, we balance logical order, resource constraints, and even politics. Here are some techniques for using scheduling to manage risk and reduce costs.

Chocolate chip cookiesNine Project Management Fallacies: Part 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.

Turbulence in the wake of a low-flying aircraftGuidelines for Sharing "Resources"
Often, team members belong to several different teams. The leaders of teams whose members have divided responsibilities must sometimes contend with each other for the efforts and energies of the people they share. Here are some suggestions for sharing people effectively.

Robert F. Scott and three of his party arrive at a tent left by Roald Amundsen near the South PoleManaging Non-Content Risks: Part I
When project teams and their sponsors manage risk, they usually focus on those risks most closely associated with the tasks — content risks. Meanwhile, other risks — non-content risks — get less attention. Among these are risks related to the processes and politics by which the organization gets things done.

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

Coaching services

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

The Race to the South Pole: Ten Lessons for Project Managers
On 14The Race to the Pole: Ten Lessons for Project Managers 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 project managers, the story is fascinating. Lessons abound. Read more about this program. Here's an upcoming date for this program:

The Race to the South Pole: The Power of Agile Development
On 14The Race to the Pole: An Application of Agile Development 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. Lessons abound. Among the more important lessons are those that demonstrate the power of the agile approach to project management and product development. Read more about this program. Here's an upcoming date for this program:

The Collected Issues of Point Lookout: 2001-2012Looking for insights, tips, and concrete suggestions for the conundrums and kerfuffles of workplace life? The Collected Issues of Point Lookout is a collection of articles from my weekly newsletter, all in a single ebook of 1263 pages, searchable and cross referenced. Newly released, order by 30 Jun 2013, New York Time, at the introductory price of only , a savings of USD 9.00! Check it out!
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?
My free weekly email newsletter gives concrete tips and suggestions for dealing with the challenging but everyday situations we all face.
A Tip A DayA Tip a Day arrives by email, or by Yahoo! Widget, each business day. It's 20 to 30 words at most, and gives you a new perspective on the hassles and rewards of work life. Most tips also contain links to related articles. Free!
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.
If your teams don't yet consistently achieve state-of-the-art teamwork, check out this catalog. Help is just a few clicks away!
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.
SSL