Microtasks

Sometimes we procrastinate on projects because we don’t know where to begin.  A goal like “write a book” might seem straightforward enough when first set, but when it’s time to act, the goal becomes this huge, amorphous blob.  Procrastination soon follows.

A popular suggestion is to define the immediate next action that must be taken, and then focus on that.  Once that’s done the next action after that should become clear.  I’ve had mixed results with this approach.  It helps in some cases, but sometimes it isn’t enough to get things moving.  Even when the next action is simple and achievable, I’ll still sometimes avoid getting started because I know it’s only going to lead straight into that enormous blob of complexity again.

A solution I’ve found more effective is to break a large project down into a lengthy list of “microtasks,” planning it all the way from beginning to end if possible.  A microtask is a very basic action item, so small that you’d be hard pressed to break it down any further without it being ridiculous to do so.  An example of a microtask is to make a 5-minute phone call.  If you have to break it down into dialing the phone number, you’re going too far.

A typical microtask can be completed in less than 30 minutes, ideally in less than 10 minutes.  Again, these are very small, well-defined actions.

You may be thinking that it isn’t always possible to break a large project down into microtasks before you’ve gotten started.  Sometimes, however, another person has already done most of the work for you.  For example, if you want to know how to write a book, you can find books with step-by-step instructions on how to do that.  I wouldn’t say they break it down all the way to the level of microtasks, but they do come close.

There are indeed situations where there’s simply too much uncertainty to plan a project from beginning to end at microtask granularity.  A good example is software development, which often works best with an iterative development process.  In such situations, you can still use microtasks to plan out as far as you can reasonably see.  Then when you reach a certain milestone, update your plan for the next stretch ahead.

Microtask outlines

For many tasks it can be helpful to create a microtask outline showing all the steps you’ll need to complete from start to finish.

Here’s an example 20-step microtask breakdown for the task of writing a new blog article.  The steps are in sequential order:

  1. Define a primary objective for the article (inform, persuade, entertain, or inspire).
  2. Brainstorm topic ideas, or review the list of reader-submitted topic suggestions.
  3. Select a topic.
  4. Do a quick and dirty, free-form writing session to get ideas down without regard to structure.
  5. Decide how to organize the ideas for clarity (chronological, topical, hierarchical, sequential, etc).
  6. Sort the output of #4 based on the desired structure.  Define the main sections and subsections.
  7. Identify supporting material to include (examples, analogies, quotes, statistics, images, stories, etc), and add it to the outline.
  8. Refine the outline from #6 and #7 for completeness and balance.
  9. Expand each section of the outline into paragraphs (and bullet lists if appropriate).
  10. Insert meaningful subheadings into the article.
  11. Write the opening.
  12. Write the closing.
  13. Edit the article for content, clarity, and conciseness.
  14. Spell-check the article.
  15. Brainstorm possible titles for the article (clear, interesting, keyword-rich).
  16. Select a title.
  17. Select blog categories for the article.
  18. Decide when to post the article (now or future-post).
  19. Publish the article.
  20. After the article has been online for several hours, evaluate reader feedback and fix any reported typos.

Notice that every item begins with a verb.  OK, so #20 starts with a preposition, but it gets to the verb soon enough.  The verbs are important because these are physical actions to be taken, not just ideas to ponder.  The more clear and concise your verbs, the better your outline.

To an experienced blogger, the list above may seem excessively anal.  I don’t need such a list myself because after writing about 600 articles, the process is deeply internalized.  However, for a new and inexperienced blogger just starting out, such a list can be very valuable.  It helps you avoid getting stuck.  Most steps are simple enough that they can be completed in minutes.  The two main exceptions are #4, which involves getting your ideas down any way you can, and #9, which is where you expand the outline into paragraphs.  For anyone capable of writing an article, however, these steps are straightforward enough that they shouldn’t induce the desire to procrastinate (but if they do, you can always break them down further).

When I’m kicking off a really big project, I often like to create a microtask outline from start to finish.  Sometimes these lists can be several pages long and may take days to create.  But I usually find the effort worthwhile.  Once the list is complete, it makes the implementation go much more smoothly.  It also makes it possible to create decent estimates of when a project will be done.  I’m really bad at estimating a project’s length until I’ve created a microtask outline for it.

