Jobs to Be Done: The Framework That Makes Your Positioning Actually Stick

Most SaaS companies describe what their product does. Almost none describe what job it’s hired to do.

Two companies sell “project management software.” One positions around features: Gantt charts, time tracking, resource allocation. The other positions around the job: help remote teams feel coordinated without micromanaging.

The second one wins. Every time.

Because people don’t buy products. They hire them to get a job done. When you understand the job your customers hire you for, positioning becomes obvious. When you focus on features, you sound like everyone else.

Jobs to Be Done (JTBD) is a framework for understanding what customers are actually trying to accomplish in their lives. It shifts the question from who is my customer (demographics) to what progress are they trying to make (motivation). And that shift is where differentiated positioning comes from.

The Product Marketing Alliance has reported that the vast majority of companies struggle with differentiated positioning. The reason isn’t a lack of creativity. It’s a lack of understanding about what job the customer actually needs done.

What is Jobs to Be Done, and why it beats personas

JTBD focuses on the progress a customer is trying to make, not who they are on paper.

A traditional persona tells you Sarah is a 35-year-old marketing director at a 200-person SaaS company who likes yoga and reads HBR. Useful for a slide. Useless for positioning.

JTBD tells you Sarah hires your product when she’s stressed about team alignment and needs to feel confident nothing is falling through the cracks, without becoming a micromanager.

One describes a person. The other describes a situation and a desired outcome. Only one of those helps you write a sentence that makes someone feel understood.

The milkshake example, fast

Clayton Christensen’s milkshake story is the classic illustration. A fast-food chain wanted to sell more milkshakes, so they studied who bought them. Demographics said busy morning commuters. That told them nothing about why.

The real insight came from the job. Commuters had a long, boring drive and wanted something filling, easy to consume with one hand, that lasted until lunch. The milkshake’s competitors weren’t other milkshakes. They were bagels, coffee, bananas, and doing nothing at all.

That’s the whole point. When you understand the job, you can position against the real competition.

Your project management tool isn’t competing with other PM tools. It’s competing with Slack chaos, buried email threads, and the low-grade anxiety of not knowing what’s happening. When everyone positions around features, differentiation is impossible. When you position around the job, the field clears.

The three jobs your customers actually hire you to do

Every product gets hired for three jobs at once: functional, emotional, and social.

• Functional: the practical task they need done.
• Emotional: how they want to feel.
• Social: how they want to be perceived.

Most SaaS companies only talk about the functional one. That’s exactly why their positioning feels generic.

Take Slack.

The functional job is team communication. Send messages, share files, organize channels. Every competitor can claim that.

The emotional job is reducing information anxiety. Teams hire Slack when they’re tired of wondering if they missed something important or if their message vanished into an inbox. They want to feel connected and informed without drowning.

The social job is appearing modern and efficient. A team using Slack signals it’s forward-thinking. Email feels dated. Slack feels current.

Understand all three and your messaging changes. Slack doesn’t say “team communication platform.” It says “where work happens.” The functional job is implied. The emotional and social jobs are doing the real work.

How to run JTBD interviews that reveal real motivation

JTBD interviews are built around switching moments, not satisfaction scores.

The core question: “Tell me about the last time you switched from [old solution] to [new solution].” Then you follow the timeline from trigger to outcome.

Start with the trigger. What broke? What was the breaking point? Don’t accept “we needed better collaboration.” Drill in: “What happened that day that made you realize the old way wasn’t working?”

Explore what they considered. This is where you find the real competitive set, including non-consumption (doing nothing) and workarounds (spreadsheets, email, manual tracking) you’d never spot in competitor research.

Understand the decision criteria. Why you? What were the concerns? What did they almost pick instead?

Probe the desired outcome. “What were you hoping would be different?” This is where the emotional job lives. Customers rarely say they wanted “better project management.” They say they wanted to stop worrying about dropped balls, or to finally feel their team was aligned.

The questions that work, grouped by stage:

Trigger:

• What prompted you to look for a solution like ours?
• What was happening that made the status quo unacceptable?
• Can you remember the moment you thought “there has to be a better way”?

