whoisjoe.com

Email Strategy

  

November 24, 2013

Home About Projects Blog LinkedIn ReThink Security

I’ve seen a few different articles about people’s different e-mail strategies and they certainly seem to be a hot topic. With our ever reliance on e-mail as a primary mechanism for communication it’s important to be able to keep up with the constant stream of messages coming in.

You ultimately have to devise a strategy that works for you, and there are many out there already, I’ll be throwing my hat into the ring. To sum up my strategy, stop organizing, start searching and use flags to make sure nothing slips through the cracks.

Here are a few of the strategies that I’ve tried historically and why I’ve decided they don’t work for me. Ultimately I’m an Occam’s razor kind of guy, so I try to stay away from complexity.

  • Inbox Zero - I have too many items that need more a day to process and I don’t like feeling guilty about todo messages. I don’t have an easy way to archive and search through the archive, however I use a lot of tactics from I0 with my strategy using Flag For Follow-up.
  • Labels/Folders - I’ve tried folders, but folders assume that I know how I want things to be organized before the messages come in. I’ve tried organizing by client, by project, etc. but it always falls apart. I also have to remember to organize them as they’re coming in.
  • "Getting Things Done" - This is more of a time management strategy, but it could be applied to e-mail as well. It’s too complicated for a messaging system.

Here’s my detailed strategy: I don’t really use folders or filters, other than spam, github and mailing lists (which are all kind of the same thing). Those go into their respective folders and I almost never look at them.

My e-mail is generally in three states: unread, flagged, read, and it all stays in the inbox. Then I use searching to find stuff later.

  • Unread - I haven’t read it (also may mean I’ve read it on my phone, but requires action since flagging doesn’t work on the iPhone properly, this will be taken care of or flagged when I get to my computer)
  • Flagged For Follow Up (F^3) - I need to take some action that will take more than a couple minutes to respond to.
  • Read (and not flagged) - no action needed at this point (essentially archive).

There’s one other flag I use “Informational” which is for e-mails that I need quick reference to, but don’t need my attention any more.

In the morning I plow through all e-mails. I read them all quickly. Respond to anything I can off the top of my head. Anything that takes longer than a few min to respond to I’ll flag it for follow up. Once I get through my inbox I start tackling my flagged box.

If it’s time sensitive (needs a response quickly), but won’t take too long to follow up, I do those first. Then I’ll tackle the ones that are time intensive, but do require some time (or I need other people to help with). Finally I’ll take care of the ones that are time intensive.

If the F^3 folder gets into the double digits I carve out some time during the day to get it down and make a concerted effort to make sure there’s no cruft left over or somebody who has been waiting for my response for days.

If I zero out my F^3 box and everything is “read” I send out an e-mail to folks letting them know that if they’re waiting for something from me that I’ve lost it. This only happens once or twice per year, but it’s an opportunity for me to alert anybody who thinks their request is still in the queue to remind me.

I go through this process a few times per day, but generally either stay in front of the mails as they come in by keeping mail up and running the whole day, or I shut it down to get work done that requires more focused attention then let them build up and start at the top again.

I use Mail.app for my mail with the GPG plugin and my SMIME Cert installed. I use the following mail settings to make it suck less:

This one will default to SMIME instead of PGP for encrypting and signing.

defaults write org.gpgtools.gpgmail DefaultSecurityMethod -int 2

The one will force attachments to be displayed in icon mode instead of view mode.

defaults write com.apple.mail DisableInlineAttachmentViewing -bool yes

I use a setting to highlight addresses not ending with @securityinnovation.com which will make any other domain show up red. This reduces the risk of sending SI sensitive information outside of SI.

I am adamant about adding images to each sender in my contacts list. This makes it easy for me to recognize anybody who is sending me email, which makes it easier to find the information I need.

I set mail to mark whether I’m on the to or cc line of e-mails, which is nice, but it doesn’t play into how I respond to e-mails because senders aren’t reliable enough with those fields.

Using this strategy I don’t have to search for e-mail much. Anything I need is right in front of me in my F^3 folder or it’s unread. That means I don’t waste time searching through folders or tags or labels.

I rely on Mail.app’s built in search index, which can be good, but it does struggle with 10,000+ messages to search through. It does a good enough job, though that I’m happy.

Since I rely on searching to find e-mail it’s important for senders to send me mail with good subject lines and content. If the mail gets read and isn’t flagged, and doesn’t have a good subject and body it may get lost. Maybe I’ll write another blog post on e-mail etiquette sometime, but for now this article describes How to Email Busy People

In case I don’t get to my version, here’s a sneak peak off the top of my head:

  • Use Subjects - These are incredibly important to help sort and filter email mentally.
  • Be concise - Send all the information needed and with recommendations on action in the first paragraph. If you need to support your recommendation, do that after and mark it as such. Example: “I’m increasing our weekly coffee purchases from 3 lbs per week to 7 lbs per week. If you’re interested why, or disagree, please read on…”
  • Respect the Thread
    • Reply to the right thread - Most modern e-mail clients build threading in. They either do this by subject or thread index or some other mechanism. Try to keep each conversation thread separate, even if you have multiple conversations going with the same person.
    • One subject per thread - similar to above, but talking about multiple clients or unrelated issues in the same e-mail
  • Break questions into lists - if you have multiple questions I have to answer in an e-mail, break them into lists. I can copy your questions and respond inline easily. This makes it easy for you to know that I’ve answered all your questions and makes it easy for me to do the same.
  • Use my name if I need to do something - on its own separate line start with something like “Joe: Check on the widgets before Monday” I can quickly grab that todo item out of my mail and act on it. If you bury your ask in the middle of a paragraph I may forget and lose it.
  • Use to, cc and bcc properly - I’ve almost given up on this, but if people could use the fields properly I think email could be more efficient.

Posted By: Joe Basirico

  • 81 More Posts
  • So, You're a Manager Now
  • A Mixtape in 2022
  • The Middle Path of Planning and Reflection
  • Micromanagement and Trust
  • On Giving Advice
  • Emergency Preparedness During Coronavirus Frenzy
  • Mind Map Your Life
  • Start With the Hard Part
  • Delight in the Details
  • Introducing ReThink Security
  • Newsletter & Recommendations
  • Take a Moment
  • Triage Decision Making
  • Show Your Work
  • Getting Back Up
  • Max Out vs. Continuous Development
  • Mental Diet and Exercise
  • Asking for Help Part 2 - Alerting
  • High Water Mark
  • Who Do You Want to Be
  • Presentation Tips
  • Asking for Help
  • China Hijacking the Internet
  • Recording Audio with AirPods in Imovie
  • Active Decisions
  • Create/Publish Scripts
  • Specialize or Do Not Specialize
  • Exactis Breach
  • Optimizing Images
  • What I Track
  • What I’m Thinking About May
  • What I’m Thinking About March
  • What I’m Thinking About January
  • Building a Collaborative & Social Application Security Program
  • Lazy Days in the Cloud
  • Delegate Then Do
  • So you want to be a better programmer
  • Project Success
  • Don't Short Circuit a Lesson
  • Scale Your Solution to the Problem
  • Digital Currencies
  • Fortnightly
  • Why You Should Have Trust Issues with Pokemon Go, and Every Other App on Your Phone
  • In Defense of Reverse Engineering and Responsible Disclosure
  • Ruby open allows command injection if user controlled
  • New Mac Install Guide
  • Understanding Customer Needs and Helping Them Mature
  • My Experiences with IOS8 and Yosemite so far
  • The Importance of Vulnerability Disclosure Programs and Bug Bounties
  • My New Record Player and Beck - Morning Phase (The Vinyl Experience)
  • An Hour of Code with Code.org
  • Gmail Changes to Displays Images by Default
  • Why I Donated to Help Jailbreak iOS7 & You Should Too
  • Email Strategy
  • Shutdown
  • Anatomy of a Distributed Denial of Service (DDoS) Attack
  • NASA Forced to Suspend All Public Outreach & Education Programs
  • Joe_CMS Open Source!
  • Mobile Application Security Testing FAQs: Post #1
  • How Much Security Does Obfuscation Get You?
  • Why Privacy Matters Even if You Have 'Nothing to Hide'
  • What LinkedIn Should Have Done with Your Passwords
  • Constant Vigilance
  • Boeing Paying Hackers to Break into Their Systems
  • My Reading Cycle
  • Developing Tools for Professional Hackers
  • Finding Your Inner Evildoer (4/4): An Evil Streak
  • Finding Your Inner Evildoer (3/4): A Good Imagination
  • When to Rebuild Your Process from Scratch
  • Finding Your Inner Evildoer (2/4): Complete Knowledge of the System
  • Continuous Incremental, Personal Improvement
  • Finding Your Inner Evildoer: Part 1
  • CISCO Password Revealer
  • Battling with Word and Excel
  • Which is More Secure: Windows or Linux?
  • The High Cost of an Application Security Data Breach
  • Using the ConfigurationManager to Access your ConnecitonStrings in the Web.Config
  • New WikiRater Features
  • When is it OK to Build up Technical Debt
  • Time Management with the Pomodoro Technique
  • Manage Energy Not Time
  • Goals, Results and Activities - defining your productivity
© 2022 whoisjoe.com