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? 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 Conflict Management:
Masked Messages
- Sometimes what we say to each other isn't what we really mean. We mask the messages, or we form them
into what are usually positive structures, to make them appear to be something less malicious than they
are. Here are some examples of masked messages.
The Nominal Fallacy at Work
- Using logical fallacies at work — intentionally or otherwise — costs real money. The nominal
fallacy is probably responsible for much delay in addressing our real problems.
Newtonian Blind Alleys: II
- Some of our decisions don't turn out well. The nature of our errors does vary, but a common class of
errors is due to applying concepts from physics originated by Isaac Newton. One of these is the concept
of spectrum.
Newly Virtual Politics: Choices
- Pandemic or not, workplace politics marches on, though politics might take slightly different forms
in a pandemic. Those different forms make new choices available, and render some formerly effective
choices ineffective.
Risk Acceptance: One Path
- When a project team decides to accept a risk, and when their project eventually experiences that risk,
a natural question arises: What were they thinking? Cognitive biases, other psychological phenomena,
and organizational dysfunction all can play roles.
See also Conflict Management and Conflict Management for more related articles.
Forthcoming issues of Point Lookout
Coming February 26: Devious Political Tactics: Bad Decisions
- When workplace politics influences the exchanges that lead to important organizational decisions, we sometimes make decisions for reasons other than the best interests of the organization. Recognizing these tactics can limit the risk of bad decisions. Available here and by RSS on February 26.
And on March 5: On Begging the Question
- Some of our most expensive wrong decisions have come about because we've tricked ourselves as we debated our options. The tricks sometimes arise from rhetorical fallacies that tangle our thinking. One of the trickiest is called Begging the Question. Available here and by RSS on March 5.
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
