Point Lookout An email newsletter from Chaco Canyon Consulting
Point Lookout, a free weekly email newsletter from Chaco Canyon Consulting
December 11, 2002 Volume 2, Issue 50
 
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

What Haven't I Told You?

by

When a project team hits a speed bump, it often learns that it had all the information it needed to avoid the problem, sometimes months in advance of uncovering it. Here's a technique for discovering this kind of knowledge more systematically.

Oliver was stunned. "Let me see if I understand — Dana, you're saying that the reason we can't get the emulator to run is that we need the 4.03 system upgrade? And Jan, you knew the emulator wouldn't run in 4.01, but you thought Dana wouldn't need the emulator before March? Do I have this right?"

Wooden shoes"Yep," from Dana.

"Right," from Jan.

"Well," Oliver continued, "how come Jan didn't know we would need the emulator in January?"

"Easy," Jan replied. "The schedule said March."

Dana added, "Back when we were scheduling, the Ajax Phase 2 tests didn't need the emulator, so I didn't tell you I needed it."

Oliver, Dana, and Jan are caught in a trap that awaits many project teams. Together, they had all the information they needed to avoid the trap. They just didn't know they did. Each one of them thought everything was OK — until the problem arose. And it was only when the problem arose that they found out, together, that if they had only shared what they already knew, they could have avoided the problem altogether.

You've probably had this experience yourself, but you can reduce the chances of having it again by playing a game called "What Haven't I Told You?" It's similar to brainstorming.

Project "surprises"
are often emergent.
They're made of
little pieces,
each of which was
known to somebody.
You play the game with a small group of about ten or fifteen people, and it helps if someone acts as a facilitator and scribe. In each round, the players think of something that they know but haven't talked about, and that they haven't heard anyone else talk about. Then in turn, the players describe their items to the group. The scribe records each item. As in brainstorming, there is no evaluation.

As a player, you try to think of something so detailed or arcane that other people probably don't know it or haven't thought of it. And it should be important enough that it has implications for at least some other people on the team.

After the ideas stop flowing, the group can rank them according to relevance, cluster them according to relationship criteria, or apply morphological analysis.

Here are some tips for finding good stuff for your next game of What Haven't I Told You? Ask yourself these questions:

  • If I wanted to sabotage the team's effort in a subtle way, what information would I withhold? What would I change? What would I lie about?
  • If someone else were trying to sabotage my efforts, what information would they want to withhold from me, or change, or lie to me about?
  • Aside from my formal deliverables, what am I doing that anyone on the team could conceivably care about?

You don't need to be a team to benefit from playing this game. What haven't you told yourself? Go to top Top  Next issue: Caught in the Crossfire  Next Issue
Bookmark and Share

Rick BrennerThe article you've been reading is an archived issue of Point Lookout, my weekly newsletter. I've been publishing it since January, 2001, free to all subscribers, over the Web, and via RSS. You can help keep it free by donating either as an individual or as an organization. You'll receive in return my sincere thanks — and the comfort of knowing that you've helped to propagate insights and perspectives that can help make our workplaces a little more human-friendly. More

Your comments are welcome
Would you like to see your comments posted here? rbrenrRDecxzDDUPZFHlOner@ChacveizddsxHkpRiQaxoCanyon.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:

Working on a puzzleFirst 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.
Don't rely solely on your spell checkerEmail Antics: Part III
Nearly everyone complains that email is a time waster. Yet much of the problem results from our own actions. Here's Part III of a little catalog of things we do that help waste our time.
Governor Scott Walker of WisconsinIndicators of Lock-In: Part I
In group decision-making, lock-in occurs when the group persists in adhering to its chosen course even though superior alternatives exist. Lock-in can be disastrous for problem-solving organizations. What are some common indicators of lock-in?
An FBI SWAT team assists local law enforcement in New Orleans in August 2005The Paradox of Structure and Workplace Bullying
Structures of all kinds — organizations, domains of knowledge, cities, whatever — are both enabling and limiting. To gain more of the benefits of structure, while avoiding their limits, it helps to understand this paradox and learn to recognize its effects.
Panama Canal constructionAvoid Having to Reframe Failure
Yet again, we missed our goal — we were late, we were over budget, or we lost to the competition. But how can we get something good out of it?

See also Personal, Team, and Organizational Effectiveness, Effective Meetings and Problem Solving and Creativity for more related articles.

Forthcoming Issues of Point Lookout

Langston Hughes, poet and leader of the Harlem RenaissanceComing September 2: That Was a Yes-or-No Question: Part II
When, in the presence of others, someone asks you "a simple yes or no" question, beware. Chances are that you're confronting a trap. Here's Part II of a set of suggestions for dealing with the yes-or-no trap. Available here and by RSS on September 2.
Navy vs. Marine Corps tug off war in Vera Cruz, Mexico ca. 1910-1915And on September 9: Holding Back: Part I
When members of teams or groups hold back their efforts toward achieving group goals, schedule and budget problems can arise, along with frustration and destructive intra-group conflict. What causes this behavior? Available here and by RSS on September 9.

Coaching services

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

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 an upcoming date for this program:

Managing in Fluid Environments
Most Managing in Fluid Environmentspeople now work in environments that can best be characterized as fluid, because they're subject to continual change. We never know whats coming next. In such environments, managing — teams, projects, groups, departments, or the enterprise — often entails moving from surprise to surprise while somehow staying almost on track. It's a nerve-wracking existence. This program provides numerous tools that help managers who work in fluid environments. Read more about this program. Here are some upcoming dates for this program:

The Race to the South Pole: The Organizational Politics of Risk Management
On 14The Race to the South Pole: The Organizational Politics of Risk Management 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. We'll use the history of this event to explore lessons in risk management, its application to organizational efforts, and how workplace politics enters the mix. A fascinating and refreshing look at risk management from the vantage point of history and workplace politics. Read more about this program. Here's an upcoming date for this program:

Team Development for Leaders
TeamsTeam Development for Leaders at work are often teams in name only — they're actually just groups. True teams are able to achieve much higher levels of performance than groups can. In this program, Rick Brenner shows team leads and team sponsors the techniques they need to form their groups into teams, and once they are teams, how to keep them there. Read more about this program. Here's an upcoming date for this program:

How to Spot a Troubled Project Before the Trouble StartsLearn how to spot troubled projects before they get out of control.
52 Tips for Leaders of Project-Oriented OrganizationsAre your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around.
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 Effective MeetingsLearn how to make meetings more productive — and more rare.
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 RSS Feed, 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!
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.
Comprehensive collection of all e-books and e-bookletsSave a bundle and even more important save time! Order the Combo Package and download all ebooks and tips books at once.
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