In trying to determine what features need to be included at what point in the Chandler roadmap we began to think about target users. But after wrestling with a variety of demographic/psychographic approaches we thought it might be better to explore Target USE cases rather than Target USERS since the predominate usage modality may be similar across several user types. For example we might expect a variety of folks to adopt and use Chandler primarily for the calendar functionality. These users could span a range from soccer moms trying to maintain the family schedule, to administrative assistants who maintain delegated calendars, or project managers who are keeping track of a project schedule. The one thing they all have in common is the need for event-based management.

We also need to consider adoption dynamics both positive attractors that pull the user to adopt and also barriers that would keep one from adopting Chandler regardless of how strong the pull from the attractors might be. Of course the weight or strength of any specific attractor or barrier will depend not only on the usage modality, but on the particulars of the individual. For example I might find the shared calendar features extremely attractive, but since I depend upon my Palm device to take my calendar/to do list with me, if Chandler were unable to sync easily with my Palm I just wouldn't use it for a desktop calendar no matter how great the features. Chao on the other hand who may be just as attracted by the shared calendar features does not use a PDA and so lack of Palm calendar sync is not a barrier for him.

Examples of usage modality would include the major parcels:

• email
• calendar
• address book

but also includes the intertwingularity of cross-domain or multi-domain use like:

• outline view
• knowlege management (documents, URLs, etc.)
• project managment (example holiday card list)

---

Parcel-specific USE cases

Email USE Case

Calendar USE Case

Address book USE Case

---

Cross domain USE cases

Project Management USE Case

Holiday card list

I want to send out holiday cards to a subset of the people in my address book. I haven't flagged any contacts specifically as holiday card recipients (which would be a computer-cenetric approach). I want to use the cross-domain functionality of Chandler to help me compile a list of recipients and send out eHolliday Cards. How might this work? First I would want to send cards to members of certain groups of contacts:

• family
• close friends
• important business associates
• those who have sent ME a holiday card
• those to whom I have sent a holiday card previously

Some of these may already be members of GROUP lists within Chandler for example family members may have a keyword or attribute in their Chandler record tagging them as members of a family group.

-- PieterHartsook - 13 Aug 2003