I recently saw an example of personas done from a usage occassion as opposed to being role based - so instead of "Mike - Salesperon" or "Tammy - Student", it was done from the perspective of segmentation of audience based on their usage, "Sam - loyal book buyer" or "Mary - occassional reader".
Is this just really a semantic difference??
I've always done personas based on role, however I've got a project that has potentially 12 - 15 of different roles, with several of them falling into a more generic "Producer" & "Consumer" buckets (I don't want to be that generic, because not all consumers have the same needs, nor do the producers).
I'm wondering what the group thinks about fewer, usage-based, personas where I would lose some of the depth of the individual roles, to focus on a few core personas about how people will be using the system: "Plan Creator", "Team Member", "Frequent Publisher", "Occassional Browser" - or something like that?.
This is for a very large, internal, cross-department application.