Rules

Most people don’t manage their inbox effectively. Emails should be treated as a list to do. As you complete a task you can just delete the email.

Your inbox should only contain 'tasks', that are actionable items on your list of things to do. Everything that is in your 'Inbox' (including sub-folders) should only be to-do items.

So do it now, delete all emails you have done. If you want to keep some for reference, move them to a new folder that is not in your inbox.

In fact, you could go so far as to say you should not do anything unless you have an email telling you to do it (which is why we send ourselves emails). However, very simple tasks can be requested and replied 'done' via IM.

Email is a very powerful business tool. The main problem, however, is that for most people it is out of control - emails build up until they are impossible to manage. To help minimize mailbox clutter, try these tips:

• Send emails that contain clear tasks, not banter
• If an email you receive is not clear, phone the sender and ask for clarification, then document it in a follow-up email “As per our conversation…”. Too many people reply by email asking for more information, which wastes time and does not guarantee a response.
• If you speak to them, follow this rule: Do you seek clarification via the telephone first?
• If you can't get through, follow this rule: Do you chase your Product Owner before he has to chase you?

Using your mailbox as a task list also saves you from having to use inefficient paper-based cards to track your tasks.

VIDEO - Top 10+ Rules to Better Email Communication with Ulysses Maclaren

If someone asks you to perform a task by email, don't reply "OK, I will do that" or fail to reply at all. Instead, do the task and reply "Done" when the task has been completed, and then delete the email. This way the person requesting the task knows that it has been done, and doesn't waste time following you up.

Read "Definition of Done" for more information about the steps that need to be finished before replying to a done email.

Alternatives to classic "Done" emails

• If the task is already done, then reply "Already done - the reason is XXX"
• If you don't agree with the task or are unable to complete the task, reply "Not done - the reason is XXX"
• If there are multiple tasks (some "Done" and some "Not Done"), reply to each item individually "Done" or "Not Done"
• If the task can't be 100% completed at the time, you may reply "Partially done - the reason is XXX"
• If you have already sent a "Done", then the client asks you to undo the change, reply "Undone"

Tip 1: Say "Done" first

For clarity, "Done" (or "Not done" / "Already Done" / "Partially Done") should be the first word(s) so the reader knows the status straight away.

Tip 2: Provide details in your "Done"

In any reply, include relevant information, such as URLs, screenshots, and pieces of code/text that have been updated. This allows others to check what was done straight away.

Tip 3: Replying "Done" to multiple tasks

It is important that you clearly reply to each of the multiple tasks.

Figure: Original email with the client request

Tip 4: Replying "Done" to huge tasks

Ideally, all PBI's should be done in less than 2 days. If you are given a task that is going to take more time than that, then split it by following breaking up monster tasks.

Tip 5: Don't consolidate emails

If you get multiple emails or tasks, don't consolidate them. Reply to each email individually as you go. This way the person requesting the work hasn't lost the email history and can understand what the work is done relates to. It also means that testing and/or feedback can come in as soon as possible after the 1st completed task.

Tip 6: Delete "Done" emails - Aim for 0 inbox

There is no point in keeping emails that just clutter your inbox. You don't need to keep the original email because after you have replied "Done", there is a copy in "Sent Items". If you must keep an email, then move to your "Saved Items" folder.

Tip 7: When appropriate, use text instead of images

SELECT
ProdName = CASE WHEN Download.ProdCategoryID <> ''

THEN ProdCategory.CategoryName
ELSE Download.ProdName END,
Downloads = (SELECT Count(*) FROM ClientDiary
WHERE ClientDiary.DownloadID = Download.DownloadID 

AND ClientDiary.CategoryID = 'DOWN'
AND ClientDiary.DateCreated > '01/01/2010'
AND ClientDiary.DateCreated < '01/01/2020')
FROM
Download
LEFT JOIN ProdCategory 
ON Download.ProdCategoryID = ProdCategory.CategoryID    

ORDER By Downloads DESC

Tip 8: Handle an email once

Follow a tip from Adam Cogan:

During my accounting days we had large physical in-trays and you were always picking up papers, looking at them, deciding it’s ‘too hard to do right now’, and then picking up another piece of paper... I learnt that a sign of an efficient person is that they handle a piece of paper once.

Likewise, when you get an email - don't just open it, have a quick look and close it with the idea that you will go back to it later. Read it, make a decision and do the action. Delete as many emails as you can on the first go. In the same vein, when you complete all tasks in an email, delete everything in that thread.

Tip 9: Consider alternatives in a team environment

In a development team environment, it is better to move emails to tracking systems. E.g.:

1. Azure DevOps Work Items
2. GitHub

Tip 10: Include a video when appropriate

See how to record a quick and dirty "Done Video".

Tip 11: Remember to thank people - don't be too brief and icy

When replying 'Done' to a bug or issue someone reported, remember to thank the person for taking the time to send it. A short "Thank you for reporting this" helps to make your 'Done' warmer.

When a colleague or a client asks you to do a task verbally, or you have discovered there’s a task you need to do but don’t have time to do it immediately, what method do you have for remembering to do it?

The best solution is to send yourself an email CC'ing the person who asked you, including "As per our conversation..." This way both of you know that the job needs to be done. This is really important especially when you are working for clients so there is a record of the requests for work.

Note: If the request is relevant to client work or an existing product backlog then it would be better to create or update a PBI and @ mention the Product Owner and relevant people as per the rule do you use @ mentions in pbi.

Implement a policy of following up important conversations (usually by phone or IM) with an email that begins with the words "As per our conversation". The intent is to document what was said and agreed upon.

When possible, the even better way of confirming requirements is to actually share screens of the drafted requirements and add the words “checked by XXX”.

Watch the video below and see how a single email can make your job easier.

This is not just a 'cover my ass' email. This is for several reasons:

• To make sure that you did not get the message wrong
• To keep an audit trail of agreed decisions
• To keep people, who were not a party to the conversation, informed about the progress

Use this approach internally and with clients. As a result, expect to see "as per our conversation" emails that:

• Require a task to be completed
• Explain the logic of the decision
• Include URLs that were referred to
• Can be referred back to in the future

Sometimes you might not reach the client or Product owner via phone and have to make a decision by yourself. In this case, it's still important to record everything in an email, starting with "I tried calling you but didn't get through":

It's easy to fall into the trap of sounding rather robotic if you start every email with "As per our conversation", or "As per the message I just left on your mobile", etc. Here's a list of nice email openers that have the same effect:

