Published on <a href="https://blog.prototypr.io/jobs-to-be-done-vs-personas-60b8440e1318?source=rss----eb297ea1161a---4">| Prototyping: From UX to Front End &mdash; Medium</a> gusepo <img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-bcs6EtqAhIUpezfIwZc2w.png">Portraits from Pexels.com
in search of the best way for representing customer goals.
Few weeks ago I was looking for an effective ways for performing user research to design new features for an existing product. I decided to have a look at the Jobs-to-be-Done method promoted by <a href="https://medium.com/u/7ca8972daf76">Intercom</a> on their <a href="https://www.intercom.com/books/jobs-to-be-done">free book on the theme</a>. The book explains how the company adapted the method, used for decades in physical product innovation, to the needs of a their customer messaging apps.
I found many interesting ideas in the book. It explains how to look at a your product as a solution to customers goals and it suggests to think about competitors as different solutions to same goals.
<blockquote>When you’re thinking about competitors, it’s best to ignore product categories and instead ask yourself who else is fighting for that same job.</blockquote>
<blockquote>The newspaper industry thought they were in the business of selling news printed on paper. Had they realized their business was “keep people entertained”, or “keep people in the know”, their new competitors like mobile games, Twitter, and Facebook would have been a more obvious threat.</blockquote>
Intercom book provides insights on customers mixed feelings about changing habits, and presents case histories on how the method was successfully used inside the company.
<img alt="" src="https://cdn-images-1.medium.com/max/660/1*xLr7pnoYQB3H0Am5xQVGRQ.png">Why customers switch products, Intercom
I got a bit disappointed when I read <a href="https://medium.com/u/9f0edf3fc60d">Paul Adams</a> chapter about the issues he finds in using Cooper’s Personas tool. According to Paul, Personas focus too much on people profiles than on their goals.
<blockquote>When I worked at Google, I created dozens if not hundreds of personas across many projects. We followed Cooper’s method carefully, along with iterations of our own. Universally, I found their value limited. They often helped with building empathy amongst employees who were disconnected from their users, but they rarely led to breakthrough ideas or fresh thinking about a problem.</blockquote>
If you are not familiar with Personas tool, it is a Goal-Directed methodology introduced in software product design by the software superstar Alan Cooper in 1995. In his blog post <a href="https://www.cooper.com/journal/2003/08/the_origin_of_personas">The origin of personas</a> Cooper extensively explain the story of the method. The tool is extensively used for digital products user research, I personally believe Personas method is valuable in helping product teams taking user-centered decisions when designing or prioritizing features.
Speaking with my friend <a href="https://medium.com/u/53a8a818fb12">Fabio Nucatolo</a> and on <a href="https://www.linkedin.com/groups/72842">Linkedin User Experience group</a> I found some articles addressing the differences between Personas and Jobs-to-be-Done and some examples on how the 2 methods can coexist.
According to <a href="https://twitter.com/page_level">Page Laubheimer</a> at <a href="https://www.nngroup.com/articles/personas-jobs-be-done/">Nielsen Norman Group</a>
<blockquote>Well-executed personas are based largely on rich behavioral characteristics, attitudinal data, and insights about mental models, and they require qualitative research with real users to uncover the why behind users’ behaviors. These rich personas typically will include information related to specific goals that users must achieve when they use the product; these goals are directly comparable to the information found in the jobs-to-be-done definition.</blockquote>
<a href="https://www.nngroup.com/articles/personas-jobs-be-done/">Personas vs. Jobs-to-Be-Done</a>
I agree with <a href="https://medium.com/u/b029308b1b5">Shahrzad Samadzadeh</a> when she claims that
<blockquote>Without personas, jobs bury emotional and social needs under a thick layer of functional analysis.</blockquote>
<a href="https://www.cooper.com/journal/2017/1/bringing-together-personas-jobs-to-be-done-and-customer-journey-maps">Bringing Together Personas, Jobs To Be Done, and Customer Journey Maps | Cooper</a>
Finally I like <a href="https://medium.com/u/b295e4654af6">Claire Menke</a> at <a href="https://medium.com/u/b32aa0132f1b">Udemy</a> solution to reconcile the 2 methods.
<blockquote>At Udemy we use JTBD as a layer of refinement within a persona — how a student views learning (their persona) shapes the situations they face, as well as how they will react to overcome a challenge or take advantage of an opportunity in their lives (their JTBD).</blockquote>
<a href="https://blog.prototypr.io/the-goldilocks-experience-of-developing-a-foundational-research-framework-finding-a-practice-a8c647b906e3">The “Goldilocks Experience” of developing a foundational research framework — finding a practice…</a>
What do you think? I’m happy to ear more opinions on JTBD Vs Personas in the comments.
<img src="https://medium.com/_/stat?event=post.clientViewed&amp;referrerSource=full_rss&amp;postId=60b8440e1318" width="1" height="1" alt="stat?event=post.clientViewed&amp;referrerSou">
<hr>
<a href="https://blog.prototypr.io/jobs-to-be-done-vs-personas-60b8440e1318">Jobs-to-be-Done Vs Personas</a> was originally published in <a href="https://blog.prototypr.io">Prototypr</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.

Jobs-to-be-Done Vs Personas

Top Stories