Building a growth team that doesn't optimise itself into a corner
Growth teams measured on short-term conversion metrics make decisions that improve this quarter's numbers and degrade next year's retention. This is not incompetence — it is the logical outcome of misaligned incentives. The team structure, metric ownership, and reporting chain that produces genuinely compounding growth is different from the setup most companies default to, and the differences are specific.
How growth teams paint themselves into a corner
The standard growth team setup looks like this: a VP of Growth or Head of Growth owns acquisition and conversion metrics. The team is measured on MQLs, signups, trial starts, or paid conversions — depending on the product model. Experiments are prioritised based on their expected impact on these metrics. The team reports to the CEO or the CRO, has a dedicated engineering pod, and runs weekly or fortnightly experiment reviews.
This setup has a structural flaw that is not immediately visible: the metrics the team owns end at the point of conversion. What happens after a user converts — whether they activate, whether they retain, whether they expand — belongs to someone else. Product owns activation. CS owns retention. The growth team's job ends when a user enters the funnel.
This creates a specific failure mode: the growth team optimises the messaging and onboarding flow to maximise the number of users who start a trial or complete a signup, regardless of whether those users are the ones who will retain and expand. Urgency-based email sequences, aggressive paywall prompts, and friction-reducing signup flows all improve short-term conversion. They also attract a higher percentage of low-intent users who churn quickly, inflate the denominator on activation and retention metrics, and create a perpetual headwind for the CS team.
Over time, a growth team operating this way does not just fail to improve retention — it actively degrades it. The product experience gets tuned for short-term conversion signals that do not correlate with long-term value. The onboarding flow gets optimised for click-through rates rather than activation depth. By the time the retention problem is visible in the NRR data, the growth team has shipped two years of decisions that need to be unwound.
The metric ownership problem
The core issue is that conversion rate and retention rate are owned by different teams with different incentives and different time horizons. The growth team sees a 15% improvement in trial-to-paid conversion as an unambiguous win. The CS team sees a 10% increase in 60-day churn among the same cohort as an unambiguous problem. Neither team is wrong — they are each looking at the part of the data that falls within their mandate.
The fix is not to merge growth and CS into a single team (this creates a different set of problems). The fix is to change the primary metric that the growth team owns. The metric that aligns growth incentives with long-term product health is qualified activation rate — not conversion rate. Qualified activation is defined as the percentage of new users who complete the set of actions in the first session or first week that your cohort data shows to be predictive of 90-day retention.
This metric has three useful properties. First, it forces the growth team to care about the quality of users it attracts, not just the volume — because unqualified users who convert but do not activate drag the number down. Second, it creates a direct connection between growth work and retention outcomes, aligning the growth team's incentives with the long-term product health. Third, it is a leading indicator rather than a lagging one: you can measure qualified activation within seven days of a user's first session, versus 90 days for retention. The feedback loop is much tighter.
The reporting chain that makes this possible
Changing the growth team's primary metric from conversion rate to qualified activation requires a reporting chain that aligns incentives accordingly. The growth team cannot report to a CRO whose performance is evaluated on monthly bookings and quarterly revenue. The CRO's incentive is to maximise short-term conversion, and under pressure — when a quarter looks soft — that incentive will override the growth team's longer-term focus.
The growth teams that sustain genuinely compounding results over a multi-year horizon typically report to the CPO or the CEO. This is not because these leaders are inherently more aligned with long-term outcomes — it is because their evaluation criteria include retention and product quality, not just bookings. A CPO whose annual review includes NRR and 90-day activation rate has structural reasons to support a growth team that optimises for these outcomes. A CRO whose annual review includes only ARR added does not.
If the organisational politics of changing the reporting chain are too difficult, a workable compromise is a dual accountability structure: the growth team has a primary reporting line to the CPO and a secondary accountability to the CRO for bookings-related metrics. This is imperfect, but it surfaces the tension between short- and long-term metrics explicitly rather than resolving it by default in favour of the short-term.
The team composition that reduces optimisation tunnel vision
Growth teams that optimise themselves into a corner are typically composed of people who are excellent at running experiments and interpreting results, but who have limited exposure to the downstream consequences of their decisions. They see the conversion funnel in detail and the retention curve only vaguely.
The structural fix is to embed at least one person on the growth team whose primary context is retention — either a CS-aligned product manager who attends growth experiment reviews, or a data analyst who is responsible for tracking cohort retention alongside conversion metrics. This person's job is not to veto experiments. It is to flag when an experiment that improves a conversion metric is likely to degrade a downstream retention metric, based on the pattern of users it attracts or the behaviour it reinforces.
This sounds like a small organisational change. In practice, it shifts the growth team's decision-making culture meaningfully over six to twelve months. When someone in the room is consistently asking "what does this do to 90-day retention?" the team starts asking the question itself, before the experiments ship. The question gets built into the prioritisation framework. The metric ownership problem does not disappear, but it stops being invisible.
- 01Change the primary metric from conversion rate to qualified activation rate. Define qualified activation as the set of first-week behaviours that your cohort data shows to be predictive of 90-day retention. Measure this for every cohort, by acquisition channel. This is the number the growth team is accountable for improving.
- 02Route the growth team's reporting line through product, not sales. A growth team reporting to a CRO is optimised for bookings. A growth team reporting to a CPO is optimised for product quality and long-term retention. The reporting chain determines which incentive wins when they are in tension.
- 03Embed a retention anchor in every growth experiment review. Every experiment review should include a projection of the expected impact on 90-day retention of the cohort the experiment affects. This does not need to be precise — an order-of-magnitude estimate is sufficient. It prevents the team from treating conversion metrics as uncaused causes.
- 04Require growth experiments to ship with retention tracking. Every experiment that changes the acquisition or onboarding flow should have a retention tracking plan attached to it: what cohort data will be collected, when it will be reviewed, and what result would indicate that the experiment produced a retention side-effect. This makes the downstream consequences of growth decisions visible rather than invisible.
- 05Audit your onboarding flow for conversion-retention trade-offs annually. Ask: which elements of our current onboarding were designed to improve a conversion metric rather than to accelerate time-to-value? For each one, measure whether it has produced a retention trade-off. Some of these trade-offs are acceptable. Most are not — and most have never been explicitly evaluated.
Frequently asked questions.
What should a growth team's primary metric be?
The primary metric should be qualified activation — not signups, not trial starts, not even paid conversions as a raw number. Qualified activation is defined as users who have completed the set of actions in the first session or first week that your data shows to be predictive of 90-day retention. This metric forces the growth team to care about the quality of users it brings in, not just the volume, and directly aligns its incentives with the long-term health of the product and NRR.
How should growth teams be structured relative to core product?
Growth teams should own the acquisition funnel, first-use experience, and upgrade flow, but should not have independent authority to ship changes to core product features without product team sign-off. The boundary matters because growth optimisation and core product development have different time horizons and risk tolerances. A growth team with full autonomy over the core product will systematically optimise short-term metrics at the expense of the long-term user experience, and the damage may not be visible for 12–18 months.
When should a company form a dedicated growth team?
Form a dedicated growth team when the funnel is large enough that conversion improvements produce material revenue impact — typically at $1–3M ARR — and when the core product team is too focused on feature development to run experiments systematically. Before this point, growth experiments should be owned by the founding team or a single growth-focused product manager. A dedicated growth team too early creates organisational overhead without enough leverage to justify it, and fragments the product decision-making process before the company has enough data to make systematic experimentation useful.
How do you prevent a growth team from optimising for vanity metrics?
Require every metric the growth team tracks to have a demonstrated causal or strongly correlational relationship with 90-day retention or NRR. Do this explicitly, in writing, when the team is formed. Any metric that the team wants to add to its dashboard must pass this test before it can influence experiment prioritisation. This prevents the accumulation of engagement proxies — time on page, email open rates, feature click-through counts — that look like progress but predict nothing about whether the business is actually growing.
Working on this?
If this is the problem on your desk, a 30-minute intro is the fastest way to find out whether I can help.
Request an intro →