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? rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.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:
When Change Is Hard: II- When organizational change is difficult, we sometimes blame poor leadership or "resistance."
But even when we believe we have good leadership and the most cooperative populations, we can still
encounter trouble. Why is change so hard so often?
Scope Creep and the Planning Fallacy- Much is known about scope creep, but it nevertheless occurs with such alarming frequency that in some
organizations, it's a certainty. Perhaps what keeps us from controlling it better is that its causes
can't be addressed with management methodology. Its causes might be, in part, psychological.
More Obstacles to Finding the Reasons Why- Retrospectives — also known as lessons learned exercises or after-action reviews — sometimes
miss important insights. Here are some additions to our growing catalog of obstacles to learning.
Anticipating Absence: Quarantine and Isolation- When the pandemic compels some knowledge workers to quarantine or isolate, we tend to treat them as
if they were totally unavailable. But if they're willing and able to work, even part-time, they might
be able to continue to contribute. To make this happen, work out conditions in advance.
Ten-Minute Training- Despite decades of evolution of technology-assisted workplace learning, instructor-led classroom formats
remain the most popular and effective. Now perhaps videoconferencing can help to achieve that effectiveness
at lower cost.
See also Project Management for more related articles.
Forthcoming issues of Point Lookout
Coming October 1: On the Risks of Obscuring Ignorance- A common dilemma in knowledge-based organizations: ask for an explanation, or "fake it" until you can somehow figure it out. The choice between admitting your own ignorance or obscuring it can be a difficult one. It has consequences for both the choice-maker and the organization. Available here and by RSS on October 1.
And on October 8: Responding to Workplace Bullying- Effective responses to bullying sometimes include "pushback tactics" that can deter perpetrators from further bullying. Because perpetrators use some of these same tactics, some people have difficulty employing them. But the need is real. Pushing back works. Available here and by RSS on October 8.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.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
rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed
My blog, Technical Debt for Policymakers, offers
resources, insights, and conversations of interest to policymakers who are concerned with managing
technical debt within their organizations. Get the millstone of technical debt off the neck of your
organization!- 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
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 