January 01, 2019

Effective Communication Skills: It's a ladder to be a Leader



Communication is basically conveying your message to other party. Communication can be in any form: written or verbal and most importantly non- verbal.  Effective Communication skills plays an important role in our daily life activities but at workplace, it’s the essential skill to have. Mostly software engineers are introvert rather than extrovert but tester’s role demands to be an extrovert. Because you have to communicate within and across department. Testers communicate to BA /Client for requirements, to developers to communicate fault (written and verbal communication involved) and present reports to management regarding project / product quality. Where technical skills are important, so are soft skills. Soft skills are often ignored by technical professionals which somehow results in a flop. On the other hand, communicating effectively cane elevate your career graph from ordinary to stardom.

To acquire effective communication skills, one has to pay attention to following simple but effective points:

1-      Art of Listening:

Listening is most important skill but only a few people know how to listen properly. . Listening along technical skills is a rare combination. In order to have a prosperous career, one need to focus on listening.  In order to be a great communicator, one need to listen other’s carefully. According to research, when you listen to answer /reply back, you misinterpret. So always try to listen carefully without interrupting. Always try to listen to understand the problem or situation; not to bounce back.

2-      Speak with respect to Audience

Everyone loves to talk but what to talk is another major area to talk about. J Put focus on your listener, while speaking, you need to adjust your conversation w.r.t audience. In order to communicate to BA, you should know business and so with developers and management as well, this will make discussion more understandable and effective. As a speaker, always speak up confidently and slow down. As a tester, it will help to understand and argue better. 

3-      Keep it Simple and Clear

Whether its email, writing any FS / Test case document or speaking to customer/ stake holders, always have clear and simple message. Don’t beat about the bush, clearly summarize the problem and get straight to the point. If there are more than one problem, number these and explain with respect to priority. Speak/ Write with proper confidence, there should be no such words which denies or weaken your statement.  As a tester, you need to write many testing artifacts like test cases, test plans, Bug reports etc so you need to be able to write graciously.

4-      Be Diplomatic

Testers work in destructive way. You put focus to identify faulty or problem areas so mostly people doesn’t like it so you have to be very diplomatic with your words. You have to tell people the mistakes /problems without making them realize. This has to be done in every phase of SDLC whether its Impact Analysis Meeting or Defect Reporting.

5-      Be Specific and organized

Never ever write an email or attend a meeting without homework. If you go with blank mind, it will take time to settle with the situation. As a tester, you need to inquire about application, risks, plans, etc. You need to prioritize your Points with respect to situation. Tester should have the ability when to leave questions open- ended and when to go into deeper details. Sometimes, it’s really very risky not to ask the questions especially when you are having some management position where your decision an affect application or company directly. Always prioritize your points with respect to business stakeholder’s point of view. If something is important to business, that’s the most important, rest is just rest.

6-      Provide Information on Time

Information should be routed between BA, developers and testers. These teams should be synced. In case of any critical information, if information is not on time, it’s useless.  BA, developers and QA, these 3 should always be attached so that everyone has updated information. In case, QA doesn’t have updated information of Business that can directly affect quality of the product and same in vice versa.

7-      Make an Eye contact while listening /speaking

Making eye contact with your speaker or listener gives and impression that you are actively participating and understanding whatever is being explained. It gives a good sense of reliability. Good interaction with your client /end party helps you to understand them better.

, , , , , ,