Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 15, Issue 4;   January 28, 2015: The Limits of Status Reports: II

The Limits of Status Reports: II

by

We aren't completely free to specify the content or frequency of status reports from the people who write them. There are limits on both. Here's Part II of an exploration of those limits.
The cockpit of an A340 Airbus airliner

The cockpit of an A340 Airbus airliner. Airbus cockpits, like most modern cockpits, are designed along the lines of the "dark cockpit" principle. This design paradigm limits interruptions of pilot attention. Essentially, if all is well, the instrumentation refrains from announcing to the pilot that all is well. And when an anomaly arises that requires pilot action, the annunciator itself is the device that the pilot must use to take that action.

We can't do quite that well with status reports, but removing from the stream of reports all those reports that do not require management attention would be a good first step. A more advanced, but just as worthy, second step, would be to remove from reports that are filed any materials of the "all is well" type.

Photo by Timo Breidenstein.

In Part I of this discussion of the limits of status reports, we emphasized the experience and emotions of report authors. Let us now examine five more needs of report authors that arise from somewhat more concrete origins.

Situationally driven report cycles
The report cycle is the interval between successive reports. Calendar-driven or clock-driven report cycles are probably most common. Situationally driven report cycles are those in which events in the project trigger reports.
In relatively quiescent phases of projects, calendar-driven or clock-driven report cycles inevitably lead to reports that contain little useful information. When report authors are repeatedly compelled to generate such useless documents they sometimes develop a cynical attitude toward status reports generally, which can blossom into disrespect for supervisors, policy, and project governance. To reduce this risk, require reports on a calendar-driven or clock-driven schedule, but only if the situation warrants — that is, only if the report has useful content.
Adequate time and resources
Useful status reports highlight important information, distinguish new items from previously reported items, and include projections of future conditions and the assumptions that justify those projections.
Authoring status In relatively quiescent phases of
projects, calendar-driven or
clock-driven report cycles inevitably
lead to reports that contain
little useful information
reports that are actually worth reading requires time and effort. If time and effort are unavailable or severely limited, authoring reports conflicts with other efforts related to the task for which status is being reported.
Budgetary consistency
Projects already underway are operating with existing budgets, which were developed under assumptions regarding status-reporting procedures that were in place when the budgets were last revised.
Revisions of status-reporting procedures that create time and effort burdens significantly greater than those that were assumed in those budgets will compel report authors to reallocate time and resources, or worse, to find ways to circumvent the intention of the new status-reporting procedures. Budget revisions should accompany any changes in status-reporting procedures that require significant additional effort.
Necessary tools
Authoring status reports can be as simple as composing text documents — or not. If high quality reports require access to data, or data analysis, a lack of appropriate tools can make authorship a real burden.
If people lack the tools that would aid them in producing reports with data-related content, the quality of the reports will undoubtedly disappoint. Be certain that the necessary tools are available, and that report authors (or their assistants) know how to use them.
Necessary knowledge
In large projects, status reporting can require compiling reports from component elements of the project. Report authors can be completely dependent on cooperation by the leaders of those component elements.
Such cooperation is possible only if the conditions described above are met at every level of the project that must contribute to the higher-level status report, and if organizational leaders make clear that cooperation is expected.

If status report quality in your organization is disappointing, investigate. How many of these conditions are satisfied? How many are not?  The Limits of Status Reports: I First issue in this series  Go to top Top  Next issue: Bottlenecks: I  Next Issue

52 Tips for Leaders of Project-Oriented OrganizationsAre 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? rbrenyrWpTxHuyCrjZbUpner@ChacnoFNuSyWlVzCaGfooCanyon.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 Effective Communication at Work:

Freight Peer Exchange participants discuss freight business opportunitiesHow to Eliminate Meetings
Reducing the length and frequency of meetings is the holy grail of organizational science. I've attended many meetings on this topic, most of which have come to naught. Here are some radical ideas that could change our lives.
Senator Jeff Sessions grills Budget Director Sylvia Burwell on President Obama's 2015 Budget March 5, 2014That Was a Yes-or-No Question: I
In tense situations, one person might question another. As the respondent replies, the questioner interjects, "That was a yes-or-no question." The intent is to trap the respondent. How does this work, and how can the respondent escape the trap?
Donald Trump (left) and Hillary Clinton (right), candidates for U.S. President in 2016The Paradox of Carefully Chosen Words
When we take special care in choosing our words, so as to avoid creating misimpressions, something strange often happens: we create a misimpression of ignorance or deceitfulness. Why does this happen?
President Obama meets with leaders about job creation, December 3, 2009Naming Ideas
Participants in group discussions sometimes reference each other's contributions using the contributor's name. This risks offending the contributor or others who believe the idea is theirs. Naming ideas is less risky.
A wall of stoneRed Flags: II
When we find clear evidence of serious problems in a project or other collaboration, we sometimes realize that we had overlooked several "red flags" that had foretold trouble. In this Part II of our review of red flags, we consider communication patterns that are useful indicators of future problems.

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

Forthcoming issues of Point Lookout

A game of Jenga underwayComing September 4: Beating the Layoffs: I
If you work in an organization likely to conduct layoffs soon, keep in mind that exiting voluntarily before the layoffs can carry significant advantages. Here are some that relate to self-esteem, financial anxiety, and future employment. Available here and by RSS on September 4.
A child at a fork in a pathAnd on September 11: Beating the Layoffs: II
If you work in an organization likely to conduct layoffs soon, keep in mind that exiting voluntarily can carry advantages. Here are some advantages that relate to collegial relationships, future interviews, health, and severance packages. Available here and by RSS on September 11.

Coaching services

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