Personal knowledge management is by nature an idiosyncratic thing, so my ideal ecosystem will be different from others. That being said, I came to the conclusion a while back that omnibus solutions don't work all that well: usually software will do one or two things exceptionally well but is mediocre at other tasks. So I've been gravitating toward mashup solutions that preserve interoperability as much as possible.
Also, I've gravitated toward solutions that leverage mobile tech as much as possible: services that offer mobile interfaces, services that take and send text messages. That's mostly because I'm not working consistently in an office, and I like to check the calendar and set tasks on the fly; your mileage may vary.
So here's the criteria I have for applications:
- Tags. If you're going to work across services, you need to be able to filter everything via the same set of tags (or labels, in Google's terms). Tags allow you to specify project, role, etc. and to bring the same shape to data across services. Currently there's no way to synch tags across services, so I do this by hand, and ruthlessly prune. With a little initial effort, you get unanimity in tags across services. When it works, you can pull everything relevant into the same view. You can also assign the same data to multiple tags, meaning multiple roles and projects -- something that early web-based PM software such as Basecamp wouldn't allow.
- Mobile interface. Mobile interface accessible through a mobile browser, SMS (texting) interface preferred.
- Stability. Got to have uptime; preferably an established brand that will not disappear tomorrow.
- Data portability. Don't want to get trapped in a particular service. When necessary, apps should be able to share. Open APIs.
- Developer community. I don't write applications, but it's nice that others do. So I tend to use services that are supported by large user communities that develop plugins and etc.
- Email: Google Mail. I use GMail's tags (aka labels) extensively, and I like that I can assign colors to tags so I can visually scan through messages as well as filtering by tag. You can set filters to autotag messages. GMail also has a great mobile application if you like to check email via phone.
- Tasks: Remember the Milk, rememberthemilk.com. RTM has a GMail plugin so that you can see email and tasks in the same window. It also has tags. The tags aren't color-coded, but you do get a tag cloud, which is nice for seeing which projects are more fully developed. Mobile interface too.
- Documents, outlines, notes: Google Docs. I collaborate extensively, so the sharing features are great. With Google Gears integration, you can work offline as well, although you might prefer authoring in Word and uploading. Tags are color-coded in the same way as GMail, and I use the same tags and colors across the two. I dump all texts into GDocs that aren't confidential -- notes, ideas, outlines, chapters. I also coordinate complex collaborations in a spreadsheet. An excellent search feature also allows search-as-you-type. Again, the big advantage is tagging, which allows you to filter by project, role, or whatever. Mobile interface too.
- Calendar: Google Calendar. Same as above, plus GCal accepts appointments and sends reminders through text messaging.
- Trip scheduling: I haven't used it yet, but I intend to use TripIt: <http://www.tripit.com/>. The big news is that when you get a trip itinerary emailed to you, you forward it to TripIt and it parses the email, creating a unified view that you can access via mobile and share with individuals or the world. TripIt accepts airport reservations, hotel reservations, etc. and offers granular control so that you don't share everything on the itinerary. If your acquaintances also use the service, TripIt will inform you when you and they are in the same city and for how long.
- Notes. I've been using my blog to think out loud about tech issues and to review books; the book reviews in particular become raw material for my articles and books. The blog's an important part of the ecosystem, but it's not attached to particular projects, so I don't tag blog entries the way I do everything else.
Do you want to discuss your own information ecosystem? Leave your take in the comments.