The Limits of Status Reports: I

People who work in project-oriented organizations are familiar with a fact of life called "status report." Report recipients are usually higher in organizational rank than report authors. Often, recipients actually have supervisory authority over the authors. Status reports are usually documents that contain enough information for report recipients to do their jobs.

The difference in organizational authority between authors and recipients leads some recipients to believe that they can request status reports in any form and format, with content of whatever nature they want. Some of these requests are unrealistic.

Unrealistic report requests have consequences. Reports become superficial. They arrive late. They're outdated. Some are even fictitious, in whole or in part. Some report requestors attribute low report quality to substandard performance by report authors, but unrealistic demands for report content, format, and frequency are often the root cause.

There are constraints on what we can reasonably expect of status report authors. Here's Part I of a set of requirements that enable status report authors to produce useful reports.

Belief in the value of the report

When status report authors believe that their reports are valuable to the report requestors, and that the reports are useful for performing legitimate management functions, report authors are more likely to produce valuable reports.

Said differently, when report authors believe that their reports aren't read, or that they're used only to find fault or to question the performance of the authors or the teams doing the work, those report authors are less likely to produce reports worth reading.

Psychological safety

Psychological safety is an attribute of a group. It is the degree to which group members, as a whole, believe that personal risk-taking will not lead to harsh judgment of the risk-taker by the group. In psychologically safe groups, members feel empowered to introduce new ideas, or question accepted ideas, or report what they know.

Low levels of psychological safety inhibit members from reporting conditions, events, or prospects that conflict with the group's established views, or which conflict with the group leader's preferences. Low levels of personal engagement
tend to limit the care, energy,
and passion of authors of
status reportsIn psychologically unsafe environments, as compared to safe environments, status reports are more likely to represent the wishes of the supervisor than they are to represent truth.

Personal engagement

Personal engagement of employees is a measure of the degree to which they regard themselves as involved with and committed to the goals and objectives of their roles in the workplace, and consequently, the goals and objectives of the larger organization.

Low levels of personal engagement tend to limit the care, energy, and passion of authors of status reports. They might produce the reports, but they will do so late, or superficially, or disingenuously, or with language that obviates actually gathering valid information.

We'll continue next time with several more constraints limiting what we can ask for in status reports.   Next issue in this series   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

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 Effective Communication at Work:

Mudfights

When we steer the discussion away from issues to attack the credibility, motives, or character of our debate partners, we often resort to a technique known as the ad hominem attack. It's unfair, it's unethical, and it leads to bad, expensive decisions that we'll probably regret.

Selling Uphill: Before and After

Whether you're a CEO appealing to your Board of Directors, your stockholders or regulators, or a project champion appealing to a senior manager, you have to "sell uphill" from time to time. Persuading decision makers who have some kind of power over us is a challenging task. How can we prepare the way for success now and in the future?

If Only I Had Known: I

Have you ever regretted saying something that you wouldn't have said if only you had known just one more little fact? Yeah, me too. We all have. Here are some tips for dealing with this sticky situation.

Communication Templates: I

Some communication patterns are so widely used that nearly everyone in a given cultural group knows them. These templates demand certain prescribed responses, and societal norms enforce them. In themselves, they're harmless, but there are risks.

Exasperation Generators: Opaque Metaphors

Most people don't mind going to meetings. They don't even mind coming back from them. It's being in meetings that can be so exasperating. What can we do about this?

See also Effective Communication at Work and Effective Communication at Work for more related articles.

Forthcoming issues of Point Lookout

Coming June 4: White-Collar Contractor Sabotage

Modern firms in competitive, dynamic markets draw on many types of employer/employee relationships, including contractors. By providing privileges and perks preferentially among these different types, they risk creating a caldron of resentments that can reduce organizational effectiveness. Available here and by RSS on June 4.

And on June 11: More Things I've Learned Along the Way: VI

When I gain an important insight, or when I learn a lesson, I make a note. Example: If you're interested in changing how a social construct operates, knowing how it came to be the way it is can be much less useful than knowing what keeps it the way it is. Available here and by RSS on June 11.

Coaching services

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