These tips are for Formal emails/messages in which we inform status of tasks or any other matter.
Tips and Tricks
- Do not repeat words, use synonyms
- Use connectors
Core
The goal is to give a simple, clear, and focused message. If they have any questions, or we sent too much information, then we failed on communicating.
Formal email ?
- Give a clear message by segmenting our ideas/topics on different sentences. We always forget about
,and., yet they are super important.
- Re-read the message draft. Notice that several improvements can be made regarding wording, phrasing, and punctuation. Believe me, it happens on a daily basis.. frequently.
- Add images and/or videos to give a clear message, as images are worth a thousand words.
- Is the client going to read it ? If so, are they technically knowledgeable ? Add some technical details, but not too much. Otherwise we lose the focus of the message.
- Consider sending a separate email if more technical details are needed.
Internal informal email / end of day status ?
- Add a brief description for each task we tackled, their final status and useful details.
- Rise any blockers with time.
- Give a more technical approach, adding source links for any special implementation or issue we encountered. If we did face an issue, consider:
- Give a detailed (or semi-detailed) description of our issue: how we approached it, and how we solved it/final status of the day if not. This helps as any teammate can give us a hand.
- Include links to any site/documentation used.
- Include media for clarification.
- Attach code segments if needed for a conversation.