Hi,
I've started a list of:
1. Candidate list of workflows and features we need user
documentation for.
2. A list of scenarios to sketch out in screencast demos.
and now I'm collecting feedback: What am I missing? What's overkill?
UI we need HOW-TOs for:
GETTING STARTED
+ Importing and Exporting calendar data in and out of Chandler from
Outlook, Palm, iCal, Entourage, Ecco Pro, Evolution, Sunbird?
+ Email and Sharing Account setup
+ Pulling down email with special Chandler headers
+ Setting up special Chandler IMAP folders
STAYING STRONG
+ Dump and Reload: Migrating between versions of Chandler desktop
EVERYDAY WORKFLOWS
+ End-to-End Sharing workflows: Publishing and Subscribing with
Chandler and Cosmo
+ How Edit/Update works
+ How Mine/Not-mine works
USAGE SCENARIOS and WORKFLOWS for Screencasts
The more I think about building screencasts around real user use
cases and workflows, the more I like it. I think it can prove to be a
really powerful, subtle way to communicate Chandler's target users to
people who come by to check out Preview. Instead of showcasing
features, we'll be showcasing real use cases, which will be a much
more concrete way for users to 'get' how they might use the app in
the Preview timeframe. Ideally, the workflows prompt viewers to ask
themselves, 'Do I do these kinds of things?'...which I think is a
much more compelling and useful than showing people a list of
features which they may or may not figure out uses for.
Question: Should we base the screencasts on real people and real
usage scenarios from our interviews?
The scenarios below need some fine-tuning, but here's a high-level
description to give you a sense of what they might look like. (e.g.
The scenarios below don't get into nitty-gritty issues like
recurrence, conflict management and time zones.)
Scheduling
Personal Scheduling
+ Helen overlays her Work and Home calendars to schedule a dinner party
+ Helen then overlays her husband's calendar to narrow the available
times
+ Helen sends out a message to friends with a list of 3-4 times and
questions about people's food preferences.
+ After receiving many replies in her regular email client, Helen
drags the final email she sends out confirming date, time, place and
menu to her special Chandler events IMAP folder.
+ The email, stamped as an event shows up in her Chandler and she
adds it to her Home calendar, which she shares with her spouse.
Workgroup Scheduling
+ Helen overlays her own Work calendar with Angie's calendar and
another Hub's calendar to figure out a good time for a half-day
management offsite.
+ Helen sends out an email proposing a few good times...etc
Triaging/Dashboard
Helen's personal Dashboard
+ Iterating on a task to write-up a Proposal for Angie to launch a
new Project
+ We could work this scenario into the 'Collaborating on an item'
with Bart scenario below.
Collaborating on an item
+ Helen and Bart go round and round on an email framing a project
launch mtg
- Who should be included in the email?
- Who should provide input on the email?
- How do we frame the project?
- What is the goal of the mtg?
- What are the agenda items?
+ Helen sends out a first pass
+ Bart adds comments
+ Others get looped in via Email and reply with their comments
+ Final draft gets sent out to entire working group
+ All the while, the draft cycles in and out of Helen and Bart's
shared Project collection NOW section
Heavy collaboration via Cosmo: Shared Dashboard
+ Helen and Bart work together on Project Task list and Calendar
+ After a 1-on-1, Helen asks Bart to please update the shared Project
Collection with the various Tasks and Milestones dates they discussed
+ Bart updates the Collection via Cosmo, where he has an account and
subscribes to multiple collections.
+ Helen goes back into the Project later on to Triage the new items
Bart has entered. There is one Task Helen has moved to the top of the
queue and would like Bart to start on right away. She writes him a
note: Please start on this as soon as you can...and sends it to him.
Lightweight collaboration via Cosmo: Shared Calendar
+ Ivan received a ticket to the shared Office calendar weeks ago, but
ignored it then and has since forgotten about it.
+ Ivan sends Helen an email telling her his summer vacation dates.
+ Helen replies asking Ivan to please enter this information on the
office calendar and supplies him with the read-write sharing ticket
again.
+ Ivan clicks on the ticket and goes to Cosmo to enter his PTO
+ Ivan uses the Jump-to-date field to jump to the right week.
+ Ivan d-clicks on the calendar canvas to enter his PTO dates.
+ When he is done, he clicks on the mail-to link in the detail view
of his PTO event item to send out an email to everyone in the office,
informing them of his PTO dates.
Mimi
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
