One of the best ways to control project success is to meet or exceed expectations. \u00a0One of the best ways to understand and impact expectations is through regular status and review. \u00a0Therefore, status reporting habits are an excellent way to improve the chances of success for your project.<\/p>\n
I had an experience that has made me a firm believer in providing my clients with a weekly status. \u00a0In this case, the problem came from a sub that I trusted, and a customer\u00a0that was happy and trusting. \u00a0I would periodically touch base on progress and tasks. \u00a0I left things to run on their own as did the client.<\/p>\n
We had some communication issues that led to my sub doing more testing and rework than the customer desired. \u00a0This\u00a0confusion would have been a small problem if caught early, but instead, it went on for weeks. \u00a0Thus, by the time the client saw a large number of hours on small numbers of tasks, it looked like they were getting over-billed. \u00a0In a sense, they were. \u00a0Therefore, we ended up eating a bunch of billed hours and rolled the sub off of the client.<\/p>\n
A weekly status of hours and work would have brought this issue to a head earlier. \u00a0That early catch would have been easy to correct and saved headaches on both sides. \u00a0This\u00a0situation could have ended worse, but part of the reason I did not over-communicate was due to the great relationship I had with the client.<\/p>\n
I learned from this bad experience that communicating status is an important detail to address. \u00a0I now send a status each week to every client large and small. \u00a0Most status reports are one project and one page. \u00a0However, sometimes I go to multiple projects per client and multiple pages. \u00a0I may also append some pages of notes or deliverable recap to make it easy to link tasks to outcomes.The status I send is not very complicated. \u00a0I list what was done, roughly how many hours were spent on the tasks, and then estimates of tasks and time for the week ahead.<\/p>\n
The status report takes less than fifteen minutes to put together each week. \u00a0However, I did spend close to an hour creating a template that is easy to fill out and still looks pretty good. Thus, the time I invested has more than paid for itself over the last few years.<\/p>\n
The status I send is not very complicated. \u00a0I list what was done, roughly how many hours were spent on the tasks, and then estimates of tasks and time for the week ahead. \u00a0This takes maybe fifteen minutes to put together each week. \u00a0However, I did spend close to an hour creating a template that is easy to fill out and still looks pretty good. Thus, the time I invested has more than paid for itself over the last few years.<\/p>\n
The art of making a weekly status valuable is in its brevity. \u00a0Keep to simple line items and maybe even a summary at the top. \u00a0Consider that a client will only read the first part of the status. \u00a0Anything below the fold may be missed. \u00a0In particular, this scanning of status will occur as they receive one week after week. \u00a0Yes, it is a little bit of a CYA, but the real goal of this is to make sure you are on the same page as your clients about work to be done and priorities.<\/p>\n
A weekly status call would be a good way to keep it simple, but I recommend a written version as well. \u00a0The report provides something for future reference by your client. \u00a0However, it also provides you a great checklist to make sure your tasks completed each week match what you said you would do. \u00a0Communicating status seems like something everyone knows and values, but it is easy to get away from the process. \u00a0Beware if you do. \u00a0The lack of communication can cost contracts, clients, or even reputation.<\/p>\n","protected":false},"excerpt":{"rendered":"
One of the best ways to control project success is to meet or exceed expectations. \u00a0One of the best ways to understand and impact expectations is through regular status and review. \u00a0Therefore, status reporting habits are an excellent way to improve the chances of success for your project. A Failure of Communicating Status I had […]<\/p>\n","protected":false},"author":1,"featured_media":282,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"footnotes":""},"categories":[13],"tags":[4,22,21],"class_list":["post-280","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-consulting-strategies","tag-best-practices","tag-communication","tag-consulting"],"yoast_head":"\n