What Haven't I Told You?

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?"

"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?  Top    Next Issue

The 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

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.

This article in its entirety was written by a human being. No machine intelligence was involved in any way.

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:

Dealing with Negative Progress

Many project emergencies are actually the result of setbacks — negative progress. Sometimes these mishaps are unavoidable, but often they're the result of patterns of organizational culture. How can we reduce the incidence of setbacks?

Untangling Tangled Threads

In energetic discussions, topics and subtopics get intertwined. The tangles can be frustrating. Here's a collection of techniques for minimizing tangles in complex discussions.

Unnecessary Boring Work: I

Work can be boring. Some of us must endure the occasional boring task, but for many, everything about work is boring. It doesn't have to be this way.

Wacky Words of Wisdom: VI

Adages, aphorisms, and "words of wisdom" seem valid often enough that we accept them as universal and permanent. Most aren't. Here's Part VI of a collection of widely held beliefs that can be misleading at work.

Improvement Bias

When we set about improving how our organizations do things, we expose ourselves to the risk of finding opportunities for improvement that offer very little improvement, while we overlook others that could make a real difference. Cognitive biases play a role.

See also Personal, Team, and Organizational Effectiveness and Personal, Team, and Organizational Effectiveness for more related articles.

Related programs

Although the game of "What Haven't I told You" can be valuable for almost any group to play every once in a while, its value increases as the pace of unexpected events increases. My program, "Managing in Fluid Environments," explores how to apply this process to bring forth valuable but hidden information in situations where changes come along at such a rapid rate that the next change comes along before we reach the "New Status Quo" of the changes we're already dealing with. More about this program.

Are you planning an offsite or retreat for your organization? Or a conference for your professional society? My programs are fresh, original, and loaded with concrete tips that make an immediate difference. rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.comContact me to discuss possibilities.

Forthcoming issues of Point Lookout

Coming January 1: The Storming Puzzle: II

For some task-oriented work groups, Tuckman's model of small group development doesn't seem to fit. Storming seems to be absent, or Storming never ends. To learn how this illusion forms, look closely at Satir's Change Model and at what we call a task-oriented work group. Available here and by RSS on January 1.

And on January 8: The Storming Puzzle: III

For some task-oriented work groups, Tuckman's model of small group development seems not to fit. Storming seems to be either absent or continuous. To learn how this illusion forms, look closely at the processes that can precipitate episodes of Storming in task-oriented work groups. Available here and by RSS on January 8.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.com or (650) 787-6475, 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, )
• Get 2003-4 in Why Dogs Wag (PDF, )
• Get 2005-6 in Loopy Things We Do (PDF, )
• Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
• Get 2009-10 in The Questions Not Asked (PDF, )
• Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )

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-1000 words in your inbox in one hour. License any article from this Web site. More info