Let's diving into one of my favourite frameworks for understanding user needs: Jobs-To-Be-Done (JTBD). After implementing this at Pawmates and seeing its impact firsthand, I'm excited to share how you can use this powerful tool in your design process.

What is JTBD? 🤔

Think of JTBD as the "why" behind user behavior. Instead of focusing on who your users are, it explores what they're trying to accomplish. Like being a detective of user motivations!

When to Use JTBD in Your Design Process:

1. Early Discovery Phase

   • Before creating user personas

   • During initial user research

   • When defining product strategy

2. Problem Definition Stage

   • Identifying core user needs

   • Understanding emotional drivers

   • Mapping functional requirements

3. Solution Ideation

   • Generating "How Might We" questions

   • Brainstorming features

   • Validating solutions

My Experience at Pawmates 🐾

When tackling Pawmates' UI inconsistency issues, I used JTBD to dig deeper than surface-level problems. Here's how:

Step 1: Identify Core Jobs

• Analyzed user behavior patterns

• Conducted user interviews & testing

• Mapped emotional and functional needs

Step 2: Create Job Statements

• "Help me find compatible playmates for my dog"

• "Make me feel confident about meeting new pet owners"

• "Keep me informed about my pet community"

Step 3: Run 5 Whys Analysis

• Started with surface problems

• Dug deeper into root causes

• Formulated "How Might We" questions

Here is an example of a Job Statement @ Pawmates:

'When I move to a new city with my dog, I want to find compatible dog owners in my neighborhood, So I can build a reliable network for playdates and pet sitting.'

JTBD + User Personas: A Power Couple 💪

JTBD and User Personas aren't competitors – they're complimentary! Here's how to use them together:

1. Start with JTBD

   • Uncover core motivations

   • Identify key jobs

   • Map functional requirements

2. Layer in Personas

   • Add context to jobs

   • Humanize your data

   • Create relatable stories

3. Validate Both

   • Identify gaps

   • Refine your understanding

An example of a JBTD + User Persona Hybrid:

'Sarah, a first-time dog owner in Toronto, needs to: When I'm working long hours at my startup job, I want to connect with trusted pet owners nearby, So I can ensure my puppy gets proper socialization and exercise while building my local support network.'

Context:

• Age: 28

• Location: Downtown Toronto

• Living situation: Studio apartment

• Pet: 6-month-old French Bulldog

• Schedule: Hybrid work, 50+ hours/week

• Pain point: Guilt about leaving puppy alone

This hybrid approach combines:

• Situational context (Persona)

• Emotional drivers (JTBD)

• Functional needs (JTBD)

• Environmental factors (Persona)

• Desired progress (JTBD)

• User characteristics (Persona)

  
  

Pro Tips from My Experience 💡

1. Balance Depth vs. Breadth

   • Don't try to solve every job

   • Focus on high-impact areas using RICE frameworks

2. Document Everything

   • Track your findings

   • Keep data on a shared team document

Lessons Learned at Pawmates

What worked:

• Running 6 competitor analyses using JTBD

• Combining emotional and technical requirements

• Using JTBD to inform our design system

What I'd do differently:

• Complete JTBD analysis before creating personas

• Focus more deeply on fewer jobs

• Spend more time on validation

Ready to Try JTBD? Here's Your Starter Kit:

1. Start Simple

   • Pick one user problem

   • Write clear job statements:

     • When I [situation/context], I want to [motivation/goal], So I can [desired outcome/progress].

   • Focus on progress, not features

2. Gather Data

   • Interview users

   • Observe behaviors

   • Track patterns

3. Create Solutions

   • Use "How Might We" questions

   • Brainstorm ideas

   • Test and iterate

Remember: JTBD isn't about replacing your existing tools – it's about enhancing them. It's like adding a powerful lens to your design toolkit that helps you see user needs in a whole new way.