WORKSHOP — HALF-DAY SPRINT · $497

Half a day. Leave with 8–12 customer jobs mapped, your backlog ranked against what actually drives retention, and 2–3 unmet jobs your roadmap is currently ignoring.

A structured 4-hour session via Zoom. Your team maps the real jobs your customers hire your product to do, then classifies your backlog against those jobs using the Kano model. You walk out with a prioritised roadmap input your whole team built together — and can actually defend.

Jake McMahon Jake McMahon, ProductQuant
Book the sprint →

SPRINT DETAILS

Duration 4 hours on Zoom
Participants 2–6 people
Pre-work 1 hour async — so we work with your real data
Recording Full session recorded

$497 one-time · no recurring fee

Delivered by Jake McMahon · Founder, ProductQuant · 8+ years B2B SaaS product analytics · Australian product leader
⏱
Duration
4 hours (half-day)
👥
Format
Live via Zoom, 2–6 participants
📋
Deliverable
JTBD map + ranked backlog + 30-day plan
💰
Price
$497 whole team
The Problem

You know what the debate sounds like. It happens every sprint.

Sprint planning starts. You present three priorities. The head of sales says customers are asking for X — they heard it twice this week and wrote it down. The engineer says the platform has real technical debt that’s slowing everything down. You have your own read on what matters. Nobody is wrong. Nobody agrees. You spend 45 minutes on a conversation you’ve had before, and you end the meeting with a roadmap that looks roughly the same as it did going in.

The backlog isn’t empty. It’s overflowing. The problem isn’t that you have nothing to build — it’s that you have no shared language for deciding what to cut. Every item has a champion. Every cut feels like a loss. So the list grows, nothing ships cleanly, and the team spends more time negotiating priorities than executing them.

The thing nobody says out loud: the debate keeps happening because the underlying question hasn’t been answered. What are your customers actually trying to accomplish? Not the features they’ve requested — the functional jobs they hired your product to do.

When that question has a documented, team-built answer, the debate changes. You’re no longer arguing opinions against opinions. You’re checking items against evidence. That’s what this sprint produces.

Before & After

What changes after the sprint.

Before the sprint
  • Every sprint planning ends with the same debate — no shared language to decide what to cut
  • Features ship based on whoever argued loudest, not what customers actually need
  • No documented answer to what your customers are trying to accomplish
After the sprint
  • 8–12 jobs documented in functional terms — a shared language your whole team can use
  • Backlog ranked by retention impact: must-haves, delighters, and dead weight clearly separated
  • 2–3 unmet jobs identified with evidence and a 30-day validation plan ready to execute
Outcomes

Four outputs built live with your team. On your actual backlog.

✓8–12 jobs-to-be-done mapped
Jobs synthesised from your actual customer conversations — stated in functional terms your whole team can work from.
✓Backlog ranked by retention impact
Every feature classified: must-haves vs delighters vs dead weight. Clear criteria for what to cut at the next planning session.
✓2–3 unmet jobs identified
The highest-leverage opportunities in your market — jobs important to customers but not well served by your product or any competitor.
✓30-day discovery plan
A concrete plan for the next 30 days: which job to focus on, what evidence to gather, and what Monday morning looks like for your team.

The mapped jobs tell you what to build. The ranked backlog tells you what to build first. The 30-day plan tells you what to validate before committing.

8–12 core jobs-to-be-done mapped from your customer evidence
Not hypothetical jobs pulled from a framework doc — jobs synthesised from your actual customer conversations, sales calls, and support tickets. Each job is stated in functional terms: what the customer is trying to accomplish, not how they want to accomplish it.
Backlog ranked by retention impact — must-haves vs delighters vs dead weight
Every feature in your backlog mapped against the jobs that emerged from the sprint. You’ll know which features are threshold requirements, which are genuine differentiation opportunities, and which are consuming roadmap capacity without moving any needle your customers care about.
2–3 unmet jobs your product is positioned to own
The jobs that are currently important to your customers but not well served by your product or any competitor. These are the highest-leverage opportunities in your market — identified through the sprint, not through guesswork. What you do about them is a longer conversation, but you’ll have the evidence to have it.
A 30-day discovery plan to validate the top job with your team
A concrete plan for the next 30 days: which job to focus on, what evidence to gather, which customer segments to talk to, and what the validation questions look like. The sprint identifies the opportunity; this plan tells your team what to do on Monday morning.
Sprint Format

Live, structured, built for small product teams.

