If you want to succeed as a Business Development officer or Project Manager or as a Programmer, you cannot escape communicating with the client. It is that point where you will understand the requirement or you will handle all User Acceptance Tests related questions. How fine your coding might be, how immaculate your process, or how efficiently you can handle things; all these will just go in vain if the buyer is not happy with you. And you and you only responsible for transferring the right message to the client and in the right way.
In the beginning I would like to discuss at what points the communication becomes the only way of survival, for you as well as for the product you build.
- In the beginning of the project when client helps you to understand the system he wants.
- When the project is going through rough phase like employee resignation, internal disturbance.
- When the client is demanding something which might be difficult to implement or is next to impossible.
- When you know the requirement is easy to accomplish but might cross the budget involved.
- When a deadline is about to miss and you are no way responsible for this or have no control over it.
- And in the end, when client is understanding the system for acceptance.
In all these situations, if you cannot put the right message in the right way, you would always be in trouble. But what are the obstacles to frame the right question or right answers. Lets discuss.
- The receiving end if is not attentive and only wants to send his message across without paying heed to the other communicator.
- The lack of language skill to put the fact in the right way.
- Country, race and religion barrier.
- When the relationship is already at stake or some mis-communications already happened.
Before we discuss what would be the way out in each of the situation written above, let me tell you what are the golden rules for proper communication.
- Be informative: It is useless to communicate when you are not all knowledgeable. If the client is saying something wrong, you need to intervene at the right time with the proper solution. A communication cannot build with the person who does not know anything about the system.
- Be an active listener: If you are not attentive to what the client is saying, you cannot analyze. You must be an attentive listener.
- Be a clarifier: Do not move to the next point, unless you are very sure of the last point. You must raise all your doubts, all questions, possibilities which come to your mind.
- Be a verifier: If there is any example or instance, verify that before you move to next point of communication. Like if the client gives any reference, check if it really exists and if exists if it is exactly the same as the client is saying.
- Be analyzer: Like a chess player, you must consider the implications of each and every references the client moots. You should then tell implicitly all the possibilities and their impacts.
- Be aggressive: Do not be submissive like ‘Yes Sir’ or ‘OK Sir’ and try to rule the conversation. At the same time aggression does not implies haughtiness. So you shall be polite enough to moot all your points.
- Be considerate: Do not tell blatantly that I won’t do it or It is not possible. Rather put it in different way like ‘as my knowledge and understandings, this cannot be done in the budget. However, allow me to study further before I confirm my claim’.
- Don’t be an accuser: Do not accuse the client. No body like to share the blame. You can however say that ‘Whatever you said is correct, however, in our situation following that might lead to some difficulties’. So, you please say, if following your statement was viable or not.
- Do not use absolute terms: Absolute terms are like ‘Always’, ‘Never’, ‘Impossible’ etc. Instead use ’sometimes or generally’, ’seldom’, ‘difficult or somehow not feasible’ etc.
- Don’t be defensive nor attacking: Do not take blame nor accuse. Like ‘I am not accusing you but you know….’ or ‘I knew the fact, but I alone was not blamable. You know there were …’
Now, in the beginning of the article, I gave some examples of various situations. Lets discuss some of the possible stands you might consider for each of the cases.
- When the project starts, you role is to understand the requirements. Before that begins you must do your homework. Gain some knowledge on the business domain, existing solutions. Here, you also take client’s country and religion into consideration. At this juncture, you are going to build a relationship and a trust which will will help you to sail through the project. Don’t make any comments which could hurt the client. Don’t attack anyone’s sentiments. You must be suggestive but not critic. Try to gather as much information from client as you can and analyze the whole conversation. Once done, frame all your questions, possibilities, implications and suggestions.
- Be honest and place the right reason responsible the rough phase. At the same time, let the client know the solutions you thought of and possible date when everything will be resolved.
- Politely state what could be implications if you implement what the client is saying. Try to highlight the financial loses he might incur.
- You must be straight enough to say that the budget might cross and at the same time, present him the reasons for that. Like employee hours involvements, purchases involved etc.
- Again, before you communicate that, you must come out with an alternate deadline. Present him the reasons and the next deadline. If he gets frustrated, ask him what could be his step if he were in the same situation like you.
- This is once again a critical step. Here you must convince the client for each and every fault he points. If it is a bug or mistake just admit and give him a date for the rectification. If he is at fault, help him to understand the situation and jointly get out of the situation.
Once you have the mastery over the art, you will feel a confidence to handle every situation in the right manner. And to do that, you need to admit and understand that, for every problem communication is the only solution.





