Mark Forster

> How do you envision you’ll work through all of the captured notes? Do it all at the end of the day?

Not entirely sure yet. My current setup involves an Apple shortcut that sends a text blob to my email inbox with the subject "Note to self", where I have a filter set up to send emails with that subject line to a specific folder.

Once the notes are in my inbox, I go through them whenever I get around to clearing my other emails, and I parse each item into my action planner. For that, I'm currently using Mark Forster's "Resistance Zero"[0] system to moderate success, but I've been experimenting with other ways of tracking and actioning my to-dos.

Given the software is open source, I plan to try and hack something together that automatically routes my voice notes as plaintext to that same email filter.

I try to adopt the Unix philosophy when assembling my personal productivity workflow. To that end, I consider this device a composable "quick capture" tool, and nothing more.

> Recording the thought or idea is the easy part, but it only defers the action.

I find that this is very untrue for me.

The tiny bits of friction with other quick-capture systems I've tried add up to a substantial "loss factor" over time. If I use pen/paper, I need to ensure I have my notepad and pen on me at all times. If I use my phone, I also need to have it on me at all times, and then also manage to avoid getting distracted by social media. Either action requires fumbling around with a physical…

Very interesting. When I need to make myself work on something (which creates a new problem: deciding to force yourself to do something) I have 2 main techniques (I just realized you could probably do both methods together.)

Method 1. Incrementing time boxes (the first step is similar to yours actually). Set a timer for 1 minute and do it for one minute. Then 2 minutes, then 3, and so on. (At some point you'll be working on it and forget about the timer, and that's ok.) (Credit to Mark Forster[1] and/or Khatzumoto[2] for that idea.

[1] I believe it's in his "Get Everything Done" book as mentioned here http://markforster.squarespace.com/forum/post/2713432

[2] http://www.alljapaneseallthetime.com/blog/timeboxing-trilogy-part-5-incremental-timeboxing-and-mixed-timeboxing/

Method 2. Start with a blank piece of paper (or text file). Write down the goal. In outline form, indent and write the first thing needed to do that. If needed, indent again and write down the first thing to do that, and so on, until you have something to start on. Note that I'm not talking about outlining and planning the project, just the first step (of the first step, ...). A great benefit is it helps you focus on deciding where to start, breaks it down to something small enough to start on, and it keeps track of where you are in the process, what you're trying to do. I guess it helps with working memory (which helps with executive function). Proceed to work on the project indenting and un-indenting as…

Wow. What I haven't tried before... One html file wiki (tiddlywiki i think). Something like 3 self written web task editors before DropBox happened. Mori (kind of evernote from the past), Google Wave (still missing it), made couple of money tracking apps with couchdb, remotestorage and other offline capable but syncing apps for personal use on mobile.

Currently

Notes:
Plain text notes with markdown elements synced via DropBox edited in NvAlt on Mac, and Notesy on iOS.

Sketches:
Moleskine notebooks of various sizes (mostly Reporter). Currently experimenting with even smaller ones (Cahier journals)

Visual References:
After years of screenshots on my desktop and reference folders full of unnamed images I made lightweight pinterest clone https://github.com/vorg/kollektor

Articles:
Pocket as 'todo readme' solution but currently working on and app for hyperlinking pdf's for computer graphics papers.

ToDo:
Gave up on per project hierarchical task list as they always get old and dusty. So instead I split information into long living stuff and references (links, project requirements, hardware specs etc) that goes into notes. And one task list for MIT (most important tasks) daily similar to Autofocus system (Autofocus system - http://markforster.squarespace.com/blog/2009/1/6/autofocus-system-instructions.html?printerFriendly=true) + smaller ones for bug lists per project, TaskPaper for Mac, and TaskMator / Listacular for iOS. I even wrote custom editor for TaskPaper notes…

I used GTD religiously for a while, but I ran into the same issue of having difficulty deciding what to do right now. After trying a bunch of different approaches to how to set up 'contexts', I eventually came across Mark Forster's 'AutoFocus', which after a bunch of adjustments turned into this:

http://markforster.squarespace.com/blog/2015/5/21/the-final-version-perfected-fvp.html

Key paragraph that explains why this worked better for me than GTD did:

> There are three main requirements which have to be kept in balance. These are urgency, importance and psychological readiness. Traditional time management systems have tended to concentrate on the first two of these. The neglect of psychological readiness is probably the reason that most people don’t find time management systems particularly effective or congenial.The most distinctive feature of FVP is the way that its algorithm is primarily based on psychological readiness - this then opens the way to keeping urgency and importance in the best achievable balance.

I still use a rudimentary GTD approach for collecting stuff (various inboxes) and keeping track of a project as a whole, but I've so far this 'AutoFocus' (or rather the unfortunately named 'Final Version') approach has been the only one that didn't fall apart quickly.

Just my testimonial for the book The Now Habit.

I found it on the library shelf at work. Was skeptical but interested. Borrowed it. Loved it. Told people. Endured their jokes about how long I would take to finish reading it, if ever.

Started using some of its exercises and remedies. Ran out of renewals. Returned it to work. Wanted a hardcover but couldn't find one. Bought it from the Kindle store instead.

Just finished reading it. Am beginning to read it again so I can apply the bits that I haven't yet.

One more thing, given this book you should consider to avoid losing your focus by spending endless time with additional productivity literature, but for my part I use a couple of simple things with it: Mark Forster "Final Version" lists (http://markforster.squarespace.com) and Pomodoro Technique (http://www.pomodorotechnique.com). Final Version leads me to select the task for which I feel the most resistance and tension as the task that I will address (not necessarily complete!) next. The Pomodoro Technique helps me to do what The Now Habit calls "persistent starting": get started, and no matter how many times I get into a slump or come back from a break, just get started again.

I read the FVP post [1]...I'm slightly incredulous: it's just a list. That you scan and pick things from. I'm not sure if I should be impressed or underwhelmed at the simplicity.

There are no categories, no contexts, no markers, no due dates...

I'm not sure what makes this is a "system". What's odd is that the author seems to have had previous incarnations/systems, that were actually more complex, e.g. had separate lists with review periods, curation, etc., but he seems to have evolved (which I really appreciate continual improvement) to "fuck it, just use one list".

I know I'm committing an error of logic, but his FVP stats seem to indicate he's basically retired/in a low stress environment [2], so perhaps all the regalia of GTD (which fwiw I don't practice) are more applicable in the corporate environments that spawned it.

However, if it works for you, that's great. It's been awhile since I've poked around in the "productivity system" space. Interesting stuff.

[1]: http://markforster.squarespace.com/blog/2015/5/21/the-final-version-perfected-fvp.html

[2]: http://markforster.squarespace.com/blog/2015/5/27/a-day-with-fvp.html