"As per our conversation" alternatives:

• Thanks for the chat
• Good talking to you
• As discussed...

"As per the message I left on your mobile" alternatives:

• I couldn't catch you on the phone today.
• I just left you a quick voicemail.
• I called earlier but couldn't get through.
• Hey I just called earlier to say...

Other cases exist, include your reason at the top

To:	John
Subject:	RE: PowerBi error

Hi John,

Apologies for the brevity. Am still in the hospital but wanted to check this.

To:	John
Subject:	RE: PowerBi error

Hi John,

Apologies for the brevity. Am still in the hospital but wanted to check this.

Video - Top 10+ Rules to Better Email Communication with Ulysses Maclaren

It is good practice to be clear on what you want. One way you can make things clearer is to number tasks or questions.

VIDEO - Top 10+ Rules to Better Email Communication with Ulysses Maclaren

All business emails (that are useful) should be in one of the four following formats

1. FYI- to spread information

   • Daily Scrum - to report on daily progress in a Sprint
   • Sprint Review/Retro emails
   • Sprint Planning emails, etc

2. Tasks- Sending someone numbered tasks

   • To Myself - to send yourself a task, and CC interested parties
   • Tasks to one or more other people
3. Test Please - to ask for testing and acceptance of a task
4. Done - replying to a task email, to show details of what has been done

If your email doesn't fit into one of the above categories, it probably doesn't need to be sent.

When asking for changes to be made to any file like a web page, Word document, PowerPoint slide or code, always include the original version of the content ("X") together with the changes you require ("Y"). This means you have at hand a history of the page or file as it currently stands allowing for convenient future reference and also makes it very clear to the person doing the changes exactly what the new file is meant to look like.

Make the changes even easier to see and understand by highlighting in red what you want to delete (only do this on the "From" section) and in yellow what you want to be added/updated (only do this on the "To" section). All text we do not write ourselves should be indented, so this includes paragraphs we are copying and pasting (see Do you use indentation for readability?)

Video: Top 10+ Rules to Better Email Communication with Ulysses Maclaren

Alternative - What if there are too many changes?

Sometimes you have a lot of content and too many changes, making the process "from X to Y" too arduous. In this case is recommended to use Word 'Track Changes' functionality.

Alternative - What if you have a website managed by GitHub?

Some websites use GitHub to manage their files (e.g. SSW Rules). GitHub makes reviewing changes easy through "Pull Requests".

Sometimes you will need to send a new version for an email. This often is due to 2 main reasons:

• You received a substantial feedback about the email you've sent that requires a new version
• You realized you've made a mistake and want to send an updated version of an email

Having an entire new version of an email is important as it:

• Ensures that you understood a feedback and incorporated it immediately
• Cleans up the email thread history to only have relevant content

How to send a v2 (Outlook)

1. Open your v1 email in Sent Items
2. Click Actions | Resend this message
3. Include V2 on the first line of the email body

4. If the email is a reply, then keep the email history leading up to your original email.
5. Replace your v1 with your v2 email, as if the v1 never happened

Tip: If you are doing a lot of these, you can add the 'Resend This Message' button to 'Quick Access' toolbar in Outlook.

When emailing external parties, it is a good idea to CC the other colleagues within your organization that may have an interest in the email. Some of the benefits of CC'ing others are:

• It can save time
• Gives the email more credibility if you have CC'd others in your organization
• Colleagues may correct your mistakes

In addition, I often see people replying only to the sender of the email, ignoring the fact that there were other persons included in the original email. Obviously the original sender intended to keep everyone in the loop, so it would be polite to CC everyone included on the original communication. The converse is true also - don't cc people unnecessarily - you're just adding to the email problem!

What if the other person drops people?

Sometimes the other person will 'little r' reply instead of 'Reply All'. It is not a good habit to little r reply aside for when there are any exceptions noted below. This can be problematic as those dropped off the loop are needed as part of the decision making. Decisions will be harder to be made in a timely manner or end up being made without a full team agreeance over.

At this point if you are still Cc'd, you should reply and add all those dropped from the loop, back into the loop as soon as possible.

Exception

• If not all recipients need to be informed
• The opinions of the rest of the recipients do not matter as they are unlikely to disagree
• If the original email was to an alias with many subscribers, in general you should not Reply All.
• Also, if the sender requests a 'little r' reply, then you should not 'Reply All'.

VIDEO - Top 10+ Rules to Better Email Communication with Ulysses Maclaren

Sometimes you get the same task from 2 different people. Sometimes even the same person sends over-lapping emails. Sometimes you find duplicated PBIs.

Whether you keep a backlog or are just using your email inbox as a to-do list, you have a choice to make:

A: Get rid of the duplicates and only keep one (you need to spend time informing everyone about the merge)

B: Recommended - Keep them all and when you do it, reply to all the emails with your ‘Done’ OR close each of the PBIs. (Of course it is a good idea to relate those tasks by adding links or the email subjects)

Reducing noise in email threads is easy now we have Office365 and OneDrive.

Sometimes when organising or planning you will need to gather responses from a lot of people, but having many people reply to the email can create a long and messy thread.

An easy alternative to this is to use Office365 in OneDrive to create a survey in Excel, and then send an email invitation with the link to your participants. They respond in the survey instead of by email, and the long, cluttered thread is avoided.

For a quick introduction to how to use Office365 from OneDrive, watch this video:

Sometimes you're not able to complete a task right away or anytime soon. In this case, people usually just say:

I can't do this week, but I should have it done by the end of next week.

Another scenario is when the task should be done or will expire after a period of time. For example:

Send Google Analytics data after a month.

or

Remove course banner once the course is completed.

Efficient people don't rely on their memory and instead, use some way to make sure they don't forget to do that task. The most common ways are to either make a note in a paper diary, stick a post-it note to his screen. But there are better ways.

To ensure you follow up any task like these, there are two ways to set yourself a task to follow up in the future:

#1 Email reminders - followupthen.com (recommended)

There is a brilliant service called FollowUpThen which can do all the administrative work for you.

Simply BCC or email <period of time>@followupthen.com and it will send you an email when that time expires, reminding you to follow up with another email.

Note that you are sending this email thread to a 3rd party, so if you're dealing with any confidential information, strip it out before using this tool.

#2 Outlook | Options | Delay Delivery

