What Haven't I Told You?
by Rick Brenner
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?"
"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.
are often emergent.
They're made of
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 or as . 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? 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.
More articles on Personal, Team, and Organizational Effectiveness
- Abraham, Mark, and Henny
- Our plans, products, and processes are often awkward, bulky, and complex. They lack a certain spiritual quality that some might call elegance. Yet we all recognize elegance when we see it. Why do we make things so complicated?
- Snapshots of Squirming Subjects
- Today we use data as a management tool. We store, recall, and process data about our operations to help us manage resources and processes. But this kind of management data is often scattered, out of date, or just plain incorrect, and taking a snapshot doesn't work. There is a better way.
- Getting Around Hawthorne
- The Hawthorne Effect appears when we measure employee attitudes or behavior — when people know they're being measured, they modify their behavior. How can we measure attitudes with a minimum of distortion from the Hawthorne Effect?
- Let Me Finish, Please
- We use meetings to exchange information and to explore complex issues. In open discussion, we tend to interrupt each other. Interruptions can be disruptive, distracting, funny, essential, and frustratingly common. What can we do to limit interruptions without depriving ourselves of their benefits?
- Organizational Firefighting
- Sometimes companies or projects get into trouble, and "fires" erupt one after another. When this happens, we say we're in "firefighting" mode. But it's more than a metaphor — we have a lot to learn from wildland firefighters.
See also Personal, Team, and Organizational Effectiveness, Effective Meetings and Problem Solving and Creativity for more related articles.
I offer email and telephone coaching at both corporate and individual rates.
Contact Rick 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
- Cognitive Biases and Workplace Decision-Making
- For most of us, making decisions is a large part of what we do at work. And we tend to believe that we make our decisions rationally, except possibly when stressed or hurried. That is a mistaken belief — very few of our decisions are purely rational. In this eye-opening yet entertaining program, Rick Brenner guides you through the fascinating world of cognitive biases, and he'll give concrete tips to help you control the influence of cognitive biases. Read more about this program. Here's an upcoming date for this program:
- MITRE, in Bedford, MA: October 21, Monthly Meeting, Boston SPIN.
- The Politics of Meetings for People Who Hate Politics
- There's a lot more to running an effective meeting than having the right room, the right equipment, and the right people. With meetings, the whole really is more than the sum of its parts. How the parts interact with each other and with external elements is as important as the parts themselves. And those interactions are the essence of politics for meetings. This program explores techniques for leading meetings that are based on understanding political interactions, and using that knowledge effectively to meet organizational goals. Read more about this program. Here are some upcoming dates for this program:
- Managing Virtual Meetings for Real Results
- Leading or participating in virtual meetings — teleconferences, Web conferences, video conferences, and more — is challenging. Miscommunications, misunderstandings, distractions, politics, and interpersonal conflict all thrive in the typical environment of the virtual team. We'll inventory the challenges virtual meeting leaders and participants face, and provide tools for anticipating and addressing them. The focus of this program is practical — attendees will learn concrete techniques for preventing and dealing with the problems that arise in virtual meetings. Read more about this program. Here's an upcoming date for this program:
- 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 project managers, the story is fascinating. Lessons abound. Read more about this program. Here's an upcoming date for this program: