I just started to read a book I recently bought about web project management: “Real Web Project Management: Case Studies and Best Practices from the Trenches” (Thomas J. Shelford & Gregory A. Remillard).

This is not my first book on the subject and although I’m only on chapter 3, I can say that I agree with most of the things I’ve read so far. The other positive feeling I get about this book is that (at least in my case) it is very close to the reality of my job.

Shelford and Remillard describe in quite a successful way what really happens when you’re trying to manage complex web projects.

The chapter I’m currently reading is about “communication playing a key role in project management”. Here are some excerpts:

Communication is composed of much more than just speech. The effective communicator will use all the available communication tools at his disposal to get his message across. These include writing, body language, listening, tone of voice, and even dress. (page 56)

and

[...] Communicating is your most vital skill as you manage a Web project through to its completion. (ibid.)

As I wrote earlier, I agree with the authors. Communicating with everyone involved in a project is essential if you want to avoid assumptions or misunderstandings for example. Even if writing reports and talking to your colleagues can be a time-consuming exercise sometimes.

Speaking of colleagues, I have a comment on the interaction you need to have with them during a project. You can be the best communicator on earth, you can be the smartest person too, you can be patient and nice to everyone, but there is never a guarantee that your message will go through.

The reasons why a communication can fail are multiple and are intrinsic to the communication process and this is something that everyone should be aware of when interacting with other project team members.