Write yourself an email in Outlook.Before pressing send, click Options | Delay Delivery , and then specify when you want to be reminded.

The email will sit in your outbox until the required time, when it will be sent to whoever you specified (you in this case).
When you receive it in your inbox, action the task.

#3 Outlook | Follow Up flag

When you require a reminder to follow up on an email by a certain date:

1. Click the Follow Up button

2. Select an appropriate date from the drop-down or choose Custom to add additional reminders

You can even set a custom reminder for the recipient :)

3. Outlook shows an info tip with the exact follow-up date you chose
4. A To-Do item is also added to your Outlook To-Do list

5. On the due date you will receive a Reminder popup from Outlook
6. If you chose to add a custom reminder you will also receive a Reminder popup from Outlook

There are times you should have your email checked by someone else before sending. Simply ask for that person to come over and check it on your computer or IM him/her if the person is not close by (e.g. in a different room). This way you are guaranteed instant feedback and you won't clog up someone else's inbox with unnecessary emails.

Examples are:

• Where you are a little unsure
• When you are new to a company and sending an email to a large distribution list
• Sending a complicated email
• Sending a sensitive email (where the content could be perceived as confrontational)
• In application development, when you need a quick 'test please', and the person is immediately available. This provides you a chance to check and collaborate on the finished change before the 'done email' is sent. It also shows the email was double checked.

Doing this will ensure:

• You avoid grammatical and spelling errors
• The layout and tone of the email is professional
• You haven’t forgotten anything important
• The receiver knows who else agrees with the content

Web content - Check grammar and links

When you action a task for adding or making big changes to web content (such as a rule or suggestion), you should first paste the content into a new Word file and run the "Grammar & Spelling Check". Once you confirm there are no errors, you may add the content to the site.

After that, run SSW LinkAuditor in order to keep 0 bad links on that page.

Make sure that anyone tasked in emails is explicitly added to the "To:" line. This helps them identify emails where they have tasks.

A fair percentage of people open an email and don’t read who is on the "To:" or "Cc:" lines.

It’s common to send emails to a team and ask them to do a task, but usually that is not a good idea. They may all assume that someone else will do the task or reply.

As the old quote goes: “If everyone is in charge of something, no one is!”

It’s generally a better idea to direct each email/task to one specific person.

The only exception to this would be if you have a ticketing system, like Zendesk, that automatically adds emails to a backlog, and you have a generic task that could be completed by anyone.

If an email isn't clear, a phone call generally sorts problems out quickly.

We've all received a cryptic email at some point. Don't just reply saying "I don't understand". Call the person who sent the email instead. Chances are if the sender of the task couldn't explain the task well enough the first time, it's likely a voice conversation is needed to clarify the issue.

Having clarified the issue by phone, update the task by replying to the original email with the new details arising from the conversation. Remember to start with an "As per our conversation".

However, sometimes you cannot immediately reach the task owner. In this case, you should try to contact the person a few more times. If you are still not able to contact them, you should reply to the email and put the following in the first line:

Always include the relevant URL to your "Done" emails, like when you make a change to a web page. This way people can check the work that was done.

If you are using a task tracking system like Azure DevOps, GitHub, or Jira, also include the link to the PBI/issue/task.

Ensure your changes are live

Video: Top 10+ Rules to Better Email Communication with Ulysses Maclaren

An email with just the word "done" can often be enhanced with a screen capture or code snippet.

In any reply, include relevant information, such as URLs, screenshots, and pieces of code/text that have been updated. This allows others to check what was done straight away.

Benefits

This has several benefits:

• Improved visibility and transparency - The client can see the work actually being done
• Reduced cost of fixing a bug - the cost of a bug goes up based of the length of time taken for the client to ask for a change. If you tell a developer to change something he did today, it is many times cheaper for him to fix, than if he got the same request 2 months later (when he has forgotten was it was about)
• The client can raise questions based on what he sees in the code
• Finally, in the very unlikely case that the code repository and backup goes corrupt, your emails are a backup!

Examples

To:	Jason
Subject:	RE: Northwind - Include one more field to the form

Hi Jason,

Done - added "State" field to the contact form - northwind.com/contact

[Insert code changes]

Tips

• Read Screenshots - Do you use balloons instead of a 'Wall of Text'?.
• On browser screenshots, make sure you include the top-left area - so you can see the URL and what browser it is. E.g. Chrome or Edge.
• If you are using Azure DevOps or GitHub, you should also include a URL to the work item.
• Include a .diff file for greater code/text changes.

Often we receive a reply to an email and it has one word - "Done."

If the sender can't remember what was asked and the respondent has deleted the history, it's hard to tell what's going on. It's not possible to check whether all questions were answered, or what URL was in the original email. Also, we can't Cc someone else on the new reply because the email is missing half the information.

So the only way is to go back into 'sent items', find what was asked for and copy and paste it into my reply, which can be very frustrating.

So, never delete the email history! Surely we aren't that hard up for disk space ;)

When someone sends you a .doc file or images that are attached when you reply 'done' they (and others CCed) won't be able to see the appropriate history. If it is a word .doc or an image; open it and copy and paste the text/image into the history, where the image should have been. Don't leave it as an attachment.

**Warning: ** iPhones strip inline images. If someone has replied to a beautifully crafted email (with inline images) with their iPhone, it will now be a clipped plain text email with your image as an attachment and would not be included in the "Reply All"...Grrrr

So in such a case, you will want to skip that email and go back to the last HTML email and paste in the extra response. For clarity, add something like:

Related Rule

• Do you keep the history of an email?

To reply to a bug effectively and efficiently in your emails, you need to include:

• Current Status - the bug is fixed (screenshot of working application) or not fixed (ask for more detailed information from the client)
• Investigation - the reason for the bug, or if you don't know, what you investigated, e.g. checked Windows event logs and found nothing helpful
• Solution - how you fixed the bug (code snippet if necessary)

When sending an email it is very important to have context and reasoning, and make yourself as clear as possible. This way anyone can understand what was done at any time in the future. Never assume that others will understand anyways. Make sure there are always enough details in the thread/your response for anyone else to acknowledge what is going on.

A nice way to provide extra clear information is by adding screenshots with useful captions.

VIDEO - Top 10+ Rules to Better Email Communication with Ulysses Maclaren

