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.
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".
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.
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
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.
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.
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.
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.
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
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.
What is the stated justification there?
TFA sheds no light on the unique advantages offered by detailed personas.
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.
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)
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.
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!)
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"
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.
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.