I usually work with specifically grouped information in separate docs. Market research (competitive analysis etc), User needs and behaviors (including personas), and Biz requirements (sometimes including technical constraints, but sometimes its better as a fourth bucket). The reason I keep these separate is that I like to NOT have ownership of these, but have them provided buy subject experts, kept current and then I utilize them in the design process. Mark
On Thu, Feb 26, 2009 at 6:10 PM, Tom <[email protected]> wrote: > We're working on building some personas for some desktop software. > I've been going over Todd Warfel's template and Steve Mulder's > (The User is Always Right). > > Steve includes Business Objectives, Todd does not. The argument is > that you want to include what you as an organization want to > accomplish. > > I guess I would argue that a persona is not about my organization and > it's goals, it's about the person and their goals. And if I am > satisfying their goals, that's going to be good for my org and my > software. > > Am I missing something as to why they should be included? Love to > hear your thoughts. > ________________________________________________________________ > Welcome to the Interaction Design Association (IxDA)! > To post to this list ....... [email protected] > Unsubscribe ................ http://www.ixda.org/unsubscribe > List Guidelines ............ http://www.ixda.org/guidelines > List Help .................. http://www.ixda.org/help > ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
