Tips for Productivity and Happiness at Work
Every so often, I get asked what my strategy is for "getting things done". This morning, I had a short session of mass productivity, and on my ride into work, got inspired to jot down a few tips productivity tips. Keep in mind that I grew up in the back woods of Montana with no electricity and I'm mostly Irish.
- Write stuff down. The first and most important means to getting things done is to keep a todo list. I keep mine on Ta-da List and update it daily, if not hourly. My two most important lists are "When I have time" and "This Week". I regularly re-order "This Week" for the current day.
- Quit reading e-mail and blogs. One of the ways I can tell I'm in uber-productive mode is my unread (or starred) mail piles up and I haven't read any blog posts (or blogged myself) in a couple days. I like GMail because I can easily star an e-mail after briefly skimming it. For some reason, flagging e-mail in Thunderbird or Mail.app doesn't work for me - I rarely go back and find those e-mails. With GMail, I'm always conscious I need to revisit starred messages.
- Work on open source late at night, with a beer on your desk. While I do get the opportunity to work on open source at my day job, I still find that I'm most productive at night. Maybe this is because no one bugs me via e-mail or IM, or maybe it's just because the world is asleep. The strange thing is I often find myself motivated at 3 p.m. for my 11 p.m. workload. However, when I get to 11 p.m., I'm not motivated to work on anything. I've found that cracking open a beer at 11 when I start helps me focus and quit worrying about all the other computer-related tasks I need to do. Also, on beer #2 or 3, you'll start to forget what time it is and really start getting things done. NOTE: this isn't for rookies. If you're a lightweight and get hammered on two beers - just go to bed when you start coding with one eye shut. It helps to sleep in the next day after doing this. If you finish off a six-pack before going to bed, it's probably best not to check your code in - you're probably going to spend the next day fixing it anyway. Regardless, this is a great way to get started on a new feature because you're less concerned about the details and more concerned about the big picture. I've also found that "bug fixing juice" can be great for fixing bugs - it gives you a different perspective on the problem. I told you I was Irish didn't I? ;-)
- Work disconnected. To further facilitate not checking e-mail or reading blogs, I've found that going to a coffee shop w/o connectivity is my most productive environment. They have liquid motivation in the form of coffee, and you can feed your brain with breakfast/lunch or some kind of snack. My most productive days are the ones where I show up at my local Einstein's (bagel shop) at 6 a.m., have two cups of coffee, and work with my headphones on. After the coffee and uber-productivity, I often have an awesome ride to work and barely notice the miles. NOTE: I've found that I'm more productive writing code late at night and authoring articles/books in the early morning.
- Listen to music while you work. Some noise-cancelling headphones and your favorite music can do wonders for your productivity. Of course, earbuds work just as well - whatever makes the music sound good. Good music can really help you "get into the groove" of what you're working on, regardless of whether it's writing or coding.
- Work long hours on Monday and Tuesday. This especially applies if you're a contractor. If you can only bill 40 hours per week, working 12-14 hours on Monday can get you an early-departure on Friday. Furthermore, by staying late early in the week, you'll get your productivity ball-rolling early. I've often heard the most productive work-day in a week is Wednesday.
- Avoid meetings at all costs. Find a way to walk out of meetings that are unproductive, don't concern you, or spiral into two co-workers bitching at each other. While meetings in general are a waste of time, some are worse than others. Establish your policy of walking out early on and folks will respect you have stuff to do. Of course, if you aren't a noticeably productive individual, walking out of a meeting can be perceived as simply "not a team player", which isn't a good idea.
- Sleep. While working late nights can be productive in the short term, doing it consecutively will burn you out quickly. Getting a good night's sleep can often lead to greater productivity because you're refreshed and ready to go.
- Work on something you're passionate about. If you don't like what you're doing for a living, quit. Find a new job as soon as possible. It's not about the money, it's all about happiness. Of course, the best balance is both. It's unlikely you'll ever realize this until you have a job that sucks, but pays well.
To follow up on that last point, I think one of the most important catalysts for productivity is to be happy at your job. If you're not happy at work, it's unlikely you're going to be inspired to be a more efficient person. Furthermore, if you like what you do, it's not really "work" is it?
Here is some general advice I give to folks about jobs and careers. I realize that I'm biased here because I have a good job and I've been fairly successful in my career. However, I also grew up with virtually nothing, and learned all my computer skills on my own. Therefore, I believe that anyone can be successful (meaning: happy with that they do, and financially stable at the same time) if they put their mind to it.
- If you're not happy at work, quit. I got into contracting early-on in my career (6 months out of college), so I got spoiled with good rates early on. It was also the late 90s, so you could easily switch jobs if you didn't like the one you were in. However, I've always had the policy that if you hate your job for more than 2 weeks, quit. It's just not worth it. Some people enjoy bitching about their jobs and complaining about their co-workers, so this doesn't apply to everyone. However, if you're truly miserable - quit. I've done this a couple times, and it's always led to better opportunities (even if I had to wait 3 months). Julie's done it once or twice and it's always worked out for the better. Once she even got a 20% raise by quitting her traveling-consultant gig with KPMG and going back to her old company, Qwest.
- Always try to be a contractor before a full-time employee. This especially applies to younger folks who don't need the security of insurance for the family, stock plans, etc. Contractors typically make 50% more than full-time employees and tend to be excluded from company politics that might make the workplace difficult to deal with. While you won't get billable vacation time, you will get the freedom to take however much vacation you want - as long as you get your stuff done. The higher rates can generally make up for the unbillable time while on vacation. However, if you travel too much for fun (or conferences, etc.), it's likely your year-end salary will equal that of a full-time employee. If you make good money as a contractor, you'll also get the opportunity to start your own company (to save money on taxes). This can be a great learning experience. The biggest fear that folks have about "going independent" is they'll have a hard time finding their next gig. If you're productive and blog about what you're doing, this shouldn't be a problem. I haven't had an "interview" since 2002 and haven't updated my resume since then either. Networking at your local JUG and conferences is key.
- Don't work at a company with a two-week vacation policy. I've never worked at a company with a two-week vacation policy, and I hope I never will. The two full-time gigs I've had in my career have had no vacation policy. This is usually only found in startups - but it generally amounts to "get your shit done, and you can take off all the time you want". My parents both work for the BLM (government agency) and they get 6 weeks off a year. Furthermore, they can earn "comp time" (more days off) by simply working overtime. If you have the ability to take time off whenever you want, it'll likely lead to you being more motivated to work long and hard - b/c you know when you finish that project, you're heading to Cancun for a week.
- Don't travel if you have kids. If you're single, traveling for work is pretty cool. New places, new people to meet - and seeing the world can be very cool. If you have a spouse, it's likely your desire to travel will decrease, but it's still not that bad. If it helps your career, it's probably a good move. It also helps to save money since everything you do is generally expensible. When Julie and I first met, she traveled 100% and made $20K more per year b/c of it. When you have kids, everything changes and traveling sucks. You miss their first steps, and when they get to toddler-age, they'll want to go with you. Hearing your daughter say "Daddy, can I go with you?" can be heart wrenching when you're leaving on a Sunday afternoon to spend a week with people you've never met before.
- Ask for more responsibility. If your job sucks, but the company is pretty cool - you may want to ask for a shift in responsibilities. I was once an HTML Developer at a .com. It sucked because we were constantly waiting on the Java Developers to fix bugs we found in their code. Finally, I got tired of waiting and asked my boss to show me how to fix the Java bugs. Granted, I wrote some pretty horrendous code at first, but my boss and co-workers helped a lot and w/in a year I was doing 80% of the Java Development.
- Most things can be learned by reading. If you want to learn something new (for your current or next career), the best thing to do is read. The world's knowledge resides in books and you can learn a lot. Of course, the best way to retain that knowledge is by doing, but reading is a great first step.
Those are my tips, many of them off the top of my head. I may add more as time goes on - but hopefully this helps in the meantime. Please share yours if you have any.
Posted by Brad M on April 14, 2006 at 12:00 PM MDT #
Posted by eu on April 14, 2006 at 01:09 PM MDT #
Posted by David B on April 14, 2006 at 01:44 PM MDT #
Posted by Gabriel K. on April 14, 2006 at 02:50 PM MDT #
Posted by Seshadri Ramani on April 14, 2006 at 03:41 PM MDT #
You may consider:
Posted by Jaime F. Zarama on April 14, 2006 at 04:48 PM MDT #
What? Maybe that's good for productivity, but certainly not for Hapiness! One of the small joy that I have each day is to browse through my daily list of links and blogs, and contributing to my own of course :)
[Geeks Are Sexy] Tech. News
Posted by [GEEKS ARE SEXY] Tech. News on April 14, 2006 at 09:18 PM MDT #
Posted by Josh Delsman on April 15, 2006 at 12:31 AM MDT #
Posted by slim on April 15, 2006 at 01:04 AM MDT #
Posted by Amish Gangar on April 15, 2006 at 01:36 AM MDT #
Posted by Frank Zappa on April 15, 2006 at 01:40 AM MDT #
Posted by Brandon Boss on April 15, 2006 at 01:57 AM MDT #
Posted by Rob Morgan on April 15, 2006 at 02:15 AM MDT #
Posted by Arno on April 15, 2006 at 04:07 AM MDT #
Posted by Johnny Chadda on April 15, 2006 at 04:11 AM MDT #
Posted by Myrak on April 15, 2006 at 04:58 AM MDT #
Posted by Lars Fischer on April 15, 2006 at 05:53 AM MDT #
--- <em>web design london</em>
Posted by Juuuisu on April 15, 2006 at 06:50 AM MDT #
Posted by Jeff on April 15, 2006 at 09:36 AM MDT #
Posted by Sanjiv Jivan on April 15, 2006 at 09:54 AM MDT #
Posted by E.Grossman on April 15, 2006 at 10:35 AM MDT #
Posted by Mark on April 15, 2006 at 10:56 AM MDT #
Posted by Ben Reubenstein on April 15, 2006 at 11:21 AM MDT #
Posted by David on April 15, 2006 at 11:21 AM MDT #
Posted by Classical Coder on April 15, 2006 at 11:35 AM MDT #
Posted by Berlin Brown on April 15, 2006 at 12:34 PM MDT #
Posted by Anthony Eden on April 15, 2006 at 01:07 PM MDT #
Wearing a headset and listening to loud music helps concentration because it makes harder for other people to interrupt you.
It is easier to forget about music pounding into your ears than it is to stop doing what you are doing, make a response to a request and then remember what you were trying to do before. People have to make an effort to overcome noise and interrupt you and this shields you from interruptions for trivial causes.
Posted by 18.104.22.168 on April 15, 2006 at 02:07 PM MDT #
Posted by Christina on April 15, 2006 at 03:37 PM MDT #
Posted by Mr. K. on April 15, 2006 at 07:51 PM MDT #
Posted by Thiti V. Sintopchai on April 16, 2006 at 12:10 AM MDT #
- i have all my passwords, helpdesk phonenumbers, ids, pincodes, addresses, and so on stored in "codewallet pro 2005", i sync this with my pda, whenever i need such a thing i just start the app on either my pda or my laptop. Saves me much time looking for passwords or whatever and it is encrypted.
- i tried lots of different ways of storing address information, todo items, and general other tidbits, after trying a zillion of applications the past years i just went back to 1 single spreadsheet with an enormous amount of worksheets in it. Now i just have freeform space to copy and paste stuff from e-mails whereafter i can delete them. I regularly backup the spreadsheet, i renumber it with the day and then store it in a secured place.
In the spreadsheet i give hot items another color. I use a color scheme.
- i use freemind (google) for some of my hot todo areas, these are just temporary mindmaps but they work great for related clouds of todo stuff. I just wished i could link the items to my wiki. I made a new toolbar in my taskbar area in Windows (rightmouseclick, new toolbar) and point it to 1 directory which i named "A". Under there i copied several foldes among others the folder where i keep all my mindmaps but also one in which i keep my favorites which i just store as shortcuts. I organize these via total commander like files, handy when syncing.
About the mindmaps: the size of the cloud gives me an indication what currently takes the biggest space in my brain.
About the toolbar: i also placed all my desktop icons in there, a cleaner desktop gives me more quiet feeling.
- Under the A folder for the toolbar i created several handy folder which i use more often, such as "avatars", each time a website asks an avatar i know where to find it. I used to call this main overall folder "repository", handy for regular backups.
- I bought a dual layer dvd drive and combined my old cdrom backups on the larger dual layer dvds, they are more expensive but i just needs a few of the dual layer dvds so i just have a small pocket with DVDS where all my files are in.
- I dont agree with dont reading blog and such. I installed the RSS ticker extension for Firefox and just added a few RSS Feeds: the feeds from the blogs and such of my friends and some relations. Whenever they post something i see it at the bottom of my screen. On the one hand this could lead to more information and time but somehow it saves me time going through each of my rss feeds/blogs i really want to keep track off.
- Other things... i think i am going to make a blog posting about this on my own weblog, nice subject :)
Posted by b@@ on April 16, 2006 at 02:06 AM MDT #
Replying to David: Your (implied) question "what should I do about the distraction, because I can't wear headphones"
In your situation, I would find out if I could wear earplugs.
If you're like me and talk on the phone on one side, you can take out the earplug for the ear that you hold the phone to and leave the other on, then put both back in when you're done.
If there's not a policy against that, I think it would be very difficult for your manager to argue with you asking to use earplugs because you want to be more focused and productive while working.
Sometimes I listen to music, sometimes I don't; depending on what I'm doing and how much I have to intereact with others, but I often leave my earbuds in, because they help block out the distracting noise from the rest of the office.
Posted by Brandon on April 16, 2006 at 04:19 AM MDT #
Posted by David on April 16, 2006 at 10:50 AM MDT #
While I second most of your thoughts, I don't support this pretty much.
Emails -> Yes, I keep all new email alerts turned off, and shutdown my email client when I want to
'get things done'. And open it only when I want small breaks. Same goes for blogs. I believe quitting
it altogether would be an extreme step, but developing a discpline on when and how many times
to check them is of paramount importance.
Posted by Atul T on April 17, 2006 at 03:13 AM MDT #
Posted by Chester on April 17, 2006 at 04:46 AM MDT #
Posted by Lutz on April 17, 2006 at 07:29 AM MDT #
Posted by Pedro Remedios on April 17, 2006 at 08:21 AM MDT #
Posted by Bloody Fingers on April 17, 2006 at 10:39 AM MDT #
Posted by b on April 17, 2006 at 01:15 PM MDT #
Posted by Matt Raible on April 17, 2006 at 01:16 PM MDT #
Posted by yp on April 17, 2006 at 07:42 PM MDT #
Posted by Mark Johnson on April 18, 2006 at 08:50 AM MDT #
Posted by Antonio Gonzalez on April 18, 2006 at 09:13 AM MDT #
Posted by David on April 18, 2006 at 09:23 AM MDT #
Posted by Matt Raible on April 18, 2006 at 09:23 AM MDT #
Posted by Berlin Brown on April 18, 2006 at 09:55 AM MDT #
Posted by UOP on April 18, 2006 at 03:25 PM MDT #
Posted by kriti on April 20, 2006 at 07:04 AM MDT #
Posted by Mark Johnson on April 20, 2006 at 08:08 PM MDT #
The best way to work on open source is to get paid to do it. Of course, that's often a dream job that's tough to come by. However, one of the best parts about being a contractor is there's often "down time" (or you can just be productive enough to produce your own free time). You could use this time to work on open source or play with your latest favorite technology.
<em>> What is your impression of Ruby on Rails?</em>
I think it's awesome in the simplicity it brings to web applications. I did web sites waaaayyy before I did this Java stuff and I've always admired clean and simple solutions to web applications. I've bought the Ruby and Rails books, but haven't had time to read them - mostly because there's still plenty of clients interested in open source Java tools. That being said, I can't wait for the first project I can use it on. Then again, I have AppFuse - and I'm pretty damn productive with that. ;-)
Posted by Matt Raible on April 20, 2006 at 09:17 PM MDT #
Posted by Norm Thomas on April 20, 2006 at 11:14 PM MDT #
Posted by Matt Raible on April 21, 2006 at 12:49 AM MDT #
Posted by H?vard Pedersen on June 23, 2006 at 03:42 AM MDT #
Posted by cmanlong on April 16, 2007 at 10:25 AM MDT #