Two Designers, Two Scoreboards: Split Growth From Core Before You Staff

You need someone to move signups. So you post a job, call it "product designer," and hope the new hire figures out the rest. Six months later they are fighting your core team over the same screen, both sure they are right. They are both right. They are working two different jobs against two different scoreboards, and nobody drew the line.

The fix is boring and it works. Decide what growth owns and what core owns before you hire, not after. This brief pulls the split into one place so you can staff it clean.

The deep cut

• Growth and core run on separate scoreboards. A growth designer chases activation and retention; core owns the daily job the product does.
• One title for two jobs breeds turf wars. Skip the split and your growth and core designers fight over the same signup screen.
• Name the metric each role owns first. Spotify's data approach starts with the one number that tells you a bet worked.

Two jobs wearing the same title

Growth design and core product design look alike on a resume. Both draw screens, both talk to users, both ship. The gap is the goal. Siva Sabaretnam's cheat sheet lines them up side by side: different goals, different metrics, different tools. A growth designer tunes the funnel, the moment a new user decides to stay. A core designer builds the thing they stay for.

When you hire one title for both jobs, you get a person split down the middle. They optimize a signup flow on Monday and redesign a settings page on Tuesday, and they are graded on neither well. Pick the job first. Then hire for it.

Growth is a science, not a vibe

Growth design is not "make the numbers go up somehow." Carl Thomas defines it as growth science meeting human-centered design, with a fail-fast habit built in. You run a test, you learn, you kill it or keep it. Speed matters because you are buying information, not shipping a monument.

That mindset traces back to growth hacking, which Mari Luukkainen describes as fast, experiment-driven growth pulling marketing, design, and analytics into one loop. Note the word marketing. Growth work reaches past the product surface, which is exactly why it needs a boundary with core. If your growth designer never touches acquisition or onboarding data, you hired a core designer and mislabeled them.

The scoreboard decides the hire

Before you write the job post, write the metric. Florian Biesinger of Spotify makes the case for picking the one key metric that tells you a feature works, then deciding up front when you keep, kill, or iterate. Do that for the role, not just the feature. Growth owns activation and retention. Core owns the metric that proves the daily job got easier.

Dhawal Patel pushes growth designers to measure impact every week and treat customer development as a core skill, not a nice-to-have. That cadence is the tell. If a candidate cannot name what they would measure by Friday, they are wired for core work. Match the wiring to the scoreboard and the turf war never starts.

Building for scale without starving the base

Growth that ignores the core product is a leaky bucket. Judith Lopez frames growth design as user-centered and cross-functional work aimed at products that scale, which only holds if the thing users arrive at is worth staying for. Push all your talent to the funnel and the product underneath goes stale.

So staff both, and make them partners, not rivals. Growth feeds core what it learns at the edges. Core keeps the daily experience strong enough that growth's wins stick. Draw the seam where they meet, usually onboarding and first-run, and name who owns it. One owner per screen, one metric per role.

Three questions for your team

• For our next hire, do we need someone who owns activation and retention, or someone who owns the daily job the product does? Write the metric before the job post.
• Where exactly does growth's turf end and core's begin, and who owns the onboarding screens in between? Name one owner per surface.
• Can each designer tell us what they will measure by Friday? If not, we hired for the wrong scoreboard.