| 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
| |
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.
liver 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:
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 info
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.
See also Personal, Team and Organizational Effectiveness, Effective Meetings and Problem Solving and Creativity for more related articles.
Available in early 2009: 2007-2008.
Ever wonder if there isn't a better way to travel? Travel is essential, but the hassles of travel aren't. Read 202 Tips for Business Travel to learn how to convert business travel from a time-wasting hassle to a breeze. Revised and updated for 2008 with 101 new tips! Check it out!
Projects never go quite as planned. We expect that, but we don't expect disaster. How can we get better at spotting disaster when there's still time to prevent it? How to Spot a Troubled Project Before the Trouble Starts is filled with tips for executives, senior managers, managers of project managers, and sponsors of projects in project-oriented organizations. Check it out!
add value to your Web sites quickly and easily. Pick up the HTML to link to this article in a choice of formats.
Are your projects always late and over budget? Are your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around. Read 52 Tips for Leaders of Project-Oriented Organizations, filled with tips & techniques for organizational leaders. Check it out!
A Tip a Day arrives by email 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!
Save a bundle and even more important save time! Order the Combo Package and download all 21 ebooks and tips books at once, for one low price of USD 161.95 vs. USD 332.15, a savings of over 51% compared to ordering them separately.