A recent client experience came to mind when I read the following blog post:

http://sethgodin.typepad.com/seths_blog/2013/12/broken-english.html.

Seth says “you will be misunderstood”, and broadly speaking I agree with him: we all interpret what we hear in the context of our own experiences, however careful the speaker, and those experiences are all different. But I think is important to remember that there are degrees of misunderstanding; not all misunderstandings are equal.

My client had started a change project which was running into difficulty. As I started to talk to his staff, it became clear that they all had slightly different understandings of the objectives of the project. Not only did that mean that there was confusion about where they were trying to get to as a whole, but it also meant that the various workstreams were unlikely to join up.

You won’t be surprised to hear that there was not much formal documentation for the project. I’m sure my client felt he had explained what he wanted very clearly – and if he had been on the receiving end, I am certain that he would have understood himself perfectly. But his audience was not him, and he had not taken the additional step of asking his audience to play back to him to check their understanding.

One of the most important tasks for any project manager is to make sure that project objectives are defined clearly, and that everyone understands them. A key skill for project managers is therefore to be able to put things into simple, unambiguous language that fits the background and culture of everyone in the team. They must be good translators: there may still be some misunderstandings, but if they can’t reduce them to a very low minimum by adapting their language (and their listening) to their different audiences, they will not be effective. Just look what happened at Babel!