***Disclaimer*** - This is definitely a rant, but I think we should all take a moment to reflect on our emailing habits.

Work email is a fun topic because everyone abuses it, myself included.  It is far and away one of the biggest disturbances throughout the day.  I would be willing to bet you're either nodding incessantly, or screaming "What the heck are you talking about!?" at the monitor as you read this.  Either way, I would be glad to elaborate.

Problem:  The Cc Game

You might Cc someone because you think the person in the To field will respond better if they see that someone else has been invited to the conversation.  That's wrong, don't do it.  The people who get included on these emails can't get to other emails that are actually important, or may skip over the wrong emails.  If you feel like that is the only way to get an answer, then email is probably the wrong medium of communication.

CYA is a culprit motive of the Cc game, but we shouldn't have to feel like we need to cover our footprints with everything we do.  If you feel that way, it's probably a good idea to discuss it with someone.

Another reason to Cc someone (or better yet, a mailing list) is a shift of responsibility.  For all intents and purposes, it's like raising a flag to identify a problem, and then offloading the burden to all included parties.  Again, don't.  If you need help, you should have a prioritized list of people to talk to about your problem.  If you don't know who to talk to, don't use the spaghetti test (throw it at the wall and see what sticks).  Ask someone else who might know who you should ask.  Sometimes, there's even a process to dictate that for you.

A side effect of playing the Cc game is that people hit the Reply To All button.  If you're going to hit Reply To All, take a second to skim the recipients, and knock off the unnecessary ones.

Funny side note:  I saw an email today that had individually listed a few of my team members and myself in the To line, and then our emailing list in the Cc field.  Redundant!

To be clear: email is not unnecessary, but its misuse is.  Good communication has a strong correlation with success but it can be a double edged sword.  Over communication is distracting, and has a direct negative effect on productivity.  One general piece of advice I found while googling this topic was to only include recipients if you would actually call them on the phone about the issue at hand.  If you wouldn't include all of my team members in a meeting about your priority, then by Modus Ponens it is also unnecessary to include them in the Cc.

I'm not alone with this opinion, others feel this way tooMany other peopleLots of them.  This is all subjective, and is endlessly debatable.  I offer no concrete advice on when specific behavior is appropriate, but instead encourage you to think about who is on the receiving end before you press "Send," because I will.

Wednesday, February 17, 2010 7:18:21 PM (Eastern Standard Time, UTC-05:00)  #    Comments [0] -
Productivity | Email

How often are you “in the zone?” Is it a couple of times each day? Once a day? Once a week? Once a Month? Regardless of how often, I would be willing to bet that your best work is done while in the zone. Recognize this phenomenon and savor every juicy second.

Being in the zone means that time is irrelevant, and you are coding up a storm; absolute genius is flowing from your fingertips. All of your concerns take a back seat, and productivity rides shotgun.

[insert sound effect here]

clip_image002

Talk about instant buzz-kill! There are few things more sobering than an interruption while in the zone. It is a fragile state of Zen, and any interruption borders on personal offense.

Getting in the zone is like falling asleep. Some people are good at it while others have to work hard. It generally requires silence and an environment void of distractions. A leaky faucet stands between you and a good night’s sleep. You are a programmer, so naturally you have debugged the situation and come to the following conclusion: that faucet is going to die a horrible death. Thankfully, you have a meeting with the true head of the household (the wife), and decide that you should outsource the project to a specialist. A plumber fixes the leaky spout and you can once again examine the inside of your eyelids for holes.

Much like the faucet example, a developer must deal with distractions in the same way.

1. Diagnose the problem (Who wants what, and why?).

2. Solve it (Give them what they want so they will go away!).

3. Try to get back in the zone.

What’s more is the net effect of these interruptions.

“Consider that it takes 15 minutes for a developer to enter a state of flow. If you were to interrupt a developer to ask a question and it takes five minutes for them to answer, it will take a further 15 minutes for them to regain that state of flow, resulting in a 20 minute loss of productivity. Clearly, if a developer is prevented from flowing several times during the day their work rate declines substantially.” – Software Nation

Zone management seems impossible. To some degree, it is. Email is a raging river that will never end. Coworkers will always have questions. People around you will always chat and gossip. Silence is underrated. Even discomfort can jostle the flow.

Rest assured there is a point to this rant. Take control over what is yours, and protect your zone by any means necessary. If that means you need a $200 pair of comfortable headphones to drown out the world, so be it. If it means only allowing emails to break the floodgates once or twice an hour, go for it. Find what works for you and exploit it, because being in the zone is our number one secret to productivity.

Monday, September 28, 2009 10:14:53 PM (Eastern Daylight Time, UTC-04:00)  #    Comments [0] -
Productivity

I know this is kind of trivial...  It’s almost insulting to show someone how to open a file.  I’ll do it anyway, because I’m willing to bet that there is someone out there who is not aware that a file can be opened this way.  In Visual Studio 2008 there is a drop down list in the basic toolbar used for performing searches.  This elusive toolbar item is packed with hidden usability.

Command Box ExampleIf you type “> of “ followed by the name of a file, it will display a list of filenames that match your input, as well as their qualified locations within the current project.  Using the arrow keys, you can select any of the results that come up.  Pressing the enter key on any of the results will open the file.  I like this because I don’t have to think as hard about where a file is located.

Okay, okay.  You got me…  What I’m really trying to present is that Visual Studio 2008 Commands can be executed from the Find/Command Box.  Entering “>” into the command box indicates that this input is a command to be executed.  In that open file example, “of” is a command for opening a file.

The following command will open a new tab with the specified Url directly in the IDE:

>nav http://www.stackoverflow.com/

The following command will create a new file with the specified name:

>File.NewFile MyNewFile.txt

MSDN has plenty of information about this topic.  Enjoy :-)

Monday, July 13, 2009 5:00:03 PM (Eastern Daylight Time, UTC-04:00)  #    Comments [0] -
Commands | Productivity | Visual Studio

John Nelson

mugshot I am a passionate C# Developer working in ASP.NET on an e-commerce solution for ticketing software. I work across all of the application layers, including server side functionality, and client side programming with jQuery and MS Ajax. Although my full time job is in WebForms, I spend many of my off hours working with MVC. I am especially interested in productivity and good programming practices.

Disclaimer
The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

© Copyright 2010
John Nelson
Statistics
Total Posts: 25
This Year: 3
This Month: 1
This Week: 0
Comments: 1