JTBD vs Personas vs User Stories: What to Use and When

UX Strategy

Oct 5, 2026

JTBD vs personas, user stories vs jobs to be done, UX frameworks compared, product discovery methods, persona limitations, agile user stories

Summary

Personas answer who the user is, JTBD answers why they act, and user stories answer what to build next. Personas fail when teams mistake demographics for motivation.

JTBD fails when it becomes abstract theory without delivery. User stories fail when the so-that clause is invented instead of researched.

Mature teams use all three: personas to build empathy, JTBD to set direction, and user stories to ship. The mistake is picking one and asking it to do all three jobs.

Product teams love framework wars. Personas are dead, JTBD is everything, user stories are bureaucracy. The JTBD Playbook makes a calmer point: these tools answer different questions, and confusing them is the real problem.

What question does each framework answer?

Framework	Question it answers	Typical failure
Personas	Who are we serving?	Demographics mistaken for motivation
Jobs to Be Done	Why do they act? What progress do they seek?	Theory that never reaches the backlog
User stories	What do we build next?	Invented “so that” clauses nobody researched

A persona tells you your user is a 34-year-old operations manager in Riyadh. JTBD tells you she hires your software to make Monday reporting painless so she can stop working weekends. A user story tells the team what to ship this sprint. Replace one with another and you get a 34-year-old’s favorite color driving the roadmap, or a beautiful theory nobody can build from.

When should each one lead?

Early strategy and positioning: JTBD. It tells you which market you are actually in.
Empathy and communication: personas. Humans empathize with humans, not abstractions.
Delivery: user stories, but only when the job behind them is real.

What do designers take away from the comparison?

That framework loyalty is a distraction. Kalbach’s playbook is explicit that JTBD complements existing practice rather than replacing it. The designer’s job is translation: carrying the why (job) through the who (persona) into the what (story) without losing it along the way.

Why does Tremoloo share this book?

Because framework confusion costs our clients real money: research that cannot ship, stories with no user behind them. This book is the antidote we recommend most when a team’s methods have calcified into ritual.

Need help aligning your frameworks into one process that ships? Our strategy consultants do exactly that.

‹ How to Build a Job Map: Practical Steps from the JTBD Playbook

Design for How People Think: Using Brain Science to Build Better Products ›

Ready to Launch
Your Next Project?

If you’re tired of iterating in circles, we can help. We research,
design, and refine products with focused teams.

Book a 15 min call