personas

Thanks to @rickvug for kicking off the personas discussion.

I feel pretty strongly that the community owner / site owner and community member / site user are the two most important personas from a priority perspective.

eaton's description of the overall target / use case is:

[tsunami] is currently meant for small groups of individuals who are collaborating on a project and want to communicate with each other, tell the world about their project, and attract other people who are interested in helping. Imagine a small open source project, a local community group seeking to renovate a park, or a club that needs to keep in touch between meetings and attract new members.

I think an addition to this should be some guiding principles:

• the primary usage of this site will be by users
• that is, when choosing between a site building use case and a user-centric use case, Tsunami will lean towards the user-centric use case

I want to maintain at least two different personas on my Drupal-based blog: (1) Professional (2) Personal. Naturally, each would have its own set of blog entries that generally would not intersect, although they might sometimes.

My question is: What is the best way to organize and display each of these personas as its own blog, and still be able to show them together in one blog stream when I want to?

Hi all!
As a part of my course on Usability Design at the University of Leuven (Belgium), I'm doing a user and task analysis on Drupal.
I have started a user survey to collect useful data on the users of Drupal. With this data, I will create user profiles and personas to reflect some typical user groups of Drupal.

The survey can be found here: http://drupalsurvey.vanisterdael.be/index.php?sid=76524