3 ms·
OK, here's the thinking behind the negativity towards personas: it is an unnecessary abstraction that makes you think it's helping you, but actually impairs yo
by toss1 9y ago
OK, here's the thinking behind the negativity towards personas:
it is an unnecessary abstraction that makes you think it's helping you, but actually impairs your ability to deliver good tools.
To really deliver good tools, you need to get as close as possible to the actual user, ideally becoming one. I found that having a manager in the user company "gather user requirements" and deliver them to us in meetings (sometimes requested by clients thinking it would reduce costs) dramatically degraded what we could deliver and increased schedules and costs, compared to having the devs talking with and sitting next to the users for even an hour. (and yes, we did talk to the mgrs as users for their specific needs too)
Personas are an even worse level of abstraction than talking only to the managers.
You must focus on the very details of the interface where the rubber meets the road, not on some 3rd- or 4th-level abstraction.
Even in you get all the micro-details and include then in your "Jane Persona" abstraction, it won't help you interpolate the data sets from Task A and Task C to figure out how to implement Task B any better than looking directly at your two data sets. And, talking to actual user "Jane Real Person" will beat both of those options, because you'll probably learn something new.
Always go as close as you can to the source. Abstraction is often just a good way to fool yourself.
[edit: redundant repeated words ]