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 jobsJenn 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 Top Next Issue
Is 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 welcomeWould you like to see your comments posted here? rbrendbTtLLSVlUPPCNkAner@ChacthFxWKdRwnLylOCDoCanyon.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.
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 Workplace Politics:
- What Insubordinate Nonsubordinates Want: III
- When you're responsible for an organizational function, and someone not reporting to you doesn't comply
with policies you rightfully established, trouble looms. What role do supervisors play?
- Grace Under Fire: II
- When we debate at work, things sometimes turn unpleasant. Out of control, one party might maneuver the
other into losing control. If we have better tools for recognizing these tactics, we're better able
to maintain self-control. Here's Part II of such a toolkit.
- Gratuitous Complexity as a Type III Error
- Some of the technological assets we build — whether hardware, software, or procedures —
are gratuitously complex. That's an error, but an error of a special kind: it can be the correct solution
to the wrong problem.
- Appearance Anti-patterns: II
- When we make decisions based on appearance we risk making errors. We create hostile work environments,
disappoint our customers, and create inefficient processes. Maintaining congruence between the appearance
and the substance of things can help.
- Quasi-Narcissistic Quasi-Subordinates
- One troublesome kind of workplace collaboration includes those that combine people of varied professions
and ranks for a specific short-term mission. Many work well, but when one of the group members displays
quasi-narcissistic behaviors, trouble looms.
Forthcoming issues of Point Lookout
- Coming October 5: Downscoping Under Pressure: I
- When projects overrun their budgets and/or schedules, we sometimes "downscope" to save time and money. The tactic can succeed — and fail. Three common anti-patterns involve politics, the sunk cost effect, and cognitive biases that distort estimates. Available here and by RSS on October 5.
- And on October 12: Downscoping Under Pressure: II
- We sometimes "downscope" projects to bring them back on budget and schedule when they're headed for overruns. Downscoping doesn't always work. Cognitive biases like the sunk cost effect and confirmation bias can distort decisions about how to downscope. Available here and by RSS on October 12.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrendbTtLLSVlUPPCNkAner@ChacthFxWKdRwnLylOCDoCanyon.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