Using Trello for Jobs-to-Be-Done (JTBD)
Extremely intuitive drag-and-drop Kanban interface — virtually zero learning curve, new users productive within minutes. When combined with Jobs-to-Be-Done (JTBD), this makes Trello a strong candidate for teams who want a structured, repeatable workflow without sacrificing flexibility. Jobs-to-Be-Done (JTBD) works best in Trello when you leverage its core workflow features 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 Trello
Create a JTBD research repository
Create a project in Trello 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 Trello, 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
In the backlog, tag each user story or initiative with the parent Job Story it addresses. If an item doesn't connect to a validated job, add a "Needs JTBD Validation" label before it enters sprint planning.
Create a competition map
In Trello, 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 Trello features matter for Jobs-to-Be-Done (JTBD)
Trello has 0 of 2 core Jobs-to-Be-Done (JTBD) features natively.