Duration
4 hours
A focused half-day block via Zoom. Structured in four phases: evidence review, job mapping, Kano classification, and discovery planning.
Participants
2–6 people
Small enough to keep the mapping session productive. Works best with product + one person from sales or CS who has direct customer context.
Pre-work
1 hr async
You invest 1 hour before we start. That hour is what means we work with your real customer data — not opinions in the room. The structured exercise takes each participant through collecting evidence from sources they already have.
Recording
Included
Full session recorded and shared with the whole team. Refer back to the job mapping discussion at any point.
Facilitation
Jake live
Jake facilitates the full session, running the job mapping exercises and the Kano classification in real time with your team.
Scheduling
Flexible
Book a discovery call to confirm the sprint date and pre-work instructions. Sprint typically runs within 2 weeks of booking.
Session Agenda

How the 4 hours runs.

01
Evidence review (45 min)
Each participant shares what they collected in pre-work — sales call notes, support tickets, churn interviews. Jake synthesises the patterns as a group.
02
Job mapping (90 min)
The core of the sprint. Jake facilitates the JTBD mapping exercise: surfacing functional jobs from the evidence, naming them precisely, and building the team-agreed list of 8–12 jobs.
03
Kano backlog classification (60 min)
Every item in your backlog mapped against the jobs that emerged. Jake runs the Kano classification: threshold requirements, delighters, and dead weight identified with evidence.
04
Discovery planning (45 min)
Jake identifies the 2–3 highest-value unmet jobs and builds the 30-day discovery plan with the team — what to validate, who to talk to, and what Monday morning looks like.
Fit

Who this sprint is built for — and who it isn’t.

Good fit
  • Product teams with a growing backlog where prioritisation debates happen every sprint and rarely resolve cleanly
  • Teams preparing a roadmap review or strategy offsite who want the discussion grounded in customer jobs, not opinions
  • PMs who’ve done user interviews but haven’t synthesised them into a structured jobs map their whole team can work from
Not the right fit
  • Teams without a shipped product yet — you need real customers and real usage to map real jobs
  • Teams looking to run user research for a new feature — this ranks what exists, not explores what to build new
  • Teams validating an idea from scratch — the Kano classification works on a live backlog, not a hypothesis list
Social Proof

What teams walk away with.

“Placeholder — replace with a real quote from a past session participant.”

Name, Title
Company

“Placeholder — replace with a real quote from a past session participant.”

Name, Title
Company

“Placeholder — replace with a real quote from a past session participant.”

Name, Title
Company
Pricing

One sprint. One price. Whole team included.

Per Sprint (whole team)
$497

One-time payment. No recurring fee. Up to 6 participants included.

A half-day with a product strategy consultant runs $1,000–$2,500. This costs $497 for your whole team and delivers a structured, documented output you own.

  • 4-hour facilitated Zoom sprint with Jake McMahon
  • Pre-work exercise for all participants — so we start with real data
  • 8–12 core jobs-to-be-done mapped and documented
  • Kano classification of your current backlog
  • 2–3 unmet jobs identified with evidence
  • 30-day discovery plan for the top job
  • Full session recording
Book the sprint →
30-day guarantee: if the sprint doesn’t deliver 8+ mapped jobs and a ranked backlog, you’ll get a full refund.
Common Questions

Questions.

Or book directly →
What customer evidence do we need to bring? +
The pre-work exercise guides participants through collecting evidence from sources they already have: sales call notes, support conversations, churn interviews, or user interviews. You don’t need a formal research library. Even a handful of structured customer conversations is enough to run a productive sprint.
Who should we bring to the sprint? +
The most productive combination is product + someone from sales or CS who has direct customer contact. A founder or CEO can replace either role. No more than 6 participants — the job mapping exercise becomes unproductive above that number.
Is this the same as a design sprint? +
No. A design sprint focuses on prototyping and testing a solution. The JTBD Sprint focuses on understanding what customers are actually trying to accomplish before deciding what to build. The outputs are different: you leave with job maps and backlog classification, not wireframes or prototypes.
What if we have more than 6 people who want to join? +
The sprint works best with the core product team. If you want to include a broader group, get in touch before booking and we can discuss a custom format.
How does this connect to roadmap planning? +
Directly. The Kano classification maps your existing backlog against real customer jobs, so you can walk into the next planning cycle with evidence for which items belong in the roadmap and which should be deprioritised. The 30-day discovery plan gives you a structured path to validate before committing. The mapped jobs tell you what to build. The ranked backlog tells you what to build first.

Your next sprint planning meeting is coming.

You can walk into it with the same debate you had last time. Or you can walk in with 8–12 mapped jobs and a ranked backlog. Half a day is the difference.

4 hours · $497 one-time · whole team included

Book the sprint →