What makes a good GTD list manager?

Kelly Forrister recently posted her thoughts on what makes a good GTD list Manager. She proposes several requirements and key features to look for in a good GTD list manager:
 
  • Sorting lists by context
  • Ability to assign a due date
  • Portable for on the go access
  • Easily accessible
  • 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.

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.

If you have not read Kelly's excellent blog post, I encourage you to read it: What makes a good GTD List Manager?

The timing couldn't be better for me, as I'm in the process of doing a product analysis and writing copy for eProductivity for Lotus Notes, my own GTD implementation tool for Lotus Notes. 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. I'll post my thoughts here, in a future blog post.

Copyright © 2001, 2002-2018, ICA.COM, Inc. - All Rights Reserved. eProductivity™ and ICA are trademarks or registered trademarks of ICA.COM, Inc.
"GTD®" and "Getting Things Done®" are registered trademarks of the David Allen Company. Lotus® and Lotus Notes® are registered trademarks of IBM Corporation.