-DOs and DON’Ts related to communication via emails; -Top tips for effective email communication; -Email etiquette and why it is important; -Importance of timing; -Lessons learned and best practices applicable to our projects … and other interesting and useful material which will help you to write better emails.

1. Effective communication via email Tech Talk #4 September 28, 2011 Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

2. You will learn: DOsand DON’Ts related to communication via emails; Top tips for effective email communication; Email etiquette and why it is important; Importance of timing; Lessons learned and best practices applicable to our projects … and other interesting and useful material which will help you to write better emails. Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

3. What is communication? Communication is the activity of conveying meaningful information. Communication requires a sender, a message, and an intended recipient, although the receiver need not be present or aware of the sender's intent to communicate at the time of communication; thus communication can occur across vast distances in time and space. Communication requires that the communicating parties share an area of communicative commonality. The communication process is complete once the receiver has understood the message of the sender (from Wikipedia). Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

4. Oral and Written Communication. Pros. Oral communication Real time - the message Is conveyed immediately to the receiver Immediate feedback Non-verbal communication like body language and voice tonality plays a significant role Saves time Less formal method as compared to written and adds a personal touch to your message Written communication Concrete form of documentary evidence Can be used for future reference purposes Can be easily distributed to many people thus making it a bulk communication method, the accuracy of the information conveyed is same across the entire audience Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

5. Oral and Written Communication. Cons. Oral communication No written evidence Harder to use for future references Can’t be easily distributed to many people This form of communication can be misinterpreted or misunderstood very easily Communicating effectively through oral forms require high skills Written communication No immediate feedback Lack of feedback Absence of non-verbal communicationto convey message effectively Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

6. Email communication. Advantages Fast and cheap Ideal way to reach persons who are difficult to get on the phone You can compose and review your message before sending Ideal for international communications (expense, problems reaching colleagues, differences in time zones) You can easily include all or part of previous messages, or the message you are responding to, including point by point responses to questions, etc. Ability to send same message to predefined groups of people Ability to include attached files, documents, pictures, datasets Messages easily achievable and storable in a database; search by sender, date, subject, or put into separate mailboxes Ability to paste from other applications directly into email document (e.g., a review of a paper found on a website) .. And many others. Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

7. How to write effective emails? Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

8. Before you even start typing What is the goal of you email? Who is your target audience? Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

9. Subject Line Should convey the essence of email Brief and to the point Urgency of the message must be indicated in the subject line Be diplomatic, be assertive Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

10. Good or Bad? <Empty> Hi Reminder Status Report Some questions Candidate CV Meeting Minutes Summary Approval Request: PHP Training Draft: Email to Microsoft Reminder: End of Probationary Period, Oct 1, Ivanov CV_Ruby_Ivanov Meeting Minutes. DO Product Backlog. Oct 1 Summary. Grammar Blogs Research Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

11. Email Structure A usual business letter consists of four main blocks: Salutation Main Part Close Signature (stating an addresser’s name and title) Thus, it is essential to consider every point as thoroughly as possible in order to avoid probable misunderstandings with Clients and uphold the Company’s reputation at a proper level. Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

12. Salutation In case you don’t know an addressee’s name: Dear (Title/Last Name), Dear Sales Manager, Dear Sir, Dear Madam, If you address an individual you don’t know or an organization (although it is too formal and rarely used): Dear Sir or Madam, Dear Sirs, (British variant), Ladies and Gentlemen, (American). If you know an addressee and have formal relations: Dear Ms. Johnson, If you know a person well enough and have informal relations with him or her, “Dear” may be skipped. This case is applicable to both external and internal correspondence. Dear Frank, John. For long-lasting correspondence with an addressee or for internal e-mails you may use Hi Frank, Hello Bob (Note: “Hi” should be used with the name of an addressee) If a letter is intended for a number of addressees within the Company: Hi everyone, Greetings! Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

13. Main Part Main Part consists of 3 parts: Opening phrases. Body. Closing phrases. There are some formal phrases that are commonly used in business letters. Using them will help you put the reader into the appropriate mood, give him or her a glimpse of information you are going to speak about, thus making your communicative task more effective and easier. Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

14. Main Part - Opening Let the recipient know the goal of your email Write Your First Email Line Like a Tweet to Grab Interest  Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

15. Opening Phrases (formal) Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

16. Opening Phrases (less formal) Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

17. Body Relate content to the reader Limit your message to one subject Keep to a 15 line message (about half a computer screen) if you can Good idea to use bullets Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

18. Body How to email someone for the first time: Don't assume that they know you, or care to know you Write a one-line introduction setting the context, introducing yourself, and explaining your role How to structure an email requesting a decision: State the topic briefly Explain the issue State pros/cons Give a recommendation with rationale Provide guidance on when you need the answer Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

19. Body - Call to action The call to action is the Instructions or information we want the reader to take away from the message. Or The Actions that need to be taken Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

