What is a design-driven approach?
Written by
Passionate Designer & Founder
A design-driven approach means treating design decisions as strategic business decisions, not visual finishing work. The designer is in the room when positioning is being set, not handed a brief after the strategy deck is done. Companies that do this well use design to shape what the product is and who it's for, not just how it looks.
Most companies claim to be design-driven and are not. The tell is sequencing. In a genuinely design-driven organisation, design input happens during problem definition. Airbnb in 2013 used design methods to reframe their product from "air mattress rental" to "belong anywhere." That narrative shift drove revenue from $200,000 per week to $1 million per week in the months that followed. Apple's product development process, where the design team worked in parallel with engineering rather than downstream of it, is the other well-known case. Both show design influencing the product concept, not decorating the output.
In practice, a design-driven approach at a SaaS company looks like this: the product roadmap gets reviewed through a positioning lens before features are specced. The marketing site is treated as a narrative artefact, not a conversion template. The onboarding flow is designed around the customer's moment of doubt, not the company's feature checklist. Design-driven growth is what happens when all three of those things are true at once.
The mistake I see most often is companies adopting design processes, sprint ceremonies, design systems, component libraries, without adopting design thinking at the strategic level. You can have a perfectly maintained Figma design system and still be designing the wrong product for the wrong audience at the wrong price point. The system organises execution. It does not fix the upstream strategic question. Execution without strategy compounds nothing.
What it actually requires organisationally
Across our 4x Awwwards-winning work, the projects that generated the most measurable business impact were not the ones with the most refined UI. They were the ones where we were brought in before the brief was written, when the real question was still "who is this for and what do we want them to believe." That upstream work, combining brand positioning, category design, and narrative architecture, is what makes the downstream design compound into something real.
The tradeoff is organisational politics. A design-driven approach requires design to have a seat at the table in commercial conversations, which disrupts established power structures at most companies, particularly ones where product and marketing have historically owned strategy. The companies that pull it off typically have a founder who came from design, or who has seen design-driven growth work firsthand and is willing to restructure decision rights accordingly. That's a harder internal sell than adopting a new design tool, and most companies stall there.
For a Series-B SaaS company, adopting a design-driven approach means two concrete things. First, bring your design partner into the positioning conversation before the campaign brief exists. Second, measure design outputs against business metrics, activation rate, trial-to-paid conversion, net revenue retention, not aesthetic scores or delivery speed. Design that cannot be connected to a number is decoration. Our product design agency for SaaS overview covers what the strategic partner relationship looks like versus a production-only engagement. To talk through whether your current setup can generate design-driven growth, book a 20-min intro. For the full guide, read our design-driven growth overview.
