Triage Workflow Framework

• Dashboard_CSG.ppt:
• Dashboard_CSG.pdf:

Notes from discussion after the presentation

• Observation: WHO is a significant facet.
  • Idea: It would be great if we could have faces to represent WHO, and be able to create attributes/relationships by dragging the faces, or dragging the faces into places.

• Observation: Tasks yield other tasks, if so they become a PROJECT

• Idea: A task in a table, the next few rows display indented (or some other special way) and list the items "related" to this item (the item is an attributeValue).

• Observation: Hard to find a task the right size for a given time period.
  • Idea: View that makes it easy to look at 100 things and pick out one that is the appropriate size/scope/context/etc.

• Observation: More metadata you have to enter, the more you'll resist doing it, an obstacle.
  • Idea: Make application smart so that it enters metadata automatically.
  • Observation: If you knew how the data might be used, you would be more willing to enter the data.

• Idea: templates for tasks: for a particular kind of task, the user just cares about certain types of metadata.

• Q: Has anyone used Picassa?
  • Observation: Picassa tray is an adhoc temporary collection.
  • Idea: Would be cool if Chandler had a tray for information the user wants to have accessible and handy.
  • Idea: have operations that only affect the tray.

• Observation: Stamping works for one off, but can't be a tool for associating a lot of emails with a task.
• Observation: Stamping is the first step in the workflow, and we don't give the tools for the steps for more advanced steps, not for 1.0.

Next steps:

• Jeffrey to write up tray idea
• Apps/design meeting to tackle dashboard, follow our usual process to figure out how to apply the ideas to something we can accomplish in 0.7.

Comment from Mitch: Many ideas go back to original vision of the project. New: design organization is attempting to flesh out a fuller narrative: Use cases, workflows, principles. Dedicated high level design attention to these issues. Purposes of these meetings: socialize ideas with developers. Improve the ideas and to get buy in.