On Mon, Mar 2, 2009 at 9:14 PM, Jared Spool jsp...@uie.com wrote:
Have you asked your colleague what he wants to use this persona for? Can he
give examples on how this might change the design? [snip]
Ok, sparing the mundane details of interoffice juggling, it turns out that
the personas he is
Thanks everyone for the great answers. I have a follow up question.
The colleague that has put together the initial persona sketches has
included a couple of attributes that are specifically geared toward
selling the end product.
Specifically, for example, he created one called Decision Maker
On Mon, Mar 2, 2009 at 7:14 AM, Tom Dell'Aringa pixelm...@gmail.com wrote:
It seems to me a persona is not about selling, it's about designing
properly. And if we design properly, we won't have to concern
ourselves with how the sales force is going to sell it, because it
will satisfy our
A successful project has to balance user goals and business goals.
I agree with Jared that it is important to be able to draw clear
connections between the two. Seeing where the goals align will point
to your easiest wins. When they are in conflict or merely skewed from
one another, there will
On Thu, Feb 26, 2009 at 9:16 PM, Jared Spool jsp...@uie.com wrote:
Hi Tom,
Excellent question. Here's my take:
First, I want to ask: are we talking about whether the business objectives
are in the persona or with the persona description document? [snip]
I was mainly speaking to the
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
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
This is something that I've run into before, and here are my thoughts
on it.
1) to include business objectives in a persona is to build in the
assumption that your customers care about your business. They do not.
2) The underlying reasoning -- to my mind -- to build a persona is to
On Feb 26, 2009, at 3:10 PM, Tom wrote:
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
