defining requirements: use cases

One thing that isn't clear to me is who *exactly* is the target 
audience for Chandler and why they would adopt it.

Some use case scenarios would be helpful, showing who uses Chandler 
and why.  It might also be useful to write some scenarios for people 
who do *not* swtich to Chandler to illustrate which market segments 
you are willing to leave behind.


(Note: when you create scenarios, it's a good idea to write use cases 
for wildly dysfunctional and/or perverted people and organizations, 
not just chirpy happy clean-cut people/organizations.  While 
sociopaths are probably (hopefully!) do not constitute a significant 
market niche, most people have some secrets, some dysfunction, and/or 
some sadness in their life.

Think of the dysfunctional scenarios as corner cases in the design space.)
-- 
Kaitlin Duck Sherwood
Author of the _Overcome Email Overload_ series, http://www.EmailOverload.com
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Process" mailing list
http://lists.osafoundation.org/mailman/listinfo/process