Agenda April 10th, 2006

• Tues design meeting
  • discuss format and prep
• Fallows discussion
• Alpha3 planning
• Design list summaries

Tues Design Meeting - Email

• Framing 4 options
  • 1) personal, small group collab (omni outliner on steriods)
  • 2) small group for benefit better than collaboration tools - desktop yahoo groups
  • 3) desktop webmail - gmail on desktop
  • 4) replace desktop email - thunderbird

• ask for other scenarios
• usage scenarios
  • goal of first exercise - understand distinction between them
• talk about the feature list for each scenario
• seed space of features
• existing stickies - katie/grant's list
• cut implementation options
• space for topics that can include implementation

Jim Fallows Discussion

• what message to we want to give?
• good take away
  • understand at some level that there is an approach shift - overlay a framework of semantics to orient the user
  • agenda gave you lists and attributes and hierarchy, one note gives pages, tabs, notes
  • chandler gives you people, sense of time, place, subject, contacts
  • talk about open design process
• uninterested in detail for detail sake
• Sheila will find out if he has downloaded the app or not
• not interested in calendars - interested in pims
• stamping - what feature set it exposes in 0.7 would be a good example
• how far do we get into ecosystem stuff - what works now...what will work in 0.7
• lightweight sharing - calendar, tasks is worth mentioning
• send him some pieces of information specifically of the materials we have
  • BayCHI^? notes and nutshell cartoons page
• do we need something standardized...message
• 0.7 design - what it's going to be - what agenda ideas are we using
• we are not targeting the same user base as agenda - the 5% of users that loved agenda
• do we have concerns about what he could write?
• it would be too bad if Chandler came across as yet another collaboration project - like backpack, basecamp etc
• what are the kinds of concrete things that help people get it
• are there concrete features that illustrate this?
• exchange invitations gave meaning to a subset of communications
• take that and expand so the system understands more
• system out of the box will have that understands
• stamping - easy workflow
• from/to being independent of email to p2p feeling of sharing
• data soup - shared space
• user defined attributes, tagging
• framework within the create your own space - information architecture
• Chandler out of the box structure based on things we have learned - high level symantic structure

Alpha3 planning

• free-busy - punt on views - alternative (defer to alpha 4)
• invitation - separate the from fields, buttons, updated, send by
• dashboard - triage status (sort implications) - sort by explicit ordering
  • having the triage column work will have implications on sorting/sections
  • writing up a proposal before we start alpha 3
• ticklers
• sharing format
• stamping discussions
• calendar stuff
  • bucket #1 - we need to sub prioritize the list

• the sidebar - people being confused about my calendar, checkboxes
• multiple items on multiple calendars
• displaying multiple colors - context - task, recurrence...list of subtleties gets really long
• free-busy views

• next step on performance

• branding - frame requirements
  • Pieter and Ted can identify what buckets will get filled with the plan
  • product name search
  • come up with the list of discrete tasks we need to do
  • plan proposal

Design list

• dogfood email (Sheila)
• summary for design list (Sheila)

-- SheilaMooney - 17 Apr 2006