Miscommunication in a project, illustration
If you are a web designer or a programmer I am sure this thing happens a lot. Usually they are the victims of the miscommunication, they are the ones that make hundreds of revisions to the project because of miscommunication.
When I used to work as a Web Designer in my previous job (2 years back), usually company would make a mistake of not sending any web designer to the project meetings. They would send all the non-IT staff, like sales manager, marketing manager, COO…etc.
Usually in these meetings many things would be discussed about the project’s design (look & feel), and project specifications. These meetings are very important for the web designer to get the feeling of what the customer wants. Because, if you do not hear it from customer’s mouth, someone else would explain it differently and you would be designing a website for this imaginary customer. And the end result would be, of course, something that is not what the customer wanted.
So moral of the story? Make sure the person responsible for the project development be in the meeting, especially in the first meetings where the project specifications are drawn.
Click here to see the whole cartoon (10 images) My favorite is “How the programmer wrote it” The guy did some hell of a programming there ;) How about you? Which one do you like?
Related Posts
- Project Guttenberg - free eBooks
- list of project mgt tools
- Ohloh.net - open source projects directory
- Microsoft launches it’s own image editing software
- Flash Project: Color In Motion
