Tag Archives: GTD

Moving On

[I’m typically not very good at going back to drafts and I don’t have much time to write this. But I can RERO this. It’s an iterative process in any case….]

Been thinking about different things which all relate to the same theme: changing course, seizing opportunities, shifting focus, adapting to new situations, starting over, getting a clean slate… Moving on.

One reason is that I recently decided to end my ethnography podcast. Not that major a decision and rather easy to make. Basically, I had stopped doing it but I had yet to officially end it. I had to make it clear, in my mind, that it’s not part of the things I’m doing, these days. Not that it was a big thing in my life but I had set reminders every month that I had to record a podcast episode. It worked for ten episode (in ten months) but, once I had missed one episode, the reminder was nagging me more than anything else.

In this sense, “moving on” is realistic/pragmatic. Found something similar in Getting Things Done, by David Allen.

It’s also similar to something Larry Lessig called “email bankruptcy,” as a step toward enhanced productivity.

In fact, even financial bankruptcy can relate to this, in some contexts. In Canada, at least, bankruptcy is most adequately described as a solution to a problem, not the problem itself. I’ve known some people who were able to completely rebuild their finances after declaring bankruptcy, sometimes even getting a better credit rating than someone who hadn’t gone bankrupt. I know how strongly some people may react to this concept of bankruptcy (based on principle, resentment, fears, hopes…). It’s an extreme example of what I mean by “moving on.” It goes well with the notion, quite common in North American cultural contexts, that you always deserve a second chance (but that you should do things yourself).

Of course, similar things happen with divorces which, similarly, can often be considered as solutions to a problem rather than the problem itself. No matter how difficult or how bad divorce might be, it’s a way to start over. In some sense, it’s less extreme an example as the bankruptcy one. But it may still generate negative vibes or stir negative emotions.

Because what I’m thinking about has more to do with “turning over a new leaf.” And taking the “leap of faith” which will make you go where you feel more comfortable. I’m especially thinking about all sorts of cases of people who decided to make radical changes in their professional or personal lives, often leaving a lot behind. Whether they were forced to implement such changes or decided to jump because they simply wanted to, all of the cases I remember have had positive outcomes.

It reminds me of a good friend of mine with whom I went through music school, in college. When he finished college, he decided to follow the music path and registered for the conservatory. But, pretty quickly, he realized that it wasn’t for him. Even though he had been intensely “in music” for several years, with days of entering the conservatory, he saw that music wasn’t to remain the central focus of his career. Through a conversation with a high school friend (who later became his wife and the mother of his children), he found out that it wasn’t too late for him to register for university courses. He had been thinking about phys. ed., and thought it might be a nice opportunity to try that path. He’s been a phys. ed. teacher for a number of years. We had lunch together last year and he seems very happy with his career choice. He also sounds like a very dedicated and effective phys. ed. teacher.

In my last podcast episode, I mentioned a few things about my views of this “change of course.” Including what has become something of an expression, for me: “Done with fish.” Comes from the movie Adaptation. The quote is found here (preceded by a bit of profanity). Basically, John Laroche, who was passionately dedicated to fish, decided to completely avoid anything having to do with fish. I can relate to this at some rather deep level.

I’m also thinking about the negative consequences of “sticking with” something which isn’t working, shifting too late or too quickly, implementing changes in inappropriate ways. Plenty of examples there. Most of the ones which come to my mind have to do with business settings. One which would require quite a bit of “explaining” is my perception of Google’s strategy with Wave. Put briefly (with the hope of revisiting this issue), I think Google made bad decisions with Wave, including killing it both too late and too early (no, I don’t see this as a contradiction; but I don’t have time to explain it). They also, I feel, botched a few transitions, in this. And, more importantly, I’d say that they failed to adapt the product to what was needed.

And the trigger for several of my reflections on this “moving on” idea have to do with this kind of adaptation (fun that the movie of that name should be involved, eh?). Twitter could be an inspiration, in this case. Not only did they, like Flickr, start through a switch away from another project, but Twitter was able to transform users’ habits into the basis for some key features. Hashtags and “@replies” are well-known examples. But you could even say that most of the things they’ve been announcing have been related to the way people use their tools.

So, in a way, it’s about the balance between vision and responsiveness. Vision is often discussed and it sounds to some people as a key thing in any “task-based group (from a team to a corporation). But the way a team can switch from one project to the next based on feedback (from users or other stakeholders) seems underrated. Although, there is some talk about the “startup mentality” in many contexts, including Google and Apple. Words which fit this semantic field include: “agile,” “flexible,” “pivot,” “lean,” and “nimble” (the latter word seemed to increase in currency after being used by Barack Obama in a speech).

Anyhoo… Gotta go.

