04/04/2022
Marketing 101 : Back to basics Persona vs JTBT
“User personas are fictitious yet realistic representations of your target users”,. They define the user, their needs, wants, behaviors, anxieties, motivations, frustrations, etc.
Personas focus extensively on behaviors .
🤔Why are user personas created?❓❓
1.🎯Persona defines who the story is about . the main character has attitude , motivation , goal and pain points etc.
3. 🎯Goal- defines what the persona wants or needs to fulfill . the goal is the motivation of why the persona is taking action . when goal is reached, the scenario ends.
2. 🎯Scenario - Defines when, where, and how the story takes place . the scenario is the narrative that describes how the persona behaves as a sequence of events.
BUT How do you create a good user persona ?
💎Begin with comprehensive user research
💎Identify common attributes:
💎Create a cluster of personas:
What Is Jobs To Be Done?
Jobs To Be Done is an alternative approach to understanding the user. Jobs-to-be-done focus on user problems and needs, while well-executed personas include the same information and also add behavioural and attitudinal details.
Theodore Levitt quote, “People don't want to buy a quarter-inch drill, they want a quarter-inch hole.”
Rather than focusing on a list of features for a product, the JTBD framework forces to think about outcomes:
Would users be able to (happily and easily) complete the job they “hired” for?
Does this solution provide a better outcome than existing ones?
How Do You Create A 👍 Good Jobs To Be Done List📄?
There are few established standards for creating JTBD lists. However, typically, it is categorised as functional, social, and personal outcomes.
Lets take an example of a 📱 mobile phone
Functional needs may be:
Listen to music and speak in calls comfortably
Long battery life
Fit into their budget
Social needs may be:
Appear like a user of premium products
Not hear voices/sounds from around them
Personal needs may be:
Feeling comfortable on the ear
Be easy to clean
🎛️A blended approach to Personas and JTBD
Clearly, these are two very distinct approaches—
But consider for a moment that these two approaches have a common goal: to actually helps users do what they need to do.
JTBD is useful in clarifying end goals, where user personas are useful in building empathy and discovering pain points users encounter
🚀Avoid demographics as much as possible
🚀Replace the background story for the exposition,
🚀Limit behavior descriptions to those relevant to the product context,
🚀Go a bit deeper in exploring the user's frustrations and needs
🚀Keep the persona nomenclature:
Comment “more” if you like this piece of content.