Status Risk and Risk Status
by Rick Brenner
One often-neglected project risk is the risk of inaccurately reported status. That shouldn't be surprising, because we often fail to report the status of the project's risks, as well. What can we do to better manage status risk and risk status?
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 high
when 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.
- 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.
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? rbrenMMAOjAAkEhAtoedVner@ChacwcHIhCKQeJGReeVLoCanyon.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
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.
More articles on Project Management:
- Flanking Maneuvers
- Historically, military logistics practice has provided a steady stream of innovations to many fields, including project management. But project managers can learn even more if we investigate battlefield tactics.
- Nine Project Management Fallacies: Part IV
- Some of what we "know" about managing projects just isn't so. Understanding these last three of the nine fallacies of project management helps reduce risk and enhances your ability to complete projects successfully.
- TINOs: Teams in Name Only
- Perhaps the most significant difference between face-to-face teams and virtual or distributed teams is their potential to develop from workgroups into true teams — an area in which virtual or distributed teams are at a decided disadvantage. Often, virtual and distributed teams are teams in name only.
- Long-Loop Conversations: Asking Questions
- In virtual or global teams, where remote collaboration is the rule, waiting for the answer to a simple question can take a day or more. And when the response finally arrives, it's often just another question. Here are some suggestions for framing questions that are clear enough to get answers quickly.
- Why Scope Expands: Part I
- Scope creep is depressingly familiar. Its anti-partner, spontaneous and stealthy scope contraction, has no accepted name, and is rarely seen. Why?
See also Project Management for more related articles.
Forthcoming Issues of Point Lookout
- Coming May 27: Compulsive Talkers at Work: Peers, Part II
- Our exploration of approaches for dealing with compulsive talkers now concludes, with Part II of a set of suggestions for what to do when peers who talk compulsively interfere with your work. Available here and by RSS on May 27.
- And on June 3: Just Make It Happen
- Many idolize the no-nonsense manager who says, "I don't want to hear excuses, just make it happen." We associate that stance with strong leadership. Sometimes, though, it's little more than abuse motivated by ambition or ignorance — or both. Available here and by RSS on June 3.
I offer email and telephone coaching at both corporate and individual rates.
Contact Rick for details at rbrenzxpwXvvWbGCnEoIiner@ChacEUdIwLgQjNuLecDHoCanyon.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:
Reprinting this article
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
- Cognitive Biases and Workplace Decision-Making
- For most of us, making decisions is a large part of what we do at work. And we tend to believe that we make our decisions rationally, except possibly when stressed or hurried. That is a mistaken belief — very few of our decisions are purely rational. In this eye-opening yet entertaining program, Rick Brenner guides you through the fascinating world of cognitive biases, and he'll give concrete tips to help you control the influence of cognitive biases. Read more about this program. Here's an upcoming date for this program:
- Managing in Fluid Environments
- Most people now work in environments that can best be characterized as fluid, because they're subject to continual change. We never know what's coming next. In such environments, managing — teams, projects, groups, departments, or the enterprise — often entails moving from surprise to surprise while somehow staying almost on track. It's a nerve-wracking existence. This program provides numerous tools that help managers who work in fluid environments. Read more about this program. Here's an upcoming date for this program: