Home
BYTE Newsletter
Keep up with all the BYTE News and Reviews

Subscribe
Jonathan Feldman

Jonathan Feldman

Contributing Editor

Email Overload: Disease Or Symptom?

Comments | Jonathan Feldman, InformationWeek | December 27, 2012 08:36 AM


10 Best Business Tools In Google+
10 Best Business Tools In Google+
(click image for larger view and for slideshow)
We all say we want less email. But, do we really mean it? I think we're saying: I want less irrelevance in my life. Much in the same way we complain about time-wasting meetings -- instead of focusing on creating fantastic and nimble work sessions -- I'm not sure we're focusing on the right problem.

Readers of my recent column on email overload noted that advances in technology and social media can fix the email glut problem. InformationWeek executive editor Lorna Garey points out that until social media gets federated, we'll continue to rely on email as a common ground for collaborators. Other readers also acknowledged that there are significant cultural changes needed beyond just turning off email notifications on social media platforms.

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

Vendors helpfully let me know about their inbox products, and they're impressive. For example, I'm pretty sure that I will start using SaneBox soon -- it is "importance-filtering" for the 21st century, taking the "priority inbox" one step further, with follow-up reminders, antispam-like mail summaries, and a system for deferring less important emails.

[ Read Google Releases Gmail 2.0 For iOS. ]

Mailbox App, with its organization and deferral system, also offers features that I want, because I yearn for its "inbox zero, daily."

This is all great stuff. But the most telling discussion point came from InformationWeek's John Foley, who wrote a cover story 10 years ago about personal information glut, the biggest culprit of which was, you guessed it, email. It's 10 years later and we're losing the struggle between incoming information and ways to handle that information.

Can we agree to stop the madness and train employees to reduce email burden? Well, we can, but it's distressing to see the sorts of draconian solutions that are proposed. No saying "thank you" over email! Days or specific times when email is prohibited! Have an email sent-item quota! Create an email perp wall! It smacks of the time I took a job and at least five employees told me of the "no laughing" rule of the old boss.

Global CIO
Global CIOs: A Site Just For You
Visit InformationWeek's Global CIO -- our online community and information resource for CIOs operating in the global economy.

I think email overload is simply a symptom of the larger dysfunctions in our organizations, the factory-like, "scientific" management touted by Max Weber that sounded good in the late 1800s. That management has allowed us to create larger and larger organizations. But now we need to ask whether huge organizations are in fact a desirable thing, and how we expect people to act human when we ask them to specialize like insects. These huge organizations create pain that create many bad things, including email burden.

Why do people send so many darn emails? They feel like they can grab attention. Even if their jobs are meaningless, they're creating something permanent when they create an email. They cover their butts by documenting every little thing. (The latest trend of folks CC'ing themselves makes me shudder every time I see it.)

Here's a thought experiment for you. Consider two people in the same room, one of whom works for a large multinational corporation, and one of whom works for a startup, and think about who has a higher email burden per capita, and why. "Stupid bureaucracy" is what most people came up with, as I played through this experiment with a number of folks.

Trevor Lohrbeer, a startup and decision support consultant and blogger, noted that CYA -- cover your a** -- doesn't happen at startups, because, "if you're a startup with less than 50 people, and someone's not working out, they get fired."

I'm not saying that we shouldn't provide guidance. IT has a key role in providing guidance. But we should provide guidance that addresses the problem, not exacerbates it. Let's invite employees at large organizations to be a part of the solution. I mostly like the guidance that is given at Email Charter: Respect recipients' time; slow or short is not rude; celebrate clarity; quash open-ended questions; slash surplus CCs; tighten the thread (meaning, get rid of the trail and summarize, or pick up the phone); let people know that they don't need to respond; and choose to spend less time doing email (which is very different from a quota).

But we also need to remember that we are treating symptoms, not the causes. To treat the cause of disengagement, which breeds the lonely "I'm here!" emails, leaders need to make employee engagement and meaningful work a priority, instead of simply enacting edicts about what types of behaviors and outcomes are needed.

To treat the root cause of CYA, focus more on learning how to create the right outcomes, and less on punishments for the wrong outcomes. To cut down on irrelevant email chatter, have more focused in-person interactions. To encourage thoughtful documentation of an agreed-upon plan instead of off-the-cuff emails, create more time in the project lifecycle instead of everything being "hurry up and wait."

Is this possible, or will we be having this same conversation again in another 10 years? The answer: Unless we reinvent the large organization, I think we will.

Jonathan Feldman is a contributing editor for InformationWeek and CIO for a rapidly growing city in North Carolina. Write to him at jf@feldman.org or at @_jfeldman.



Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

BYTE encourages readers to engage in spirited, healthy debate, including taking us to task. However, BYTE moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. BYTE further reserves the right to disable the profile of any commenter participating in said activities.

COMMENTS

Tune In to BYTE
Facebook Twitter LinkedIn Newsletter RSS
Whitepapers
whitepaper
In this paper you will learn the five trends shaping the future of enterprise mobility. Learn how the rise of social media as a business application, the lurring between work and home, the emergence of new mobile devices, the demand for tech savvy employees and changing expectations of corporate IT will fundamentally change the workplace.
whitepaper
In a survey of more than 1,700 information workers (iWorkers) in North America, notebooks, desktops, and smartphones were found to be “must-have” devices, while tablets, slates, and netbooks were relegated to “nice-to-have” status, according to a commissioned study conducted by Forrester Consulting on behalf of Dell and Intel.
Sponsored by: Dell
Upcoming Events