Friend and colleague, Kelly Forrister, recently posted her thoughts on what makes a good GTD list Manager.
I think Kelly's done a great job of defining the key requirements of a good GTD list manager. She proposes several key features to look for:
Sorting lists by context
Ability to assign a due date
Portable for on the go access
More attractive to you than repelling
Doesn't force priority codes
Place to capture additional notes
Ability to search and sort in various ways.
Robust enough to handle all of your stuff.
The timing couldn't be better for me, as I'm in the process of doing a market analysis and writing copy for eProductivity for Lotus Notes, my own GTD implementation tool for Lotus Notes. I think Kelly's list serves as a good foundation of the core features that any sound GTD implementation tool, whether low-tech (e.g. paper) or high tech (e.g. Lotus Notes) should offer.
In addition to my own criteria, I plan to run vanilla Notes and eProductivity for Lotus Notes through Kelly criteria and see how they fare. Might make for an interesting discussion. I'll blog my thoughts over on NotesOnProductivity.
GTD Times recently (and quietly) launched. I've been asked to be a guest contributor; I'll be in great company.
This is a GTD Community planned in part by my late friend Marc Orchant. Marc and I had spoken about this project and I'm delighted to see it continue on, if nothing else as a tribute to a topic he was so passionate about. - GTD. GTD Times is now in the capable hands of his friend, Oliver Starr.
GTD Times promises to become the premier go to site for all things GTD, and I'm excited to be a part of the community.
I'll start contributing to GTD Times, shortly. (I'll still be blogging here,too.)
I'm honored to be a part of the GTD Times team.
You can read Oliver's welcome and introduction, here.
Behind the scenes, things remain busy as we work with clients that are currently getting things done with Lotus Notes and eProductivity using David Allen's GTD methodology.
At the end of last year, we completed the eProductivity beta program, and at the end of this month, we will wrap up a four-month eProductivity workgroup pilot program. We are now getting ready to turn on the web site so that the world can see what we've been up to. We still have some work to do on promotional materials, strategic partner relationships and training people to become future eProductivity coaches to support enterprise deployments.
I've decided to make eProductivity available both as purchased or subscription software so that users may choose the option that will serve them best. I'm going to need a bunch of people to test the new license activation system, if you'd like to help and (get a free preview of eProductivity at the same time), contact me.
I've just posted the next installment in my series about how to ramp up quickly with GTD. In today's segment I share about the most important aspect of the eProductivity equation and that is: methodology.
To learn more about my Knowledge Worker Productivity equation and to join an ongoing discussion about the GTD methodology as an aspect of knowledge worker productivity visit the Notes on Productivity Blog.
Last week, an executive at a large global consulting firm with over 100K Lotus Notes users called me to ask for help getting up to speed with GTD and Notes. He told me that he was feeling overwhelmed at work with a growing number of projects and responsibilities and in his pursuit of a solution he had found and read David Allen's book, Getting Things Done. He was also aware that while Lotus Notes is an excellent tool for messaging, collaboration, and information management, it wasn't supporting him in the way that he needed. He was calling to get eProductivity for Lotus Notes and some coaching to help him set up Notes to be more productive. After a fruitful conversation, and my promise to help him, he asked me, "How can I ramp up quickly with GTD & Lotus Notes?" Continue Reading ""How can I ramp up quickly with GTD & Lotus Notes?"" »
Zig Ziglar tells a story of how for 40 years of his life he chose to be fat. That's right. You see, according to Ziglar, he never accidentally ate anything.
Last year, I realized that when it comes to the internet (among other things) I was choosing to be fat. I was consuming more Internet calories than I needed and it wasn't even the good stuff. Worse yet, like junk food, the Internet -- the very tool that had enabled my high-tech lifestyle -- was distracting me from getting things done. So, at the beginning of 2008, I decided to reduce my daily internet intake in order to improve my productivity.
What I expected to be a one-month experiment turned into a 3-month adventure and I learned a lot along the way...
In the past 6 weeks, much as been written about these papers, both praising and challenging Michael's collaboration report card. Rather than get into that discussion, I'd like to tell you a little about the 7 Pillars of collaboration model and why I think it's a valuable tool to evaluate any collaboration tool, whether it's SharePoint, Lotus Notes, or a cloud computing application. Then, I'll provide some links where you can learn more about SharePoint and how it rates according to Sampson's 7 Pillars of Collaboration model.