Updated November 22, 2026
Growth design at scale
Mike Stilling is a Staff designer at Stripe, working on the surfaces where people become Stripe users. Before that, Mike was often the only designer focused on marketing and growth at smaller SaaS companies. This guide covers what changes when growth design moves from a startup to a company where millions of people pass through the same few screens.
The short answer
At scale, growth design is less about doing everything yourself and more about making the right changes, with the right people, safely. The craft is the same: clear hierarchy, honest copy, and less friction. What changes is the stakes. When a page is seen by millions of people, a small improvement is worth a lot, and a small mistake costs a lot too.
What changes at scale
At a startup like Rewatch, Mike was the sole designer focused on marketing. That meant owning brand, the marketing site, sales decks, and content, and shipping fast. (More on that.) In a large company, the shape of the job is different:
| Startup growth design | Growth design at scale | |
|---|---|---|
| Scope | The whole funnel, often alone | A few high-impact surfaces, very deeply |
| Traffic | Often too little to test reliably | Enough to detect small changes |
| Owners | You and a couple of engineers | Many teams: product, platform, risk, legal, marketing, data |
| Risk | A bug is a quick fix | A bug can affect a huge number of people |
| Main lever | Speed | Judgment, alignment, and leverage |
None of this means big-company work is slow. It means speed comes from different places: clear problem framing, prototypes that settle debates, and good relationships with the teams who own the systems underneath.
The surfaces that matter most
At Stripe, Mike's work centers on registration, sign-in, contact sales, and broadly anywhere lots of people are deciding whether to convert. More recently that has grown to include AI-powered experiences, like live chat on stripe.com and LLM-driven personalization.
These surfaces share a few traits:
- They're short, but heavily loaded. A sign-up form might have a handful of fields, and every one of them carries product, risk, compliance, and routing requirements.
- They serve very different people at once. A solo founder and a Fortune 500 procurement team can land on the same page. The design has to work for both without becoming a maze.
- They're shared. Many teams depend on what happens there, so changes ripple.
- Small details compound. Copy, field order, error states, and load time all matter more when multiplied by huge traffic.
The lesson from smaller companies still applies: focus on the pages that actually get traffic. At Rewatch, the homepage got about 6.5x more traffic than every blog post combined over 30 days. That one fact justified shifting time toward foundational pages. At scale, the same thinking helps you pick which surface, and which step within it, deserves attention.
Working across many teams
Growth surfaces sit between teams. Mike's peers at Stripe have described this part of the job well. A user researcher noted that Mike "can be trusted to straddle this boundary between teams and satisfy two sets of stakeholders with sometimes differing viewpoints." A staff product manager called Mike "a fantastic thought partner" who "collaborated without ego."
A few habits help:
- Find the owners early. Before designing, learn who owns each system the surface touches. Bring them in before the design is precious.
- Make the problem shared. Write down what's wrong, who it affects, and what success looks like. Teams align faster on a problem than on a solution.
- Prototype to decide. A working prototype turns opinions into a concrete thing people can react to. One Stripe product marketer said a prototype of Mike's "was instrumental in gaining leadership approval." There's more on this in prototyping in code for designers.
- Keep a good vibe. Great work that comes out of bad team dynamics doesn't last. Being easy to work with is a real part of the job.
Shipping safely
When a surface is seen by millions of people, how you ship matters as much as what you ship.
- Roll out gradually. Release to a small share of traffic first, watch the numbers and the support queue, then expand.
- Design the edge cases. Errors, slow connections, unusual accounts, accessibility needs, and different languages and regions are where high-traffic flows break.
- Measure what you meant to change. Agree on the metric before launch, and check guardrails like support contacts or drop-off further down the funnel. See running design experiments at scale.
- Keep it reversible. Feature flags and clean rollbacks make it safe to try bolder ideas.
What good looks like at the staff level
At the staff level, growth design is measured less by how much you personally ship and more by the leverage you create:
- Choosing the right problems. Spending time where traffic, revenue, and user pain overlap.
- Raising the quality bar. Holding a high bar on craft while staying fast. A Stripe product manager noted Mike's ability "to juggle multiple projects and meet all deadlines while still maintaining a high bar."
- Closing the gap with engineering. Knowing what's technically reasonable before an engineer is involved. A Stripe design engineer said that Mike's knowledge of front-end principles "creates a working relationship rooted in empathy between disciplines."
- Growing other designers. Mentoring, sharing workflows, and making the whole team faster. Mike mentors designers through Stripe's formal mentorship program and helps scale AI and code-based prototyping across the design org. See scaling code prototyping across a design org.
Frequently asked questions
How is growth design different at a large company than at a startup?
At a startup, one designer often owns the whole funnel and ships changes in hours. At a large company, each surface has more traffic, more owners, and more risk. Small changes can have large effects, so the work leans more on alignment, careful rollout, and measurement, and less on solo speed.
What surfaces does a growth designer own at scale?
Usually the high-traffic moments where people decide whether to become a customer: registration, sign-in, contact sales, pricing, onboarding, and the marketing pages that feed them. Increasingly it also includes AI-powered experiences like chat and personalization.
How do you get buy-in for growth design work in a big organization?
Show, don't pitch. A working prototype that people can click through turns abstract debate into a concrete decision. Pair it with the data that explains why the surface matters, and bring the teams who own adjacent systems in early.
What makes a growth designer effective at the staff level?
Scope and leverage. Staff-level growth designers pick the problems that matter most, work across product, engineering, marketing, data, and leadership, and raise the quality bar for the people around them through systems, prototypes, and mentorship.