38
{ Business Correspondence Writing emails that won’t get ignored

Business correspondence

  • Upload
    ciklum

  • View
    1.046

  • Download
    2

Embed Size (px)

DESCRIPTION

On Wednesday, December 21, #MandCPL wiht Vadim Izdebskiy organized a workshop called “Business correspondence: writing e-mails that won't get ignored”. Agenda: - Got mail? - The Do’s and the Don’ts - Practical exercise - Q&A - Bonus:Outlook and Gmail tips & tricks

Citation preview

Page 1: Business correspondence

{

Business Correspondence

Writing emails that won’t get ignored

Page 2: Business correspondence

Who is this guy?

9+ years in software development

From Junior C++ developer to Program Manager / Tech Consultant

Teams from 3 to 10 people

Customers from Belgium, Australia, Canada, US, Germany, UK, Malta, Denmark

…Email Nazi!

Page 3: Business correspondence

So, need to write an email?

Page 4: Business correspondence

{Stolen thoughts and ideas

A bit of Theory

Page 5: Business correspondence

Self Fulfilling email Inquiry Open-Ended dialog Action email

What is the Purpose?

Page 6: Business correspondence

Spends a long time crafting the ‘perfect’ email.

Believes that their request is original, unique, and special.

Cannot imagine why anyone would turn them away.

Desires to tell the whole story

Who is Sender?

Page 7: Business correspondence
Page 8: Business correspondence

Gets a lot of email Regularly gets asked a

standard set of questions and favors

Does not have a lot of free time

Does not mind helping you, if it is fast

Who is Receiver?

Page 9: Business correspondence

2.7 seconds

Time to take decision

Page 10: Business correspondence
Page 11: Business correspondence

To construct email that:

Will actually be read Will actually be understood Will not annoy receiver Doesn’t take too much time to

react

Our Goal

Page 12: Business correspondence

{Building blocks

Composition

Page 13: Business correspondence

Never ever forget it!

One phrase summary Short, informative, related Reflects the purpose

Subject:

Page 14: Business correspondence

People who need to

respondor

take action

To:

Page 15: Business correspondence

People who need to

be informed

CC:

Page 16: Business correspondence

What about BCC:?

Page 17: Business correspondence
Page 18: Business correspondence

Introduction Problem description Conclusion

Body:

Page 19: Business correspondence

{http://level2.ciklum.net/index.php?option=com_userdet

Signature

Page 20: Business correspondence

{Length, look, style

Tips on Content

Page 21: Business correspondence

Remember to KISS Pretend face-to-face intro Use text message trick Minimize questions Do word trimming

…but be personal

Tips

Page 22: Business correspondence

Use Simple English Ask for reaction explicitly Split to parts for different

people/actions/questions Bold people names (use @, twitter-

style) Use links instead of attachments Define abbreviations Put reference info to the very end

Dos

Page 23: Business correspondence

Don’t overuse High Importance (!) and red color

Don’t use Royal English Don’t misspell names Avoid jargon

Avoid using different fonts, sizes and colors

Donts

Page 24: Business correspondence
Page 25: Business correspondence

Ready to press ‘Send’?

Page 26: Business correspondence

Read it!(three times)

Page 27: Business correspondence
Page 28: Business correspondence
Page 29: Business correspondence

{The Good, the Bad and the Ugly

Examples

Page 30: Business correspondence

-----Original Message-----From: David W Sent: Thursday, March 30, 2006 10:32 AMTo: Roberts, JohnSubject: repeated server warnings John, Below is terminal output I got the first time I started the server process.  The warning about the lock file is coming out every 30 seconds.  Where is it trying to write this file?  Would this be caused by some kind of permission problem?

Thanks, 

David WinchNGT Development  Mar 30, 2006 10:21:48 AM java.util.prefs.FileSystemPreferences$2 runINFO: Created user preferences directory.Mar 30, 2006 10:21:49 AM java.util.prefs.FileSystemPreferences$3 runWARNING: Could not create system preferences directory. System preferences are unusable.Mar 30, 2006 10:22:19 AM java.util.prefs.FileSystemPreferences checkLockFile0ErrorCodeWARNING: Could not lock System prefs. Unix error code 805449496.Mar 30, 2006 10:22:49 AM java.util.prefs.FileSystemPreferences checkLockFile0Err

Page 31: Business correspondence

-----Reply Message-----From: Roberts, John Sent: Thursday, March 30, 2006 11:04 AMTo: David W Subject: RE: repeated server warnings David, What environment variables do you use in the command line? I have not come across this before. Probably, permissions to default locations where the java.util.prefs.FileSystemPreferences class tries to write preferences are insufficient.

Please, let me know if I can help more.

Regards, John RobertsSupport Engineer

Page 32: Business correspondence

----- Message-----From: Roberts, John Sent: Friday, March 31, 2006 03:12 PMTo: Neit, Paul Subject: Build environment corrupted?

 

Paul,

 

While trying to make the latest build I am getting the following error:

$ . ./ngtmake_9_1.ksh

Error: cannot access ngt9-13.jar

The testing team is stuck on getting the release acceptance. Could you please look into the problem ASAP and let me know?

Thanks in advance,

John Roberts

Support Engineer

Page 33: Business correspondence

From: Cathy Sent: Monday, January 30, 2006 4:16 PMTo: Gille, AndrewCc: Subject:

Andy, I don’t know for sure but check what it takes to load NDPT data into the test DB.

 

Thank you, Cathy.

-----Original Message-----From: Gille, Andrew Sent: Thursday, January 26, 2006 10:32 AMTo: Goodwriter, CathyCc: Grace, BillSubject: Problem loading production database

 

Dear Cathy,

 

Could you please help me with understaing of a root cause for such a strange behavior of database loading scripts. I wonder why time being consumed exceeds the limits set in the functional requirements. We have been testing the database with customer data this week and require your input asap. Bill, what do you think of this?

Sincerely, 

Andrew Gille

Page 34: Business correspondence

{Yep, I know

Homework

Page 35: Business correspondence

Report a technical problem on a customer side that blocks your work

Addressee: Vadim Izdebskiy, Program Manager

Problem: No access to source code Timeline: End of major phase, time to

build Urgency: Severity 1 issue Action: Resolution required from

customer

Exercise 1

Page 36: Business correspondence

You are missing a deadline

Addressee: Vadim Izdebskiy, Program Manager

Milestone: RC code freeze

Exercise 2

Page 37: Business correspondence

Thank you!

… and MORE!

I will be happy to discuss it with you FURTHER

Page 38: Business correspondence

Bonus