Updated November 20, 2026
What is a growth designer?
Mike Stilling is a Staff designer at Stripe, and the label people most often put on that work is "growth." Drawing on Mike's experience, this guide is a plain-language take on what that means, what the job actually involves, and how it differs from product design.
The short answer
A growth designer designs the moments where people decide whether to become, and stay, a customer. That's marketing pages, sign-up, sign-in, onboarding, pricing, upgrade paths, and contact-sales flows. The work is measured by whether a business outcome moves: more qualified sign-ups, more people reaching the first useful moment in the product, more revenue.
The craft is the same as any other product or web design. What changes is the scope, the partners, and the scorecard.
What growth designers work on
At Stripe, Mike's work centers on the surfaces where people become Stripe users: registration, sign-in, contact sales, and broadly anywhere lots of people are deciding whether to convert. More recently that includes AI-powered experiences, like live chat on stripe.com and LLM-driven personalization.
Across companies, growth design usually covers some mix of:
- Acquisition: marketing pages, landing pages, ads, and anything that brings someone from "never heard of it" to "maybe."
- Conversion: sign-up and sign-in flows, pricing pages, and contact-sales forms.
- Activation: onboarding and the path to the first moment where the product is actually useful.
- Expansion and retention: upgrade prompts, plan changes, and things that keep people around.
Day to day, that means designing and shipping projects, iterating on experiments, building code-based prototypes, and partnering with product, engineering, marketing, data, and leadership to turn ambiguous ideas into shipped things.
Growth design vs product design
Most people describe growth design as a specialism within product design, and that's a fair description. The difference is mostly about what you own and how you're judged.
| Product designer | Growth designer | |
|---|---|---|
| Owns | A feature or area of the core product | Moments across the funnel, often spanning marketing site and product |
| Judged on | Does the feature work well for the people using it? | Did the metric move? |
| Partners | PM and engineering on one team | PM, engineering, marketing, data, sales, sometimes ML |
| Pace | Larger, longer-lived projects | More, smaller changes and experiments |
| Surfaces | In-product UI | Website, sign-up, onboarding, pricing, in-product prompts |
In practice, growth designers end up straddling marketing and product. You'll be in a brand review in the morning and a sign-up form edge-case discussion in the afternoon.
Skills that matter
The fundamentals still matter most: hierarchy, typography, white space, and clear writing. Beyond that, the skills that have made the biggest difference in Mike's work are:
- Messaging. In B2B SaaS you can't explain a product with pictures alone, so copy does a lot of the work. At Rewatch, Mike used analytics to show that pages with concise, feature-based copy converted at a significantly higher rate than pages relying on benefit-based jargon. Relatable benefits still won on social as a hook. (More on that.)
- Reading data without worshipping it. You need to find where people drop off and spot when a "win" is noise. You also need to know when a number is telling you nothing.
- Knowing how things are built. Growth work is a lot of small changes. If you can prototype in code or ship front-end changes yourself, you skip hand-offs and know what's cheap or expensive before engineering is involved. There's more on this in the design engineer guide.
- Business sense. Is the company product-led, sales-led, or both? That changes what "conversion" even means, and which pages deserve your time.
- Picking what matters. At Rewatch the homepage got about 6.5x more traffic than every blog post combined over 30 days. Shifting time from low-performing content to foundational pages was the single highest-leverage call Mike made there.
Where growth design goes wrong
Mike is a bit skeptical of how growth design gets practiced. A lot of it is:
- Hacks over needs. Urgency banners, dark patterns, and clever tricks rarely beat a product that solves a real problem and explains itself clearly. Mike wrote a whole post questioning whether marketing design growth hacks work on B2B SaaS sites.
- Measuring things that can't be measured. Plenty of tests are underpowered or run on pages with too little traffic to say anything meaningful. A "lift" you can't reproduce isn't a lift.
- Incremental forever. Small tests can only take you so far. Sometimes the right move is a bigger rethink, and data alone won't tell you that.
In Mike's view, good growth design is about helping a business anticipate and adapt. Clarity and less friction do most of the work. Experiments help you learn, but they're not the whole job.
How to get into growth design
If you're a product, web, or marketing designer who wants to move toward growth:
- Get close to the numbers. Ask for access to analytics and learn where your product's funnel leaks.
- Own a conversion surface end to end. Pick a sign-up form, a pricing page, or a landing page and take it from problem to shipped to measured.
- Learn enough code to prototype. HTML, CSS, and a little JavaScript, plus modern AI-assisted tools, make it realistic. See prototyping in code for designers.
- Write things down. Document what you changed, why, and what happened. It's how you build a growth portfolio, and how you get buy-in next time.
- Work with marketing, not around it. Many of the highest-traffic surfaces are marketing pages. Treat them as product.
Frequently asked questions
What does a growth designer do?
A growth designer designs the parts of a product and website that decide whether people become and stay customers: marketing pages, sign-up, sign-in, onboarding, pricing, upgrade paths, and contact-sales flows. The work is judged by whether a business metric moves, not only by whether the design is good.
What is the difference between a growth designer and a product designer?
A product designer usually owns a feature or area of the core product and is judged on whether it works well for the people using it. A growth designer works across the funnel, from first visit to activation and expansion, and is judged on movement in metrics like sign-ups, activation, and revenue. The craft is the same. The scope, the partners, and the scorecard are different.
Do growth designers need to know how to code?
It is not a hard requirement, but it is a big advantage. Growth work involves a lot of small, fast changes and experiments. Designers who can build prototypes or ship front-end changes themselves skip a lot of hand-offs and can tell what is technically cheap or expensive before an engineer is involved.
Is growth design just A/B testing?
No. Experiments are one tool. Most of the impact comes from understanding why people are or are not converting and fixing the real problem, usually clarity, friction, or a missing need, rather than tweaking button colors.
What metrics do growth designers work on?
Common ones are visitor-to-sign-up conversion, sign-up completion, activation (reaching the first meaningful moment in the product), contact-sales submissions and qualified leads, upgrades, and retention. Which one matters most depends on whether the business is product-led, sales-led, or both.