Microtask outlines are especially useful for repeatable projects.  When I was actively publishing downloadable computer games several years ago, I had to go through a similar launch process for each game.  This included testing and fixing bugs, creating the game installers (license agreement, order form, readme file, etc.), preparing the final gold master builds, creating the game sales pages, updating the web site and online database with the new game info, writing and sending out a press release, creating a support FAQ for the game, creating a hints and solutions page (for puzzle games), creating a shipping package for the game (CD, instruction sheet), submitting the game demo to dozens of shareware download sites, soliciting reviews from shareware game reviewers, announcing the game to the newsletter and customer lists, following up on PR inquiries, and so on.  For a simple shareware game, this process normally took several days, even when I had a full-time producer helping me.  It also cost about $2000 for the contractors and services used.  But because I’d created a two-page microtask outline of the whole process, it normally went very smoothly.  I was able to focus on the task at hand and didn’t have to worry about forgetting a key step.

A microtask day – your daily 50

You might find it worthwhile to experiment with planning a whole day in microtask fashion.  If you work about 8 hours a day (hopefully not for an evil bovine master), and your average microtask is 10 minutes, you’ll have a to-do list of about 50 microtasks.  I’ve done this a few times, but in most cases I find that level of granularity to be overkill.  Nevertheless, I encourage you to try this at least one day to see how it works for you.  Be sure to create your daily 50 list the day before you’re going to implement it.  You can use it for just your workday or for your entire day, including personal time.  (Sadly for some of you overworked minions, there isn’t much difference between the two.)

What works best for me is a hybrid approach, blending microtasks with longer tasks on my daily task list.  For example, on today’s to-do list, my morning (9a-noon) has just two tasks:  write this article on microtasks and future-post it for Tuesday (I’m writing this on Monday), and write a second article to future-post for Wednesday.  My afternoon includes mostly microtasks.  Since Erin and I moved recently, I have to update my mailing address with a couple dozen entities, so I have a long list of short phone calls to make.  While I’m doing that, I’ll be multi-tasking.  Whenever I’m on hold, I’ll be filling out various pieces of government and insurance paperwork… in crayon of course.  ;)

Managing complexity

How do I decide whether to break a larger task down into microtasks?  I make this decision based on the task’s perceived complexity.  If the task seems clear enough, and it doesn’t freak me out to put it on my daily list, I’ll add it as-is.  But if it’s new, unfamiliar, or complicated, I’ll break it down into microtasks when I plan my day.  This keeps me from hitting resistance when it’s time for action.  I like my work periods to flow smoothly from one task to the next without having to stop and think so much about what to do next.

Experiment to learn what works best for you.  You may be the kind of person who can put “launch a new web business” on your to-do list and know that you’ll get it done.  I’m not that kind of person.  I hate working in the dark.  I need to see where my actions will lead; otherwise, I’ll hit a snag and end up procrastinating.  A proper plan with the right level of subdivision can be very motivating.  It’s nice to see that if I just follow the steps, I’ll generate the intended result (or at least something close to it).

From intention to action

It’s perfectly fine to set a goal or intention without having a clue as to how it will manifest.  But once you do have a clue, it becomes your job to pull it down into physical form.  You have to meet the cosmos halfway.  If you lack the clarity to take action, then focus on your intentions.  But once those first few steps present themselves, it’s your turn to cooperate with the manifestation process and prove you’re really serious.  Otherwise, those action steps will just keep staring you in the face until you get off your behind and get to work.

A microtask outline is like a recipe.  When you follow a recipe, you’re able to focus on the process of doing without having to worry about how you’re going to do it.  You just need to follow the steps exactly as they’re written.  Similarly, when you create a microtask outline for a project, you separate planning from doing.  This helps the action phase go more smoothly, and it’s easier to slide into a productive flow.  You know that if you follow your outline, you’re going to get a result.  It may not be perfect, but it will get done.


Discuss this post in the Steve Pavlina forum.

© 2007 by Steve Pavlina. If you find these ideas helpful, please leave a donation for Steve so you can enjoy the spirit of giving too.

Download The Journal

Workshop Suggestions

Erin and I have been discussing putting on workshops or seminars here in Las Vegas, based on material from our web sites.  I’d like to share with you some possibilities and invite your feedback, either via the forums (public), my contact form (private to Steve), or Erin’s contact form (private to Erin).

Why workshops?

While we can share many ideas via our blogs, forums, and podcasts, there’s just no substitute for face-to-face contact.  A live workshop is so much more immersive and expressive.  It also gives attendees the opportunity to interact with each other in a way that can’t be done online.

