Warner glared his famous glare, and for once, he had a legitimate complaint. "Let me see if I have this right," he began. "You knew back in July that we had memory footprint problems, but you waited to report it until now. Is that right?"
Robin had nowhere to go. "Yes, that's right. We felt it was best to wait until we were sure we had a problem."
"Well, we have a problem now, don't we?" Warner replied.
"Yes, and that's why…" Robin began, but Warner wouldn't let her finish.
"That's why you're reporting it, I know, I know."
Robin has made a serious error, but the mistake isn't hers alone. She failed to alert the project sponsor to a problem when she first became aware of it. And Warner's intimidating style tends to discourage early reporting of trouble.
Together, they're living out one of the consequences of status risk: the risk of failing to report status promptly and fully. Here are some sources of status risk:
Status risk is highwhen realistic status
reporting is punishable
- Rewarding positive reports and punishing negative reports
- At any link in the status reporting chain, the report recipient might be signaling that only positive reports are acceptable. The signal can be unintentional, or it can be very deliberate.
- Prior experience
- People can bring to the reporting task their experiences with prior projects or prior managers. If they've learned along the way that realistic reporting is punishable, they're likely to apply those past lessons.
- Turnover
- When new people assume responsibility for work underway, their perceptions about status are likely to be inaccurate.
- Wishful thinking
- Because most of us want things to go well, we sometimes fool ourselves that our wishes match reality, especially if we've become attached to the task. See "Managing Wishful Thinking Risk," Point Lookout for October 21, 2015, for more about wishful thinking.
Making status reporting a group task helps mitigate status risk. Form a status review team that's responsible for reviewing status reports. Normally, they'll easily reach consensus, but any failure to reach consensus is valuable information in itself — it signals the need for a closer look by management.
Even when we manage Status Risk, there remains the too-common failure to report — or even to track — Risk Status. Most status reports focus on budget, schedule, milestones achieved, work completed, and so on. But we rarely report or track the status of our initial risk profile, and that can lead to surprised (and very upset) project sponsors. Including a review of the risk profile in each status report helps to limit the incidence of surprising disasters.
Status Risk and Risk Status are intimately intertwined. In part, the sources of status risk contribute to our spotty reporting of risk status. And by creating the conditions for surprising disasters, failure to track risk status can enhance status risk. Address both — or don't bother. Top
Next Issue
Are your projects always (or almost 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 and techniques for organizational leaders. Order Now!
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:
Nine Project Management Fallacies: I
- Most of what we know about managing projects is useful and effective, but some of what we "know"
just isn't so. Identifying the fallacies of project management reduces risk and enhances your ability
to complete projects successfully.
Unnecessary Boring Work: I
- Work can be boring. Some of us must endure the occasional boring task, but for many, everything about
work is boring. It doesn't have to be this way.
Unresponsive Suppliers: II
- When a project depends on external suppliers for some tasks and materials, supplier performance can
affect our ability to meet deadlines. How can communication help us get what we need from unresponsive
suppliers?
The Planning Fallacy and Self-Interest
- A well-known cognitive bias, the planning fallacy, accounts for many unrealistic estimates of project
cost and schedule. Overruns are common. But another cognitive bias, and organizational politics, combine
with the planning fallacy to make a bad situation even worse.
Power Distance and Risk
- Managing or responding to project risks is much easier when team culture encourages people to report
problems and to question any plans they have reason to doubt. Here are five examples that show how such
encouragement helps to manage risk.
See also Project Management for more related articles.
Forthcoming issues of Point Lookout
Coming September 17: Workplace Bullying Doesn't Work
- A common belief about perpetrators of workplace bullying is that they have an outsized view of themselves and their power. The truth might be rather different. They could be dealing with an addiction cycle — a sense of weakness after the effects of previous bullying incidents have dissipated. Available here and by RSS on September 17.
And on September 24: Time Is Not a Resource
- In the project management community, it's often said that time is the most precious resource. Although time is indeed precious, to regard it as a resource — like finance, equipment, or people — can be a dangerous mistake. Time is not a resource. Available here and by RSS on September 24.
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
