Using Slack for Jobs-to-Be-Done (JTBD)
De facto standard for workplace communication — most PMs will use Slack daily, and it appears constantly in job descriptions. When combined with Jobs-to-Be-Done (JTBD), this makes Slack a strong candidate for teams who want a structured, repeatable workflow without sacrificing flexibility. Jobs-to-Be-Done (JTBD) works best in Slack 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 Slack
Create a JTBD research repository
Create a project in Slack 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).
Define and map Job Stories
In Slack, 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. Use a numbered priority in the task title to reflect opportunity score.
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 Slack, create a simple table or board representing the jobs your product handles and the competing solutions (including non-consumption and workarounds). Use card descriptions to document how each competing solution serves each job and where your product's opening is.
Which Slack features matter for Jobs-to-Be-Done (JTBD)
Slack has 0 of 2 core Jobs-to-Be-Done (JTBD) features natively.