If you receive email via BCC, other recipients are not aware that you were sent a copy so it's actually a VERY BAD idea to Reply All in this case. It's ok to reply to the message you were BCCed on, but it's not ok to send your reply to the people on TO or CC list. Only the sender should receive replies from BCCed people.

This extends even further to the person using BCC in the 1st place. Generally when using BCC, you should always pause to make sure you are doing the right thing.

9 times out of 10, you will find that your motivation for using BCC is something less than fully candid... and it's almost always better to use CC or forward instead.

If you have to address an email to multiple people (including to yourself), include each person's name as a heading. This helps them quickly locate which part of the email that applies to them.

Video: Top 10+ Rules to Better Email Communication with Ulysses Maclaren.

If you think someone should be involved in a conversation but they're not on the recipient list, all you need to do is "Reply All", put the new recipient in the 'CC' field and include one line at the top to inform people for clarity

e.g. (Adding Drew)

Be aware that it is easy to over CC people. Try not to CC people without thinking as every person added to a thread costs $$$. So when you add someone, it is a good idea to state the reason why they are being added, so it will justify the cost of their time.

e.g. (Adding Drew to the loop as during the daily scrum today he mentioned he has worked on similar issues and might have some input)

If you need to remove someone from the loop, for example to have an internal conversation about an email to a client, put (Removing xxx from the loop) at the top of the email.

You can delete people from an email thread, but what often happens is:

• The people being dropped won’t know and won’t be able to say "I don't want to be dropped from this thread"
• The people who added them in the 1st place don't know that they included unnecessary people
• The others on the thread might not notice the change in email addresses

To fix all these issues, instead of deleting people from the email, you:

• Move them to the BCC
• On the top line of the body say "(moving George and Bob to BCC)"

VIDEO - Top 10+ Rules to Better Email Communication with Ulysses Maclaren

Sometimes the person you send your email to may not reply immediately because they're busy or just may have forgotten about it. If you need an answer, remind them by adding a PING to the thread:

1. Reply to ALL
2. Put (PING) in 1^st line of the Body
3. Plus any other instructions - such as "Hurry Up!" or "following-up, and looking forward to your reply" or "Need an answer please"

Of course you might use slightly friendlier language following up a client or a third party compared with following up a colleague! If it's really important and you need an answer you might like to consider using the phone instead of email.

Often emails are rambling and unorganized, forcing the reader to wade through blocks of totally useless text. When it comes to written communication, less is more. Be concise and to the point, listing only what is relevant. People tend to ignore reading larger emails if they are on the run and leave it until a later time when they are not as busy.

"I didn't have time to write a short letter, so I wrote a long one instead."Mark Twain

Sometimes a task will not be clear, or you won't have sufficient context to understand what is required.

A bad approach is to simply delete the email or to reply with “?” and then delete it.

What you should do is call the sender and ask for specifics, then reply to the email with an as per our conversation, documenting your new understanding of the task.

If you can't get hold of the person, email them back asking specifics of what you don't understand.

Just as we should not 'judge a book by its cover' - we will not judge an email by its subject. But, we do! Because users get so many emails, getting your clients and suppliers to take notice of yours in their inbox can be quite a struggle.

Use the email Subject to grab your recipient's attention. Choosing the right subject can give an email a sense of urgency or importance that choosing the wrong subject won't!

The best way of doing this is to ensure that your subject includes either an ACTION POINT (E.g. "6.30 TONIGHT! See you at The Oaks Hotel...") or a RESULT of a task you were asked to do (E.g. "Here's the 5 mins. of FEEDBACK you requested from our meeting with Charles Merton"). You'll note from this that including the date and time in the subject gives immediacy to the email.

If there's anything to be learned from spammers, they know how to get your attention. Spammers use very tabloid based, or headline-grabbing subjects, to try and coerce you to open that email. But don't make your email subjects tabloid-tacky, instead follow a good broadsheet paper's style of attention-grabbing lines.

Never leave the subject blank! It's like writing a book and failing to give it a name!

Good Subject Examples

Always use a descriptive email subject to make it easier to find later

• Consulting:

  Subject: Northwind - Future - Meeting to get your software solution rolling, next Monday 2PM

• Dinner:

  Subject: Dinner Tonight, 6.30PM at The Oaks

• Bugs:

  Subject: BUG - Northwind form - Button not working

• Call someone:

  Subject: SSW User Group - This month needs a speaker - Call Tom Howe pronto!

• Feedback on a product:

  Subject: Northwind app - User Interface feedback

• Test please:

  Subject: Test Please - Product Name v1.11

Of course, we also use a structured approach for emails - especially when sending them internally.

We use the following format for the subject internally and encourage clients and external contacts to use this format as well.

Example:

The advantage of this is that when you sort by the subject in Outlook, you get all of the emails grouped together, and it is easy to recognize the client/product, because the subject contains the relevant information.

Additionally, you should be able to determine which emails are the most important. Using a meaningful subject with keywords makes it easy to identify and categorize emails without actually opening them (and it also makes it easy to find them in "Sent Items"). When emails are really important, write IMPORTANT in the subject. Other emails considered important or urgent should have the following in the subject field:

• BUG
• INCOMPLETE
• URGENT

Other words to be used are:

• TIMESHEETS
• INVOICES
• PROSPECT
• TO-DO - for tasks pending
• FYI - information you want to keep around for a while, for yourself or for others (never for a task)
• FUTURE - ideas for the future
• IGNORE - for the rare occasion when something is requested and you really don't want to do it yet
• Product name - Registered User Support
• Product name - Pre-Sales Support
• Project name
• Client name

Some email threads go on forever... sometimes the topic subtly changes... so when should you change the subject?The answer is "cautiously" and early on before there are many replies. The reason is email threading.

When do you change the subject?

• A: When the original email theme has been superseded by new content.
  At that point change the email subject to a more relevant description of the content of the thread. E.g. From
  "Field of Study" To
  "Next Years Conference WAS: Field of Study"
• B: If the original subject was too generic, like "Reminder" or "Invoice". This is especially common on automatically generated emails, change the subject by adding the client or project name to the email subject. E.g. From
  "Invoice" To
  "Northwind website - Invoice for March WAS: Invoice"

Then be clear to show it was intentional

When you change the subject of an email or an appointment add to the first line:(changed subject)

Remember, never forget the importance of a good email subject in improving communications.

Often there are two email threads that have separate tasks in them, but that both relate to a very similar topic. In this case, it can be useful to give them the same subject, with a number afterwards to differentiate them.

