Jobs to Be Done gives a growth-driven design strategy its organizing question: what progress is a visitor trying to make when they arrive, and what will they hire a page to accomplish [1][4]. Clayton Christensen's research reframed buying as hiring a product to do a job, with functional, social, and emotional dimensions that demographics alone cannot explain [1]. The GDD strategy stage lists Jobs to Be Done beside UX research, buyer personas, and customer journey mapping as core components, so the job becomes the unit that page strategy is built around [4]. User research supplies the evidence: quantitative audits show where visitors stall, and qualitative interviews reveal the circumstance and desired outcome behind the job [5]. Those findings turn into problem statements, journey maps, and page messaging that the launchpad site then validates with live traffic [5][6].
\n","summary":"The milkshake story explains more about website strategy than most redesign briefs do. This answer connects Jobs to Be Done theory, from Christensen's hiring framing to Strategyn's outcome-driven practice, to the research steps inside the growth-driven design strategy stage: how job interviews are run, how jobs and personas differ and combine, and how a discovered job becomes a problem statement, a buyer journey, and the messaging on each page a launchpad can test.","publishedAt":"2026-07-17T14:26:31.319","verifiedAt":"2026-07-17T00:00:00","editorialStatus":"APPROVED","lastReviewedAt":"2026-07-17T14:26:31.179","nextReviewDueAt":"2027-01-17T00:00:00","templateVersion":"v2","aliases":["jobs to be done website strategy","JTBD in growth-driven design","jobs to be done user research web design","milkshake framework website design","JTBD vs personas website","user research in GDD strategy phase","applying jobs theory to web design","how to run jobs to be done interviews","jobs to be done buyer journey","job stories vs personas","customer jobs website messaging","outcome-driven innovation web design"],"confidenceScore":85,"confidenceLabel":"High","canonicalUrl":null},"contributor":{"id":"dc83f9a1-5273-4639-bffb-43d5fa44c2bf","slug":"lean-labs","displayName":"Lean Labs","websiteUrl":"https://lean-labs.com/","sameAs":["https://lean-labs.com/","https://www.linkedin.com/company/lean-labs"]},"contributorOrganizationProfile":{"entityId":"dc83f9a1-5273-4639-bffb-43d5fa44c2bf","legalName":null,"description":"Lean Labs is a HubSpot Diamond Solutions Partner that helps B2B SaaS startups and scaleups grow through AI-powered marketing services, including lead generation websites, Answer Engine Optimization (AEO), and Loop Marketing. Founded in 2013, the company combines expert strategy with AI agents to deliver scalable, high-ROI growth systems for funded startups from Seed to Series C.","websiteUrl":"https://lean-labs.com/","imageUrl":"https://www.leanlabs.com/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Flogo.0d6c5685.png&w=256&q=75","sameAs":["https://lean-labs.com/","https://www.linkedin.com/company/lean-labs"],"slogan":"Experts at strategy, marketing, design and development augmented by AI","subtitle":"Growth marketing agency ยท HubSpot partner","facts":["Practicing GDD on client sites since 2017","Contributes published answers on 3 topics: Growth-Driven Design, Growth-Driven Design for B2B, Answer Engine Optimization"],"coiNote":"Sells services in this topic. All answers reviewed independently.","foundingDate":"2013-01-01T00:00:00","numberOfEmployeesText":null,"contactPoint":{"email":"hello@lean-labs.com","contactType":"sales"},"address":{"city":"Land O' Lakes","state":"FL","country":"US","postalCode":"34638","addressType":"operational","streetAddress":"16703 Early Riser Ave, Suite 111"},"headquartersText":"Land O' Lakes, FL, US","organizationType":null},"contributorPerson":{"slug":"kevin-barber","displayName":"Kevin Barber"},"sections":[{"id":"4f04e6ec-c153-4d7a-98d0-deb80dbece96","sectionKey":"jtbd_explainer","sectionType":"markdown_section","heading":"What is Jobs to Be Done?","introMarkdown":"Jobs to Be Done is the theory that people buy products to make progress in a specific circumstance, not because of who they are demographically. Clayton Christensen and his co-authors stated it plainly in Harvard Business Review: when we buy a product, we essentially hire it to help us do a job, and if it does the job well, we hire it again [1]. The job is the progress a person is trying to make, the circumstance is the context that shapes it, and the alternatives are everything else that person could hire to make the same progress [1].\n\nThe canonical illustration is Christensen's milkshake study. A fast-food chain found that nearly half its milkshakes sold before mid-morning to solo commuters, who hired the shake over a bagel or a doughnut because it was tidy, it staved off hunger until lunch, and it gave a bored driver something to do on a long commute [2]. Demographic segmentation would never have surfaced that pattern, because the real competitor set was defined by the situation, a long boring drive plus looming late-morning hunger, and not by the buyer's age or income [2]. Two customers with identical profiles hired the milkshake for entirely different jobs at different times of day, which is the point: the job, not the demographic, predicts the purchase [1][2].\n\nStrategyn, the consultancy Tony Ulwick founded to operationalize the theory as outcome-driven innovation, defines a job as the task, goal, or objective a customer is trying to accomplish in a given situation, and ties customer-defined outcome metrics to that job so progress becomes measurable [3]. Christensen's article adds the dimension websites most often miss: a job is never purely functional, it carries social and emotional weight, how the buyer wants to be perceived and how they want to feel [1]. For a strategy stage, that is the useful part. If you know the functional job, the social job, and the emotional job a visitor is trying to get done, you know what every page has to accomplish before you write a single headline [1][3].","introHtml":"Jobs to Be Done is the theory that people buy products to make progress in a specific circumstance, not because of who they are demographically. Clayton Christensen and his co-authors stated it plainly in Harvard Business Review: when we buy a product, we essentially hire it to help us do a job, and if it does the job well, we hire it again [1]. The job is the progress a person is trying to make, the circumstance is the context that shapes it, and the alternatives are everything else that person could hire to make the same progress [1].
\nThe canonical illustration is Christensen's milkshake study. A fast-food chain found that nearly half its milkshakes sold before mid-morning to solo commuters, who hired the shake over a bagel or a doughnut because it was tidy, it staved off hunger until lunch, and it gave a bored driver something to do on a long commute [2]. Demographic segmentation would never have surfaced that pattern, because the real competitor set was defined by the situation, a long boring drive plus looming late-morning hunger, and not by the buyer's age or income [2]. Two customers with identical profiles hired the milkshake for entirely different jobs at different times of day, which is the point: the job, not the demographic, predicts the purchase [1][2].
\nStrategyn, the consultancy Tony Ulwick founded to operationalize the theory as outcome-driven innovation, defines a job as the task, goal, or objective a customer is trying to accomplish in a given situation, and ties customer-defined outcome metrics to that job so progress becomes measurable [3]. Christensen's article adds the dimension websites most often miss: a job is never purely functional, it carries social and emotional weight, how the buyer wants to be perceived and how they want to feel [1]. For a strategy stage, that is the useful part. If you know the functional job, the social job, and the emotional job a visitor is trying to get done, you know what every page has to accomplish before you write a single headline [1][3].
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":0},{"id":"3404de13-6c4e-4b54-8d49-97473c7d13d0","sectionKey":"jtbd_in_gdd","sectionType":"markdown_section","heading":"Where does Jobs to Be Done fit in a growth-driven design strategy?","introMarkdown":"Jobs to Be Done is a named component of the growth-driven design strategy stage, listed alongside UX research, buyer personas, and customer journey mapping in the methodology's strategy framework [4]. GDD front-loads this research before any building, because the strategy stage produces the assumptions the rest of the process will test [5]. The work is time-boxed, usually 10 to 14 days, so the goal is enough job clarity to launch a testable site rather than a finished catalog of every customer motivation [6].\n\nThe practical move is to treat every key page as something a visitor hires. A pricing page is hired to answer whether this will fit the budget without booking a sales call. A case study page is hired to de-risk a recommendation the visitor has to defend to a boss or a committee. A homepage is hired to confirm, in a few seconds, that this company serves someone in exactly their situation. Framing pages this way changes what the strategy prioritizes. Journey mapping stops being a diagram of your funnel and becomes a map of the visitor's progress from first struggling moment to confident decision, built on their needs and pain points rather than your internal org chart [4]. The fundamental assumptions the strategy documents, beliefs about what visitors want and how they look for it, are really hypotheses about the job, and the launchpad site exists to confirm or kill them with live behavior [5][6].","introHtml":"Jobs to Be Done is a named component of the growth-driven design strategy stage, listed alongside UX research, buyer personas, and customer journey mapping in the methodology's strategy framework [4]. GDD front-loads this research before any building, because the strategy stage produces the assumptions the rest of the process will test [5]. The work is time-boxed, usually 10 to 14 days, so the goal is enough job clarity to launch a testable site rather than a finished catalog of every customer motivation [6].
\nThe practical move is to treat every key page as something a visitor hires. A pricing page is hired to answer whether this will fit the budget without booking a sales call. A case study page is hired to de-risk a recommendation the visitor has to defend to a boss or a committee. A homepage is hired to confirm, in a few seconds, that this company serves someone in exactly their situation. Framing pages this way changes what the strategy prioritizes. Journey mapping stops being a diagram of your funnel and becomes a map of the visitor's progress from first struggling moment to confident decision, built on their needs and pain points rather than your internal org chart [4]. The fundamental assumptions the strategy documents, beliefs about what visitors want and how they look for it, are really hypotheses about the job, and the launchpad site exists to confirm or kill them with live behavior [5][6].
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":1},{"id":"e3442982-576a-4435-8c60-d94f11ed7091","sectionKey":"personas_vs_jtbd","sectionType":"table_section","heading":"How do Jobs to Be Done and personas differ?","introMarkdown":"Personas and Jobs to Be Done answer different questions, and a growth-driven design strategy uses both rather than choosing one [1][4]. A persona describes who the buyer is; a job describes what progress that buyer is trying to make. The table summarizes the split, and the prose below explains how the two combine in practice.","introHtml":"Personas and Jobs to Be Done answer different questions, and a growth-driven design strategy uses both rather than choosing one [1][4]. A persona describes who the buyer is; a job describes what progress that buyer is trying to make. The table summarizes the split, and the prose below explains how the two combine in practice.
\n","outroMarkdown":"The two lenses cover each other's blind spots. Christensen's team was direct about the risk of personas used alone: a correlation between an attribute and a purchase, a certain job title tends to buy, does not explain why the purchase happens, so a strategy built only on attributes optimizes for the wrong thing [1]. Jobs restore the causal reason, the circumstance and the progress, which is what tells you what a page has to say. Personas, in turn, keep the job grounded in a real audience: the same job to evaluate a vendor quickly reads differently for a cautious procurement lead than for a hands-on founder, and that difference drives tone, proof, and price framing. In a GDD strategy, you use the job to decide what each page must accomplish and the persona to decide how it should sound. Neither is optional, and a strategy that keeps only personas often ends up describing its audience without ever stating what those people came to get done [1][4].","outroHtml":"The two lenses cover each other's blind spots. Christensen's team was direct about the risk of personas used alone: a correlation between an attribute and a purchase, a certain job title tends to buy, does not explain why the purchase happens, so a strategy built only on attributes optimizes for the wrong thing [1]. Jobs restore the causal reason, the circumstance and the progress, which is what tells you what a page has to say. Personas, in turn, keep the job grounded in a real audience: the same job to evaluate a vendor quickly reads differently for a cautious procurement lead than for a hands-on founder, and that difference drives tone, proof, and price framing. In a GDD strategy, you use the job to decide what each page must accomplish and the persona to decide how it should sound. Neither is optional, and a strategy that keeps only personas often ends up describing its audience without ever stating what those people came to get done [1][4].
\n","contentJson":{"rows":[{"cells":["Core question","Who is the buyer?","What progress is the buyer trying to make in this circumstance? [1]"]},{"cells":["Built from","Role, firmographics, goals, and common objections","The struggling moment, the desired outcome, and the alternatives the buyer would otherwise hire [2][3]"]},{"cells":["Unit of analysis","A representative person","A situation and the progress it demands [1]"]},{"cells":["Failure mode","Correlates attributes with buying without explaining what causes it [1]","Can undervalue real differences in tone, budget, and authority between segments"]},{"cells":["Role in GDD strategy","Defines who the site serves and how it should speak [4]","Defines what each page must accomplish and what content earns the hire [4]"]}],"columns":["Aspect","Buyer persona","Job to Be Done"]},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":2},{"id":"5b32848a-ffe4-4cc0-a8e7-b2ec903cdd8e","sectionKey":"run_interviews","sectionType":"markdown_section","heading":"How do you run Jobs to Be Done interviews?","introMarkdown":"Jobs to Be Done interviews reconstruct the story of a real decision, in the buyer's own words, to surface the job behind it. The research splits into two halves in the GDD strategy stage: quantitative work that audits the current site and its analytics to find where visitors stall or exit, and qualitative interviews that explain what those visitors were trying to accomplish and why [5]. The interviews are where the job actually gets discovered rather than guessed.\n\nRecruit people who recently made the decision you care about, ideally within the last few months while memory is fresh, and interview across the accounts that matter: recent customers, people who chose a competitor, and people who chose to do nothing. Ask them to walk you back to the first moment they realized they had a problem, then forward through everything that happened up to the purchase. Productive questions mirror the milkshake study: what was going on when you first started looking, what did you try before this, what almost made you give up, and what finally pushed you to decide [2]. You are listening for the struggling moment, the desired outcome, the alternatives they weighed, and the anxieties that slowed them down.\n\nAvoid asking what people want or which features they would like, because those answers predict behavior poorly. Ask what they did and what happened, which is verifiable. Ten to fifteen focused interviews usually surface the dominant jobs and the language buyers use to describe them, and that language matters: the exact phrases customers repeat become the headlines and proof points a page needs later. The output is a short set of documented jobs and fundamental assumptions about motivation and information-seeking that then drive global and page-level strategy [5].","introHtml":"Jobs to Be Done interviews reconstruct the story of a real decision, in the buyer's own words, to surface the job behind it. The research splits into two halves in the GDD strategy stage: quantitative work that audits the current site and its analytics to find where visitors stall or exit, and qualitative interviews that explain what those visitors were trying to accomplish and why [5]. The interviews are where the job actually gets discovered rather than guessed.
\nRecruit people who recently made the decision you care about, ideally within the last few months while memory is fresh, and interview across the accounts that matter: recent customers, people who chose a competitor, and people who chose to do nothing. Ask them to walk you back to the first moment they realized they had a problem, then forward through everything that happened up to the purchase. Productive questions mirror the milkshake study: what was going on when you first started looking, what did you try before this, what almost made you give up, and what finally pushed you to decide [2]. You are listening for the struggling moment, the desired outcome, the alternatives they weighed, and the anxieties that slowed them down.
\nAvoid asking what people want or which features they would like, because those answers predict behavior poorly. Ask what they did and what happened, which is verifiable. Ten to fifteen focused interviews usually surface the dominant jobs and the language buyers use to describe them, and that language matters: the exact phrases customers repeat become the headlines and proof points a page needs later. The output is a short set of documented jobs and fundamental assumptions about motivation and information-seeking that then drive global and page-level strategy [5].
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":3},{"id":"642678c6-ffae-4f31-aa2f-49d3d8080b33","sectionKey":"jobs_to_problem_statements","sectionType":"markdown_section","heading":"How do jobs become problem statements?","introMarkdown":"A job becomes a problem statement when you write it from the visitor's side as the specific progress they are stuck trying to make. A useful format names the situation, the desired outcome, and the obstacle: when a marketing lead has to replace an aging website but cannot risk months of downtime, they want a way to ship improvements incrementally so they can show results before the budget is questioned. That sentence is testable in a way that 'we need a modern website' is not.\n\nProblem statements are the bridge between raw interview notes and page decisions. Each documented job produces one or more of them, and each statement carries the emotional and social stakes the interviews surfaced, not just the functional task [1]. In growth-driven design these become the fundamental assumptions the strategy records, explanations of user behavior and motivation that then shape global and page strategy [5]. Writing them explicitly forces two useful disciplines. First, it separates the job, which is stable, from your current solution, which is one of many the visitor could hire. Second, it exposes where you are assuming rather than knowing, which tells you what the launchpad site should measure first.\n\nKeep the set small. A strategy that tries to answer twenty problem statements at launch dilutes every page, so the point of the time-boxed strategy stage is to isolate the few jobs that drive most of the value, state them sharply, and let live data confirm or correct them during continuous improvement [6]. A problem statement that survives contact with real traffic becomes a permanent fixture of the site's messaging.","introHtml":"A job becomes a problem statement when you write it from the visitor's side as the specific progress they are stuck trying to make. A useful format names the situation, the desired outcome, and the obstacle: when a marketing lead has to replace an aging website but cannot risk months of downtime, they want a way to ship improvements incrementally so they can show results before the budget is questioned. That sentence is testable in a way that 'we need a modern website' is not.
\nProblem statements are the bridge between raw interview notes and page decisions. Each documented job produces one or more of them, and each statement carries the emotional and social stakes the interviews surfaced, not just the functional task [1]. In growth-driven design these become the fundamental assumptions the strategy records, explanations of user behavior and motivation that then shape global and page strategy [5]. Writing them explicitly forces two useful disciplines. First, it separates the job, which is stable, from your current solution, which is one of many the visitor could hire. Second, it exposes where you are assuming rather than knowing, which tells you what the launchpad site should measure first.
\nKeep the set small. A strategy that tries to answer twenty problem statements at launch dilutes every page, so the point of the time-boxed strategy stage is to isolate the few jobs that drive most of the value, state them sharply, and let live data confirm or correct them during continuous improvement [6]. A problem statement that survives contact with real traffic becomes a permanent fixture of the site's messaging.
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":4},{"id":"f19e7b6c-6be9-456d-8373-2171acef2024","sectionKey":"jobs_to_buyer_journey","sectionType":"markdown_section","heading":"How do jobs shape the buyer journey?","introMarkdown":"Jobs turn a buyer journey from a funnel diagram into a sequence of progress a visitor makes, one hire at a time. Growth-driven design maps the customer journey from the ideal customer's needs and pain points rather than from your internal sales stages, so each step reflects what the visitor is trying to get done at that moment [4]. A single decision usually spans several smaller jobs in sequence: understand whether this is even the right category, judge whether this vendor is credible, confirm the fit for their specific situation, and justify the decision to whoever else has to approve it.\n\nMapping the journey against jobs tells you how many pages a path actually needs and what each one owes the visitor. A visitor in a problem-aware moment hires content that names their situation and frames the options. A solution-aware visitor hires content that compares approaches and proves outcomes. A decision-ready visitor hires content that removes final risk: pricing clarity, guarantees, and proof from peers in the same circumstance. Skipping a step, pushing a cold visitor straight to a demo request, breaks the journey because the earlier job was never done.\n\nThe strategy documents these paths as global and page-level strategy, the structure the launchpad will build and then test [5]. Because growth-driven design launches quickly and improves continuously, the journey map is a starting hypothesis, not a finished artifact: live behavior shows where visitors actually stall between jobs, and each improvement sprint targets the transition that is losing the most people [6].","introHtml":"Jobs turn a buyer journey from a funnel diagram into a sequence of progress a visitor makes, one hire at a time. Growth-driven design maps the customer journey from the ideal customer's needs and pain points rather than from your internal sales stages, so each step reflects what the visitor is trying to get done at that moment [4]. A single decision usually spans several smaller jobs in sequence: understand whether this is even the right category, judge whether this vendor is credible, confirm the fit for their specific situation, and justify the decision to whoever else has to approve it.
\nMapping the journey against jobs tells you how many pages a path actually needs and what each one owes the visitor. A visitor in a problem-aware moment hires content that names their situation and frames the options. A solution-aware visitor hires content that compares approaches and proves outcomes. A decision-ready visitor hires content that removes final risk: pricing clarity, guarantees, and proof from peers in the same circumstance. Skipping a step, pushing a cold visitor straight to a demo request, breaks the journey because the earlier job was never done.
\nThe strategy documents these paths as global and page-level strategy, the structure the launchpad will build and then test [5]. Because growth-driven design launches quickly and improves continuously, the journey map is a starting hypothesis, not a finished artifact: live behavior shows where visitors actually stall between jobs, and each improvement sprint targets the transition that is losing the most people [6].
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":5},{"id":"56e19854-8807-403c-b603-d9c57fb8a4b4","sectionKey":"jobs_to_page_messaging","sectionType":"markdown_section","heading":"How do jobs shape page messaging?","introMarkdown":"Page messaging is where the job gets answered, so every core page should lead with the progress its visitor came to make. The discipline is simple to state and hard to hold: open each page by naming the job and the outcome, not the company or the feature. A visitor who hired the page to judge fit for a regulated industry should see that reassurance in the first screen, before any product tour.\n\nJobs decide three things on a page. They set the headline, which should restate the visitor's desired outcome in the visitor's own words, drawn from the phrases interviews surfaced. They set the proof, because most jobs include reducing the buyer's own risk, so each claim needs evidence a skeptic would accept: numbers, named results, and testimony from someone in the same situation. And they set the next step, which should match where the visitor sits in the journey rather than pushing everyone toward the same request.\n\nThis is also where social and emotional jobs earn their place [1]. A page that answers only the functional job, does the product do the task, often loses to one that also answers whether the choice will make the buyer look smart to their boss and whether they will feel confident they chose right. In growth-driven design, messaging is treated as a hypothesis: the launchpad ships the version that best fits the documented jobs, and continuous improvement tests headlines, proof, and calls to action against live behavior to see which framing of the job actually converts [5][6].","introHtml":"Page messaging is where the job gets answered, so every core page should lead with the progress its visitor came to make. The discipline is simple to state and hard to hold: open each page by naming the job and the outcome, not the company or the feature. A visitor who hired the page to judge fit for a regulated industry should see that reassurance in the first screen, before any product tour.
\nJobs decide three things on a page. They set the headline, which should restate the visitor's desired outcome in the visitor's own words, drawn from the phrases interviews surfaced. They set the proof, because most jobs include reducing the buyer's own risk, so each claim needs evidence a skeptic would accept: numbers, named results, and testimony from someone in the same situation. And they set the next step, which should match where the visitor sits in the journey rather than pushing everyone toward the same request.
\nThis is also where social and emotional jobs earn their place [1]. A page that answers only the functional job, does the product do the task, often loses to one that also answers whether the choice will make the buyer look smart to their boss and whether they will feel confident they chose right. In growth-driven design, messaging is treated as a hypothesis: the launchpad ships the version that best fits the documented jobs, and continuous improvement tests headlines, proof, and calls to action against live behavior to see which framing of the job actually converts [5][6].
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":6},{"id":"01546605-e914-4ea9-88a5-2c498a7905da","sectionKey":"contributor_perspective","sectionType":"markdown_section","heading":"How Lean Labs applies job thinking to buyer journeys","introMarkdown":"Lean Labs builds its growth-driven design strategy around a job-shaped model of awareness. The agency maps cold, warm, and hot audiences and designs page flows that move a visitor from problem-aware to solution-aware to product-aware, typically in two to four steps per core solution [7]. Founder Kevin Barber's position, developed across more than 100 builds as a HubSpot partner since 2013, is that roughly 80 percent of a website's success comes from messaging and buyer journey and only about 20 percent from custom design, which is another way of saying the site wins or loses on how well it understands the visitor's job [7].\n\nBarber's corollary is that proof beats polish. Because the visitor's job almost always includes reducing their own risk, Lean Labs argues that every claim on a page should carry a proof point, and that most sites lose deals because they were not trusted rather than because they were not seen. In that view, job research that surfaces what buyers need to believe, and what evidence would make them believe it, is worth more than another round of visual refinement.","introHtml":"Lean Labs builds its growth-driven design strategy around a job-shaped model of awareness. The agency maps cold, warm, and hot audiences and designs page flows that move a visitor from problem-aware to solution-aware to product-aware, typically in two to four steps per core solution [7]. Founder Kevin Barber's position, developed across more than 100 builds as a HubSpot partner since 2013, is that roughly 80 percent of a website's success comes from messaging and buyer journey and only about 20 percent from custom design, which is another way of saying the site wins or loses on how well it understands the visitor's job [7].
\nBarber's corollary is that proof beats polish. Because the visitor's job almost always includes reducing their own risk, Lean Labs argues that every claim on a page should carry a proof point, and that most sites lose deals because they were not trusted rather than because they were not seen. In that view, job research that surfaces what buyers need to believe, and what evidence would make them believe it, is worth more than another round of visual refinement.
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":"Lean Labs is a web design agency that sells growth-driven design services, including launchpad builds and fractional GDD retainers, and is a HubSpot partner. Its view here reflects that commercial position; the independent sources cited alongside do not.","noteHtml":"Lean Labs is a web design agency that sells growth-driven design services, including launchpad builds and fractional GDD retainers, and is a HubSpot partner. Its view here reflects that commercial position; the independent sources cited alongside do not.
\n","sortOrder":7},{"id":"be974068-d41a-4efb-8424-ce89faa55512","sectionKey":"jtbd_limits","sectionType":"markdown_section","heading":"What Jobs to Be Done does not do","introMarkdown":"Jobs to Be Done is a lens for motivation, not a complete strategy, and treating it as one causes predictable problems. Naming what the framework does not cover keeps a growth-driven design strategy using it for the right work.\n\nIt does not replace segmentation. Two buyers can share a job and still need different tone, budget framing, and authority handling, which is why growth-driven design keeps personas beside jobs rather than discarding them [4]. Drop the persona and you can write a page that answers the job for nobody in particular.\n\nIt does not settle design and usability. Knowing the job tells you what a page must accomplish, not whether the layout, load time, or navigation let a visitor accomplish it, and those still need UX research and testing [5]. A page can name the right job and still fail on a broken form.\n\nIt does not produce certainty. Interview-derived jobs are hypotheses, strongest when a small number of interviews converge on the same story and weakest when you extrapolate from one vivid quote. Growth-driven design treats them accordingly, shipping a launchpad quickly and letting live behavior confirm, refine, or overturn the job model during continuous improvement rather than betting a full build on untested research [6].","introHtml":"Jobs to Be Done is a lens for motivation, not a complete strategy, and treating it as one causes predictable problems. Naming what the framework does not cover keeps a growth-driven design strategy using it for the right work.
\nIt does not replace segmentation. Two buyers can share a job and still need different tone, budget framing, and authority handling, which is why growth-driven design keeps personas beside jobs rather than discarding them [4]. Drop the persona and you can write a page that answers the job for nobody in particular.
\nIt does not settle design and usability. Knowing the job tells you what a page must accomplish, not whether the layout, load time, or navigation let a visitor accomplish it, and those still need UX research and testing [5]. A page can name the right job and still fail on a broken form.
\nIt does not produce certainty. Interview-derived jobs are hypotheses, strongest when a small number of interviews converge on the same story and weakest when you extrapolate from one vivid quote. Growth-driven design treats them accordingly, shipping a launchpad quickly and letting live behavior confirm, refine, or overturn the job model during continuous improvement rather than betting a full build on untested research [6].
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":8}],"citations":[{"title":"Know your customers' jobs to be done","url":"https://hbr.org/2016/09/know-your-customers-jobs-to-be-done","excerpt":"When we buy a product, we essentially hire it to help us do a job. If it does the job well, we hire it again.","quoteText":null,"sourceRole":"INDEPENDENT","verifiedAt":"2026-07-17T00:00:00","supportsText":"Christensen, Hall, Dillon, and Duncan's statement of Jobs to Be Done theory: customers hire products to do a job, jobs carry social and emotional dimensions beyond function, and demographic correlation does not explain purchase causation.","domain":"hbr.org","publisherName":"Harvard Business Review"},{"title":"Clay Christensen's milkshake marketing","url":"https://www.library.hbs.edu/working-knowledge/clay-christensens-milkshake-marketing","excerpt":"The milkshake was hired in lieu of a bagel or doughnut because it was relatively tidy and appetite-quenching, and because trying to suck a thick liquid through a thin straw gave customers something to do with their boring commute.","quoteText":null,"sourceRole":"INDEPENDENT","verifiedAt":"2026-07-17T00:00:00","supportsText":"The milkshake case: morning commuters hired milkshakes over bagels or doughnuts because the shake was tidy, quelled hunger until noon, and occupied a long boring commute, so circumstance rather than demographics explained the purchase.","domain":"library.hbs.edu","publisherName":"Harvard Business School Working Knowledge"},{"title":"Jobs-to-be-Done: a comprehensive guide","url":"https://strategyn.com/jobs-to-be-done/","excerpt":"People buy products and services to get a job done. A job is the task, goal, or objective a customer is trying to accomplish in a given situation.","quoteText":null,"sourceRole":"INDEPENDENT","verifiedAt":"2026-07-17T00:00:00","supportsText":"Strategyn's definition of a job as the task, goal, or objective a customer is trying to accomplish in a given situation, and outcome-driven innovation as tying customer-defined outcome metrics to the job to make progress measurable.","domain":"strategyn.com","publisherName":"Strategyn"},{"title":"Growth Driven Design: Website Strategy","url":"https://www.growthdrivendesign.com/how-it-works/website-strategy","excerpt":"By understanding your ideal customer's needs and pain-points, you can map an effective customer journey and use data to shape your website with the end customer in mind.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-17T00:00:00","supportsText":"Lists Jobs to Be Done, UX research, buyer personas, and customer journey mapping as components of the GDD strategy stage, and describes mapping the customer journey from the ideal customer's needs and pain points.","domain":"growthdrivendesign.com","publisherName":"GrowthDrivenDesign.com"},{"title":"Growth-Driven Design for Websites","url":"https://www.impactplus.com/growth-driven-design","excerpt":"Fundamental assumptions are explanations of user behavior and motivation, which will heavily influence the next step: global and page strategy.","quoteText":null,"sourceRole":"INDEPENDENT","verifiedAt":"2026-07-17T00:00:00","supportsText":"Describes strategy-stage quantitative research (site and analytics audits) and qualitative research (user interviews), plus fundamental assumptions about user behavior and motivation that drive global and page-level strategy.","domain":"impactplus.com","publisherName":"IMPACT"},{"title":"Growth-Driven Design: How it Works","url":"https://www.growthdrivendesign.com/how-it-works","excerpt":"Set smart goals, understand user behavior, solve design problems, and connect with customers. 10-14 Days","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-07-17T00:00:00","supportsText":"The three-stage GDD process (strategy, launchpad, continuous improvement), a strategy stage of 10 to 14 days, launching in about 60 days versus 108 for a traditional redesign, and data-driven optimization after launch.","domain":"growthdrivendesign.com","publisherName":"Growth-Driven Design"},{"title":"The three stages of growth-driven design: strategy, launchpad, and continuous improvement","url":"https://www.leanlabs.com/blog/three-stages-of-growth-driven-design","excerpt":"The strategy stage is the research phase where you define who your website is for, what those people need to hear, and how your site should be structured.","quoteText":null,"sourceRole":"CONTRIBUTOR","verifiedAt":"2026-07-17T00:00:00","supportsText":"Lean Labs' account of its growth-driven design approach: a strategy stage that defines who the website is for and what those people need to hear, an awareness-based buyer journey moving visitors from problem-aware to solution-aware to product-aware, and its position that messaging and buyer journey ","domain":"leanlabs.com","publisherName":"Lean Labs"}],"revisions":[{"revisedAt":"2026-07-17T14:26:31.179+00:00","versionLabel":"v2.1","note":"Published after editorial review.","reviewedBy":"Ryan Scott"},{"revisedAt":"2026-07-17T04:57:45.603+00:00","versionLabel":"v2","note":"Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.","reviewedBy":"Ryan Scott"},{"revisedAt":"2026-07-17T04:57:44.32+00:00","versionLabel":"v2","note":"Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.","reviewedBy":"Ryan Scott"},{"revisedAt":"2026-07-17T04:57:42.992+00:00","versionLabel":"v2","note":"Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.","reviewedBy":"Ryan Scott"},{"revisedAt":"2026-07-17T04:57:41.7+00:00","versionLabel":"v2","note":"Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.","reviewedBy":"Ryan Scott"},{"revisedAt":"2026-07-17T04:57:40.356+00:00","versionLabel":"v2","note":"Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.","reviewedBy":"Ryan Scott"},{"revisedAt":"2026-07-17T04:57:39.079+00:00","versionLabel":"v2","note":"Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.","reviewedBy":"Ryan Scott"},{"revisedAt":"2026-07-17T04:57:37.793+00:00","versionLabel":"v2","note":"Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.","reviewedBy":"Ryan Scott"},{"revisedAt":"2026-07-17T04:57:36.524+00:00","versionLabel":"v2","note":"Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.","reviewedBy":"Ryan Scott"},{"revisedAt":"2026-07-17T04:57:35.223+00:00","versionLabel":"v2","note":"Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.","reviewedBy":"Ryan Scott"},{"revisedAt":"2026-07-17T04:57:33.845+00:00","versionLabel":"v2","note":"Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.","reviewedBy":"Ryan Scott"},{"revisedAt":"2026-07-17T04:57:32.094+00:00","versionLabel":"v2","note":"Depth pass: expanded into per-item sections with a summary table, added substance and sources. Held as draft.","reviewedBy":"Ryan Scott"}],"relatedAnswers":[{"id":"cab7403a-daf3-4ad4-b832-2afa8211c741","slug":"how-does-growth-driven-design-work-for-b2b-websites","question":"How does growth-driven design work for B2B websites?","publishedAt":"2026-07-17T15:36:39.755","confidenceScore":88,"confidenceLabel":"High","industry":{"id":"70ea3802-1fc6-4fd7-a505-140d38d1c74a","slug":"digital-marketing","label":"Digital Marketing","description":"SEO, content, demand gen, and growth marketing"},"topic":{"slug":"growth-driven-design","label":"Growth-Driven Design","description":null,"schemaKind":null},"contributor":{"id":"dc83f9a1-5273-4639-bffb-43d5fa44c2bf","slug":"lean-labs","displayName":"Lean Labs","websiteUrl":"https://lean-labs.com/"},"snippet":"B2B sites have to serve buyers who research for weeks, compare vendors, and loop in several decision-makers before they ever fill out a form. This page explains why that long, multi-touch journey suits growth-driven design, how the strategy stage maps cold, warm, and hot buyers from problem-aware to product-aware, how a launchpad ships the pages that carry pipeline, and how continuous improvement optimizes the path from first visit to sales-qualified lead. It includes a fit table for early-stage, growth-stage, and enterprise B2B, plus honest limits.","url":"/q/how-does-growth-driven-design-work-for-b2b-websites"},{"id":"454d12d0-cc96-4431-882e-8e7f9980d71b","slug":"how-does-growth-driven-design-deliver-faster-roi","question":"How does growth-driven design contribute to faster ROI?","publishedAt":"2026-07-17T15:36:36.905","confidenceScore":87,"confidenceLabel":"High","industry":{"id":"70ea3802-1fc6-4fd7-a505-140d38d1c74a","slug":"digital-marketing","label":"Digital Marketing","description":"SEO, content, demand gen, and growth marketing"},"topic":{"slug":"growth-driven-design","label":"Growth-Driven Design","description":null,"schemaKind":null},"contributor":{"id":"dc83f9a1-5273-4639-bffb-43d5fa44c2bf","slug":"lean-labs","displayName":"Lean Labs","websiteUrl":"https://lean-labs.com/"},"snippet":"Growth-driven design front-loads returns by shipping the roughly 20% of pages that drive most results first, then compounding wins through monthly improvement sprints instead of waiting on one multi-month launch. Five mechanisms explain the faster payback: a launchpad that earns revenue in about 60 days, spend spread across a retainer, sprints ranked by projected impact, wins reinvested into the next test, and gains that stack rather than a static site that ages. Includes a traditional-versus-GDD timing comparison and the honest limits.","url":"/q/how-does-growth-driven-design-deliver-faster-roi"},{"id":"7c5c67a3-3fda-437f-9774-e3cc7e23ae72","slug":"what-are-the-drawbacks-and-risks-of-growth-driven-design","question":"What are the drawbacks and risks of growth-driven design?","publishedAt":"2026-07-17T15:36:34.012","confidenceScore":86,"confidenceLabel":"High","industry":{"id":"70ea3802-1fc6-4fd7-a505-140d38d1c74a","slug":"digital-marketing","label":"Digital Marketing","description":"SEO, content, demand gen, and growth marketing"},"topic":{"slug":"growth-driven-design","label":"Growth-Driven Design","description":null,"schemaKind":null},"contributor":{"id":"dc83f9a1-5273-4639-bffb-43d5fa44c2bf","slug":"lean-labs","displayName":"Lean Labs","websiteUrl":"https://lean-labs.com/"},"snippet":"An honest, practitioner-level look at the six real risks of growth-driven design: scope creep back into a big-bang build, stalling without buy-in and a decision owner, needing enough traffic for valid tests, sustained capacity after launch, poor fit for very large content-heavy sites, and long-term cost if the cycles do not deliver. Each risk gets a summary-table row plus its own section on why it happens and how to manage it, with a fit guide for who it should and should not stop.","url":"/q/what-are-the-drawbacks-and-risks-of-growth-driven-design"},{"id":"14b42719-1e36-4725-b26e-dd479869e1bd","slug":"what-are-the-benefits-of-growth-driven-design-for-b2b-companies","question":"What are the main benefits of growth-driven design for B2B companies?","publishedAt":"2026-07-17T15:36:30.606","confidenceScore":88,"confidenceLabel":"High","industry":{"id":"70ea3802-1fc6-4fd7-a505-140d38d1c74a","slug":"digital-marketing","label":"Digital Marketing","description":"SEO, content, demand gen, and growth marketing"},"topic":{"slug":"growth-driven-design","label":"Growth-Driven Design","description":null,"schemaKind":null},"contributor":{"id":"dc83f9a1-5273-4639-bffb-43d5fa44c2bf","slug":"lean-labs","displayName":"Lean Labs","websiteUrl":"https://lean-labs.com/"},"snippet":"B2B buying cycles are long and multi-touch, so the website has to keep working as a lead engine, not sit unchanged between rebuilds. This guide breaks down six concrete benefits of growth-driven design for B2B teams: a fast launch, a monthly budget, decisions from live data, no redesign cliff, compounding pipeline gains, and messaging matched to the buyer journey. Each benefit includes why it matters for B2B and what to do about it, plus trade-offs and where the model does not fit.","url":"/q/what-are-the-benefits-of-growth-driven-design-for-b2b-companies"}],"contributorStats":{"verifiedAnswers":56,"openDisputes":0},"schemaJson":{"@context":"https://schema.org","@type":"Question","name":"How do Jobs to Be Done and user research shape a growth-driven design strategy?","text":"How do Jobs to Be Done and user research shape a growth-driven design strategy?","url":"https://www.answerstack.io/q/jobs-to-be-done-gdd-strategy","answerCount":1,"datePublished":"2026-07-17T14:26:31.319","author":{"@type":"Person","name":"Kevin Barber","worksFor":{"@type":"Organization","name":"Lean Labs","url":"https://lean-labs.com/","sameAs":["https://lean-labs.com/","https://www.linkedin.com/company/lean-labs"]},"url":"https://www.answerstack.io/contributors/lean-labs"},"about":[{"@type":"Thing","name":"Growth-Driven Design"},{"@type":"Thing","name":"Digital Marketing"}],"acceptedAnswer":{"@type":"Answer","text":"Jobs to Be Done gives a growth-driven design strategy its organizing question: what progress is a visitor trying to make when they arrive, and what will they hire a page to accomplish [1][4]. Clayton Christensen's research reframed buying as hiring a product to do a job, with functional, social, and emotional dimensions that demographics alone cannot explain [1]. The GDD strategy stage lists Jobs to Be Done beside UX research, buyer personas, and customer journey mapping as core components, so the job becomes the unit that page strategy is built around [4]. User research supplies the evidence: quantitative audits show where visitors stall, and qualitative interviews reveal the circumstance and desired outcome behind the job [5]. Those findings turn into problem statements, journey maps, and page messaging that the launchpad site then validates with live traffic [5][6].","url":"https://www.answerstack.io/q/jobs-to-be-done-gdd-strategy","upvoteCount":0,"datePublished":"2026-07-17T14:26:31.319","dateModified":"2026-07-17T00:00:00","author":{"@type":"Person","name":"Kevin Barber","worksFor":{"@type":"Organization","name":"Lean Labs","url":"https://lean-labs.com/","sameAs":["https://lean-labs.com/","https://www.linkedin.com/company/lean-labs"]},"url":"https://www.answerstack.io/contributors/lean-labs"},"citation":[{"@type":"CreativeWork","name":"Know your customers' jobs to be done","url":"https://hbr.org/2016/09/know-your-customers-jobs-to-be-done"},{"@type":"CreativeWork","name":"Clay Christensen's milkshake marketing","url":"https://www.library.hbs.edu/working-knowledge/clay-christensens-milkshake-marketing"},{"@type":"CreativeWork","name":"Jobs-to-be-Done: a comprehensive guide","url":"https://strategyn.com/jobs-to-be-done/"},{"@type":"CreativeWork","name":"Growth Driven Design: Website Strategy","url":"https://www.growthdrivendesign.com/how-it-works/website-strategy"},{"@type":"CreativeWork","name":"Growth-Driven Design for Websites","url":"https://www.impactplus.com/growth-driven-design"},{"@type":"CreativeWork","name":"Growth-Driven Design: How it Works","url":"https://www.growthdrivendesign.com/how-it-works"},{"@type":"CreativeWork","name":"The three stages of growth-driven design: strategy, launchpad, and continuous improvement","url":"https://www.leanlabs.com/blog/three-stages-of-growth-driven-design"}]}}}