“People don’t want a quarter-inch drill. They want a quarter-inch hole.”— Theodore Levitt, paraphrased; later sharpened by Clayton Christensen as “jobs to be done.”
What it means
Your customer is not paying you for what you make. They are paying you for what changes in their life when they use it. The drill is the deliverable; the hole is the job. The drill exists in your warehouse; the job exists in their kitchen wall.
This reframe is uncomfortable because it makes most product roadmaps look beside the point. A roadmap full of features is a list of drills. A roadmap shaped by jobs-to-be-done is a list of holes that need to exist for someone, on a particular day, for a particular reason. Most teams discover, when they sit down and try to write the latter, that they have been arguing about the wrong thing for months.
Deming reached the same place by a different road. He told executives the customer is not buying the product; the customer is buying the result of the production system. If the system can’t articulate the result, the system is shipping blindly.
The shape of a good job-to-be-done
- It names an outcome, not a feature.“Get a paycheck inside two weeks of applying” beats “match drivers to recruiters.” The first is what the customer is buying; the second is what you happen to do.
- It is in the customer’s voice.If your aunt could read it and understand without further explanation, you’re close. If she needs a glossary, you’re still in vendor-speak.
- It survives the technology change.Drills become drill bits become laser cutters. The hole stays. A job that doesn’t survive a technology pivot wasn’t a job — it was a delivery mechanism.
- It tells you who you compete with.If the job is “put a picture on the wall,” your competition is double-stick tape and a bare wall. That’s a real strategic insight. “Drill manufacturers” is not.
Why CenterLeap asks for this third
We already know why you exist (purpose) and for whom (customer). The job is the third leg: what is that customer paying you to accomplish? It pins the first two to the floor.
Once the job is named, every feature decision has a fast test: does this make the job easier, faster, cheaper, more reliable — or none of the above? Most teams discover their backlog is crowded with “none of the above” once they bother asking.