
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? Top
Next Issue
The 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? rbrenfHlRlTgqCIXkUHBTner@ChacrEuHRQPYVKkOucGfoCanyon.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.
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:
Coincidences Do Happen
- When we notice similarities between events, or possible patterns of events, we often attribute meaning
to them beyond what we can prove. Sometimes we guess right, and sometimes not. How can we improve our guesses?
The Artful Shirker
- Most people who shirk work are fairly obvious about it, but some are so artful that the people around
them don't realize what's happening. Here are a few of the more sophisticated shirking techniques.
Cooperations That Need to Be Collaborations
- Modern products and services are so complex that many people cooperate and collaborate to produce them.
When people are cooperating but the work actually requires collaborating, risks arise that can threaten
the success of the effort.
Improvement Bias
- When we set about improving how our organizations do things, we expose ourselves to the risk of finding
opportunities for improvement that offer very little improvement, while we overlook others that could
make a real difference. Cognitive biases play a role.
Rescheduling: Project Factors
- Rescheduling is what we do when we can no longer honor the schedule we have now. Of all causes of rescheduling,
the more controllable are those found at the project level. Attending to them in one project can limit
their effects on other projects.
See also Personal, Team, and Organizational Effectiveness and Personal, Team, and Organizational Effectiveness for more related articles.
Forthcoming issues of Point Lookout
Coming April 30: On Planning in Plan-Hostile Environments: II
- When we finally execute plans, we encounter obstacles. So we find workarounds or adjust the plans. But there are times when nothing we try gets us back on track. When this happens for nearly every plan, we might be working in a plan-hostile environment. Available here and by RSS on April 30.
And on May 7: Subject Matter Bullying
- Most workplace bullying tactics have analogs in the schoolyard — isolation, physical attacks, name-calling, and rumor-mongering are common examples. Subject matter bullying might be an exception, because it requires expertise in a sophisticated knowledge domain. And that's where trouble begins. Available here and by RSS on May 7.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenfHlRlTgqCIXkUHBTner@ChacrEuHRQPYVKkOucGfoCanyon.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
Follow Rick
Recommend this issue to a friend
Send an email message to a friend
rbrenfHlRlTgqCIXkUHBTner@ChacrEuHRQPYVKkOucGfoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed

- 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