Design Meeting - Jan 9th 2006

Agenda

Notes

Design Lists

• should we consoladate Chandler, Cosmo, Scooby design discussions - yes
• current lists
  • cosmo - like dev list
  • scooby - like dev list
  • dev - we could change this to chandler but will probably leave it at now
  • design - should use this for all projects - use tags
• design list tagging
  • [Sc,Cos,Ch][project] - scooby, cosmo, chandler
  • [B][brainstorm]
  • [d/f][F/B][feedback] [dogfood]
  • [Sum][summary]
  • [Resch][fyi][research]
  • [release vs bluesky]
  • can we do abbreviations - shortcuts

Summarizing info on design lists

• weekly friday summary - sent by Sheila (content from Mimi and Priscilla)
• one email for all projects consolidating design issues and next steps.

0.7 tenets

• should center stuff around a target user
• we will probably have a different target user for each tenet

Brainstorm of all design projects

Chandler

• Target user for 0.7 for each tenet
• Tenets : drilling down on concrete goals
  • scheduling
  • dashboard/tasks
  • modular APIs
  • end user testing support

• Process for decision on which bugs are in for 0.7
• Process for high priority fixes

• Design for 0.7
  • content model
  • dashboard
  • detail view/markup bar
  • context menus
  • preferences
  • calendar navigation
  • sidebar issues
  • preview area of minical
  • timezone issue
  • calendar palettes
  • sharing and autosynching

• Extensibility plan for 1.0
  • presentation pending

Scooby

• 0.1: final planning page
  • release tenets
  • target user/goals
  • wireframes/prototype?
  • what release is that?
  • some initial demo - what is that called?

• Vision document ?
• 1.0 target user?
• Strategy?
• Roadmap?

Cosmo & Hosted Service

• What is the vision/strategy for service?
• 0.3 plan and goals
• 0.3 design tasks?
  • login/admin tools design
  • browsing

• Product roadmap?
• Feature roadmap?
• Vision/strategy for cosmo?

System

• Personas for 1.0
• System strategy and vision?
• Roadmap
• Target user
• 1.0 use cases
• Decide on features
• Assemble a group to discuss - Mitch, Lisa, BCM, Bkirsch, design team

Wiki Website/Communication

• Virtuality paper
  • IA summit
  • CHI paper

• Fix vision paper - white paper for someone that knows nothing about the project can download and read
• Nutshell write up
• Weekly summary of design discussions
• Writeup of design process
• Dogfood processing and communication
• Release metrics
  • jared executes
  • ted input
• Process bugs, problems
  • labelling bugs in bugzilla
  • decision about which ones fixed in 0.7 process
  • prioritize bugs/problems feedback:when?

Problems/Issues

• How do we get more representative feedback?
• Should we use scripted workflows?
• Who is the target user?
• How do we incorporate people who show up on the list?