r2 - 16 Aug 2006 - 09:41:44 - MimiYinYou are here: OSAF >  Journal Web  >  MimiYin > KnownDesignIssuesAlphaFourDashboard

KNOWN ISSUES FOR DASHBOARD USABILITY

Do we need to consider providing flavors of Kinds:

Tasks
  • Projects
  • Waiting fors
  • Calls
  • Follow-up

Communications

  • Messages (FROM and TO)
  • Follow up with ... (the moral equivalent of David Allen's @Person agenda lists)

Events

  • Meetings (Start date/time, End date/time)
  • Flights (Separate timezones for Start date/time and End date/time)
  • Anniversaries (Mark Event status: FYI, No End date/time)
  • Holidays (Mark Event status: FYI, No End date/time)

Explicitly click a button to Update items for further communication

  • Otherwise all edits are just treated as personal annotations
  • OR, we can get rid of Update-Draft status for now

Should we implement dumb clusters?

  • Detect email threads through message IDs
  • Not allow people to create their own clusters or edit them

What if I edit and update to tell you that I'm DONE with something?

  • Currently, according to the stamping spec, when you receive an Update, the item is re-triaged as NOW.
  • Can we have it show up at the top of the NOW section, but have it still be marked as DONE? The item gets filed into the DONE section when the user manually clicks 'Purge'.

Additional auto-triaging?

  • Sent items = DONE
  • Read items = DONE
  • Past events = DONE
  • Future events = LATER
  • User-definable auto-triaging
  • Can only be done if we have the Purge workflow

Other known issues

  1. Too many new items flowing into the NOW section.
  2. The date column needs to be smarter (e.g. Tickler date reverting back to the Event date once the Tickler has been fired.
  3. Better visual cues to differentiate between Created/Last modified/Date received and Event/Tickler dates.
  4. Showing Event dates as durations (e.g. 2-4PM)
  5. Having recurring Ticklers
  6. Displaying more than 1 line of text in the table
  7. Need for clusters and hierarchy (a la Omni-Outliner) (aka custom sections)
  8. Private and Public Per-User Annotations for Triage status, Stamps, Event status, Alarms, Notes field, Labels
e.g. The PPD team shares a collection. Sheila is assigned the task to write-up a summary of the Email discussions on the design list. This item is a task to her. But when she sends it out, she doesn't want to send it out as a Task. How does she keep track of the item as a personal task, yet share it with the group as a Communication?
  1. Lack of ability to customize columns in the table with user-defined attributes

-- MimiYin - 16 Aug 2006

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r2 < r1 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.