Ideas for more brainstorming/design sessions:

How would you mark-up your items? What other semantics/attributes would you add to your information to help you: 1) Find it later and 2) Group the right information together, so you can draw it up as a list later on.

• What do I need to do today?
• I'm at the hardware store, what are all the things I need to get?
• What's the status of this project?
• What's interesting to read across all these mailing lists I subscribe to?

Now, can we cluster all of these attributes into high-level conceptual groupings?

Then, can we do an orthogonal grouping exercise and bucketize these attributes into 4 levels of use

...where each subsequent level of use requires a little more effort on the user's part to find the attribute. (ie. hiding things in context menus.) What are the most important ways to mark-up items? What are some less important, more specialized semantics that only advanced users interested in highly accurate information management systems would bother with? How can we build a shallow ramp to help users get from one end of the spectrum to the other?

• Level 1: Primary way items are organized in the Dashboard view
• Level 2: Mark-up bar affordances
• Level 3: Attribute in detail view
• Level 4: Attribute user has to add

What are some usage scenarios for collaborative managing tasks or Web 2.0 personal information?

Some examples include:

• Apps team swagging
• Mitch and Esther sharing tasks
• Managing the non-code deliverables tasks
• Collaboratively managing delicious bookmarks for a group research effort
• Collaboratively managing the Design mailing list to help focus conversations

What are some different ways to implement David Allen's notion of Altitudes of Information Management in Chandler? ie. Runway view v. 10,000 foot view v. 20,000 foot view

• How will this system be different in Chandler?
• How will this system be better in Chandler?
• How will this system be not-as-good in Chandler?