Consideration:

• What did you consider before choosing us?
• What were you doing before you had any solution at all?
• What almost stopped you from switching?

Outcome:

• What would have to happen for this to count as a success?
• How would your day be different if this worked perfectly?
• What are you hoping to eliminate completely?

The timeline approach works because it grounds answers in behavior, not opinion. People are terrible at predicting what they’ll do. They’re accurate at describing what they did. Anchor everything in the past tense.

JTBD examples from SaaS companies that nailed it

The best-positioned companies understand all three jobs.

Notion doesn’t sell “productivity software.” It positions around helping knowledge workers feel organized without being boxed in by rigid structure.

• Functional: organize information and workflows.
• Emotional: feel creative control over your workspace.
• Social: appear thoughtful and intentional about how you work.

Figma could be “design software.” Instead it’s about collaboration without losing creative control. “Nothing great is made alone” speaks straight to the emotional and social jobs, not the functional one.

Calendly avoids “scheduling software” and goes after the anxiety: kill the back-and-forth email dance. “Scheduling infrastructure for absolutely everyone” frames it as essential infrastructure, not optional software.

Notice what these have in common. They differentiate through context, not feature lists.

How to turn JTBD insights into positioning that differentiates

Research is only useful if it changes what you say. Here’s how to make the translation.

Identify your primary job. Look for patterns across the switching stories. What job comes up again and again? What outcome do customers keep describing in their own words? Most products serve several jobs, but one usually dominates. Build your positioning around that one and let the others live in the supporting messaging.

Map the real competition. JTBD always surfaces competitors you’d never find in a feature matrix. If customers hire you to “feel confident nothing’s falling through the cracks,” you’re competing against manual tracking, anxious micromanagement, and the status quo of hoping it all works out. That expanded view is where fresh angles come from. You stop comparing features and start positioning against the pain of the current state.

Use this template:

When [situation], [target customer] hires [product] to [functional job] so they can [emotional outcome] without [constraint or anxiety].

Worked example:

When remote teams feel disconnected and information gets lost, marketing leaders hire Notion to organize their team’s knowledge so they can feel confident everyone has access to what they need, without building rigid processes that slow people down.

The template forces you to include the situation (when), the emotional outcome (so they can feel), and the constraint you remove (without). Skip any of those and you’re back to feature-speak.

Great positioning starts with the job, not the product. Lead with the situation and the desired outcome, and differentiation stops being a creative exercise. It becomes a documentation exercise.

Where this fits in a Systems-Led Growth motion

JTBD research is one of the highest-leverage inputs you can feed into a system.

In an SLG setup, customer interview transcripts don’t sit in a folder. They flow through AI workflows that extract job stories, generate positioning variations, and build messaging frameworks from the exact language customers use. One interview becomes a quote library, a set of job stories, and several drafts of positioning copy, without anyone starting from a blank page.

That’s the difference between doing JTBD research and building with it. The first gives you a deck. The second gives you infrastructure that keeps your positioning current as the jobs evolve.

The positioning advantage starts with the job

Most teams skip the research and jump straight to messaging. That’s exactly why their positioning sounds like everyone else’s. They optimize for clarity about features instead of connection to motivation.

The companies that break through understand a simple thing: customers don’t buy project management software. They hire a solution to feel organized, confident, and in control of complex work without becoming the bottleneck.

So run three JTBD interviews this month. Ask about switching moments, not satisfaction scores. Follow the timeline from trigger to outcome. Listen for the functional, emotional, and social jobs underneath.

When you actually understand why customers hire you, positioning stops being invention and becomes description. You’re not making up differentiation. You’re writing down value you already create.

The job was always there. Most companies just never asked.

Want a system that turns customer research into positioning assets automatically? See how we build it.

Related reading: Pipes Before the Chocolate: The AI Marketing Strategy That Actually Compounds · score yourself with the matching audit · start with an audit · read the manifesto · Internal Communications for GTM Teams: How to Stop Saying the Same Thing Five Different Ways