Hello,

I would like to write on a subject that needs to be addressed much more. This is a major skill which gets overlooked too often. And that skill is listening.

Everyone has to listen to someone. Employees listen to their boss. Developers have to listen to clients. Husband listen to their wives ( and vice versa).

• For the coder, it maybe about negotiating a product deadline. Perhaps, the client does not want to comprehend why the deadline has to be shifted to a specific date. If both parties do not listen to each other, then the negotiation can be very stressful indeed.
• It could also be about the fee for the service. You do all the talking yet the client refuses to budge, and pays the same fee ( time and again ) for the service.
• It could be about the project scope, which neither party refuses to compromise on.

The flaws in the listening process are not just from the client. They are evident in the developer too.

• Perhaps the developer does not comprehend the features so well.
• The developer keeps using jargons and making the client feel out of place.
• Or it is comprehending exactly which needs are most crucial to the client ( and so he works on other irrelevant features first).

Which ever the reason or the party involved, listening is a crucial and sometimes
a neglected art for tas a whole.

Here a few tips we can use to improve our listening habits. Lets apply specifically these when we are with clients, the next time around;

1. Finishing sentences:
Do not cut in when he is still speaking. This shows respect, and conveys to the other party that you not only want to listen but care about what he is saying.
Do not be suprised that I listed this first. This is a common habit that we all do ( especially when we think we know more than the client ) . And you do that too. You do not completely hear the client wheh he is talking about his product specifications.

All the client usually wants is a simple app. And because you have your own view about what is good for the client you present an app full of buttons and
hyper links. Most of the time, the client will never use 80% of the buttons and features for which you introduce. For all you know, all he wants is a CRUD app.
2. A know it all: Do not think you know it all. Of course you have a fair idea about what the client wants. However take time to open both your ears and
listen to the specs as if you knew nothing about the industry or subject matter.

3. Do not code for the money: Of course you take on the prject because the client is willing to pay. However I advise to take on projects for which you
learn something ( or at least have a bit of an interest ) . Still, I stress on the word learn. Coding soley for the money can make you do a quick and unfinished jobs. Understand the project specs so much that you give the client value for his money.

4. Do not react:
Some clients are unrefined in their feedback. And some of their feedback can hurt. And most feeback can usually build you up. Some clients just tell it like it is. Thats the truth. Do not get defensive, and shut your ears up. If you diagree with something , ask for more info . Resist the urge to let your ego get in the way of building you up. Let your work speak for itself. Your work will justify and defend yourself. Control any anger you might feel, otherwise you will close the feedback loop. Treat the feedback in an objective manner
Here are my few tips. Please feel free to share any that you may have. I would appreciate it. Have a great day.

Until later. Cheers.