Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 2, Issue 23;   June 5, 2002: Status-Report as a Second Language

Status-Report as a Second Language

by

Sometimes, the clichés the losing team's players feed to sports reporters can have hidden meaning. So it is with Project Status Reports, especially for projects in trouble.
Submitting a status report

After the game, the reporters descend on the locker rooms. Most fascinating to me are the quotes from players in the Loser's Locker Room. They're feeling bad, yet most of the time they manage to say something that doesn't have to be bleeped. "They wanted it more than we did," or "The ball just didn't bounce our way." Some of these clichés have hidden meanings, and if you know the team well enough, you can understand what the players are really saying.

So it is with project status reports. Sometimes we struggle to put the best spin on the facts, or to convey indirectly a message that we cannot — or dare not — convey directly.

Have you learned to read, write, and speak Status-Report? Status-Report is a language that uses the same grammar and syntax as your own language, but the words mean something different. If you want to learn Status-Report, here are some examples.

What You Read
What It Might Mean
Forward progress continues to be inhibited by external difficulties.
It's not our fault.
This month we made good progress toward implementing the necessary infrastructure.
We're still trying to figure out what the heck we're supposed to be doing.
Fortunately, the delays have provided us with an opportunity to address other outstanding issues.
We're finding work for everybody so we won't lose them while we're waiting.
Requirements of important users for new versions with enhanced capabilities have driven us to provide alpha releases.
Sales has been beating us up so bad that we had to send them something. Heaven only knows if it works.
Progress toward completing this work has been slowed by an assortment of problems in other parts of the system.
We're stuck. We have no idea for how long. Pray.
The requisition to purchase the new software is running into some approval problems.
The recent reorg has had political implications. We might have to cut a deal.
It was determined that we will continue to watch the situation and assess our options at a later time.
We have no clue what to do about this.
No deliverables are completed at this time.
There is disagreement about the meaning of "completed." Or maybe "deliverable."
A detailed project plan cannot be created at this time because it is not yet known exactly what system will be designed and built.
I hate paperwork.
One problem could be lack of manpower. It was decided that if this was a major hindrance, we should look at ways of allocating resources for this purpose. The executive committee will follow up.
Management doesn't want to fund this project at an adequate level. We will try to get people to work on it anyway.

Find an old status report from a troubled project — maybe a report you wrote yourself. Translate it from Status-Report into plain language. How much more useful would it have been in that form? Go to top Top  Next issue: Getting Home in Time for Dinner  Next Issue

Rick BrennerThe article you've been reading is an archived issue of Point Lookout, my weekly newsletter. I've been publishing it since January, 2001, free to all subscribers, over the Web, and via RSS. You can help keep it free by donating either as an individual or as an organization. You'll receive in return my sincere thanks — and the comfort of knowing that you've helped to propagate insights and perspectives that can help make our workplaces a little more human-friendly. More

Your comments are welcome

Would you like to see your comments posted here? rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.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 Personal, Team, and Organizational Effectiveness:

The Marx brothers: Chico, Harpo, Groucho and ZeppoTINOs: Teams in Name Only
Perhaps the most significant difference between face-to-face teams and virtual or distributed teams is their potential to develop from workgroups into true teams — an area in which virtual or distributed teams are at a decided disadvantage. Often, virtual and distributed teams are teams in name only.
The Boy Who Cried Wolf, illustrated by Milo Winter in a 1919 Aesop anthologyWhy Don't They Believe Me?
When we want people to believe us, and they don't, it just might be a result of our own actions or demeanor. How does this happen?
Eastern Redcedar in crossection, with white sapwood on the outside edges, and red to deep reddish-brown heartwoodThe Retrospective Funding Problem
If your organization regularly conducts project retrospectives, you're among the very fortunate. Many organizations don't. But even among those that do, retrospectives are often underfunded, conducted by amateurs, or too short. Often, key people "couldn't make it." We can do better than this. What's stopping us?
A voltmeter with a needleHigh Falutin' Goofy Talk: II
Speech and writing at work are sometimes little more than high falutin' goofy talk, filled with puff phrases of unknown meaning and pretentious, tired images. Here's Part II of a collection of phrases and images to avoid.
An empty subway carAnticipating Absence: Internal Consulting
Most consultants are advisors from outside the organization. But when many employees are unavailable because of the Coronavirus pandemic, we need to find ways to access the knowledge that remains inside the organization. Internal consulting can help.

See also Personal, Team, and Organizational Effectiveness for more related articles.

Forthcoming issues of Point Lookout

Three gears in a configuration that's inherently locked upComing April 24: Antipatterns for Time-Constrained Communication: 1
Knowing how to recognize just a few patterns that can lead to miscommunication can be helpful in reducing the incidence of problems. Here is Part 1 of a collection of communication antipatterns that arise in technical communication under time pressure. Available here and by RSS on April 24.
A dangerous curve in an icy roadAnd on May 1: Antipatterns for Time-Constrained Communication: 2
Recognizing just a few patterns that can lead to miscommunication can reduce the incidence of problems. Here is Part 2 of a collection of antipatterns that arise in technical communication under time pressure, emphasizing those that depend on content. Available here and by RSS on May 1.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrendPtoGuFOkTSMQOzxner@ChacEgGqaylUnkmwIkkwoCanyon.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!
101 Tips for Managing ConflictFed up with tense, explosive meetings? Are you the target of a bully? Learn how to make peace with conflict.
Reader Comments About My Newsletter
A sampling:
  • Your stuff is brilliant! Thank you!
  • You and Scott Adams both secretly work here, right?
  • I really enjoy my weekly newsletters. I appreciate the quick read.
  • A sort of Dr. Phil for Management!
  • …extremely accurate, inspiring and applicable to day-to-day … invaluable.
  • More
52 Tips for Leaders of Project-Oriented OrganizationsAre your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around.
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.
Comprehensive collection of all e-books and e-bookletsSave a bundle and even more important save time! Order the Combo Package and download all ebooks and tips books at once.
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!