Using Jira for Jobs-to-Be-Done (JTBD)
Industry standard for software development teams — most PMs will encounter Jira in their career. When combined with Jobs-to-Be-Done (JTBD), this makes Jira a strong candidate for teams who want a structured, repeatable workflow without sacrificing flexibility. Jobs-to-Be-Done (JTBD) works best in Jira when you leverage its idea management to implement the framework's key practices directly in the tool your team already lives in.
JTBD frames product decisions around the functional, emotional, and social "jobs" customers hire a product to accomplish. Discovery focuses on the job, not the demographic.
How to set up Jobs-to-Be-Done (JTBD) in Jira
Create a JTBD research repository
Create a project in Jira named "JTBD Research". Each card represents one interview or research session. Use labels for: Job Executor, Job Category (Functional/Emotional/Social), and Outcome Importance (High/Medium). Custom fields work well here.
Define and map Job Stories
In Jira, create a dedicated space for Job Stories using the format: "When [situation], I want to [motivation], so I can [expected outcome]." These replace user stories in a JTBD workflow. Add a custom field for "Opportunity Score" (importance − satisfaction rating from research).
Map outcomes to product features
On your Jira roadmap, link each initiative back to one or more Job Stories. Avoid shipping features that don't connect to a validated job. The roadmap should be readable as a list of jobs you're making easier, not a list of features you're adding.
Create a competition map
In Jira, create a simple table or board representing the jobs your product handles and the competing solutions (including non-consumption and workarounds). Use fields for: Competing Solution, How Well It Serves the Job (1–5), and Our Opportunity Score.
Which Jira features matter for Jobs-to-Be-Done (JTBD)
Jira has 1 of 2 core Jobs-to-Be-Done (JTBD) features natively.