Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 20, Issue 17;   April 22, 2020: Intentionally Misreporting Status: I

Intentionally Misreporting Status: I

by

When we report the status of the work we do, we sometimes confront the temptation to embellish the good news or soften the bad news. How can we best deal with these obstacles to reporting status with integrity?
A portion of the Viet Nam Veterans Memorial in Washington, D.C.

A portion of the Viet Nam Veterans Memorial in Washington, D.C. The United States' approach to conduct of the Viet Nam War is now viewed as having suffered from several strategic errors. One of these was the emphasis on enemy "body count" as a metric for engagement success. Pressure on field commanders to achieve high levels of this metric was so great that "body count inflation" occurred, as field commanders took steps to deliver reports that their superiors wanted to receive. The ensuing distorted view of "ground truth" made for difficulties in prosecuting the war. See "Declassification of the BDM Study, 'The Strategic Lessons Learned in Vietnam,'" available here.

Many of us file status reports regularly. Writing them is no fun. When the work is going well, writing the reports can feel like a boring chore that seems to be taking time away from doing real work. And when the work isn't going well, writing a status report can be a dreaded, painful chore that many find difficult to perform with integrity.

Whatever your role, reporting status with integrity is part of being a professional. Management relies on truth in status reporting as the foundation of its decision-making process. Because making appropriate decisions on the basis of misleading or incomplete status information is essentially impossible, misleading status reports are a threat to the enterprise, and therefore they threaten everyone's jobs.

Here's an example:

Jenn manages a sizeable enterprise effort — 85 people and a budget to match, over a period of just over two years. She and her team have divided the work into a set of tasks, each led by a task lead. Late last week, over coffee in his office, Mike told Jenn that Marigold, the module Mike's task team is working on, finally looks like it will pass its tests. Marigold has been a real problem. It's now two months late, but Mike is "very certain" that Marigold is "over the hump," as he put it.

So Jenn was looking forward to Mike's status report, which was due at the close of business last Friday. It didn't arrive. She texted him, emailed him, and voicemailed him, but here it is, 9:05 Monday morning, and he hasn't yet responded. Jenn's status report was due at 9:00. She needs to say something about Marigold.

Jenn has a difficult choice. Mike is a friend and respected engineering manager. Her choices for reporting Marigold's status are "Green" (all is well); or "Yellow" (probably OK pending resolution of an outstanding issue); or "Red" (in deep trouble needing prompt intervention); or "TBD" (I'm still investigating); or "Unknown" (no status report received).

Senior management has previously given everyone guidance: if status is unreported they want to know it. A missing status report could indicate communication system failures, accidents, ill health, concealment of major failure, insubordination — almost anything. Jenn also realizes that reporting status as "Unreported" could make trouble for her friend. She's tempted to report Marigold status as TBD.

I hope the problem is now a little clearer. Misleading status reports
are a threat to the
enterprise, and therefore
to everyone's jobs
Jenn is pondering the TBD choice, because Marigold's status is still being determined. Or she could report Marigold status as Yellow, because she had received an oral status report from Mike that indicated that the test was underway and the results would be available soon. Or she could report Marigold status as Green, because Mike was "very certain" that all is well, and Marigold would pass the test.

All of these choices are "technically" honest in the sense that there exist facts to support each choice. But these choices are also "technically" dishonest, because they would convey a misimpression of the true situation, namely, that Marigold's status is unreported.

The choice one makes in these situations depends on one's definition of "honesty" in status reporting. One test people use to determine honesty is the Evidence Test:

Do I have the facts and evidence I need to support the status I chose to report?

And another very different test is the Reality Test:

Upon receiving my report, will the recipient of my report have an impression of the situation that's actually in alignment with reality, as I know it?

Reports that pass the Evidence Test might not pass the Reality Test. But even though the reports Management needs are those that pass the Reality Test, many people write reports that pass the Evidence Test more closely than they do the Reality Test. Because Reality reports can trigger management actions that friends, colleagues, managers, and executives don't like, some people are reluctant to file Reality reports. Reporting Reality sometimes requires integrity, and it can be difficult at times. But avoiding reporting Reality can be the more difficult course. Why is reporting status with integrity so difficult? I'll examine that question in more detail next time.  Next in this series Go to top Top  Next issue: Intentionally Misreporting Status: II  Next Issue

303 Secrets of Workplace PoliticsIs every other day a tense, anxious, angry misery as you watch people around you, who couldn't even think their way through a game of Jacks, win at workplace politics and steal the credit and glory for just about everyone's best work including yours? Read 303 Secrets of Workplace Politics, filled with tips and techniques for succeeding in workplace politics. More info

Your comments are welcome

Would you like to see your comments posted here? rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.comSend me your comments by email, or by Web form.

About Point Lookout

This article in its entirety was written by a 
          human being. No machine intelligence was involved in any way.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 Workplace Politics:

The spine of a human maleScopemonging: When Scope Creep Is Intentional
Scope creep is the tendency of some projects to expand their goals. Usually, we think of scope creep as an unintended consequence of a series of well-intentioned choices. But sometimes, it's much more than that.
Firefighter lighting grass using a drip torchBeyond Our Control
When bad things happen, despite our plans and our best efforts, we sometimes feel responsible. We failed. We could have done more. But is that really true? Aren't some things beyond our control?
Brian Urquhart of the Office of the UN Under-Secretaries Without Porfolios. (1 January 1956)Staying in Abilene
A "Trip to Abilene," identified by Jerry Harvey, is a group decision to undertake an effort that no group members believe in. Extending the concept slightly, "Staying in Abilene" happens when groups fail even to consider changing something that everyone would agree needs changing.
Two hermit crabs in their snail shellsThe Perils of Limited Agreement
When a group member agrees to a proposal, even with conditions, the group can move forward. Such agreement is constructive, but there are risks. What are those risks and what can we do about them?
A shark of unspecified speciesNarcissistic Behavior at Work: VII
Narcissistic behavior at work prevents trusting relationships from developing. It also disrupts existing relationships, and generates toxic conflict. One class of behaviors that's especially threatening to relationships is disregard for the feelings of others. In this part of our series we examine the effects of that disregard.

See also Workplace Politics and Managing Your Boss for more related articles.

Forthcoming issues of Point Lookout

A dangerous curve in an icy roadComing May 1: Antipatterns for Time-Constrained Communication: 2
Recognizing just a few patterns that can lead to miscommunication can reduce the incidence of miscommunications. Here's Part 2 of a collection of antipatterns that arise in communication under time pressure, emphasizing those that depend on content. Available here and by RSS on May 1.
And on May 8: Antipatterns for Time-Constrained Communication: 3
Recognizing just a few patterns that can lead to miscommunication can reduce the incidence of problems. Here is Part 3 of a collection of antipatterns that arise in technical communication under time pressure, emphasizing past experiences of participants. Available here and by RSS on May 8.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.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:

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-1000 words in your inbox in one hour. License any article from this Web site. More info

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at X, or share a post Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
Technical Debt for Policymakers BlogMy 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!
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.
If your teams don't yet consistently achieve state-of-the-art teamwork, check out this catalog. Help is just a few clicks/taps away!
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.