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?
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 welcomeWould you like to see your comments posted here? rbrenrHvWedhOMJBBLSjkner@ChacDsUFMiESYiwIbRCxoCanyon.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.
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:
- Email Antics: II
- Nearly everyone complains that email is a time waster. Yet much of the problem results from our own
actions. Here's Part II of a little catalog of things we do that help waste our time.
- Team Thrills
- Occasionally we have the experience of belonging to a great team. Thrilling as it is, the experience
is rare. How can we make it happen more often?
- Fill in the Blanks
- When we conceal information about ourselves and our areas of responsibility, we make room for others
to speculate. Speculation is rarely helpful. It's wise to fill in the blanks.
- Deciding to Change: Choosing
- When organizations decide to change what they do, the change sometimes requires that they change how
they make decisions, too. That part of the change is sometimes overlooked, in part, because it affects
most the people who make decisions. What can we do about this?
- The Risks of Too Many Projects: I
- Some organizations try to run too many development projects at once. Whether developing new offerings,
or working to improve the organization itself, taking on too many projects can defocus the organization
and depress performance.
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. rbrenyLaUKzOXcTHtlVRMner@ChacLKrFOIHhgAYHUqgdoCanyon.comContact me to discuss possibilities.
Forthcoming issues of Point Lookout
- Coming July 26: Strategic Waiting
- Time can be a tool. Letting time pass can be a strategy for resolving problems or getting out of tight places. Waiting is an often-overlooked strategic option. Available here and by RSS on July 26.
- And on August 2: Linear Thinking Bias
- When assessing the validity of problem solutions, we regard them as more valid if their discovery stories are logical, than we would if they're less than logical. This can lead to erroneous assessments, because the discovery story is not the solution. Available here and by RSS on August 2.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenLWszJGNGhphQuoyener@ChacAeJJIKAiljaSLfvGoCanyon.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:
- Get 2001-2 in Geese Don't Land on Twigs (PDF, USD 11.95)
- Get 2003-4 in Why Dogs Wag (PDF, USD 11.95)
- Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
- Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 28.99)
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
- Creating High Performance Virtual Teams
- Many people experience virtual teams as awkward, slow, and sometimes
frustrating. Even when most team members hail from the same nation or culture, and even when they all
speak the same language, geographic dispersion or the presence of employees from multiple enterprises
is often enough to exclude all possibility of high performance. The problem is that we lead, manage,
and support virtual teams in ways that are too much like the way we lead, manage, and support co-located
teams. In this program, Rick Brenner shows you how to change your approach to leading, managing, and
supporting virtual teams to achieve high performance using Simons' Four Spans model of high performance.
Read more about this program. Here's a date for this
- Baci Grill, 134 Berlin
Road, Berlin, CT 06416: September 19,
Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- Baci Grill, 134 Berlin Road, Berlin, CT 06416: September 19, Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- 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 organizational leaders, business
analysts, project sponsors, and project managers, the story is fascinating. Lessons abound. Read
more about this program. Here's a date for this program:
- CTCPA, 716 Brook Street,
Rocky Hill, CT 06067: September 20,
Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.
- CTCPA, 716 Brook Street, Rocky Hill, CT 06067: September 20, Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.
- The Power Affect: How We Express Our Personal Power
- Many people 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.