What is design-driven growth, and how can strategic design drive business growth?

Design becomes strategic when it informs what gets built as well as how it looks. A designer who joins after the product and the message are settled has fewer things left to change. One who joins while the team is still defining the user's problem can shape what the page says, what the form asks for, or whether a feature should exist.

The business goal matters as much as the user need. An experience can be measured in its own terms, through task completion or ease ratings. Tying the work to a result the business already reports, such as qualified demo requests or support contacts in the first month, also settles what the design is for and who will check whether it worked.

Suppose a company sells scheduling software to dental practices. Demo requests are steady, and many deals stall after the demo. The sales team reports that office managers keep asking how long the switch takes and who moves the patient records.

The team reads that as a worry about the cost of changing systems, which the site doesn't address. That reading is a hypothesis. A few conversations with recent buyers would test it before anyone designs a page.

The design response is to show the switch: a short section on the product page with the steps, the expected duration and who does the work, repeated in the email that follows a demo. The company wanted more closed deals, so the measure is the share of demos that become customers, along with how long those deals take. Page views would say less, because a visit doesn't show that anyone read the new section.

Each step limits the next one. The interpretation has to explain what sales observed, and the design has to answer that interpretation. The measure is chosen before the change ships, which makes it harder to pick one afterward that suits the result. A team that repeats the sequence on its weightiest decisions gets more chances to find a change that moves the business result. Turning user insights into hypotheses and experiments covers how to write each one down.

McKinsey's 2018 report on the business value of design tracked the design practices of 300 publicly listed companies over five years in medical technology, consumer goods and retail banking. Companies in the top quarter of its design index had revenue growth 32 percentage points higher than their industry counterparts over the whole period. Their growth in shareholder returns was 56 points higher.

Those gaps are correlations across five years. Strong design practice and strong results appeared together, and the study doesn't establish that one caused the other. The figures aren't a forecast for a single project.

The practices behind the index are the more useful part. The report groups them into four themes: leadership that measures design, one connected experience for the user, work shared across functions, and continued research and iteration. Each is a way of managing design.

The words are the same in a different order, and the ideas overlap. Growth-driven design is a named method for building and improving a website in three stages: strategy, a launchpad and continuous improvement. We explain it in what growth-driven design is. Design-driven growth is the wider idea, and it applies to products, services and onboarding as much as to a website.

A company can run growth-driven design on its website and still treat design as decoration everywhere else. A company can also practice strategic design without using the named method. The method is one way to apply the idea to a website, with stages and a cadence already worked out.

Lean Labs' article on the three stages advises talking with customers, sales reps and support staff before any page is designed, because each group sees a different part of the buying decision. What they say feeds the page structure and the copy. That is strategic design at the scale of a website: research decides which pages exist and what each one says, and visual design builds on it.

Lean Labs' growth-driven design program keeps the connection going after launch. It chooses each cycle's work from page behavior, forms, CRM lifecycle stages and sales feedback. It ranks the options by expected effect on pipeline, by buyer relevance and confidence, and by effort. So an estimate of the effect on pipeline is one of the inputs to each choice of work.

Choose the measure and record it before the change. Nielsen Norman Group's guide to benchmarking describes comparing an experience's metrics with a meaningful reference: an earlier version, a competitor, an industry standard or a goal the team sets. For a change to your own site, the earlier version is the reference you control, and parts of it are hard to recover later if nobody captured them, such as observations of people attempting a task on the old page.

A before-and-after difference still needs careful reading. Other things change between the two readings, including traffic sources, the season and whatever else the team shipped. A controlled comparison, where some visitors see the old page and some the new one over the same period, is one way to learn more about a single change.

In the dental software example, the first reading could go either way. If the close rate rises, that fits the team's reading without showing the worry was the cause. If it stays flat or falls, the interpretation may have been wrong, and the buyer conversations are worth revisiting before the next change. The metrics worth tracking and the question of whether a redesign will fix low conversion rates both start from that baseline.