JTBD

The job, not the ask

A JTBD captures the underlying job a user is trying to get done - the progress they are seeking in a given situation - rather than the specific feature or solution they asked for. Unlike a feature request (which records a proposed solution) or a pain point (which records a symptom), a JTBD abstracts up to the motivation and desired outcome, along with the context that triggers it and the workaround the user relies on today. This makes it a durable, solution-agnostic input for prioritization and product strategy.

Get Tana

Related outcomes

Action item
Two teams blocked on the Atlas Cloud API
Due date
Jul 11
Product area
Autonomy
Mei will teach the Mission Planner to factor crosswind power draw into the battery-margin estimate, so a plann…
Action item
NorthGrid renewal at risk before winter inspections
Due date
Jul 11
Product area
Autonomy
Mei will teach the Mission Planner to factor crosswind power draw into the battery-margin estimate, so a plann…
Action item
Model cold-crosswind battery draw in the route planner
Due date
Jul 11
Product area
Autonomy
Priority
High
Mei will teach the Mission Planner to factor crosswind power draw into the battery-margin estimate, so a plann…
Action item
Every commitment from a meeting, with an owner, a due date, and the source it came from.
Decision
Capture what you decided, why, and what you ruled out.
Open question
Every unresolved question captured, with a name attached to it.
Risk
Capture a threat to an objective with its likelihood, impact, and mitigation plan.

JTBD

Keep an inspection window on track when the weather turns

Related outcomes

Two teams blocked on the Atlas Cloud API

NorthGrid renewal at risk before winter inspections

Model cold-crosswind battery draw in the route planner

Action item

Pull forward explainable anomaly confidence before winter

Decision

Should crews be able to override a severe anomaly on-site?

Open question

Champion at NorthGrid leaving before the renewal

Risk