This is especially true for Erin.  In her one-on-one readings, she can only speak to so many clients per week.  Due to increasing demand, she’s had to raise her prices 5-6 times over the past year.  Currently a 20-30 minute phone reading with her is $195, and she continues to receive new referrals and repeat clients.  At that price there are a lot of people who’d very much like a reading but who simply can’t afford one now.  There’s not much we can do about that though, since the pricing is based on simple supply and demand.  For a long time, Erin was booked so far in advance that people had to wait many weeks to get an appointment, and her schedule became rather inflexible.  She’s finally getting caught up, so new clients can book their readings much sooner.  Of course she continues to share freely via her blog and forum posts, but she’d really like a way to connect with more people in person.  Consequently, hosting a workshop holds a lot of appeal to her.

Location?

We’d surely begin with our hometown of Las Vegas.  The city itself is enough of an attraction that people don’t need much of an excuse to visit.  Meeting rooms on the Strip can be a bit pricey, but it’s a great location for anyone coming to town (a few minutes from the airport), and it’s centrally located for anyone who lives here.  The closest hotel to us is the Red Rock Casino, which is about 15 minutes from the Strip.  It’s one of the newest hotels and has a very nice conference center, but I’m not sure going off-Strip is a good idea.

Duration?

I think the workshop should span at least 2-3 days if people are coming from out of town, so they get enough value to make it worth their while.  I’m thinking 3 days would be ideal, perhaps spanning a weekend (Fri-Sun).

How soon?

I’d want to offer at least a few months advance notice, so people would have time to make travel plans.

Speak together or separately?

Since Erin and I cover different topics, it’s not clear whether we should do something together as a couple or host our workshops separately.  Erin gets frequent requests for a workshop on psychic development, but that subject probably wouldn’t appeal to the majority of StevePavlina.com’s visitors.  Similarly, I could speak on topics that might not interest ErinPavlina.com’s core visitors.  Most likely we’ll contribute to each other’s workshops, but we’ll primarily present them individually.  We might also offer back-to-back workshops, so people can choose to attend either one or both on the same trip.

Choice of topics?

It takes considerable effort to put a good workshop together, so choosing the right topic is important.  I’m inclined to do one on “Personal Development for Smart People,” addressing the major topics from this site, including productivity, self-discipline, finding your purpose, problem solving, habits, emotions, relationships, and financial abundance.  It would take a top-down approach to the theme of conscious living and apply it to all parts of your life, first explaining the high-level ideas and then going through practical exercises to apply them in everyday situations.  I find this idea more attractive than doing a very narrow workshop on a topic like self-discipline — I don’t like explaining individual tools without establishing the overall context in which they can be used (i.e. using self-discipline as a tool to enhance your service to others).

Erin’s most requested topic is psychic development.  She easily has enough material to fill a multi-day workshop on developing intuition, meditation, tuning in to spiritual guidance, lucid dreaming, astral projection, and more.

I think these are two very different kinds of workshops, each appealing to different types of people (although with some overlap), so I don’t think it would make sense to blend them together.

However, Erin and I can both contribute to each other’s workshops.  For example, Erin can share ideas for enhancing your intuition to make better decisions and thereby boost productivity.  And I can share my experiences of being totally freaked out every time I visit the astral realms.  :)

Erin and I would greatly appreciate your feedback on this.  Here are some of our biggest questions:

  1. If we host a workshop or seminar in Las Vegas, under what conditions, if any, would you choose to attend?
  2. On a scale of 1-5, how appealing is this idea to you (1 = I’d never go, 5 = I wouldn’t miss it for the world)?
  3. What personal development topics are of greatest interest to you?  What would you want to learn?
  4. In what area(s) of life are you struggling the most (finances, relationships, health, career, etc)?
  5. If you could make only one specific improvement in your life by attending such a workshop, what would it be?
  6. What is your preferred learning style?  Do you prefer highly interactive, experiential workshops with lots of activities?  Or do you prefer more lecture and/or PowerPoint presentation, packing in as much raw content as possible?  Or do you enjoying mixing it up?
  7. How significant a role does pricing play in your decision?  Does $300 for a 3-day workshop seem reasonable to you?  (That price is near the low-end of typical pricing for a 3-day personal development workshop.)
  8. Do you prefer big seminars with hundreds of attendees or a more intimate setting with a few dozen at most?

Please let us know what you think.

P.S. The forum discussion of this post includes a simple poll, so you can vote on question #2 above.


Discuss this post in the Steve Pavlina forum.

© 2007 by Steve Pavlina. If you find these ideas helpful, please leave a donation for Steve so you can enjoy the spirit of giving too.

Download The Journal

Tech Blog by Ezra Hill