Design Principles
Jobs to Be Done
People "hire" a product to get a job done — frame the experience around the job, not the features.
Where it comes from
The lens is most associated with Harvard professor Clayton Christensen, who illustrated it with the story of a fast-food chain discovering that customers were 'hiring' its milkshakes to make a dull morning commute more bearable — a job that had little to do with the drink's flavour.
Why it matters for your website
People don't want your product — they want the job it does for them. The Jobs-to-Be-Done lens, from Christensen's work, says customers "hire" a product to make progress on a specific job in their life. Pages framed around features ("what it is") rather than the job ("what it does for you") force the visitor to do the translation, and many won't bother.
The shift is from what your product is to what progress the customer is trying to make. People don't buy a drill because they want a drill; they buy it because they want a hole — and really, because they want the shelf the hole is for. A page that describes the drill leaves the visitor to connect it to the shelf themselves.
Framing around the job also clarifies who you're really competing with. The milkshake competed not with other milkshakes but with bananas and boredom. Understanding the job — the actual progress sought — tells you what to emphasise and what the visitor is genuinely weighing.
Wrong vs right
A page that lists what the product is and does ('AI-powered analytics platform with 200 integrations') and leaves the visitor to infer why they'd care.
A page framed around the job ('find out which marketing actually drives sales, by Friday'), so the progress is obvious.
Feature-led copy that describes capabilities in the product's terms rather than the customer's situation.
Copy that names the job the visitor is trying to get done and shows the product making that progress.
Comparing only against direct competitors, missing the real alternatives the customer is weighing.
Understanding the actual job, so the page addresses what the visitor is really choosing between.
Understanding Jobs to Be Done
Jobs to Be Done reframes what a customer is doing when they use a product. In this view, people don't buy products for their own sake — they 'hire' them to make progress on a specific job in their life. The job is the goal, the circumstance, and the desired outcome; the product is just one possible way to get it done.
Clayton Christensen's milkshake story is the canonical illustration: a chain studying who bought milkshakes in the morning found customers were hiring them for a long, dull commute — they wanted something filling, one-handed, and slow to finish. That job reframed everything, from the product to the competition (boredom and bananas, not other milkshakes).
For a web page, the lesson is to frame around the job, not the features. A page that catalogues what a product *is* forces the visitor to translate features into the progress they actually want; a page framed around the job does that translation for them. Visitors aren't shopping for capabilities — they're trying to work out whether their situation will be different. It connects to outcomes over output, benefit framing, and the value proposition.
How Kweri checks it
Whether a page is framed around the customer's job rather than the product's features is largely an editorial and strategic judgement, and Kweri treats it as guidance. It can prompt the question — does this page describe what the product *is*, or the progress the visitor is trying to make? — and flag heavily feature-led copy. But knowing the actual job your customers are hiring you for requires understanding your audience, which a static review can't supply. So Kweri surfaces feature-led framing and prompts the jobs question, while the real insight comes from knowing your customers.
FAQ
What is Jobs to Be Done?
Jobs to Be Done is a lens that frames products as things people 'hire' to make progress on a specific job in their life. Customers don't want the product itself; they want the outcome it delivers. It's most associated with Clayton Christensen.
What is the milkshake example?
Clayton Christensen described a fast-food chain discovering that morning milkshake buyers were 'hiring' the drink to make a long, dull commute more bearable — wanting something filling and slow to finish. The job, not the flavour, explained the purchase.
How do I apply Jobs to Be Done to a web page?
Frame the page around the progress the visitor is trying to make, not the product's features. Name the job, the situation, and the desired outcome, so the visitor immediately sees how their situation would change — rather than having to translate features themselves.
Why is feature-led copy a problem?
Because it describes the product in its own terms and leaves the visitor to work out why they'd care. Many won't bother. Framing around the job does that translation for them, connecting the product directly to the outcome they want.
How does Jobs to Be Done help with competition?
It reveals the real alternatives. Christensen's milkshake competed with bananas and boredom, not other milkshakes. Understanding the job clarifies what the customer is genuinely weighing, so the page can address the right comparison.
Related principles
The most powerful reason to return to a product is an emotional itch it has trained users to associate with it — boredom, loneliness, uncertainty, FOMO.
Visitors buy the outcome the product creates, not the product itself — copy that leads with what a user gains beats copy that leads with what a product does.
A visitor must be able to understand what a site offers, who it's for, and why it's the right choice — within 10 seconds and without working hard to decode it.
Attribution & sources
Identified by Clayton Christensen. Catalogued from Jobs to Be Done (Clayton Christensen).
A framework most associated with Clayton Christensen's work on innovation; there's no single canonical web source.
See Jobs to Be Done on your own site
Run a free Kweri audit — a plain-English review of your site’s speed, accessibility, SEO and design, ranked by what to fix first. No login, no jargon.
Run a free audit →