Example:

Read Do you realize the importance of a good email Subject? for more on good email subjects.

Sometimes it can be useful to have multiple copies of the same email.

If you want to duplicate a particular message in Outlook, place the cursor in any of these fields: To, Cc, Bc, or Subject, and press CTRL+F.

It will open a new draft message with the very same information as the original one.

As all these rules indicate, email can either be a blessing or a curse. One of the most deadly of all the potential curses of email is when people choose to use email when it is just not the right tool for that particular task. Absolutely avoid email (at least until you after talk to the other person) in the following situations:

1. When you want to discuss an issue and make a decision
2. When you are dealing with a 'delicate' problem

Making a Decision

If you want to make a decision, asking for opinions via email is the best way to ensure one isn't made. Email discussions get off-topic, lose track, and generally go nowhere, with every email ending with "Yes, but what about..." or "Just my 2c". This leads to a lot of time-wasting.

You should either pick up the phone or have a meeting to discuss the issue, make a decision then and there, and then confirm the decision via email. The first line in your follow-up email should be "As per our conversation..." This records that a conversation was held.

The issue becomes even more important internally when you email someone in the next office and ask them a question. This is a great way of creating unnecessary emails. Instead, stand up, walk to their desk and ask them the question. Otherwise, have a folder called "AskDavid" or similar, file all your emails that you need to ask him about in there, and when he next comes to visit you, go through them and get an answer.

Dealing with Delicate Situations

Similarly, never bring up a tricky topic with someone by email. It's very easy to misunderstand or misrepresent via email. We always pick up the phone and speak to the person first when discussing important, sensitive, complex issues, or issues where some serious convincing is required. This is the standard we follow:

• Draft the email covering the issues we want to confirm
• Call the person covering every issue outlined in the draft

• Adjust the email according to the decisions made together, adding "As per our conversation..."

  • Your email should be like a Scrum Sprint Retro
  • It should start with the good and then say the stuff to improve
• Send the email

This way you can review issues together, and, importantly, decisions are confirmed in writing.

Ideally all phone conversations and meetings should be confirmed afterwards so you have a record of the decisions and action points. Meetings and phone calls should have adequate preparation so they are efficiently run. The reality is, after the meeting or phone call, we get busy on the next call. So this is the workflow that should happen:

