9 Most important characters of business emails in English

1. Clarity

- The content should be simple, easily to follow, short words rather than long one.
- Use the active voice, positive words rather than complaint one.

2. The "One Thing" rule

- Keep the message focused. The another thing should be written in another email.

3. Be political

- The message is in more the two paragraphs, it should be reduced.
- Use "Please" and "thank you"
- Use phrase that states you are not sure of something: I think that..., It is possible..., The optimal solution...

4. Meaning Subject

Bad: Important. Please read
Better: Meeting set for tomorrow at 10AM - Need a room

5. Think before you write

- Don't send e-mails in haste
- Avoid using context (background information)

6. Understand you Audience

- What they like to hear
- See your writing from their perspective

7. Sign-off like a professional

- Add signature block with appropriate contact information

8. Make sure no errors with spelling and grammar before you click the "Send"

9. Begin and end with appropriate words

- Beginning of an email: rather using "statements" than "question". For example: "How was your weekend?" -> "I hope you enjoy the weekend!"
- End of an email:
+ "Take care", "Cheers": informal
+ "Best", "Regards": formal
+ "Thank you": all cases. :)

References:
[1]. http://www.slideshare.net/jvuu/how-to-write-bulletproof-emails-in-english

Comments

Google I/O 2017 Notes

WOW! How meaningful this below video explains about the name of "I/O". Sundar Pichai talked a lot of Machine Learning Machine Learning is a very hot trend these days. Google uses it for their products. Google Assistant: Easily booking an online meal by talking with Google Assistant like a staff of partners, for example. Google Home: Hands-free calling. Google Photos: sharing suggestion, shared library, photo books and google lens. Youtube: 360 degree video, live stream. Kotlin became an official programming language for Android https://kotlinlang.org I'm on the way to Kotlin! ^^ Reference: [1]. https://www.youtube.com/watch?v=Y2VF8tmLFHw

Junit - Test fails on French or German string assertion

In my previous post about building a regex to check a text without special characters but allow German and French . I met a problem that the unit test works fine on my machine using Eclipse, but it was fail when running on Jenkins' build job. Here is my test: @Test public void shouldAllowFrenchAndGermanCharacters(){ String source = "ÄäÖöÜüß áÁàÀâÂéÉèÈêÊîÎçÇ"; assertFalse(SpecialCharactersUtils.isExistSpecialCharater(source)); } Production code: public static boolean isExistNotAllowedCharacters(String source){ Pattern regex = Pattern.compile("^[a-zA-Z_0-9_ÄäÖöÜüß áÁàÀâÂéÉèÈêÊîÎçÇ]*$"); Matcher matcher = regex.matcher(source); return !matcher.matches(); } The result likes the following: Failed tests: SpecialCharactersUtilsTest.shouldAllowFrenchAndGermanCharacters:32 null A guy from stackoverflow.com says: "This is probably due to the default encoding used for your Java source files. The ö in the string literal in the J...

JSF, Primefaces - Invoking Application Code Even When Validation Failed

A use case I have a form which has requirements as follow: - There are some mandatory fields. - Validation is triggered when changing value on each field. - A button "Next" is enable only when all fields are entered. It turns to disabled if any field is empty. My first approach I defined a variable "isDisableNext" at a backend bean "Controller" for dynamically disabling/enabling the "Next" button by performing event "onValueChange", but, it had a problem: <h:form id="personForm"> <p:outputLabel value="First Name" for="firstName"/> <p:inputText id="firstName" value="#{person.firstName}" required="true"> <p:ajax event="change" listener="#{controller.onValueChange}" update="nextButton"/> </p:inputText> <p:outputLabel value="Last Name" for="lastName"/> <p:i...

New components from PrimeFaces 6.0

There are various components have been promoted to PrimeFaces from Extensions project. TimeLine InputNumber KeyFilter ImportEnum ImportConstants Knob Source: PrimeFaces team blog

There is no expert, there is only us

Chairs in my office Once I was chatting with my teammates... Me : "I wonder why it is always necessary to refer to this source, that source, has anyone done it, is there any research? While no problem is the same, no situation is the same. Why not use our own brains to create a whole new one? Why do we have to be the insiders to consult the outsiders? Isn't that very paradoxical?" My teammate : "I agree with your point that no two situations will be exactly the same and that there is no one size fits all. But there's one like this, I don't think it's all the problems we're dealing with that only we can meet. So of course, if I can find a source to refer to first, it's still better. Just like when implementing a software feature, not every problem is the same. But I still have to go check to see if I'm the only one I've met? Or if someone has met me, I have to see if their method suits me before I decide to try it, but I don't blindly ...

vhandit

Search This Blog