Mort now understood why Ginny had wanted to meet off-site. "I'm worried," she was saying, "Dave always seems to be overloaded. Even back in March, when things were going smoothly on both our projects. So I thought I'd check with you."
"Hmm. I've been getting the same story," Mort replied. "He keeps saying that work on other projects is making him miss his dates."
Mort and Ginny then talked with Sid, the lead on Dave's third project team. Sid told them that he'd heard the same thing from Dave, too. Once all three of them — Mort, Ginny, and Sid — pooled their information, they knew they needed help from HR. That way they could possibly save all three projects, and the career of a bright but troubled employee.
By working together, and being open with each other, Mort, Ginny, and Sid combined what they knew. The information each one had wasn't enough in itself to tell any one of them what to do, but combined, they were able to choose an effective management intervention. By fusing together all they knew, they could see the real problem through the fog.
To see through the fog that hides the rocks, you sometimes need information from outside your project. Here are a few tips for seeing through the fog.
To see through thefog, you sometimes need
information from
outside it
- Share what you know with other project managers
- Compare issues lists from several projects, looking for patterns and commonalities. Compare schedules to look ahead for contention for people or resources. Talk to other customers of suppliers or subcontractors, both within your organization and outside it if you can.
- Learn from history
- If you suspect a problem might be looming, interview past project managers who've worked with the people or subcontractor that might be at issue.
- Use cluster analysis
- Search defect reports and schedule slips to find clusters of problems. When you find a cluster around a single component, consider restarting that component from scratch, possibly with a different team. Look carefully at other components that were built the same way, possibly on other projects.
- Be uniformly skeptical
- Components that were built by people who are well regarded sometimes escape early rigorous testing because of favorable bias. Examine all test plans for bias and make sure that all components are treated equally skeptically.
Projects are usually in one of four states: not yet begun, finished, in crisis, and about to be in crisis. The only transition that happens unexpectedly is from about-to-be-in-crisis to crisis. By learning to see through the fog, you can make that transition a little more gracefully, and a lot less often. 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
Would you like to see your comments posted here? rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.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.
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 Project Management:
- Some Causes of Scope Creep
- When we suddenly realize that our project's scope has expanded far beyond its initial boundaries —
when we have that how-did-we-ever-get-here feeling — we're experiencing the downside of scope
creep. Preventing scope creep starts with understanding how it happens.
- Scheduling as Risk Management
- When we schedule a complex project, we balance logical order, resource constraints, and even politics.
Here are some techniques for using scheduling to manage risk and reduce costs.
- The Retrospective Funding Problem
- If your organization regularly conducts project retrospectives, you're among the very fortunate. Many
organizations don't. But even among those that do, retrospectives are often underfunded, conducted by
amateurs, or too short. Often, key people "couldn't make it." We can do better than this.
What's stopping us?
- Scope Creep, Hot Hands, and the Illusion of Control
- Despite our awareness of scope creep's dangerous effects on projects and other efforts, we seem unable
to prevent it. Two cognitive biases — the "hot hand fallacy" and "the illusion
of control" — might provide explanations.
- Managing Wishful Thinking Risk
- When things go wrong, and we look back at how we got there, we must sometimes admit to wishful thinking.
Here's a framework for managing the risk of wishful thinking.
See also Project Management and Project Management for more related articles.
Forthcoming issues of Point Lookout
- Coming January 22: Storming: Obstacle or Pathway?
- The Storming stage of Tuckman's model of small group development is widely misunderstood. Fighting the storms, denying they exist, or bypassing them doesn't work. Letting them blow themselves out in a somewhat-controlled manner is the path to Norming and Performing. Available here and by RSS on January 22.
- And on January 29: A Framework for Safe Storming
- The Storming stage of Tuckman's development sequence for small groups is when the group explores its frustrations and degrees of disagreement about both structure and task. Only by understanding these misalignments is reaching alignment possible. Here is a framework for this exploration. Available here and by RSS on January 29.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.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
Follow Rick
Recommend this issue to a friend
Send an email message to a friend
rbrenjTnUayrCbSnnEcYfner@ChacdcYpBKAaMJgMalFXoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed
- Your stuff is brilliant! Thank you!
- You and Scott Adams both secretly work here, right?
- I really enjoy my weekly newsletters. I appreciate the quick read.
- A sort of Dr. Phil for Management!
- …extremely accurate, inspiring and applicable to day-to-day … invaluable.
- More