1. Prior to speaking to a client, speak to relevant people to help you formulate your recommendations e.g. speak to a developer about the proposal
2. Draft an email with bullet points for each issue (don't send)
3. Call up the client (or have a meeting)
4. Modify during conversation
5. Send the email to the client (cc relevant people e.g. the developer) saying "As per our conversation..."

(AKA - don't respond to a series of emails in one email) If you receive separate emails, respond to each email individually. Don't answer a few emails in one email.

• Each email is a little job (eating the elephant one bit at a time)
• You get a steady flow back as bits are achieved (can get a feel or monitor employees efficiency)
• You can move to 'todo' list folders
• You get a email history for that one topic

Do you sometimes find that people don't follow all the items you have listed in a long and carefully drafted email?

Make it easier for everyone by sending unrelated (independent) tasks one email at a time. Also, don't forget to make your requests very clear.With separate emails, When a person has completed a specific task they just have to reply "Done" to that email, delete it, then move on to the next task.

Breaking up unrelated tasks

If you have a list of things to be done, have a second look, you may find that your requests are not directly related (don't depend on each other OR are not to be done in the same environment). In this case, it is better to break it up and send separate emails.

Grouping related tasks

As per the examples above, if you are requesting many smaller tasks under the same topic, you should group them in the same email. In this case, number each task that you wish to be completed.

Breaking up monster tasks

If you have a very large task that requires days of work, it is also better to break it up and send separate emails. So that big task "Boil the Ocean" would become several emails with consistent subjects:

• "Boil the Ocean #1",
• "Boil the Ocean #2",
• "Boil the Ocean #3" etc.

The advantages are that you get an email history for specific parts, making it easier to include someone else and follow up.

TODO: Make grey boxes with clear separated emails - change from IIS to Git Repo + will become 3 emails

Replying 'dones'

When replying to emails, always reply to each email individually. Don't consolidate them all into one as it leaves unfinished email threads.

Read Do you reply 'Done' and delete the original email? to see the best ways to reply "Dones".

Written communication can easily cause misunderstandings. Help the reader understand your message better by:

• Using “>” and indentation when quoting the text from others, like the original email you are replying to, or a web page, etc.
• Your new text should be kept to the left
• Add numbers if the sender didn't and it is appropriate

This way you won't forget any questions in the original email.

GitHub

When using GitHub, you can use 4 spaces to indent a task and get clear separation between task and response. You can also use a ">" symbol to achieve a similar result.

You can find more info about GitHub syntax at Basic writing and formatting syntax.

Video: Top 10+ Rules to Better Email Communication with Ulysses Maclaren

Note: Some people also use a different text color in their reply, but this is generally overkill

Your boss asks you to change a page on your website. You discuss it with your team and come up with the changes. Wouldn't it be nice if your boss could see exactly what was changed?

Always keep a copy of what the page (or document) looked like before you make the change, and reply to the original email with the "before" and "after.

Replying inline can mess up the history of the email thread. What you should do is to copy and paste the entire email in your reply and comment on each issue at a time, keeping the history intact as per Do you reply 'Done' and delete the original email?

In the rare cases where you really need to reply inline for a special reason, it's important to write your comments in a different color. You might want to mention what color your comments are in (to make it extra clear). Make sure what you text should always be aligned left, not indented.

Email Template

Email Template

See Top 10 Rules to Better Email video for more details on how to reply to emails.

Sometimes clients will add attachment files into emails. Those files could be documents or images, which may contain details or solutions of the issue, or some helpful information.

To keep the history, it is very important to keep the attachment files into the email since it's easy to lose those files when responding.

In case the file is an image, you should insert it to the body of the email to make the history even more clear.

Note: Some clients make attachments because they are using OWA and you can't paste an image in - see suggestion for OWA

Improper spelling, grammar, and punctuation gives a bad impression of your company and can result in your message not being conveyed correctly. Emails with no full stops or commas are difficult to read and can sometimes even change the meaning of the text. And, if your program has a spelling checking option, why not use it?

Web Content

When on a web page, install Grammarly Addon for Chrome so you can automatically check web content. For example, while editing in a CMS.

Documents

When on Word, press F7 (or on the ribbon go to Review > Spelling & Grammar ) to check your .docx text.

Presentation

When on PowerPoint , press F7 (or on the ribbon go to Review | Spelling & Grammar ) to check your .pptx text.

You should also keep "Check grammar with spelling" checked in your PowerPoint Options | Proofing :

Web Content

Any other text can be checked manually. Go to Grammarly, create a New Document and Paste your content to check your text.

Related rule

• Do you use spelling and grammar checker to make your email professional?

Sometimes, in order to add someone in to the loop on something, you might write an email and attach another email as reference material.Generally this is not a good idea and you are better off replying to the original email instead so you can keep it in the history of ongoing threads.

The exception is when you are already in a conversation thread with important history and you want to add more reference material to the email, although even then it's a good idea to also quote the particular line of interest as well.

Never email sensitive information such as Credit Card details, PINs or passwords. Not only does it present serious security problems, it looks like you don't care two-hoots about other people's information.

When your attachment is too big, you should think twice.

1. Avoid large attachments. So if you are sending an email that is >1MB you need to take one second to think:

   • Could a URL be better than this attachment? (see example on the right)
   • Could I send this as a UNC to an internal share?
   • Could I .zip this?
   • Could I put this picture on Flickr or Picasa?

PS: An added advantage is that the document stays alive. If the URL has been updated and a user takes a week to get around to this email, they will view the latest version.

2. If you have to attach multiple files, consider Zip.
3. Use screen captures - pictures do tell a thousand words - but don't include unnecessarily huge images or attachments in your email. Generally the only time you will have serious size problems is if you are using Rich Text instead of HTML inside Outlook.
4. If you are sending screenshots then just send the relevant part of the image you need.

PS: Avoid .bmp. Use .jpg, .gif or .png instead.

5. If you are sending pictures (every year digital cameras are making our photos bigger and bigger) you may need to resize them down. You can either use Photoshop or for something quicker try Office Document Imaging.

6. SharePoint was built with sharing files in mind and is a great way to collaborate. If you are using SharePoint to send a file you simply need to open the context menu, click "send to" and "email a link" as shown:

When can you break these size rules?

Basically, you should be practical:

1. Keep history
2. Paste images into the email - not into a Word document and attach (so it stays with the customers' reply)
3. When you paste a URL, also paste the section of the web page you are referring to (allows for offline reading)

Every email you process takes time. Sifting through unnecessary emails becomes really frustrating. Don't clog up someone else's Inbox with unnecessary emails.

A good rule of thumb for whether an email is unnecessary is if your email comprises of less than 5 words (e.g. "OK" or "See you then") it's likely it doesn't need to be sent.

Merely saying "thanks" is often not sufficient to warrant the email but an exception to this rule is when positive reinforcement should be used when someone has done a specific behaviour that you like and want to encourage. E.g.

Large distribution group emails (e.g NorthwindAll@, SSWAll@) should be used for critical information or emails that require feedback from users. For general information, or random posts reduce email noise by using and IM group (e.g. Microsoft Teams).

Group emails serve an important purpose in providing information to the entire organisation in a way that is less likely to get lost than an Instant Message. Its also provides a good method of allowing for a good cross section of staff responses. IM messages are better suited to general comments/information or random posts.

How often have you clicked "Send" and then wished you hadn't? It's a common problem. It can be easily solved by unchecking the "Send Immediately When Connected" option in Tools/ Options/ Mail Setup. We guarantee this will save you, one day!

As useful as email signatures are for promoting your brand, using images in your signatures is a bad idea. To many recipients this can appear to be an attachment to the email. This will annoy some users, so it's better to keep your signatures as HTML or just plain text.

Outlook by default reads your emails and can flag your email as potential junk email, or adult content email by examining a list of Sensitive words. This list is not available to the public.

You should avoid any swear words or be using an angry tone as well.

We have a program called SSW LookOut! for Outlook to check for this rule.

This rule is a variation of the popular rule Do you send "As Per Our Conversation" emails?

The most dangerous time in a task's life cycle is in a handover. This is the most likely time for a misunderstanding to occur leading to a task getting lost and not being completed.

Always make sure you clearly reallocate a task with an email to the person who will complete the task like the good example below:

If you need to hand over an entire project there are more details here: Do you know how to hand over a project?

Problem: Spam. It wastes time and resources. In most cases, the amount of spam received by an organization far exceeds the amount of legitimate email.

e.g. Average volume of spam received daily at SSW

Options:

1. Software Spam Filters Microsoft Outlook Junk Filter GFI MailEssentials Red Earth Policy Patrol Websense Email Security
2. Hosted Spam Filters Google Apps Gmail (Free) Google Message Filtering Websense Hosted Email Security SpamSoap Core Filtering Microsoft Exchange Hosted Services

Solution:

At present, all email is filtered at the local Exchange server by GFI MailEssentials 12. While it removes a large amount of spam, an unacceptable amount still reaches user inboxes. The current architecture is shown here.

GMail's basic service is the only free hosted solution, so it is naturally the first one to try. With Gmail as part of the solution the architecture changes to the following. The number of emails caught by each of the filters are averages.

Process:

The following steps need to be taken:

1. Register for a Google Apps Standard Edition account. Go to http://mail.google.com/mail/ and register with your domain name.
2. Setup a catch-all account in Gmail and enable POP3 access to it. This means that only one account will need to be checked to retrieve filtered mail.
3. Setup QSS Exchange Connector (http://www.quantumsoftware.com.au/) on your local Exchange server. This software bridges Gmail with Exchange. It logs into Gmail via POP3, retrieves the messages and then distributes them to users' individual accounts based on the header recipient fields.
4. Switch over your MX records to point to Google's servers. This takes around 24 hours to take effect. When the change fully propagates, email will be delivered to GMail and retrieved by Exchange Connector.
5. Monitor the GMail spam folder for false positives. Move false positives to Inbox. After approximately a week, GMail should have learnt enough to be left unmonitored. Emails can then be retrieved by user request.

Results:

The following report was generated by GFI MailEssentials 12. Note that the MX records changed over on 12/02/08.

It can be seen that after the MX records changed over, there were a couple of days of unusual data. This was due to the MX record change over and filter learning period.

By the 16th, only 20 emails were marked as spam by MailEssentials. It can also be seen that the percentage of overall spam dropped from as high at 78% to mostly single digit percentages. GMail was now catching the vast majority of spam.

It must be acknowledged that, while these figures do not represent the amount of spam actually reaching mailboxes, they do give a good indication of how effective Gmail's filters are.

From further investigation, it was found that info[at]ssw.com.au, which receives more spam than any other account, was now receiving around 5 unsolicited messages a week, as opposed to a hundred or more prior to GMail implementation.In the first two weeks after implementation GMail caught 23124 spam emails, an average of 1652 per day.Apart from the obvious benefits, this also saved 641 MB of bandwidth allowance.In the case of info[at]ssw.com.au, a modest calculation of time saved reviewing spam would be 10 hours per year. This estimate is based on an average of 25 emails per day and 4 seconds spent reviewing each one. Actual times will obviously fluctuate, as will the amount of spam other users receive.

Possible Issues:

A third-party has access to your email.False positives. The GMail filter is very accurate but it is possible legitimate emails will be caught. In the Standard (free) Edition of Google Apps, spam emails are only retained for 30 days before being permanently deleted. With Premier Edition (US$50 for one account for a year) you have 90 days with the inclusion of Postini message management.

Inbound emails will be limited to 20MB per message.

In the current stable release (3.5.9) of QSS Exchange Connector, mailing list emails from Yahoo Groups and the like are not correctly delivered to mailboxes when "Automatically detect recipients" is turned on. This has been addressed in beta release 3.6.0.2397 and should make it to a stable release soon.

Using this method, all spam is delivered to one mailbox. This has the advantage that one person can easily review all spam. The disadvantage is that each user doesn't have easy access to his/her spam messages. If users do not personally their own messages, legitimate email is more likely to be lost. Google Message Filtering would be a solution to this issue.

It's better to use links to a portal or document store instead of having attachments in your emails.

If you're sending to a fellow employee, use a link to a document store on your intranet (e.g. intranet.northwind.com/SharedDocuments)

If you're sending to a client, it would be a link to a document store on their project portal. (e.g. projects.northwind.com/SharedDocuments)

Tip: If you're using SharePoint, then an even better way to do this is to use a tool like OnePlaceMail to insert a link from SharePoint

Using the Document ID Feature in SharePoint will help minimise broken links under the following scenarios:

1. Company Restructures / SharePoint restructures
2. Records Management – when items are moved to the Record Centre

If you are using a shared DropBox, then put in a reference like so:

When someone makes a suggestion or a complaint. Usually, you only hear from the ones who disagree. It helps to let others on the thread know you agree, by replying with "+1" and a quick sentence.

Having standards and email templates is great. It helps keep consistency, and the recipients know the format of the information they’re receiving and so can process it quickly.

It also saves time if another employee needs to send one of these out later, as they may not know the processes that go into its construction.

In order for other people to recognize emails following rules and standards, it's a good idea to include something like "<This email was sent as per XXX>" at the end of your email.

Even when the rule or standard doesn't include an actual email template, but you want to empathize you are following it, it is still valid to include that link at the bottom, so the other person can get easily get more information.

Most companies keep all their customers' (and prospects') contact information in a database (e.g. CRM, SQL Server, Access, Oracle). This allows all staff to easily locate contact details about a particular person. So when you get an email, make sure you check that email address and it is in the company database.

We have a program called SSW LookOut! for Outlook to check for this rule.

If for some reason you have to use your personal account at work (maybe the work server is down) then remember to always CC your work email account for any work related emails.

The Australian Government Privacy Act permits employers to monitor employees' email (and web browsing) logs. While employers are encouraged to develop and promulgate a clear privacy policy, it's essentially a recommendation. Many employers may not have the resources to develop such a policy, but nothing prevents them from reviewing email records on the server. The Government admits that "system administrators are usually able to access everything on the network."

The sensible response for employees is to be careful about what they say in email and abide by appropriate usage rules / etiquette even if they don't exist! Follow common sense on this one. Remember that your work email address should not be used for personal mail.

When you post to an email alias, you are posting to many, many people. Unnecessary emails are spam - only send emails that are valid or if there is a need for all to see.

To ensure privacy, and not allow parties to get hold of each others' email addresses, emails to multiple parties should be entered in the 'Bcc' field (not the 'To' field).

You should always try and reply to emails within a timely period, but this is not always possible.

Sometimes people see an email 6 months old and just delete it because it's "too old" or refuse to reply because "the customer will think we're a joke taking this long to do something!" This is a great way to lose business, no matter how long it takes to do some tasks, it's always better to get it done. Of course, there are tasks that appear to be irrelevant with the passage of time, so reply and state that you don’t believe it is needed now.

Example: A product suggestion might take 12 months to get around to, but when it's done the customer should be informed and get a link to the new version - it's possible that their need still exists, and they'll know that their ideas and suggestions are not ignored.

Reply to emails regardless of how long it takes to respond. It shows you value the sender's feedback.

Do you always demand a receipt for every email you send? This is the equivalent of crying wolf. People get prompted about receipts so often, that eventually, they change the settings to automatically ignore receipt requests. Then when someone really, really needs acknowledgment that an email has been received, you never get one, because they've turned off the mechanism.

Turning this option on all the time effectively throws the option away, not just for yourself, but everyone else as well.

Warning: If you are using this more than once a year then alarms should be ringing!

Try to use the active voice of a verb wherever possible. For instance, 'We will process your order today', sounds better than 'Your order will be processed today'. The first sounds more personal, whereas the latter, especially when used frequently, sounds unnecessarily formal.

According to Sydney Morning Herald's "Flame emails missing the mark":

"The senders of email messages expected their partners to correctly interpret their tone nearly 80% of the time, but in fact, they only scored just over 50%... Those attempting to interpret the message believed they had scored 90% accuracy".

Because there is no "tone of voice" in an email, sarcasm can easily be misinterpreted by the receiver. You can use a smiley face or emoji to soften it up a bit.

Everyone knows that you can use Google Assistant or Siri to talk to your phone, but not everyone knows that you can also use dictate in Microsoft Word, PowerPoint and Outlook.

You can choose whether you want automatic punctuation or not, and it's quite good at figuring out what the correct punctuation should be, most of the time.

Key commands that you will likely need include:

• New/next paragraph
• Backspace
• Delete/scrap/undo (removes last word)
• Delete/scrap/undo that (removes last sentence)
• Delete/scrap/undo the last x characters/words/lines/sentences
• Start list
• Start numbered list
• New/next line
• Exit list
• Bold/italicise/underline
• Exit dictation

Hot Tip - Windows Dictation

If you really get into using dictation, you can press windows key + H to dictate directly through the operating system. This is particularly useful if, for instance, you want to dictate a message in Teams, or something else that doesn't have its own dictation function built in.

Some people communicate with a 'Wall of Text'. Communicate better by using screenshots and reduce your amount of words.

You can take screen captures to the next level by adding balloons that have the appropriate text (aka speech bubbles). Sometimes you need only the text in the balloon and no text in the email.

The balloon is great because you can point to a specific part of the image. It is much easier than reading the old ‘Wall of Text’.

Going further, there are ways to improve readability of your screenshots:

Tip 1: Add a balloon when you need to point at an specific area of your screenshot

Tip 2: Be aware not to overuse balloons!

In other words, you can use:

• Plain screenshots
• Balloons
• Circles or boxes
• Arrows

They are all useful depending on the scenario. Be wise and try to make it as clear as possible to the reader.

Tip 3: Add branding to screenshots

Follow the rule Do you add branding to screenshots?

It is great when people use screenshots. You can communicate better by using screenshots with balloons and other visual elements (arrows, shapes, and highlights) instead of only text. Read the benefits of using screenshots.

We recommend you define a standard style for your visual elements by changing the default colors and shapes according to your branding.

See some examples of different visual elements under same branding:

More Information on SSW Branding

You can automatically have the SSW Snagit presets on sign-in via a script.

Instructions to create and use Snagit themes can be found at Quick Style Themes Tutorial.

Having people report bounce back emails is frustrating and time consuming. The first thing to try when you get a report is to check that your mail server isn’t on a spam blacklist. An easy way to check this is via MX Toolbox.

Next step check that you have primary and secondary (and even better tertiary) MX records setup and working.

If success on both steps the error is most likely on the senders side. Send them the an email to check their mail settings.

Figure: What to send the person

Let's say you press “Send” and get a bounce, e.g. An email in your inbox that reads:

Get the correct email address and ‘Reply to all’ with just this text in brackets:

Figure: Good Example - Correct the email address and send again.

The problem with emailing a task, is that no one knows how important that email is, in relation to all their other emails. So, what is the solution?

People can send tasks in different ways:

1. Send a simple email with no priority indication

2. Put the task straight into the backlog in the desired priority order, but send no email

3. Send an email indicating its priority. The recipient reviews it and places it into the backlog, based off the specified Business Value

The perfect email workflow

Before you email a task to someone, think about how important it is to you. Then draft your email, add the Business Value using the same scale that you would use to estimate your PBIs.

What if you need to write an email to multiple recipients?

Assign each person a Business Value. In the case of "To Myself" emails, you can also add the amount of 'Effort' required too.

With the advent of Microsoft Flow and Logic Apps, automated emails are becoming more common. And in fact any reminder or notification email you find yourself sending regularly should probably be automated.

However, the end user should be able to tell that this was sent by a bot, and not a real person, both for transparency, and also to potentially trigger them to automate some of their own workflow.

Email signatures are a great way of adding some advertising and branding. You should always use a nice email signature for external emails. Internally, you may use a short one (just your name or initials).

Full email signatures are great when they have:

• A little branding and advertising (can be a tagline or company news), so people know instantly who it is from
• Your phone number (in international format - it's important to add the country code so people from all around the world can easily add you to their contacts - as per Do you know the right format to show phone numbers?)
• Your company website link (e.g. www.ssw.com.au/)
• Your social media and blog link
• Your IM link (E.g. Teams or Facebook Messenger)
• Your position
• Your location (city/country) where you are based

Mobile Signature

Use the mobile signature when sending emails from your phone. Mobile signatures are not easily customized so they can be simpler.

PC Long Signature (Big and Fancy)

Use the complete long signature when sending a new email or appointment to a client.

This is created in HTML and goes well on emails with Word used as the email editor. Include some product advertising, like what's new on your monthly newsletter. It should have the company colors.

However, you shouldn't use your long signature on every sent email. It's recommended to have a simpler version for internal emails and appointments:

PC Short Signature

Use a really short signature (your first name or initials) or no signature at all in internal emails as people already know who you are. You may want to add a quick link to IM.

Implementation

Option 1: CodeTwo (Paid)

The easiest way to implement consistent signatures across a company is to use a 3rd party signature provider e.g. CodeTwo.com and Exclaimer.com
This way you quickly get great email signatures, with consistent branding, to all your employees and on all their devices. CodeTwo is cheaper and has a nicer design tool UI than Exclaimer, however they are both good. CodeTwo is built on Microsoft technology.

CodeTwo (and Exclaimer) give:

1. Automatic signatures are added on any device – from laptop to smartphones
2. Consistent signatures for every employee as they all use one template – consistency is important
3. Management via a portal
4. Marketing can run campaigns and schedule changes to all signatures
5. Hassle-free setup – users do not need to touch any signatures on any devices.

Option 2: Set it up manually (Free)

Mobile - How to set it up in the Outlook App

1. Go to Settings on the Outlook application
2. Click on Signature
3. Type your desired signature for mobile

PC - How to set it up in Outlook

1. Open Microsoft Outlook and go File | Options
2. Click the "Mail" tab as seen below
3. Click on "Signatures..." and add in your signatures

Browser - How to set it up in OWA

1. Open OWA (e.g. http://mail.northwind.com/owa)
2. Click "Options" on the top right side.
3. Go Settings | Mail and make following changes:

How to set it up in Office 365

1. Open Outlook in Office 365 (http://outlook.office.com/mail/inbox)
2. Click the "Settings" cog on the top right corner of the Window
3. Click on “View all Outlook settings” at the bottom of the Settings panel

4. In the "Settings" window that pops up, go to: Mail | Compose and reply.
5. Add your email signature and click "Save"

Step 1 - Remember to remove the https from your URLs in your presentations. It keeps the pages cleaner and more readable.

Step 2 - Even when you’re sending emails, or pinging someone in Teams, your URLs should be as clean as possible. This ensures that they are easy to read, and it is more aesthetically pleasing.

URLs have become increasingly cluttered with the introduction of tracking information.

For example, companies use CampaignIDs on their website to track customer activities and information, but when you’re sharing the URLs, it is better to make them clean and readable. So, delete everything after the question mark (including the CampaignID suffix).