43 Folders

Back to Work

Merlin’s weekly podcast with Dan Benjamin. We talk about creativity, independence, and making things you love.

Join us via RSS, iTunes, or at 5by5.tv.

”What’s 43 Folders?”
43Folders.com is Merlin Mann’s website about finding the time and attention to do your best creative work.

Projects, contexts and consolidated actions

Greetings and Felicitations:

How do you handle a collection of projects that share an action that can/should be consolidated into a single action?

For example, I've three different projects: Hang quilt on wall, Fix ceiling fan at Mom's, Replace refrigerator at Grandmothers. Each involves the action "phone handyman and arrange time to X", where X is different for each project.

If there were just one action, the context would naturally be phone. With two or more such actions, the natural impulse is to want to consolidate them into a single action. Different projects can't "share" a single action or sub-projects, and there is no natural or sensible refactoring of the projects that will make them part of a single project. Likewise, creating a context to capture these actions that all involve the handyman doesn't seem a proper use of contexts. (For example, a context "People/Handyman", in addition to being ephemeral, implies an action "contact handyman", since my cross-section with the handyman is zero unless I go out-of-my-way to contact him.)

One possibility, suggested by the rule of thumb "there is no problem that can't be solved with a level of indirection" is to create a "Handyman List", and make two actions in each project, "Put X on handyman List" and "Contact Handyman and arrange to complete items on Handyman List". This has the apparent weakness that one might not think of an upcoming "Handyman List" action and so end-up calling the handyman several times over the course of several days instead of waiting several days and calling the handyman once (though this might not be a problem if one were properly religious about the weekly review.)

How have you handled similar situations? What do you think of this approach? Have other suggestions for handling this or similar situations?

mwr's picture

Re: Projects, contexts and consolidated actions

I may misunderstand, but if you have a Phone context or list, wouldn't it contain the following next actions (among other items):

  • Call Handyman at 555-5555 to arrange appointment for X.
  • Call Handyman at 555-5555 to arrange appointment for Y.
  • Call Handyman at 555-5555 to arrange appointment for Z.

The next time you look at your phone list, if you look over the entire thing before deciding which calls to make, you'd either call Handyman and set up appointments for X, Y, and Z at once, or edit the items down to one next action:

  • Call Handyman at 555-5555 to arrange appointment for X, Y, and Z.

This may miss the point, since I'm basically advocating moving the process you fear missing in the weekly review into a process on the working lists themselves.

 
EXPLORE 43Folders THE GOOD STUFF

Popular
Today

Popular
Classics

An Oblique Strategy:
Honor thy error as a hidden intention


STAY IN THE LOOP:

Subscribe with Google Reader

Subscribe on Netvibes

Add to Technorati Favorites

Subscribe on Pageflakes

Add RSS feed

The Podcast Feed

Cranking

Merlin used to crank. He’s not cranking any more.

This is an essay about family, priorities, and Shakey’s Pizza, and it’s probably the best thing he’s written. »

Scared Shitless

Merlin’s scared. You’re scared. Everybody is scared.

This is the video of Merlin’s keynote at Webstock 2011. The one where he cried. You should watch it. »