20. Answer all questions, and pre-empt further questions If you do not answer all the questions in the original email, you will receive further e-mails regarding the unanswered questions, which will not only waste your time and your customer’s time but also cause considerable frustration. Moreover, if you are able to pre-empt relevant questions, your customer will be grateful and impressed with your efficient and thoughtful customer service. Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

22. If you want to emphasize, do it sparingly with boldDon’t write emails in ALL CAPS IT MAKES IT SOUND LIKE YOU’RE YELLING Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

23. Be careful with formatting Remember that when you use formatting in your emails, the sender might not be able to view formatting, or might see different fonts than you had intended. When using colors, use a color that is easy to read on the background. Use [Answer] instead of colors when commenting email thread Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

24. Date and Number Formats It is well known that currently dates (according to the Gregorian calendar) are expressed in several different ways in various countries. The order in which the year, month and day are given: The Europeans write day/month/year (e.g. 23/9/2006), while the U.S. Clients write month/day/year (e.g. 9/23/2006) Universal date format (that can be applied in any case) is the following: MMM DD, YYY (e.g. November 15, 1999 or April 05, 2000) Number format: American and English customers separate thousands with a comma and fraction numbers with a dot (3,220 means three thousand two hundred and twenty; 3.5 means three and five tenths). Europeans use the European format (e.g. 12 345,98) Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

25. Closing phrases Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

26. Use but Do not overuse the high priority option If you overuse the high priority option, it will lose its function when you really need it. We all know the story of the boy who cried wolf. Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

27. Don't leave out the message thread When you reply to an email, you must include the original mail in your reply, in other words click 'Reply', instead of 'New Mail'. It’s not possible for anyone to remember all his/her previous mails Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

28. Attachments Make sure to create an attachment if you are mentioning the same in your mail Check with the receiver if he/she would like to receive the attachment whether they have software to open attachment Do not attach very heavy attachments, provide URL instead Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

30. Goal of the email

31. Informative Subject

32. Recipients

33. Opening

34. Email length

35. Call to action

36. Signature

37. Appropriate formatting

38. Spell and Grammar Checking

39. Goal of the email !Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

40. Read your own email before sending Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

41. Email etiquette Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

42. Email Etiquette Be Polite Take the time to include a friendly greeting; Use please and thank you; Civility makes a difference in how your message is received. Don't hesitate to say thank you, how are you, or appreciate your help. Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

43. Email Etiquette Address your contact with the appropriate level of formality and make sure you spelled their name correctly; Multiple instances of !!! or ??? are perceived as rude or condescending; If your email is emotionally charged, walk away from the computer and wait to reply. Review the Sender's email again so that you are sure you are not reading anything into the email that simply isn't there. Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

44. Email etiquette You are a member of various office and department mailing lists. It’s okay to email these lists with a question, but… Choose the correct list Send to specific offices or departments rather than spamming the entire company Specify if you want the replies to go to you or the whole list Don’t say anything in an email you wouldn’t say face-to-face or on the phone; Don’t overlook the fact that your email could be forwarded on. Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

45. Email etiquette Include addresses in the Cc: field for those who you are just FYI'ing; Never expose your contact's email address to strangers by listing them all in the To: field. Use BCc. This is a serious privacy issue! Emails are forwarded to others. Keep this in mind when typing about emotional or controversial topics. Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

46. Email etiquette Formality is in place as a courtesy and reflects respect. Assume the highest level of formality with new email contacts until the relationship dictates otherwise. Refrain from getting too informal too soon in your email communications. Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

47. Email etiquette Never send anyone an email they need to unsubscribe from when they didn't subscribe in the first place! Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

48. Business Rules Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

49. Timing Each e-mail should be replied within at least 24 hours, and preferably within the same working day; If you cannot respond to an email promptly, at the very least email back confirming your receipt and when the sender can expect your response. Consider time zone; Answer simple and “quick response” emails first. Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

50. Learn to write “Ok” emails Describe Pros and Cons Propose several solutions if applicable Provide your judgment and set the best solution from you perspective Let client just reply to you with “Ok” Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

51. Process your email effectively Check your incoming email; Prioritize emails; Mark and flag those you need to follow-up; Do not leave the office with un-replied emails; Before getting upset because you perceive someone didn't respond, check to see if their reply was inadvertently deleted or sent to your Trash or Junk folder. Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

52. Emails review Approve emails to clients with you manager before sending; Take the time to review each email before clicking Send to ensure your message is clear and you are relaying the tone that you desire; Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

53. Get the feedback If you send email draft for approve/some report/etc. to client/colleague, do not leave the office before you discuss the result with him or check with client/colleague if he has time to discuss it today or you can leave and you will discuss next business day! Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

54. Sometimes a phone call is better If you have many points or a very complex point to discuss, it may be quicker to simply pick up the phone and speak to the person Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

55. Task Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet

56. Thank you! Dev-Pro.net, www.dev-pro.net, Twitter: @DevProNet