| http://wiki.osafoundation.org/bin/view/Journal/DashboardUserBrainstorm20060207 Meetings + Summary for today's Design Session on 0.7 Target Users for Plausible Dashboard
We interviewed 3 potential user groups: + Apps team Architecture Issues tracking + Mitch and Esther task tracking + Ted + Family household tasks
Below are Takeaways and Next actions. (Anyone who attended, please feel free to add your own.) Go to wiki page for a blow-by-blow. Thank you Sheila for taking notes!
Mimi
Takeaways - Tactile aspect of paper is hard to compete with. But ability to manage information collaboratively might make it worth it for some people who are currently stuck on paper. Reliability of paper or unreliability of computers is a big factor for some people.
- Paper interfaces and free-form lists (ie. Wiki, Omni-outliner) are better for fuzzy, vague projects (in the Black Box stage of a task's lifecycle).
- Electronic calendars and Bugzilla are better for recording discrete, well-defined information items (ie. scheduled appointments/meetings where you've made an
- There's a need for top-down planning (ie. Apps team Architecture Issues page) as well as bottom-up tracking of detailed tasks.
- Detailed tasks (ie. Bugzilla, Esther's day-by-day progress on mini-projects) grow out of big, fuzzy projects and are an indication of progress on those projects.
- Keeping people up-to-date on status is a major challenge and requires both a lot of face-to-face communication and email.
- The process of getting organized helps people make progress on their tasks/projects.
Design challenges for Chandler - How do we connect the dots for users between top-down project planning and detailed tasks
- How do we keep everyone involved engaged and focused on the right tasks and issues
- How do we keep different views of shared information in sync (ie. Apps team Architecture page and related Bugzilla bugs and mailing list discussions)
Next actions - Approach LPFI, Creative Commons and Berkeley for more interview subjects
- Follow up design sessions to try and map out these usage scenarios using Plausible Dashboard in 0.7
On Feb 6, 2006, at 4:30 PM, Mimi Yin wrote: This is a Reminder for tomorrow's Design Session in Whoville from 2:15-3:45.
We've narrowed the list of scenarios down to 3-4: + Family and/or Couple + Design mailing list + Mitch and Esther sharing tasks (Esther I hope you can make it!) + Working group task management (Any OSAF working group)
For those of you considering participating as an interview subject in any of these scenarios, here are some questions to ponder in the mean time: - What kinds of things do you keep track of together?
- ie. Tasks, Chores, Errands, Appointments, Lists
- How do you keep track of these things today? How do you make sure they get taken care of ?
- How do you keep communicate these things to each other today?
- How might you categorize these things? Into projects? By owner?
Thx!
Mimi
On Feb 3, 2006, at 9:39 AM, Mimi Yin wrote: Next Tuesday in Whoville from 2:15-3:45.
Now it's time to start interviewing people and groups and nailing down specific workflow requirements.
I'd like to kick-off the user interview process with a group interview that everyone and anyone who is interested can attend to either participate as an interviewee or observe.
Here are some nominees, please feel free to nominate yourself, and/or a group to be guinea pigs as well :o)
+ OSAF + Community: Design and Dev Mailing list management
+ KEI: Tracking progress on post-Al Gore talk action items and resources (still need to talk to the right people about this. I'd like to explore a number of different usage scenarios for LPFI and Creative Commons.)
+ Mitch and Esther: Shared task tracking
+ A couple: Shared household task tracking (Does anyone want to volunteer for this?)
Mimi _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list http://lists.osafoundation.org/mailman/listinfo/design
|
