Jobs to Be Done is one of four named components of the growth-driven design strategy stage, listed beside UX research, buyer personas, and customer path mapping [5]. It supplies the organizing question, which is what progress a visitor is trying to make and what they will hire a page to do about it [1][4]. Clayton Christensen and his coauthors argue that the circumstance a buyer is in predicts a purchase better than buyer characteristics do, and that jobs carry social and emotional weight beyond function [1]. In growth-driven design the research settles nothing on its own: the strategy stage is time-boxed at 10 to 14 days and produces documented assumptions about user behavior and motivation, which the launch pad site and the 14-day improvement sprints then test against live traffic [6][7].
\n","summary":"Growth-driven design lists Jobs to Be Done as a strategy-stage component beside UX research, buyer personas, and customer path mapping. This answer separates what the underlying research establishes, that circumstance predicts a purchase better than demographics, from what it does not. No cited source compares outcomes for job-derived against persona-derived messaging, no cited source specifies how many interviews a strategy needs, and the jobs a strategy documents stay hypotheses until the launch pad tests them.","publishedAt":"2026-07-17T14:26:31.319","verifiedAt":"2026-09-14T00:00:00","editorialStatus":"APPROVED","lastReviewedAt":"2026-09-15T06:27:45.513","nextReviewDueAt":"2026-12-14T00: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","job stories vs personas","outcome-driven innovation web design"],"confidenceScore":78,"confidenceLabel":"Medium","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":"Brandvious, Inc.","description":"Lean Labs helps B2B startup and scaleup companies on HubSpot grow with lead gen websites, Answer Engine Optimization (AEO), and Loop Marketing. As a HubSpot Diamond Solutions Partner since 2013, they specialize in turning marketing into a self-funding growth machine using AI-native systems like Factor8. They serve SaaS, fintech, healthcare, and AI companies, focusing on measurable outcomes like pipeline, conversion rate, and revenue growth.","websiteUrl":"https://lean-labs.com/","imageUrl":"https://www.leanlabs.com/hubfs/Imported_Blog_Media/LeanLabs-Logo-White.png","sameAs":["https://lean-labs.com/","https://www.linkedin.com/company/lean-labs"],"slogan":"We Help Companies on HubSpot Drive Growth","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":"70+ (2025)","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":null,"sections":[{"id":"4f04e6ec-c153-4d7a-98d0-deb80dbece96","sectionKey":"jtbd_explainer","sectionType":"markdown_section","heading":"What is Jobs to Be Done?","introMarkdown":"Clayton Christensen, Taddy Hall, Karen Dillon, and David Duncan defined a job in Harvard Business Review as what a person seeks to accomplish in a given circumstance, and described buying as hiring: \"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. If it does a crummy job, we fire it and look for something else to solve the problem\" [1]. Their central claim is about causation. Product teams build customer profiles and hunt for correlations in data, and a correlation does not explain why the purchase happened [1]. Christensen put the same point to Harvard Business School's Working Knowledge: being 18 to 35 with a college degree \"may be correlated with the decision, but it doesn't cause it\" [2].\n\nThe milkshake example comes from a teaching case Christensen used in his MBA course, written up by HBS Working Knowledge in 2011 [2]. The chain's marketers had asked people who matched the milkshake demographic to describe an ideal shake, changed the product to match, and sold no more milkshakes [2]. A researcher then spent a full day in one restaurant recording who bought shakes and when, and found 40 percent were bought first thing in the morning by commuters ordering to go; interviews the next morning surfaced the job, which was to occupy one free hand through a long boring commute and stave off hunger until noon [2]. The shake beat a bagel or a doughnut because it was tidier and because a thick liquid through a thin straw lasted the drive [2]. That is one chain, one restaurant, two mornings, and one researcher, so it is the origin story of the framework and not a controlled test of it.\n\nTony Ulwick's firm Strategyn defines a job as \"the task, goal, or objective a customer is trying to accomplish in a given situation\" and builds outcome-driven innovation on top of that, converting the job into a map of steps and a set of customer-defined outcome metrics [3]. Strategyn also states that Ulwick pioneered Jobs to Be Done and that Christensen later popularized it, a provenance claim the HBR article does not address and one the firm has an interest in making, since it sells outcome-driven innovation training and consulting [1][3]. What both accounts share is the definition: a job is progress in a situation, and the situation sets which alternatives a buyer weighs [1][3].","introHtml":"Clayton Christensen, Taddy Hall, Karen Dillon, and David Duncan defined a job in Harvard Business Review as what a person seeks to accomplish in a given circumstance, and described buying as hiring: "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. If it does a crummy job, we fire it and look for something else to solve the problem" [1]. Their central claim is about causation. Product teams build customer profiles and hunt for correlations in data, and a correlation does not explain why the purchase happened [1]. Christensen put the same point to Harvard Business School's Working Knowledge: being 18 to 35 with a college degree "may be correlated with the decision, but it doesn't cause it" [2].
\nThe milkshake example comes from a teaching case Christensen used in his MBA course, written up by HBS Working Knowledge in 2011 [2]. The chain's marketers had asked people who matched the milkshake demographic to describe an ideal shake, changed the product to match, and sold no more milkshakes [2]. A researcher then spent a full day in one restaurant recording who bought shakes and when, and found 40 percent were bought first thing in the morning by commuters ordering to go; interviews the next morning surfaced the job, which was to occupy one free hand through a long boring commute and stave off hunger until noon [2]. The shake beat a bagel or a doughnut because it was tidier and because a thick liquid through a thin straw lasted the drive [2]. That is one chain, one restaurant, two mornings, and one researcher, so it is the origin story of the framework and not a controlled test of it.
\nTony Ulwick's firm Strategyn defines a job as "the task, goal, or objective a customer is trying to accomplish in a given situation" and builds outcome-driven innovation on top of that, converting the job into a map of steps and a set of customer-defined outcome metrics [3]. Strategyn also states that Ulwick pioneered Jobs to Be Done and that Christensen later popularized it, a provenance claim the HBR article does not address and one the firm has an interest in making, since it sells outcome-driven innovation training and consulting [1][3]. What both accounts share is the definition: a job is progress in a situation, and the situation sets which alternatives a buyer weighs [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":"Growthdrivendesign.com lists Jobs to Be Done as one of four strategy-stage components, beside UX Research, Buyer Personas, and Customer Path Mapping [5]. That site is the methodology's primary documentation and it is not disinterested: its footer identifies Growth-Driven Design as a dba of HubSpot and credits the site build to the Lean Labs GDD team, the contributor on this page [5][6]. Its Jobs to Be Done page places the framework in the strategy phase on the grounds that it \"sets the tone of everything else you'll be doing in the future,\" from positioning through messaging and into site features [4].\n\nA pricing page is hired to settle whether this fits a budget without booking a sales call, and a case study page is hired to hand a visitor evidence they can defend to whoever else approves the spend. Treating each core page as something a visitor hires for one outcome changes what the strategy argues about, because the question shifts from what the company wants to say to what the visitor came to finish [4].\n\nThe strategy stage is capped at 10 to 14 days on growthdrivendesign.com, which limits how much job research a project can absorb before the launch pad build starts [6]. Lean Labs describes the same stage as two to four weeks [8], so the two published figures disagree and the practical range is roughly two weeks to a month. Either way the output is documented assumptions, not findings: IMPACT's guide calls them fundamental assumptions and says they are used \"to explain user behavior and motivation,\" which then feeds global and page strategy [7]. The launch pad site and the 14-day improvement sprints are where those assumptions meet traffic [6]. Stage structure, timing, and cost are covered separately in [the three stages of growth-driven design](https://www.answerstack.io/q/what-are-the-three-stages-of-growth-driven-design), [how long a growth-driven design site takes to launch](https://www.answerstack.io/q/how-long-does-it-take-to-launch-a-growth-driven-design-site), and [how much growth-driven design costs](https://www.answerstack.io/q/how-much-does-growth-driven-design-cost).","introHtml":"Growthdrivendesign.com lists Jobs to Be Done as one of four strategy-stage components, beside UX Research, Buyer Personas, and Customer Path Mapping [5]. That site is the methodology's primary documentation and it is not disinterested: its footer identifies Growth-Driven Design as a dba of HubSpot and credits the site build to the Lean Labs GDD team, the contributor on this page [5][6]. Its Jobs to Be Done page places the framework in the strategy phase on the grounds that it "sets the tone of everything else you'll be doing in the future," from positioning through messaging and into site features [4].
\nA pricing page is hired to settle whether this fits a budget without booking a sales call, and a case study page is hired to hand a visitor evidence they can defend to whoever else approves the spend. Treating each core page as something a visitor hires for one outcome changes what the strategy argues about, because the question shifts from what the company wants to say to what the visitor came to finish [4].
\nThe strategy stage is capped at 10 to 14 days on growthdrivendesign.com, which limits how much job research a project can absorb before the launch pad build starts [6]. Lean Labs describes the same stage as two to four weeks [8], so the two published figures disagree and the practical range is roughly two weeks to a month. Either way the output is documented assumptions, not findings: IMPACT's guide calls them fundamental assumptions and says they are used "to explain user behavior and motivation," which then feeds global and page strategy [7]. The launch pad site and the 14-day improvement sprints are where those assumptions meet traffic [6]. Stage structure, timing, and cost are covered separately in the three stages of growth-driven design, how long a growth-driven design site takes to launch, and how much growth-driven design costs.
\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 buyer personas differ?","introMarkdown":"The HBR article that popularized jobs keeps personas in play: \"Personas, ethnographic research, focus groups, customer panels, competitive analysis, and so on can all be perfectly valid starting points for surfacing important insights\" [1]. Growth-driven design lists both as strategy-stage components, so the methodology does not ask you to pick [5], and the table sets out what each is built from and where each one fails.","introHtml":"The HBR article that popularized jobs keeps personas in play: "Personas, ethnographic research, focus groups, customer panels, competitive analysis, and so on can all be perfectly valid starting points for surfacing important insights" [1]. Growth-driven design lists both as strategy-stage components, so the methodology does not ask you to pick [5], and the table sets out what each is built from and where each one fails.
\n","outroMarkdown":"The two failure modes point in opposite directions, which is why the methodology carries both [5]. Intercom's account in the HBR sidebar is the clearest illustration. Persona segmentation was failing because the company's typical users had little in common by demographics or job title, so Bob Moesta's team interviewed people who had recently signed on and people who had dropped the service or changed their usage sharply, reconstructing the timeline and the forces behind each decision [1]. What came back was language, and the words customers used for the product were different from the words Intercom used for it [1]. On a B2B site that split matters more than the theory implies, because Strategyn's model separates the job executor who uses the product from the buyer who signs for it, and one page often has to serve both readers [3].","outroHtml":"The two failure modes point in opposite directions, which is why the methodology carries both [5]. Intercom's account in the HBR sidebar is the clearest illustration. Persona segmentation was failing because the company's typical users had little in common by demographics or job title, so Bob Moesta's team interviewed people who had recently signed on and people who had dropped the service or changed their usage sharply, reconstructing the timeline and the forces behind each decision [1]. What came back was language, and the words customers used for the product were different from the words Intercom used for it [1]. On a B2B site that split matters more than the theory implies, because Strategyn's model separates the job executor who uses the product from the buyer who signs for it, and one page often has to serve both readers [3].
\n","contentJson":{"rows":[{"cells":["Core question","Who is the buyer and what do they care about? [5]","What progress is the buyer trying to make in this circumstance? [1]"]},{"cells":["Built from","Role, firmographics, stated goals, and recorded objections, validated in user conversations [7]","The struggling moment, the outcome sought, the alternatives weighed, and the anxieties slowing the decision [1][2]"]},{"cells":["Unit of analysis","A representative person","A situation and the progress it demands [1]"]},{"cells":["Documented failure mode","Correlation without causation. Intercom reported \"too many typical users who had little in common\" by demographics or job title [1]","Flattens real differences in budget, tone, and approval authority. Strategyn separates the job executor from the buyer who approves the spend [3]"]},{"cells":["Role in the GDD strategy stage","Named component. Defines who the site serves and how it should speak [5]","Named component. Defines what each page must accomplish [4][5]"]}],"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 a Jobs to Be Done interview?","introMarkdown":"Bob Moesta's method, as described in the HBR article, reconstructs the timeline of one real decision: \"I asked people to draw a timeline of how they got here\" [1]. In the condo case he ran that across what HBR calls scores of interviews, and the first thing it established was negative, since no demographic or psychographic profile separated the buyers and no feature set tipped the decision [1]. For Intercom, his team interviewed two groups, recent signups and people who had dropped or sharply changed their usage, to surface the forces behind each decision, which HBR lists as inertia, fear of change, and anxiety [1].\n\nAsk what happened, not what the person wants, because a recalled sequence of events can be checked against a timeline and a stated preference cannot. Growthdrivendesign.com says the discovery interview \"takes a very specific format\" and links to a downloadable template and a role-play video and not publishing a script [4]. None of the sources cited here specifies how many interviews a website strategy needs. HBR's condo work drew on scores of them and the Intercom engagement is described only as individual interviews with two customer groups [1]. Any number you are handed is a scheduling heuristic for a time-boxed stage, not a validated saturation threshold, and the count that governs in practice is what matters where the stories start repeating.\n\nIMPACT's guide describes the stage output as fundamental assumptions, with examples including the value proposition for each offer, the devices and locations visitors use, and what information they search for on the site [7]. The methodology labels them assumptions itself, and they feed global and page strategy that the launch pad then exposes to traffic [6][7]. A job that came out of six interviews and a job that came out of sixty hold the same status until the site tests them.","introHtml":"Bob Moesta's method, as described in the HBR article, reconstructs the timeline of one real decision: "I asked people to draw a timeline of how they got here" [1]. In the condo case he ran that across what HBR calls scores of interviews, and the first thing it established was negative, since no demographic or psychographic profile separated the buyers and no feature set tipped the decision [1]. For Intercom, his team interviewed two groups, recent signups and people who had dropped or sharply changed their usage, to surface the forces behind each decision, which HBR lists as inertia, fear of change, and anxiety [1].
\nAsk what happened, not what the person wants, because a recalled sequence of events can be checked against a timeline and a stated preference cannot. Growthdrivendesign.com says the discovery interview "takes a very specific format" and links to a downloadable template and a role-play video and not publishing a script [4]. None of the sources cited here specifies how many interviews a website strategy needs. HBR's condo work drew on scores of them and the Intercom engagement is described only as individual interviews with two customer groups [1]. Any number you are handed is a scheduling heuristic for a time-boxed stage, not a validated saturation threshold, and the count that governs in practice is what matters where the stories start repeating.
\nIMPACT's guide describes the stage output as fundamental assumptions, with examples including the value proposition for each offer, the devices and locations visitors use, and what information they search for on the site [7]. The methodology labels them assumptions itself, and they feed global and page strategy that the launch pad then exposes to traffic [6][7]. A job that came out of six interviews and a job that came out of sixty hold the same status until the site tests them.
\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 does a job become a problem statement?","introMarkdown":"A problem statement writes the job from the visitor's side, naming the situation, the outcome they want, and the obstacle, in one sentence: 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 can be checked against what a sales team hears on calls. \"We need a modern website\" cannot be checked against anything.\n\nLean Labs publishes a five-part format for these statements, covering why a buyer should listen, why they should consider changing their current approach, how that change works, how the product helps them make it, and what proof backs it up [8]. That is one agency's template and not a methodology requirement, since growthdrivendesign.com prescribes no problem statement format [4][5]. What writing any of them down does is separate the job, which stays stable across product generations in Strategyn's music-listening example, from your current product, which is one of several things a visitor could hire [3].\n\nTwenty problem statements at launch dilutes every page, and a 10 to 14 day strategy box makes twenty unlikely anyway [6]. Because the stage is boxed, the set stays small, and the few that make it are the ones the launch pad will be measuring [6][7].","introHtml":"A problem statement writes the job from the visitor's side, naming the situation, the outcome they want, and the obstacle, in one sentence: 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 can be checked against what a sales team hears on calls. "We need a modern website" cannot be checked against anything.
\nLean Labs publishes a five-part format for these statements, covering why a buyer should listen, why they should consider changing their current approach, how that change works, how the product helps them make it, and what proof backs it up [8]. That is one agency's template and not a methodology requirement, since growthdrivendesign.com prescribes no problem statement format [4][5]. What writing any of them down does is separate the job, which stays stable across product generations in Strategyn's music-listening example, from your current product, which is one of several things a visitor could hire [3].
\nTwenty problem statements at launch dilutes every page, and a 10 to 14 day strategy box makes twenty unlikely anyway [6]. Because the stage is boxed, the set stays small, and the few that make it are the ones the launch pad will be measuring [6][7].
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":4},{"id":"56e19854-8807-403c-b603-d9c57fb8a4b4","sectionKey":"jobs_to_page_messaging","sectionType":"markdown_section","heading":"How do jobs shape the buyer path and page messaging?","introMarkdown":"Growthdrivendesign.com maps the customer path from the ideal customer's needs and pain points rather than from internal sales stages [5]. Lean Labs documents its version as two to four steps per core offering, with each step answering a specific set of questions the buyer has at that point [8]. A single B2B decision usually spans several smaller jobs in sequence, opening with whether this is even the right category and closing with justifying the choice to whoever approves it.\n\nHBR's condo case is the clearest worked example of what a job insight changes on the offer itself. The developers stopped adding features to the units and instead shrank the second bedroom to make room for a dining room table, added moving services, two years of storage, and an on-site sorting room where new owners could decide slowly what to discard [1]. They raised prices by $3,500, which profitably covered the moving and storage, and in 2007, with industry sales off 49 percent, they reported growing the business by 25 percent [1]. That is one developer in one collapsing market, reported by the framework's own authors, so it establishes that a job insight can change what gets built, and it gives you no effect size to plan a site against.\n\nOn a page, the job decides the headline and the proof. The headline restates the outcome the visitor came for, ideally in the words the interviews surfaced, because Intercom found its customers described the product in different words than the company used [1]. The proof has to clear whatever anxiety those interviews exposed, since HBR puts anxiety and inertia among the forces working against a purchase [1]. Which next step to offer is the part growth-driven design defers to data, because the launch pad ships one version and the 14-day sprints test alternatives against live behavior [6][7].","introHtml":"Growthdrivendesign.com maps the customer path from the ideal customer's needs and pain points rather than from internal sales stages [5]. Lean Labs documents its version as two to four steps per core offering, with each step answering a specific set of questions the buyer has at that point [8]. A single B2B decision usually spans several smaller jobs in sequence, opening with whether this is even the right category and closing with justifying the choice to whoever approves it.
\nHBR's condo case is the clearest worked example of what a job insight changes on the offer itself. The developers stopped adding features to the units and instead shrank the second bedroom to make room for a dining room table, added moving services, two years of storage, and an on-site sorting room where new owners could decide slowly what to discard [1]. They raised prices by $3,500, which profitably covered the moving and storage, and in 2007, with industry sales off 49 percent, they reported growing the business by 25 percent [1]. That is one developer in one collapsing market, reported by the framework's own authors, so it establishes that a job insight can change what gets built, and it gives you no effect size to plan a site against.
\nOn a page, the job decides the headline and the proof. The headline restates the outcome the visitor came for, ideally in the words the interviews surfaced, because Intercom found its customers described the product in different words than the company used [1]. The proof has to clear whatever anxiety those interviews exposed, since HBR puts anxiety and inertia among the forces working against a purchase [1]. Which next step to offer is the part growth-driven design defers to data, because the launch pad ships one version and the 14-day sprints test alternatives against live behavior [6][7].
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":5},{"id":"01546605-e914-4ea9-88a5-2c498a7905da","sectionKey":"contributor_perspective","sectionType":"markdown_section","heading":"How Lean Labs uses job research inside a strategy stage","introMarkdown":"We run the strategy stage before any design work, and we interview three groups around a client's buyers: their customers, their sales reps, and their support staff [8]. Customers tell us what convinced them to buy, while sales tells us which objections show up before someone commits [8]. Support is the group most teams skip and usually the most useful to us, because what confuses people after the purchase is normally where the site set the wrong expectation [8].\n\nOur published position is that roughly 80 percent of whether a website succeeds comes down to messaging and buyer path work, with the remaining 20 percent being custom design [8]. That split is our own estimate from running these builds. It is not a measured result, we have not run a controlled comparison, and we are not aware of one, so read it as a description of where we put our hours and not as a number to plan a budget against.\n\nWe do not publish a required interview count, because the number that matters is what matters where the stories repeat and the stage is time-boxed either way [6]. What we do commit to is writing everything the strategy produces as a hypothesis, our problem statements included, so the launch pad has something specific to prove wrong.","introHtml":"We run the strategy stage before any design work, and we interview three groups around a client's buyers: their customers, their sales reps, and their support staff [8]. Customers tell us what convinced them to buy, while sales tells us which objections show up before someone commits [8]. Support is the group most teams skip and usually the most useful to us, because what confuses people after the purchase is normally where the site set the wrong expectation [8].
\nOur published position is that roughly 80 percent of whether a website succeeds comes down to messaging and buyer path work, with the remaining 20 percent being custom design [8]. That split is our own estimate from running these builds. It is not a measured result, we have not run a controlled comparison, and we are not aware of one, so read it as a description of where we put our hours and not as a number to plan a budget against.
\nWe do not publish a required interview count, because the number that matters is what matters where the stories repeat and the stage is time-boxed either way [6]. What we do commit to is writing everything the strategy produces as a hypothesis, our problem statements included, so the launch pad has something specific to prove wrong.
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":"Disclosure: Lean Labs is a HubSpot Solutions Partner at the Diamond tier and has built on the platform since 2013, and it sells growth-driven design engagements, including the strategy stage described here. It has a commercial interest in readers adopting this process. Lean Labs also built growthdrivendesign.com, cited on this page as a primary source and published by Growth-Driven Design, a dba of HubSpot, per that site's footer. The Harvard Business Review and Harvard Business School sources cited elsewhere on this page have no relationship with Lean Labs.","noteHtml":"Disclosure: Lean Labs is a HubSpot Solutions Partner at the Diamond tier and has built on the platform since 2013, and it sells growth-driven design engagements, including the strategy stage described here. It has a commercial interest in readers adopting this process. Lean Labs also built growthdrivendesign.com, cited on this page as a primary source and published by Growth-Driven Design, a dba of HubSpot, per that site's footer. The Harvard Business Review and Harvard Business School sources cited elsewhere on this page have no relationship with Lean Labs.
\n","sortOrder":6},{"id":"be974068-d41a-4efb-8424-ce89faa55512","sectionKey":"jtbd_limits","sectionType":"markdown_section","heading":"What Jobs to Be Done cannot settle","introMarkdown":"No source cited on this page compares outcomes between a site whose messaging came from job interviews and one whose messaging came from personas. HBR reports one condo developer growing 25 percent in a market that fell 49 percent, and HBS reports one milkshake chain reformulating after two mornings of observation and interviews [1][2]. Both are case reports selected because they worked, and neither establishes a rate at which the method works. The growth-driven design numbers that do exist are self-reported: growthdrivendesign.com attributes 14.34 percent more leads and 12.56 percent higher revenue over six months to its 2017 State of GDD survey of agencies running GDD on HubSpot versus WordPress, which is practitioners reporting on their own work, and it says nothing about Jobs to Be Done specifically [6].\n\nHBR keeps personas as a valid starting point for surfacing jobs, and Strategyn splits the job executor who uses a product from the buyer who approves the purchase, which on a B2B site is often two people reading the same page [1][3]. Segmentation survives the framework, and a page written to a job with no sense of who is reading it can answer the right question in the wrong register for one of those two readers.\n\nKnowing the job tells you what a page has to accomplish and says nothing about whether the layout, the load time, or a broken form let a visitor accomplish it, which is why UX Research is listed as its own strategy-stage component beside Jobs to Be Done [5]. IMPACT's guide keeps the quantitative site audit separate from the qualitative interviews for the same reason [7].","introHtml":"No source cited on this page compares outcomes between a site whose messaging came from job interviews and one whose messaging came from personas. HBR reports one condo developer growing 25 percent in a market that fell 49 percent, and HBS reports one milkshake chain reformulating after two mornings of observation and interviews [1][2]. Both are case reports selected because they worked, and neither establishes a rate at which the method works. The growth-driven design numbers that do exist are self-reported: growthdrivendesign.com attributes 14.34 percent more leads and 12.56 percent higher revenue over six months to its 2017 State of GDD survey of agencies running GDD on HubSpot versus WordPress, which is practitioners reporting on their own work, and it says nothing about Jobs to Be Done specifically [6].
\nHBR keeps personas as a valid starting point for surfacing jobs, and Strategyn splits the job executor who uses a product from the buyer who approves the purchase, which on a B2B site is often two people reading the same page [1][3]. Segmentation survives the framework, and a page written to a job with no sense of who is reading it can answer the right question in the wrong register for one of those two readers.
\nKnowing the job tells you what a page has to accomplish and says nothing about whether the layout, the load time, or a broken form let a visitor accomplish it, which is why UX Research is listed as its own strategy-stage component beside Jobs to Be Done [5]. IMPACT's guide keeps the quantitative site audit separate from the qualitative interviews for the same reason [7].
\n","outroMarkdown":null,"outroHtml":null,"contentJson":{},"configJson":{},"noteMarkdown":null,"noteHtml":null,"sortOrder":7}],"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. If it does a crummy job, we \"fire\" it and look for something else to solve the problem. Jobs are multifaceted. They're never simply about function; they have powerful social and emotional dimensions.","quoteText":null,"sourceRole":"INDEPENDENT","verifiedAt":"2026-09-15T00:00:00","supportsText":"Christensen, Hall, Dillon, and Duncan's statement of the theory: buying as hiring, jobs carrying social and emotional dimensions beyond function, circumstances mattering more than customer characteristics, and correlation in customer-profile data not explaining causation. Also the source for Bob Moe","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":"He discovered that 40 percent of the milkshakes were purchased first thing in the morning, by commuters who ordered them to go. ... 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-09-15T00:00:00","supportsText":"Carmen Nobel's 2011 write-up of Christensen's teaching case. Establishes the study's actual method and scale: demographic-based product changes that failed to move sales, one researcher spending a full day in one restaurant, 40 percent of milkshakes bought first thing in the morning by commuters ord","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":"A job is the task, goal, or objective a customer is trying to accomplish in a given situation. ... JTBD was pioneered by Tony Ulwick, founder of Strategyn, and later popularized by Harvard Business School professor Clayton Christensen.","quoteText":null,"sourceRole":"SUPPORTING","verifiedAt":"2026-09-15T00:00:00","supportsText":"Tony Ulwick's definition of a job as the task, goal, or objective a customer is trying to accomplish in a given situation, the outcome-driven innovation framing of jobs into job maps and customer-defined outcome metrics, the music-listening example of a job outlasting the products hired to do it, an","domain":"strategyn.com","publisherName":"Strategyn"},{"title":"\"Jobs to be Done\" for Web Design","url":"https://www.growthdrivendesign.com/jobs-to-be-done","excerpt":"This is why the Jobs to Be Done framework is critical in the strategy phase, because it sets the tone of everything else you'll be doing in the future, from positioning to messaging to website features and so on.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-09-15T00:00:00","supportsText":"The methodology's own page on Jobs to Be Done: why the framework belongs in the strategy phase because it sets the tone for positioning, messaging, and site features that follow, and the statement that the JTBD discovery interview takes a very specific format, supported by a downloadable template an","domain":"growthdrivendesign.com","publisherName":"Growth-Driven Design (a dba of HubSpot)"},{"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 path and use data to shape your website with the end customer in mind. ... 2017 Growth-Driven Design (dba of HubSpot). Made by the Lean Labs GDD Team.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-09-15T00:00:00","supportsText":"Lists the four strategy-stage components as UX Research, Buyer Personas, Jobs to be Done, and Customer Path Mapping, and describes mapping the customer path from the ideal customer's needs and pain points. Page footer carries the ownership and build credit used for the disclosure on this record.","domain":"growthdrivendesign.com","publisherName":"GrowthDrivenDesign.com"},{"title":"Growth-Driven Design: How it Works","url":"https://www.growthdrivendesign.com/how-it-works","excerpt":"Stage 01 Strategy 10-14 Days ... Stage 02 Launch Pad 60-90 Days ... Stage 03 Continuous Improvement 14-Day Sprints ... Agencies that used GDD on HubSpot Websites (vs. Wordpress) reported seeing 14.34% more leads after 6 months. Based on the \"2017 state of GDD\" survey responses.","quoteText":null,"sourceRole":"PRIMARY","verifiedAt":"2026-09-15T00:00:00","supportsText":"The three stages and their published durations: Strategy 10 to 14 days, Launch Pad 60 to 90 days, Continuous Improvement in 14-day sprints. Also the self-reported survey figures used in the limits section: 14.34 percent more leads and 12.56 percent higher revenue over six months for agencies running","domain":"growthdrivendesign.com","publisherName":"Growth-Driven Design"},{"title":"Growth-Driven Design for Websites","url":"https://www.impactplus.com/growth-driven-design","excerpt":"You will use these assumptions to explain user behavior and motivation, which will heavily influence the next step -- global and page strategy -- as well as how you continue to work through the growth-driven design cycles.","quoteText":null,"sourceRole":"SUPPORTING","verifiedAt":"2026-09-15T00:00:00","supportsText":"Splits strategy-stage research into a quantitative audit of the current site and analytics and qualitative conversations with users that also validate the assumptions in existing buyer personas, then describes fundamental assumptions (value propositions per offer, devices and locations used, informa","domain":"impactplus.com","publisherName":"IMPACT"},{"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":"In our experience, 80% of whether a website succeeds comes down to the messaging and buyer path work. The remaining 20% is custom design.","quoteText":null,"sourceRole":"CONTRIBUTOR","verifiedAt":"2026-09-15T00:00:00","supportsText":"Lean Labs' own account, used only in the contributor perspective and where labeled as one agency's practice: who it interviews during strategy (customers, sales reps, support staff) and what each group contributes; its five-part problem statement format; a documented buyer path of two to four steps ","domain":"leanlabs.com","publisherName":"Lean Labs"}],"revisions":[{"revisedAt":"2026-09-15T06:27:45.513+00:00","versionLabel":"cleanup-2026-09-14","note":"Corrected the milkshake figure from \"nearly half\" to the 40 percent HBS reports and labeled the case as a two-morning teaching anecdote, removed the unsourced ten-to-fifteen interview count and the cold/warm/hot awareness model that the cited Lean Labs post does not contain, relabeled the 80/20 messaging split as Lean Labs' own unmeasured estimate, deleted the \"founder\" title and the 100+ builds claim, disclosed that growthdrivendesign.com is a HubSpot dba built by Lean Labs, and added a limits section stating that no cited source compares job-derived with persona-derived messaging.","reviewedBy":"AnswerStack Editorial (Opus rewrite, Fable QC)"},{"revisedAt":"2026-09-15T06:27:44.312+00:00","versionLabel":"cleanup-2026-09-14","note":"Corrected the milkshake figure from \"nearly half\" to the 40 percent HBS reports and labeled the case as a two-morning teaching anecdote, removed the unsourced ten-to-fifteen interview count and the cold/warm/hot awareness model that the cited Lean Labs post does not contain, relabeled the 80/20 messaging split as Lean Labs' own unmeasured estimate, deleted the \"founder\" title and the 100+ builds claim, disclosed that growthdrivendesign.com is a HubSpot dba built by Lean Labs, and added a limits section stating that no cited source compares job-derived with persona-derived messaging.","reviewedBy":"AnswerStack Editorial (Opus rewrite, Fable QC)"},{"revisedAt":"2026-09-15T06:27:43.051+00:00","versionLabel":"cleanup-2026-09-14","note":"Corrected the milkshake figure from \"nearly half\" to the 40 percent HBS reports and labeled the case as a two-morning teaching anecdote, removed the unsourced ten-to-fifteen interview count and the cold/warm/hot awareness model that the cited Lean Labs post does not contain, relabeled the 80/20 messaging split as Lean Labs' own unmeasured estimate, deleted the \"founder\" title and the 100+ builds claim, disclosed that growthdrivendesign.com is a HubSpot dba built by Lean Labs, and added a limits section stating that no cited source compares job-derived with persona-derived messaging.","reviewedBy":"AnswerStack Editorial (Opus rewrite, Fable QC)"},{"revisedAt":"2026-09-15T06:27:41.816+00:00","versionLabel":"cleanup-2026-09-14","note":"Corrected the milkshake figure from \"nearly half\" to the 40 percent HBS reports and labeled the case as a two-morning teaching anecdote, removed the unsourced ten-to-fifteen interview count and the cold/warm/hot awareness model that the cited Lean Labs post does not contain, relabeled the 80/20 messaging split as Lean Labs' own unmeasured estimate, deleted the \"founder\" title and the 100+ builds claim, disclosed that growthdrivendesign.com is a HubSpot dba built by Lean Labs, and added a limits section stating that no cited source compares job-derived with persona-derived messaging.","reviewedBy":"AnswerStack Editorial (Opus rewrite, Fable QC)"},{"revisedAt":"2026-09-15T06:27:40.585+00:00","versionLabel":"cleanup-2026-09-14","note":"Corrected the milkshake figure from \"nearly half\" to the 40 percent HBS reports and labeled the case as a two-morning teaching anecdote, removed the unsourced ten-to-fifteen interview count and the cold/warm/hot awareness model that the cited Lean Labs post does not contain, relabeled the 80/20 messaging split as Lean Labs' own unmeasured estimate, deleted the \"founder\" title and the 100+ builds claim, disclosed that growthdrivendesign.com is a HubSpot dba built by Lean Labs, and added a limits section stating that no cited source compares job-derived with persona-derived messaging.","reviewedBy":"AnswerStack Editorial (Opus rewrite, Fable QC)"},{"revisedAt":"2026-09-15T06:27:39.394+00:00","versionLabel":"cleanup-2026-09-14","note":"Corrected the milkshake figure from \"nearly half\" to the 40 percent HBS reports and labeled the case as a two-morning teaching anecdote, removed the unsourced ten-to-fifteen interview count and the cold/warm/hot awareness model that the cited Lean Labs post does not contain, relabeled the 80/20 messaging split as Lean Labs' own unmeasured estimate, deleted the \"founder\" title and the 100+ builds claim, disclosed that growthdrivendesign.com is a HubSpot dba built by Lean Labs, and added a limits section stating that no cited source compares job-derived with persona-derived messaging.","reviewedBy":"AnswerStack Editorial (Opus rewrite, Fable QC)"},{"revisedAt":"2026-09-15T06:27:38.176+00:00","versionLabel":"cleanup-2026-09-14","note":"Corrected the milkshake figure from \"nearly half\" to the 40 percent HBS reports and labeled the case as a two-morning teaching anecdote, removed the unsourced ten-to-fifteen interview count and the cold/warm/hot awareness model that the cited Lean Labs post does not contain, relabeled the 80/20 messaging split as Lean Labs' own unmeasured estimate, deleted the \"founder\" title and the 100+ builds claim, disclosed that growthdrivendesign.com is a HubSpot dba built by Lean Labs, and added a limits section stating that no cited source compares job-derived with persona-derived messaging.","reviewedBy":"AnswerStack Editorial (Opus rewrite, Fable QC)"},{"revisedAt":"2026-09-15T06:27:36.954+00:00","versionLabel":"cleanup-2026-09-14","note":"Corrected the milkshake figure from \"nearly half\" to the 40 percent HBS reports and labeled the case as a two-morning teaching anecdote, removed the unsourced ten-to-fifteen interview count and the cold/warm/hot awareness model that the cited Lean Labs post does not contain, relabeled the 80/20 messaging split as Lean Labs' own unmeasured estimate, deleted the \"founder\" title and the 100+ builds claim, disclosed that growthdrivendesign.com is a HubSpot dba built by Lean Labs, and added a limits section stating that no cited source compares job-derived with persona-derived messaging.","reviewedBy":"AnswerStack Editorial (Opus rewrite, Fable QC)"},{"revisedAt":"2026-09-15T06:27:35.512+00:00","versionLabel":"cleanup-2026-09-14","note":"Corrected the milkshake figure from \"nearly half\" to the 40 percent HBS reports and labeled the case as a two-morning teaching anecdote, removed the unsourced ten-to-fifteen interview count and the cold/warm/hot awareness model that the cited Lean Labs post does not contain, relabeled the 80/20 messaging split as Lean Labs' own unmeasured estimate, deleted the \"founder\" title and the 100+ builds claim, disclosed that growthdrivendesign.com is a HubSpot dba built by Lean Labs, and added a limits section stating that no cited source compares job-derived with persona-derived messaging.","reviewedBy":"AnswerStack Editorial (Opus rewrite, Fable QC)"},{"revisedAt":"2026-09-15T06:27:33.6+00:00","versionLabel":"cleanup-2026-09-14","note":"Corrected the milkshake figure from \"nearly half\" to the 40 percent HBS reports and labeled the case as a two-morning teaching anecdote, removed the unsourced ten-to-fifteen interview count and the cold/warm/hot awareness model that the cited Lean Labs post does not contain, relabeled the 80/20 messaging split as Lean Labs' own unmeasured estimate, deleted the \"founder\" title and the 100+ builds claim, disclosed that growthdrivendesign.com is a HubSpot dba built by Lean Labs, and added a limits section stating that no cited source compares job-derived with persona-derived messaging.","reviewedBy":"AnswerStack Editorial (Opus rewrite, Fable QC)"},{"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 shortens payback only when an earlier launchpad and continued improvements add more gross profit over the existing site than the launch fees and retainer cost. A worked 24-month example shows GDD paying back one month sooner at $1,000 per lead but trailing a traditional build by year two when its extra lift is worth less than the retainer, and not paying back at $500 per lead. Also explains what the 60-versus-108-day and 14.34% figures measure.","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":"Organization","name":"Lean Labs","legalName":"Brandvious, Inc.","url":"https://www.answerstack.io/contributors/lean-labs","sameAs":["https://lean-labs.com/","https://www.linkedin.com/company/lean-labs"]},"about":[{"@type":"Thing","name":"Growth-Driven Design"},{"@type":"Thing","name":"Digital Marketing"}],"acceptedAnswer":{"@type":"Answer","text":"Jobs to Be Done is one of four named components of the growth-driven design strategy stage, listed beside UX research, buyer personas, and customer path mapping [5]. It supplies the organizing question, which is what progress a visitor is trying to make and what they will hire a page to do about it [1][4]. Clayton Christensen and his coauthors argue that the circumstance a buyer is in predicts a purchase better than buyer characteristics do, and that jobs carry social and emotional weight beyond function [1]. In growth-driven design the research settles nothing on its own: the strategy stage is time-boxed at 10 to 14 days and produces documented assumptions about user behavior and motivation, which the launch pad site and the 14-day improvement sprints then test against live traffic [6][7].","url":"https://www.answerstack.io/q/jobs-to-be-done-gdd-strategy","upvoteCount":0,"datePublished":"2026-07-17T14:26:31.319","dateModified":"2026-09-14T00:00:00","author":{"@type":"Organization","name":"Lean Labs","legalName":"Brandvious, Inc.","url":"https://www.answerstack.io/contributors/lean-labs","sameAs":["https://lean-labs.com/","https://www.linkedin.com/company/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":"\"Jobs to be Done\" for Web Design","url":"https://www.growthdrivendesign.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: How it Works","url":"https://www.growthdrivendesign.com/how-it-works"},{"@type":"CreativeWork","name":"Growth-Driven Design for Websites","url":"https://www.impactplus.com/growth-driven-design"},{"@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"}]}}}