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.

Kinkless VoodooPad?

Hello, I'm new here.

I'm also new to GTD, but from everything I've seen, I've been doing it in a modified version to one degree or another, using my head steno pad. I come from a line of list-makers, and it works. Well enough. I've always wanted to digitize the process, but all of my attempts to use basic to-do managers always failed misserably. Someone mentioned GTD Tidy Wiki, and I liked the idea, but didn't know enough about GTD or frankly the setup to make it work right.

One thing lead to another and I stumbled upon 43Folders and what not, and discovered Kinkless. I'd been using OOP for 6 months or more as my primary note-taking/drafting/creation app, and while I liked it, but it required too much meta time to get it to do what I wanted, but I am/was wanted to give kGTD a try, and I've finally gotten it to a point where I work with it. And it finally is both sophisticated enough to take care of most of my concerns (so I really like how automatically files things away appropriatly).

The nature of my projects changed this semester (yeah, I'm an academic/student type), and with the update of VoodooPad (which I somehow missed when it happened). The tabbed browsing/editing and multiple window features really make this the ultimate app for, just about everything that involves text. So I've reverted back to VP, and I currently use it for almost everything.

My question then, is, would it be possible to create (or for that matter are there already) a set of plugins/scripts that one could use to generate the content in VP pages for context specific lists, adgenda views, next action views, and so forth, without needing to footwork the items from one page to another by hand (or by quicksilver, even qs can't argue with automatic)?

If you could do a GTD implementation inside of an existing VP document, you could, then, have actions and projects a and context related lists export to your ipod, or a flash drive, and so forth. As well as having projects and actions automatically (or nearly so) link dirrectly from your GTD data.

I'm a social scientist, not a programer, so about all I can do is stick my finger in my ear and say "gosh wouldn't it be cool, if..." I used to be able to think conceptually in programer, but I don't have any practical suggestions that anyone would find particularly usefull I fear...

Wordtrip's picture

OK, I think I see...

OK, I think I see what you're saying... and I think you're right that I'm making it unnecessarily complicated. I'm trying to figure out how to organize the extra layers of complexity I introduced when I took my current day job 8 months ago.

I think I need to re-work my contexts basically... "Office" "Home Office" that sort of thing, I think I went to much "division of labor" with my contexts instead of actual "where I do the thing" contexts (probably one of the hazards of trying to implement things before finishing the book).

Having not used the script yet (just installed it) I'm grateful for your info on how it looks/works... that it lists what page tasks come from is what will make it easier to organize to...

Thanks again.

solidsnot;7922 wrote:
I don't know if you need to have a specific page for each context as the script will group all of your actions for you per context. If I'm understanding you right, you are using each context as a project? Your context page should just be a list of contexts such as @home, or in your case, @dayjob.

You should then list your projects on separate pages, for example:

Dayjob

Tasks:
@computer Research cat skin hats.
yada yada yada, and so on for each project. When you run the script it will output all of the lines that begin with your list of contexts to the page Actions. So, in our example, Actions would look something like this after you run the script:

Computer
---------------
Dayjob: Research cat skin hats.

If I'm understanding you right then you are unnecessarily complicating things by grouping your projects in sub and sub-sub projects. Just list your projects on their own page and then their actions. Once you run the script and have finished an action then click on the WikiLink for that particular project page and cross out that action. The good thing about this script is that it includes the name of the page from which the action is taken. This should be utilized by creative naming of projects. For example, if I have TakeOverWorld as a project (which is its own page) and I need a sub-project then I would make another page on TakeOverWorld titled TakeOverWorldAcquireNukes, or maybe just AcquireNukes if I could remember that was a subproject. This way when I run the script I can see at a glance from which project each action is coming from.

If I am misunderstanding you then my apologies, but from what I understand if you want to keep track of what projects you are doing under Charles' Work then I would structure my pages like such:

Charles' Work (Main project page)
-Wordtrip.com (Sub realm under "Charles' Work")
--SomeProject (Sub-project under Wordtrip.com)
-Jakender.com
-Dayjob

The contexts should be where you are doing the work, not the project itself.
I know I'm rambling on here but I'm just trying to make myself easy to understand. :)

 
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. »