Back to the Playbook
Strategy & DiscoverySD-11
How to prioritise using jobs-to-be-done
Prioritise important underserved jobs before mapping solutions; preserve the difference between customer evidence and team guesses.
Product statusAssisted workflowImportance and satisfaction are collected from your customers; Teklens frames the jobs and runs the comparison on the responses you bring.
Input3 required inputsRecent behaviour-based research · Importance and satisfaction responses · Initiative focus and approved Product Brain guidance
SkillsPrioritise customer jobs · Prepare task contextResearcher + Product Researcher Agent
OutcomeJTBD priority list: job map, importance and satisfaction evidence, opportunity comparison with its formula, and the chosen job.Artifact: JTBD priority list
Owner
Researcher
Human-led
Participants · Agents
Product ManagerProduct Researcher Agent
Trigger
Customer jobs and candidate product investments compete for attention.
Required context
Customer evidenceRecent behaviour-based researchFilesImportance and satisfaction responsesProduct BrainInitiative focus and approved Product Brain guidance
Optional context
JiraCandidate investmentsCustomer evidenceKnown workarounds and alternatives
Skills
Prioritise customer jobsPrepare task context
Suggested conversation arc
- 1Frame the jobs to compareExtract user goals as verb, object and situation from behavioural evidence, avoiding feature requests disguised as jobs.Skills: Prepare task context · Prioritise customer jobs
- 2Collect importance and satisfactionAsk relevant customers about importance and satisfaction with current alternatives, including workarounds. Retain the segment and comparable scales; do not substitute invented responses.
- 3Compare underserved opportunitiesCompare importance and satisfaction using the agreed method and its disclosed formula. Show raw responses, uncertainty and segment differences alongside the opportunity ranking.Skills: Prioritise customer jobs
- 4Choose the job to addressSelect which important underserved job merits investment, then map candidate solutions to it. Record exceptions and further research needed.
Output
JTBD priority list: job map, importance and satisfaction evidence, opportunity comparison with its formula, and the chosen job.
Artifacts
Creates: JTBD priority list
What good looks like
- Jobs express user goals rather than interface tasks.
- Scoring method and provenance are explicit and reproducible.
- No invented scores without measured responses.
Quality gate
The Product Manager chooses the job that merits investment.
Destination
Product BrainRoadmap
Usually next
People and agents work from the same Product Brain. The owner stays accountable. Assigned agents prepare and check. A named person approves at the gate.
Choose the path that matches your role.
Set the Product AI direction with us, or test the shared Product Brain on real work with Jira and code.