In project management world, here is typically how communication about tasks takes place.
A team member completes a task assigned to her, and then makes an additional and distinct effort to communicate that she is done with it. She can do so by email, updating a project management tool or by simply shouting out loud in the team hall.
While the shouting-out-loud may not be fun, what is worse is that she can potentially skip the shouting (or sending the email).
The stage of working on the task assigned to her, and her communication about its completion, are treated as two completely independent and distinct items. The communication requires proactive and explicit effort – sometimes very much an after-thought event!
This has the obvious failing of missing out on the communication part. After all, it’s the task that is more important, right? And you are doing a favor by additionally letting others know about it.
So imagine the day when she forgets to shout out in the hall that she is done. While you may not miss the shouting, you will certainly miss out on the communication. You would never know that you can now start something which was based on she being done. Even more, she may be wondering why you are not starting what you were supposed to. After all, she is done!
The problem is that communicating about something we are responsible for has always been kept separate – and worst even secondary and less important – than the actual work being done. Project managers consider it their responsibility going around actively asking for statuses. Team members consider updating the project management tool an unnecessary chore – better left for end of the day or when pounded on by the project manager. Software programmers simply ‘check-in’ their completed code but don’t intimate others they are done. And the list goes on.
This has the obvious failings of everybody in the team being at different levels of understandings. You may be waiting for something which is already done – which is obviously a productivity loss. There may be duplication of effort. There can be chaos and confusion. There can be a lot of shouting – but all for the wrong reason.
Common sense, right? We all know these problems. Unfortunately, this is how we fix it. We motivate more active communication. We keep enforcing it as a distinct post-work activity.
We need to merge the ‘working’ and ‘communicating’ parts.
Communicating to relevant people about what you are doing needs to be part of the task itself – not separate from it. The task is not done until it is completed and communicated to whomever it needs to be communicated to. It is not a post-activity, afterthought or favor. It is the final step of what you are doing.
Updating your project tracking tool needs be part of the work – not separate from it. Sending an email intimation should be done before you can say you are done. Telling your fellow programmers that you have checked in the code, and they can proceed, is part of your work – not a bonus item you add.
There is no such thing as no communication – you are always communicating. If you are not shouting out in the hall – all you are saying is that you are not done!
Great piece Ather and I wonder if you have suggestions on how to mix communication with task? Lot of times, project management tools are used as a ‘way to communicate’ done status of a task which is a bad idea as you mentioned. Do you literally want us to shout (and do a bit dance may be) in the hall when we are done with our task? 🙂
Thanks Majd! Firstly, it has to be treated as a mindset change, before addressing it as a tactical issue. If people start understanding that ‘Communication is part of the Task’, and the people in charge prove that by personal example, it will manifest itself into the company’s culture. As I always say, this requires a ‘change of heart’. Once that happens, other items work out themselves 🙂
A good example is Scrum – lots of communication aspects are built into the process itself – daily stand-ups, reviews, retrospectives. If you adopt it properly (as in by heart), you will automatically be doing the right things.
I don’t think so,shouting in the hall all the time and every one just updating the others in the loud voice and asking for status update all the time can become effective communication ,it will disturb other works too better to use messengers and emails for effective communication…
But overall good work by author. 🙂
Agreed. Instead of laying the burden of asking for updates only on the project manager, the entire cross functional team (CFT) should take responsibility of keeping the lead and the rest of the team, apprised of the latest developments. Unfortunately, this isn’t practiced. You will find that only 1 or 2 people from the CFT, apart from the project manager, care about staying and keeping the entire CFT up-to-speed.
Thank you! Agree and as I always say, most of the problems infesting our workplace are cultural problems rather than personality traits. If everyone has the right mindset – mindset to believe that I am not done until I communicate – organizational efficiency will dramatically improve. In situation you describe above, in my opinion, the source of the problem is not at the team members, but at the lead level, who are probably not realizing or working hard enough to inculcate that culture.
Personally I think that social collaboration tools for business are a very good way of improving communication.
They certainly help – if the culture supports it. They make it easier to channel the communication.
Importance of feedback highlighted with apt subtlety. Well done Ather – the Thinking Spirit.
Thank you! Appreciate the input 🙂
But one thing should be noted that over communication can may delay the problem. Like communication after every hour.
Agreed. Communication has to be ‘optimum’. Once we realize the value of communicating, and that ‘it is part of the task’, then figuring out this ‘optimum’ model is easy!
Thanks for the comments!
Excellent post. While you were writing this blog entry, I was convincing my fellow team members that we should communicate more and share more. So, for me reading this post really made sense.
Good! There is never such a thing as enough communication. All the best!
Pingback: Anatomy of a Good Decision | Thinking Spirits ...
Pingback: Anatomy of a Good Decision | Startup Magazine | Pakistan's 1st Entrepreneureship Magazine