But, just before I go: I am moving on with some things (including my podfade but also a shift away from homebrewing). But the key things in my life are very stable, especially my sentimental life.


Back in Mac: GTD Edition

Catherine got a MacBook (Combo Drive) last week. Though it’s her computer, I’ve been using it pretty extensively in the past few days. And it’s changing my life for the better.

Long story short. My iBook (Dual USB) from 2001 went kaput in December 2005. In a hurry to get a new computer and being a bit short on cash, I ended up a few weeks later with a refurbished eMachines desktop running XP. Though my original dissatisfaction with the machine probably had to do with the lack of RAM, I still thought fondly of my Mac OS X days and was longing for the day I could use a Mac again. Now that I can, I know why I missed Mac OS X so much.

At this point, I come to think that those people who love XP machines are those who like to play fast-paced games and/or to pirate software. I love computers for other reasons so these don’t apply to me.

Contrary to what is said in the Justin Long and John Hodgman ads, I tend to see Mac OS X as a way to get things done.

Yes, Getting Things Done is the title of a best-selling book by David Allen and has become a buzzphrase in recent years. I was indirectly influenced by some ideas from the book but I prefer to use my own methods of time-management. Still, I can easily associate the Mac with GTD the concept, if not GTD the book (which I haven’t had the time to read).

This past weekend, I read a “Final Assessment” on a Mac OS X application called iGTD. It’s a rather straightforward tool for managing tasks. Kind of a “to-do list on steroids.”

I tried iGTD for a few minutes last night. Neat app and it might end up being useful. I’ll give it more thought as time goes on but as I need to switch between different computers, I don’t think it’ll become my ultimate solution.

Trying iGTD was also a chance for me to try QuickSilver again, after all this time spent on an XP machine. I really like QS and I can really see how it fits in the GTD frame. It’s a convenient way to accomplish a large number of tasks very efficiently. It’s not the fact that it saves you a few seconds at a time which matters. It’s the fact that it makes it easy to not think about what you want to accomplish. Kind of what the QuickSilver people call “Wei Wu Wei – Act Without Doing.” QS is really a Mac OS X thing. It only works on Macs and it really fits in the Mac-based methodology for computer use.

Another example of Mac OS X apps to get things done: OmniOutliner. This is probably the single app which I most missed on XP. Sure, there are outliners on XP. But none of them made my workflow as smooth as OO did. I tried NetManage EccoPro and eventually abandoned it. EccoPro is very powerful and it was an ok replacement for the actual outlining functions but the fact that it hasn’t been developed in ages means that it lacks the kind of features which really make things go smoothly.  In other words, EccoPro is not that compatible with the Mac way of just doing things.

Things are so easy in my OO workflow! For instance, while preparing for courses, I would use OO to take rough notes while reading course material. (Actually, I took many of these notes on a PalmOS device to transfer to OO. That part was never so seamless and I tried everything to improve it but it was a vain attempt. Transferring from Palm to EccoPro is a bit simpler.) In OO, transforming raw notes into course outlines was extremely easy and efficient. I could then easily transform those outlines into printable lesson plans and slides using LaTeX, Keynote, PowerPoint, or RTF. All told, I could transform rough notes into course material in less than 10 minutes without thinking much about what I was doing. Made everything so easy that it really took me a while to adapt my workflow to XP. In fact, I can’t say I ever did. Sure, XP people will say that I could in fact do the same thing thing on XP, that I’m just an Apple fanboy. The fact that the PalmOS integration with OS X wasn’t so smooth seems to prove that point. But the key point here is not about my ability to do things. It’s about the flow part of workflow. Every method I used on XP to accomplish the same tasks eventually worked and I became quite good at them. I probably ended up spending just a few minutes more on any of these tasks. But nothing was really smooth. I could never be mindless about the process. I constantly had to make sure everything was working.

As it turns out OO also fits in the GTD frame. In fact, the first time I heard of GTD was probably on the OO user mailing-list. Some people there wanted the ultimate GTD solution based on OO. OO didn’t have a lot of GTD-savvy features but it seems that it could fit in the GTD methodology overall.

One step further, I think Mac OS X as a whole fits in the GTD frame.

But I probably will never jump on the GTD bandwagon. AFAICT, GTD is mostly based on sorting tasks and tracking them. Again, “to-do list on steroids.” But, contrary to my mother and to my wife, I’m usually no good with to-do lists. I keep accumulating stuff in them and end up more frustrating. Centralized systems work better for me so I do a lot on Gmail. Those who don’t know me extremely well certainly think that I’m completely disorganized. But I’ve found ways to organize myself through apparent chaos. In short, I’m messy and I’m proud of it. But I do respond to the very concept of “just getting things done already” which seems to be associated with GTD-friendly applications. In this case: iGTD, QS, OO, and… Mac OS X.

It sure is good to be back in Mac!