The Limits of Status Reports: II

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 informationreports 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?   First 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:

Decision Making and the Straw Man

In project work, we often make decisions with incomplete information. Sometimes we narrow the options to a few, examine their strengths and risks, and make a choice. In our deliberations, some advocates use a technique called the Straw Man fallacy. It threatens the soundness of the decision, and its use is very common.

When You Aren't Supposed to Say: III

Most of us have information that's "company confidential," or even more sensitive than that. Sometimes people who want to know what we know try to suspend our ability to think critically. Here are some of their techniques.

Inbox Bloat Recovery

If you have more than ten days of messages in your inbox, you probably consider it to be bloated. If it's been bloated for a while, you probably want to clear it, but you've tried many times, and you can't. Here are some effective suggestions.

Reframing Hurtful Dismissiveness

Targets of dismissive remarks often feel that their concerns are being judged as unimportant, which can be painful when their concerns are real. But there is an alternative to pain. It requires a little skill and discipline, but it can work.

Chronic Peer Interrupters: III

People who habitually interrupt others in meetings must be fairly common, because I'm often asked about what to do about them. And you can find lots of tips on the Web, too. Some tips work well, some generally don't. Here are my thoughts about four more.

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

Forthcoming issues of Point Lookout

Coming January 22: Storming: Obstacle or Pathway?

The Storming stage of Tuckman's model of small group development is widely misunderstood. Fighting the storms, denying they exist, or bypassing them doesn't work. Letting them blow themselves out in a somewhat-controlled manner is the path to Norming and Performing. Available here and by RSS on January 22.

And on January 29: A Framework for Safe Storming

The Storming stage of Tuckman's development sequence for small groups is when the group explores its frustrations and degrees of disagreement about both structure and task. Only by understanding these misalignments is reaching alignment possible. Here is a framework for this exploration. Available here and by RSS on January 29.

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