Status update – work remaining

Often we see that team members are not able to meet their commitments, and it is a surprise, specially for new project managers. Each time I tried to figure this out – one thing stood out.


The team member not being aware of the exact progress he or she has made. They provide status update, often in a status meeting, at the start of the week, they have hurried into, after a mostly hectic weekend. They update the status verbally, which may not be accurate and tend to paint a slightly better picture than what it is. This is a natural human tendency, which comes to the fore specially, when status update is being done in a group, face to face.

What happens after this?

The team member has provided the status and if it is correct, well and good. If it is not, and if that is not countered by the PM/others, team member internalizes the update given and accepted.  Then works at the pace that is in-line with the update, this happens in a subtle way. Result is that work may not get completed as expected.

Have you encountered this? Have you dealt with this?

What I did was to ask the PM to ensure that the team member is aware of the progress, as it is he or she who has to change or retain the pace to complete the work. Two options:

So status updates are not only a communication of the status to the PM, but also to oneself and that is required for one to take the required actions. A PM who realizes this and makes this happen for the team members will definitely have less surprises. This is something I have tried while mentoring numerous PM, and above or a variation of it always had a better outcome.

And now with Agile Scrum the above is inbuilt into the daily stand up, with few more additional aspects taken care of. More on that later…

What do you think?

One Response

Leave a Reply

What to read next