The JTBD Mindset: Stop Building, Start Solving #13

A Simple Guide to Jobs to Be Done

Hey Product Peeps! ☕

What's new?

Ever shipped a shiny new feature… only to watch it sink? 🤿

You thought it was what users needed. But the metrics said otherwise.

We’ve all been there.

The real issue? Most product work starts with what we want to build, not what customers are actually trying to get done.

Let’s flip that.

This piece is going to talk about Jobs to Be Done (JTBD) method, the mindset shift that helps you stop guessing and start building things people actually want.

And more importantly:

⭐ Why it’s not just a framework, it’s a repeatable system.

⭐ Who needs it (hint: anyone building products or messages).

⭐ How to apply it to SaaS (and beyond).

Let’s dive in 👇

Why “Jobs” Beat Features 🛠

Here’s the thing:

Customers don’t buy products.

They hire them to do a job.

• You didn’t buy Notion because it’s pretty → You hired it to organize your chaos.
• You didn’t subscribe to Grammarly for fun → You hired it to write with confidence.
• You don't just watch YouTube → You are trying to be entertained, informed or skilled.

I can go on and on, but I'll pause for now... 😄

That’s the core of JTBD. It’s not about what your product does.

It’s about the progress it enables.

Once you shift to that mindset, everything changes:

• Roadmaps start making sense
• Positioning gets sharper
• Messaging clicks
• Segments stop being vague personas

Outcome-Driven Innovation: JTBD with Teeth 💡

Anthony Ulwick’s book Jobs to Be Done: Theory to Practice lays out a method that’s insanely underrated in product circles: Outcome-Driven Innovation (ODI).

It’s JTBD, but with process, and a spreadsheet-ready playbook.

Here’s the quick and dirty version:

1. Define the job → What progress is the user trying to make? (Not “use CRM”, but “close deals faster”)
2. Map the job → Break it into steps (e.g. identify lead → qualify → outreach → close).
3. List the desired outcomes → What does “done well” mean at each step? (e.g. minimize time to qualify).
4. Measure importance vs. satisfaction → What matters most and is least satisfied today?
5. Segment by unmet needs → Not everyone struggles with the same things.
6. Prioritize solutions based on jobs → Not features. Not personas. Jobs.

And yes... this works even if you’re early-stage.

You don’t need 10,000 users to ask good questions.

You need 5 good real conversations and a willingness to listen for the job, not the feature request 👂

Jobs-to-be-Done Book | FREE PDF | Ulwick | JTBD Framework

Tony Ulwick’s latest Jobs-to-be-Done book, JTBD: Theory to Practice, details proven Outcome-Driven Innovation methods. Get this framework + tutorial FREE.

IDEA BITE PRESSAnthony Ulwick

Who Needs JTBD?

Short answer: anyone responsible for product, growth, or messaging.

Let’s break it down:

• PMs → for roadmap clarity
• Founders → for product-market fit
• UX teams → for real empathy
• Marketers → for better headlines
• Growth → for smarter segmentation
• CPOs → for strategic focus

JTBD = clarity at every layer.

From the story you tell → to the feature you build → to the upgrade you drive.

Real Talk: SaaS (and beyond) Loves JTBD 🔄

SaaS is a natural home for JTBD because:

• Jobs don’t change often
• Outcomes are measurable
• Retention = job success

But let’s not get boxed in.

The same logic applies if you’re selling hardware, services, or even content.

Example:

You’re not selling a kettle.
You’re helping someone “make a hot drink with zero effort.”
That’s why Keurig ate kettle makers’ lunch.

Focus on the job, not the tool.

Your Next Step: Steal This JTBD Starter Flow 🌊

Wanna bring JTBD into your workflow this quarter?

Start here:

🌟 Ask your users:

“What were you really trying to get done when you used our product?”
(Hint: It’s not ’use our dashboard’)

🌟 Map the journey:

Break the job into 6-10 steps.
Look for friction, workarounds, and emotional moments.

🌟 Capture desired outcomes:

For each step, ask: what does success look like?
Use language like “minimize time to…” or “reduce likelihood of…”

🌟 Prioritize based on gap:

What’s important AND underserved?
That’s your feature priority, your GTM hook, your next experiment.

🌟 Build and message around the job

Not just “we do X.”
But 👇

The Takeaway 💥

The job is the true north.

Get it right, and everything aligns: product, copy, positioning, retention, even pricing. Because when you understand the job, you don’t need to guess what to build.

You know what to build and how to sell it.

TL;DR: JTBD is the cheat code for clarity 👀

• People don’t want your product. They want a result.
• JTBD helps you figure out what result, why now, why you.
• It’s not just theory, it’s a process. ODI gives you the map.
• Start small. Talk to users. Listen for outcomes.
• Then build with laser focus.

Let's connect 🤝

Ready to stop guessing and start building with laser focus?

If you need help embedding JTBD into your team’s product, messaging, or growth strategy. I’m here to help you skip the line. I help teams go from fuzzy ideas to clear customer value through coaching, workshops, or just the right questions.

→ Book a call → Connect on LinkedIn → Or visit velonova.io

Or, if you prefer, reply with “JTBD me.” I’m in 🧠

P.S. If this piece was forwarded to you, feel free to subscribe to this newsletter, where business and product meet. No fluff. Just lessons you can apply tomorrow.

See ya!