News for hackers. Stuff that matters.
Re:Why Personas Fail by bambax on Monday January 29, 2018 @05:39AM (#16256697)
In my former life as a consultant I came to very much dislike personas as implemented by ux designers.

Personas are a magnet for prejudice: they are based on the idea that clusters of people all behave the same (old people, young people, professionals, stay-at-home mothers, what have you).

This very idea is, I think, flawed. If we really need to sort people into groups, then we should use criteria based on what people are trying to achieve right now, not inherent characteristics that are supposed to influence/define their behavior all of the time.

Therefore it would make more sense to have just one typical user, with different attitudes based on her -changing- goals.

Re:Why Personas Fail by king_magic on Monday January 29, 2018 @07:31AM (#16257084)
I’ll throw out another (admittedly anecdotal) issue - cost and effort to develop something that - in my experience - isn’t all that valuable in the end. In my life as a consultant I’ve watched a team of UX ‘experts’ churn for 2 weeks over a set of 5 personas. Jaw dropped every time we would check in - this is what you spent the last 3 days on? Even more stunning was the client’s reaction to the 3rd review of those personas. It was the same 1hr convo as the previous 2 reviews, and no one seemed to think this wasn’t a massive waste of time and their money. After the personas were done, no one ever referred back to them for the remainder of the project. It was one of the greatest ‘value minimization’ excersises I’ve seen in my career.
Re:Why Personas Fail by mistermann on Monday January 29, 2018 @09:57AM (#16257812)
Reminds me of a RACI matrix experience.
Re:Why Personas Fail by WaxProlix on Monday January 29, 2018 @01:22PM (#16259452)
RACI can at least be useful for defining who should be in what meetings early on, how communications should go out, and even CYA later on in the project. It can be good to have investment levels explicitly defined.
Re:Why Personas Fail by mistermann on Tuesday January 30, 2018 @02:27AM (#16263529)
There are probably plenty of places it's useful that I've just never been exposed to, but I bet for every one of those, there's two or more others using it who don't need it, but only because they were sold it by management consultants at a lean management training course or something like that.
Re:Why Personas Fail by jerf on Monday January 29, 2018 @10:13AM (#16257899)
Yes, the very idea that customers can be bucketed is flawed. We are all unique people.

But we do not categorize our customers into buckets because we are denying their individuality. We do it because we lack the cognitive firepower to address several thousand people individually, by multiple orders of magnitude. Categorization isn't a denial of their humanity, it's an acknowledgement of our humanity, as opposed to being some sort of post-Singularity AI or Deity that is capable of individually addressing people. We have no options to address this flaw.

Pretending that we've just got one user who wants to routinely buy Depends, yet at others for no apparent reason, is intensely into punk rock, and on another day forgets how to speak English and is only going to interact with your site in Tagalog, is just going to distort your UI in other ways. I don't think acknowledging people's individuality is accomplished by only acknowledging one individual, with that individual constructed in such a way that this one individual is representative of nobody.

Re:Why Personas Fail by TeMPOraL on Monday January 29, 2018 @10:59AM (#16258197)
I think GP is fine with bucketing, but they're saying that f(age, gender, interests, ...) is not a good hashing function.

I haven't seen studies on the topic, but on the surface of it, I'm inclined to agree - it doesn't seem to be a good bucketing strategy, and unless we're talking about cold-calling/edge of the funnel, and painting in very broad strokes, it misses the most important factor uniting them all - they're on your site, so they must want something. Hence, "we should use criteria based on what people are trying to achieve right now".

Re:Why Personas Fail by kruhft on Monday January 29, 2018 @11:40AM (#16258512)
Sounds like a problem for Expert Systems.
Re:Why Personas Fail by bambax on Monday January 29, 2018 @11:16AM (#16258319)
Yes, exactly.
Re:Why Personas Fail by michaelt on Monday January 29, 2018 @06:53AM (#16256936)

  it would make more sense to have
  just one typical user,
Some products have users with distinct - almost contradictory - requirements.

For example, some spreadsheet users want simple graphs with big numbers that will look good in presentations, and a simple UI they can use on their phone. Other spreadsheet users want to make complex graphs with labelled arrows, thousands of points, multiple different graphs with aligned axes, and things like that.

Multiple personas can be useful for expressing that fact - otherwise you're stuck saying the just-one-user wants things to be simple and complicated at the same time.

Re:Why Personas Fail by dhimes on Monday January 29, 2018 @07:40AM (#16257115)
OK but this is a 30 minute exercise: whom are we building this for?

I've seen talk about building personas where you try to specify all kinds of ancillary data about the personas: where they live, how many kids, etc.

I would love to hear about a time where the persona development led to a new insight because it's a persona. Like: this person's a parent-> probably attends parent-teacher groups-> voila! needs XXXX

Re:Why Personas Fail by blowski on Monday January 29, 2018 @08:47AM (#16257431)
When it's just abstract information, especially information that has no basis in user research, it is worthless.

But I'll give an example of where I've seen this be useful.

> Bob is a marketing guy. He mostly uses his mobile for calls, but doesn't have a headset. As a result, he can't type quickly while on the phone, so any UI he needs to use while on the phone should be optimised for mouse clicks or single keypresses.

This came out of some actual user research and was the justification for spending time on a 'point and click' friendly UI.

Re:Why Personas Fail by BoorishBears on Monday January 29, 2018 @10:04AM (#16257839)
I know it’s just an example, but does one need Bob to come to that realization? If you say you’re building for mobile, you look at the strengths and weaknesses of input on mobile devices.

The biggest strength is precise finger movement. The biggest weakness is lack of tactile feedback.

That leads to the same conclusion without extraneous data.

I feel like personas are a way to force people to think critically about the end product. That’s not a bad thing, but just deciding to critically consider what your goal is before building something already goes a long way.

Re:Why Personas Fail by wpietri on Monday January 29, 2018 @04:43PM (#16260880)
I think "does one need Bob" is the wrong way to look at it.

Humans are narrative animals. Storytelling is a human universal. Done right, personas are a way we can engage our narrative capacity to help us in thinking through the complexities of a domain. (Done wrong, they let our preconceptions and prejudices erase the complexity of our domain.)

I'm not personally a huge fan of personas. Instead, I'm big on primary user research, where we spend a lot of time studying actual people, their lives, and how our products fit into them. But if the group of makers is large enough, you need some way to organize the insights from that into something convenient for discussion.

At my last startup we were working on something related to purchasing decisions. For us, the satisficer vs optimizer distinction was key. We did dozens of user interviews, and user testing each week.

We ended up with two main personas, one for the satisficer and one for the optimizer. It was handy to be able to talk about Bob vs Cate in terms of how each would react to a given design choice. By having specific imaginary people made it easier for us to put ourselves in their shoes, to talk about how the product fit into their lives.

We would also talk about specific real people (e.g., user test subjects, actual users) and about theoretical constructs. But having fictional archetypes was useful to us in thinking empathetically without getting bogged down in a specific person's details.

Re:Why Personas Fail by skybrian on Monday January 29, 2018 @11:03AM (#16258222)
If you tell the programmers that people need to be able to use a desktop web app with one hand, they're going to want to know why. Are there really that many one-handed users out there? Sounds like a corner case.

Personas are useful if they're backed by user research. That's how you know that yes, there really are a lot of "one-handed" users among your actual customers, and here's why.

It seems like one pitfall with personas might be giving them to developers without including any of the supporting research that makes them a valuable summary.

Re:Why Personas Fail by BoorishBears on Monday January 29, 2018 @11:37AM (#16258482)
>If you tell the programmers that people need to be able to use a desktop web app with one hand, they're going to want to know why. Are there really that many one-handed users out there? Sounds like a corner case.

If your programmers are tightly integrated with product development, they should have access to the insight that makes it a priority in the first place.

If your programmers are removed from it, then they probably won’t care/ask.

I think you kind of hint at that in your last paragraph in mentioning sharing the supporting research.

Like I said, personas aren’t a bad thing, but things like user research are just good ideas anyways. Having user research lets you come to similar conclusions without a persona. If personas are what it takes to convince people to do things like crticically think and do user research about products before building I’m fine with it, but those are things you really should be doing regardless

Re:Why Personas Fail by burkemw3 on Monday January 29, 2018 @01:58PM (#16259741)
I think of Bob as a team communication tool. Hopefully, most people on the team are familiar with Bob. When I'm working with someone else on that critical thinking thing about the end product, I can ask "What about Bob?" and teammates know what I'm talking about. Bob is a mobile user might not be complex enough to warrant a persona. I think personas are more likely to be a useful tool as the number of user types/goals increases.

Personas can also be a kind of checklist as a change is made, ensuring that the change makes sense (and doesn't break) in the most common product scenarios.

Re:Why Personas Fail by funkaster on Monday January 29, 2018 @11:07AM (#16258248)
It's about trying to be empathetic about the end user. Yes, you get to the same result, but personas are mostly useful when it's very hard for the team developing a product to eat their own dogfood. It's a tool that could bring you closer to how the end user feels/could interact with the product.
Re:Why Personas Fail by blowski on Monday January 29, 2018 @10:56AM (#16258182)
It told us that it was a priority, rather than just "something that would be nice if we get around to it".
Re:Why Personas Fail by mistermann on Monday January 29, 2018 @09:59AM (#16257820)
Isn't this just common sense though?
Re:Why Personas Fail by michaelt on Monday January 29, 2018 @10:18AM (#16257926)
Evidently not, if it took user research to reveal it :)
Re:Why Personas Fail by ci5er on Monday January 29, 2018 @07:56AM (#16257200)
> I've seen talk about building personas where you try to specify all kinds of ancillary data about the personas: where they live, how many kids, etc.

What is the stated justification there?

Re:Why Personas Fail by dhimes on Monday January 29, 2018 @08:09AM (#16257247)
The idea is supposedly to "get inside the heads" of the target user. This will lead presumably lead to some sort of intuition about what their needs are and how to market to them.

TFA sheds no light on the unique advantages offered by detailed personas.

Re:Why Personas Fail by juliushuijnk on Monday January 29, 2018 @11:36AM (#16258467)
The idea is to get the user in your head as a real human being not as an abstract category.

If you design for "User who needs product X" then you come up with different design than if you think about "Jim wants to buy a gift for his nephew's birthday, he is late, the birthday is tomorrow." You can better come up with ways to support Jim. You feel the importance of a speedy delivery.

You can also think about new features like asking this user if he wants a suggestion mail sent to him for next year (minus two weeks), that has present suggestions for kids that are 1 year older.

Now I just made that up, and it might be a terrible idea, but the point is, that you could never come up with something like that without a persona.

Re:Why Personas Fail by ci5er on Monday January 29, 2018 @08:23AM (#16257311)
Hmmm. My product has "this cluster of users" vs "that cluster of users". But we really don't attempt to imagine their home-life. Or race or sex or orientation. Just what they are into feature-set wise.

EDIT: I think we call them "User-Type-A" and "User-Type-B". That doesn't sound very sexy - but it helps us prioritize feature development (esp. since "User-Type-B" never pays for anything - those features come last. But the non-paying user type is the most winge-ey - I've never figured out how that could be - but they are)

Re:Why Personas Fail by moron4hire on Monday January 29, 2018 @07:44AM (#16257130)
That's not contradictory. People need different things out of their tools at different times. People are not monotone. And understanding that one person can have N need is different than understanding that N people have individual needs.
Re:Why Personas Fail by dhimes on Monday January 29, 2018 @08:11AM (#16257262)
Exactly. How does knowing that someone's favorite color is purple add to that? I can certainly see trying to understand these peoples' lives and what their needs are, but not having a team spend two weeks in Imaginationland to come up with it.
Re:Why Personas Fail by Angostura on Monday January 29, 2018 @06:08AM (#16256801)
I disagree. Where website have a variety of different potential types of user, it can be useful to explicitly describe those different types of users, their needs and goals. Calling them Bob or Mary, can just be useful shorthand and avoid segments getting forgotten about.

In speccing and QA, I've always included a section on 'Works for Mary? Works for Bob?' etc. It's not rocket science and shouldn't be stupidly glossy in my opinion. But initial agreement can really help functional design.

Re:Why Personas Fail by pweissbrod on Monday January 29, 2018 @09:28AM (#16257646)
As I read it persona is more of an attempt at characterizing the mindset/psychology of the end user.

Your description of persona is more like a user role serves as a grouping of use cases or user stories (which is still very useful!)

Re:Why Personas Fail by Angostura on Monday January 29, 2018 @12:23PM (#16258944)
I think the two are fairly closely linked. In my mind, each persona is essentially a group of user roles collected together and given a explanatory biography and a fake moustache
Re:Why Personas Fail by michaelrichards on Monday January 29, 2018 @08:47AM (#16257433)
I disagree. The concept of personas is useful for abstracting the user's previous experiences and habits formed, not their current goals. It's a useful abstraction that should be considered an abstraction and not a concrete example. When discussing 'stay at home moms', we're encapsulating the past experiences of such personas.
Re:Why Personas Fail by harryf on Monday January 29, 2018 @09:22AM (#16257614)
I think therein lies the real reason why personas (often) fail - no one establishes the connection from the personas to the types of user / customer segments companies will have already established, from analysing their sales data and usage analytics.

By contrast to something like A/B testing, which can produce actionable results, in my experience personas frequently end up as nothing more than MeetingWare, so that everyone attending "can be on the same page"

Re:Why Personas Fail by ErikVandeWater on Monday January 29, 2018 @08:52AM (#16257453)
I think for some products this would actually be useful. Some products are inherently not exactly goal-oriented - Point A to Point B.

Take Facebook for example. It's not about achieving the objective of putting photos online, it's about the mystery of being invited to a website to share who you are with your friends and learning how you can interact through this new medium. It really mattered that Facebook targeted a specific demographic. If they didn't target that demographic exclusively, they wouldn't have succeeded, because college student's mom's would have been on there and they would have felt vulnerable, and found somewhere else to share.

Re:Why Personas Fail by crandycodes on Monday January 29, 2018 @01:24PM (#16259463)
Persona as a "mascot" for a scenario has been helpful for me. It helps to think through the idea from the user's point of view, not how the software wants to be written, so to speak. Having two personas for a scenario also helps to delineate a spectrum (i.e. a casual and pro user) when you're going to have users with different requirements going through the life cycle of your product.