{"id":165,"date":"2015-01-23T19:30:08","date_gmt":"2015-01-23T19:30:08","guid":{"rendered":"http:\/\/www.joshevilsizor.com\/?p=165"},"modified":"2017-10-15T10:20:24","modified_gmt":"2017-10-15T14:20:24","slug":"inbox-zero-you-are-doing-email-wrong-step-1","status":"publish","type":"post","link":"https:\/\/www.joshevilsizor.com\/?p=165","title":{"rendered":"Inbox Zero: You are Doing Email Wrong (Step 1)"},"content":{"rendered":"

Ever leave the office and realize that the only \u201cwork\u201d you actually accomplished was answering or sending emails?<\/b><\/p>\n

If this has ever happened to you, or happens to you often — and you want to actually get real work done — please keep reading.<\/p>\n

I should also state up front that I don\u2019t consider processing email to be actual work (unless of course, your job is somehow 100% email-driven and\/or you perform a customer service function). Email is simply a communication tool, albeit an incredibly misused one (more on that in a separate post). As such, my goal in these next three posts is to free your inbox so that you can get back to getting real work accomplished.<\/p>\n

This particular discussion\u00a0covers the most efficient\u00a0way\u00a0to accomplish step one of my inbox zero methodology:<\/p>\n

    \n
  1. Check email<\/strong><\/li>\n
  2. Complete\/capture email<\/li>\n
  3. Close-out email<\/li>\n<\/ol>\n

    Or simply, how to “do email right.”<\/p>\n

    How to do email right<\/b><\/p>\n

    I have been managing five inboxes successfully (i.e. maintaining inbox zero) for the last five years. I have done this by adhering to three simple fundamentals. They are listed below.<\/p>\n

      \n
    1. Avoid sending email<\/li>\n
    2. Establish a battle rhythm<\/li>\n
    3. Batch process emails using step two<\/a> of my inbox zero methodology<\/li>\n<\/ol>\n

      Avoid sending email<\/b><\/p>\n

      Unfortunately, email begets email — so stop sending emails.<\/p>\n

      Look at your inbox, right now. How many emails in your inbox are responses to emails that you<\/span> originally sent? How many of those will you respond to? And how many of those will prompt another\u00a0response? It\u2019s a terrible cycle, and it can be avoided by using at least two much more efficient options: phone calls and meeting agendas. When to employ these preferred options varies depending on the situation, but either one of them is more efficient than an email conversation. Using these options instead of just \u201cbanging out a quick email to Bob\u201d also\u00a0requires a significant amount of willpower and\/or a trusted personal organization system. However, once a trusted system is in place, the\u00a0willpower requirement is significantly reduced or\u00a0eliminated.\u00a0I will explain the organization element in another post.<\/p>\n

      So when is<\/span>\u00a0it efficient or appropriate to send an email? The simple rule of thumb is to ask yourself, \u201cWill this email solicit an unwanted email response?\u201d If the probability\u00a0is \u201clikely\u201d or greater, then use one of your other two more efficient options (phone\/meeting).<\/p>\n

      Here are some examples of efficient or appropriate use of email:<\/p>\n

        \n
      1. As a follow-up to a discussion (phone\/meeting) that includes information or\u00a0files\u00a0that were already promised or discussed (i.e. nothing new is being introduced)<\/li>\n
      2. Sending FYI-type information to one or more people (i.e. no action or response required)<\/li>\n
      3. Requesting a file from a person who\u00a0will understand exactly what is being requested (i.e. a standard request)<\/li>\n
      4. Anytime zero responses are guaranteed!<\/li>\n<\/ol>\n

        Establish a daily battle rhythm<\/b><\/p>\n

        What\u2019s a battle rhythm? A battle rhythm is simply a dependable daily routine. The primary reason for establishing a daily battle rhythm is to ensure that key work inputs are reviewed every day so that correct priorities are established before beginning any work. Sticking to a battle rhythm also helps to avoid getting sucked into processing emails before first determining what\u2019s most important to accomplish that day.<\/p>\n

        A battle rhythm should include all the key input processing tasks that need to be accomplished each day. For the average office worker or executive, a battle rhythm should include the same general series of tasks: calendar management, processing email, managing to-do lists, and doing actual work.<\/p>\n

        My daily battle rhythm looks like this:<\/p>\n

          \n
        1. Open to-do list (GQueues<\/a>)<\/li>\n
        2. Open email, select calendar (avoid eye contact with the inbox at all costs!)<\/li>\n
        3. Review the week ahead<\/li>\n
        4. ID all key events that will require action and capture those in my to-do list<\/li>\n
        5. Prioritize to-do list<\/li>\n
        6. Accomplish 3-5 key tasks on my to-do list<\/li>\n
        7. Batch process emails<\/li>\n
        8. Repeat steps 5-7<\/li>\n<\/ol>\n

          If the idea of accomplishing real\u00a0work before\u00a0checking email is alien and unthinkable, it is absolutely possible to swap steps six and seven for the first round of the day only. However, keep in mind that if you are not able to start your day without checking email, ultimately, everyone but<\/span> you is\u00a0driving your priorities at work.<\/p>\n

          Batch process email<\/b><\/p>\n

          To batch process email means processing every email in your inbox without stopping or working on anything else. The keys to doing this most efficiently are (1) to follow step two<\/a> of my inbox zero methodology and (2) process email at pre-determined times during the day.<\/p>\n

          This particular tenant of \u201cdoing email right\u201d might be one of the hardest, simply because it involves a significant amount of willpower. The desire to accomplish the easy task (responding to the email) instead of the more complex or less pleasurable task, is a daily battle for many.<\/p>\n

          The simple truth, and the ultimate case for batch processing email, is that processing email all at once — instead of multiple or hundreds of times throughout the day — is absolutely the most efficient way. There are numerous articles<\/a> explaining why responding to emails throughout the day is woefully inefficient (and considered multitasking<\/a>, which is also terrible<\/a>), so I will not belabor the point here. I will however, happily provide some methods for avoiding it.<\/p>\n

          Here are some additional tips to avoid email multitasking<\/p>\n

            \n
          1. Establish times in your battle rhythm to process email, and stick to them<\/li>\n
          2. Turn off all email notifications (e.g. smartphone\u00a0lights\/sounds, desktop notifications\/sounds)<\/li>\n
          3. Check email only at established times throughout the day, no matter what<\/li>\n
          4. Let subordinates\/peers\/supervisors know that if they need something from you immediately, that they should stop by or call (most good leaders should know\/do this already).<\/li>\n
          5. If you are fortunate enough to be able to shape company culture, strive\u00a0to create a climate where employees don\u2019t feel required to respond to emails within minutes — it\u2019s hurting <\/a>your business<\/li>\n<\/ol>\n

            In summary<\/b><\/p>\n

              \n
            1. Don\u2019t send email unless you\u2018re guaranteed to not get a response<\/li>\n
            2. Establish a battle rhythm that includes a time to batch process emails — and stick to it!<\/li>\n<\/ol>\n

              Stick to these simple concepts and I guarantee that you will find yourself with much more time to accomplish your<\/span> priorities.<\/p>\n

               <\/p>\n","protected":false},"excerpt":{"rendered":"

              Ever leave the office and realize that the only \u201cwork\u201d you actually accomplished was answering or sending emails? If this has ever happened to you, or happens to you often — and you want to actually get real work done — please keep reading. I should also state up front that I don\u2019t consider processing […]<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"footnotes":""},"categories":[14,3,2],"tags":[7],"class_list":["post-165","post","type-post","status-publish","format-standard","hentry","category-efficiency","category-email","category-gmail","tag-inbox-zero"],"_links":{"self":[{"href":"https:\/\/www.joshevilsizor.com\/index.php?rest_route=\/wp\/v2\/posts\/165","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.joshevilsizor.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.joshevilsizor.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.joshevilsizor.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.joshevilsizor.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=165"}],"version-history":[{"count":10,"href":"https:\/\/www.joshevilsizor.com\/index.php?rest_route=\/wp\/v2\/posts\/165\/revisions"}],"predecessor-version":[{"id":263,"href":"https:\/\/www.joshevilsizor.com\/index.php?rest_route=\/wp\/v2\/posts\/165\/revisions\/263"}],"wp:attachment":[{"href":"https:\/\/www.joshevilsizor.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=165"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.joshevilsizor.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=165"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.joshevilsizor.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=165"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}