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.
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 welcomeWould you like to see your comments posted here? rbrenUbCbXxkNiTNkdCixner@ChacIQLxmoCGRPdAnjsjoCanyon.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 Effective Communication at Work:
- Some Truths About Lies: I
- However ethical you might be, you can't control the ethics of others. Can you tell when someone knowingly
tries to mislead you? Here's Part I of a catalog of techniques misleaders use.
- Nasty Questions: II
- In meetings, telemeetings, and email we sometimes ask questions that aren't intended to elicit information.
Rather, they're indirect attacks intended to advance the questioner's political agenda. Here's part
two of a catalog of some favorite tactics.
- How 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.
- When Over-Delivering Makes Trouble
- When responding to inquiries such as "Is that correct?" we sometimes err by giving too many
reasons why it's incorrect. Patterns of over-delivery can lead to serious trouble. Here's how.
- Embolalia and Stuff Like That: I
- When we address others, we sometimes use filler — so-called automatic speech or embolalia —
without thinking. Examples are "uh," "um," and "er," but there are more
complex forms, too. Embolalia are usually harmless, if mildly annoying to some. But sometimes they can
Forthcoming issues of Point Lookout
- Coming August 23: Look Where You Aren't Looking
- Being blindsided by an adverse event could indicate the event's sudden, unexpected development. It can also indicate a failure to anticipate what could have been reasonably anticipated. How can we improve our ability to prepare for adverse events? Available here and by RSS on August 23.
- And on August 30: They Just Don't Understand
- When we cannot resolve an issue in open debate, we sometimes try to explain the obstinacy of others. The explanations we favor can tell us more about ourselves than they do about others. Available here and by RSS on August 30.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenzyjqGtaurzztQLzyner@ChacNDNKdVfiFVcfKFhAoCanyon.com or (617) 491-6289, 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, USD 11.95)
- Get 2003-4 in Why Dogs Wag (PDF, USD 11.95)
- Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
- Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 28.99)
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 words in your inbox in one hour. License any article from this Web site. More info
- The Race to the South Pole: Ten Lessons for Project Managers
- On 14 December 1911, four men led by Roald
Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen
had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished.
As historical drama, why this happened is interesting enough, but to organizational leaders, business
analysts, project sponsors, and project managers, the story is fascinating. Lessons abound. Read
more about this program. Here are some dates for this program:
- The Westin Virginia Beach Town Center, 4535 Commerce Street,
Virginia Beach, VA 23462: September 13,
Monthly Meeting, Hampton Roads Chapter of the Project Management Institute. Register now.
- CTCPA, 716 Brook Street,
Rocky Hill, CT 06067: September 20,
Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.
- The Westin Virginia Beach Town Center, 4535 Commerce Street, Virginia Beach, VA 23462: September 13, Monthly Meeting, Hampton Roads Chapter of the Project Management Institute. Register now.
- Creating High Performance Virtual Teams
- Many people experience virtual teams as awkward, slow, and sometimes
frustrating. Even when most team members hail from the same nation or culture, and even when they all
speak the same language, geographic dispersion or the presence of employees from multiple enterprises
is often enough to exclude all possibility of high performance. The problem is that we lead, manage,
and support virtual teams in ways that are too much like the way we lead, manage, and support co-located
teams. In this program, Rick Brenner shows you how to change your approach to leading, managing, and
supporting virtual teams to achieve high performance using Simons' Four Spans model of high performance.
Read more about this program. Here's a date for this
- Baci Grill, 134 Berlin
Road, Berlin, CT 06416: September 19,
Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- Baci Grill, 134 Berlin Road, Berlin, CT 06416: September 19, Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- The Power Affect: How We Express Our Personal Power
- Many people who possess real organizational power have a characteristic demeanor. It's the way they project their presence. I call this the power affect. Some people — call them power pretenders — adopt the power affect well before they attain significant organizational power. Unfortunately for their colleagues, and for their organizations, power pretenders can attain organizational power out of proportion to their merit or abilities. Understanding the power affect is therefore important for anyone who aims to attain power, or anyone who works with power pretenders. Read more about this program.