Wednesday, December 30, 2009

Fixed-schedule productivity

You know those half-days of work before you're about to go on vacation? You show up to work, have to leave by noon, and have a lot of things to get done before you go -- some of which you've been working on for weeks. It's always amazed me how, in that 3-hour span, you finish what might have taken 2 days if there weren't a pressing deadline, and often with higher quality results. You find a way to reach elusive people, get final answers to lingering questions, and cross off for good non-essential tasks.

Like most people, I generally consider myself to focused and disciplined when I work. But after I have one of these super-focused half-days, I realize how unproductive I am the rest of the time. Which is why Tim Ferriss's time management ideas (chapter 5) in the 4-Hour Workweek resonated with me and so many other people. Here's Ferriss's core argument in his words:
There are two synergistic approaches for increasing productivity that are inversions of each other:

1. Limit tasks to the important to shorten work time (80/20).
2. Shorten work time to limit tasks to the important (Parkinson's Law).

The best solution is to use both together: Identify the few critical tasks that contribute most to income and schedule them with very short and clear deadlines.
Ferriss recently tweeted about similar case for setting strict deadlines and focusing on what really matters: "fixed-schedule productivity" from Cal Newport. Newport, a post-doc at MIT, has a short version of his argument on his blog, but the longer, example-backed version from this guest blog post is better.

Here's Newport's one-sentence summary of the approach:
Fix your ideal schedule, then work backwards to make everything fit — ruthlessly culling obligations, turning people down, becoming hard to reach, and shedding marginally useful tasks along the way.
And here's his more detailed summary:

The steps to adopting fixed-schedule productivity are straightforward:

  1. Choose a work schedule that you think provides the ideal balance of effort and relaxation.
  2. Do whatever it takes to avoid violating this schedule.

This sounds simple. But of course it’s not. Satisfying rule 2 is non-trivial. If you took your current projects, obligations, and work habits, you’d probably fall well short of satisfying your ideal schedule.

Here’s a simple truth that you must confront when considering fixed-schedule productivity: sticking to your ideal schedule will require drastic actions. For example, you may have to:

  • Dramatically cut back on the number of projects you are working on.
  • Ruthlessly cull inefficient habits from your daily schedule.
  • Risk mildly annoying or upsetting some people in exchange for large gains in time freedom.
  • Stop procrastinating.

In the abstract, these are all hard goals to accomplish. But when you’re focused on a specific goal — “I refuse to work past 5:30 on weekdays!” — you’d be surprised by how much easier it becomes to deploy these strategies in your daily life.

Even though they're very similar (and I think 4-Hour Workweek was the inspiration for fixed-schedule productivity), I find Newport's case more palatable than Ferriss's -- because the steps to follow it are more concrete and his examples are of people who work a normal workday. That's not to say it's easy to stick to, but I'm trying ...

Tuesday, December 15, 2009

A plea for more Paradox of Choice research

Like Freakonomics co-author Stephen Dubner, I found Barry Schwartz's Paradox of Choice very persuasive -- even though one of my favorite free market commentators seems to equate Schwartz with the devil (here and here). In a recent blog post, Dubner cites new research that runs counter to Schwartz's argument that too much choice often leads to paralysis and unhappiness. It's interesting, but it's only from one sources and seems pretty limited.

What I can't figure out is why there's not more debate and research taking place on this issue, which seems so critical for economists, marketers, product managers, usability and design experts, and plenty of others in business and academia. How many choices to offer its users / customers / donors / etc. seems like a decision almost every organization faces in some area at some point; many face it constantly.

And it's not just makers of jam or chocolates. I've struggled with this issue with my resume writing service -- where I think we've gone from offering 2 packages, to 3, to none (custom-only), back to 2, back to 3, and for now to 6, with a frequent temptation to go back to 3. And Karan and I have wrestled with the "choice question" on our customer review site -- where I've seen in usability sessions that offering multiple ways to respond to a recommendation request causes confusion and frustration.

My datasets are unfortunately too small to provide clear evidence. But with the growing ability to measure conversions and sales so effectively on the Web, and the growing ability to run scientific A/B tests (e.g. show 50% of website visitors 5 choices, show the other 50% 2 choices), large companies with large dollars at stake surely must have some results on this that would illuminate the debate -- so that those of us interested don't have to keep reading about jam. Or have I just missed them?

Friday, December 11, 2009

Wikipedia's declining volunteer base

For many people like me, Wikipedia is the most successful example of opening content creation up to the masses and empowering and motivating volunteers to contribute high quality work. So this recent front page story from the WSJ is interesting, and a little troubling:
Volunteers have been departing the project that bills itself as "the free encyclopedia that anyone can edit" faster than new ones have been joining, and the net losses have accelerated over the past year. In the first three months of 2009, the English-language Wikipedia suffered a net loss of more than 49,000 editors, compared to a net loss of 4,900 during the same period a year earlier ...
As a few people from Wikipedia point out, the decline in the number of participants isn't necessarily a bad thing; the real question is, are entries and quality and usefulness to readers continuing to go up? Maybe a smaller number of participants can do this better than the earlier (or current) large number. But at the very least, the numbers and anecdotes suggest that the organization needs to do a better job attracting, or not scaring off, new participants -- especially among women, people over 35, and tech novices.