Skip to content
AppDues
Log in
Contact salesSign up

How a 70-person growth team scales testing, activation and feature education

Scaling growth is less about adding headcount than about changing how decisions get made. The conversation with Strava's Jason van der Merwe describes growing from zero to five cross-functional teams totalling over 70 people, while keeping a focus on user impact, rapid experimentation and helping new users find value.

What growth engineering means in practice

Growth engineering is described as established at larger companies and increasingly common among app companies. Its purpose is to link users to the value a product provides and then broaden that value. That definition shifts the job away from delivering a specification and toward asking whether the result improves outcomes for users and the business. The mindset change is significant: an engineer is expected to think like a cross-functional product manager, weigh user and business impact, and occasionally depart from the usual rules when that serves the outcome. The operating style is summarised as managed chaos — accepting that app work is messy while using frequent testing to find what works.

Testing as the route to large wins

Testing is treated as the engine of growth. When the work began, there was a dedicated new-user activation team, and the priority was new-user optimisation. One early test reduced friction for users and improved retention, becoming one of the biggest wins and a foundation for later work. The lesson is to run as many ideas as possible, because large gains usually come from experimentation rather than from a single planned launch. As the organisation expanded, the emphasis moved from a few large experiments toward solving specific problems in parallel. That creates a new risk: teams can lose the overall picture. Keeping insights and learnings visible across every team is therefore essential, so local problem-solving does not fragment into disconnected efforts.

Feature education and the newcomer perspective

Feature education helps bridge the gap between experienced internal users and newcomers. Most employees use the product every day, which gives them deep familiarity but makes it harder to judge the experience from a first-time perspective. Using tooltips, push notifications, emails and as many other channels as appropriate helps new users understand features they might otherwise overlook. The broader point is to keep moving and making decisions even when measurement is imperfect, rather than waiting for complete observability. The conversation also covers team core values and treating teams as platforms that optimise and deliver user experience.

A checklist for applying these lessons

A practical checklist drawn from these ideas: define growth work by user and business impact, not by task completion; test many ideas, starting with activation and friction; record and share learnings across teams as the organisation grows; review the product through a new user's eyes; teach features across multiple channels; and keep deciding and iterating even when data is incomplete.

Frequently asked questions

What is growth engineering?

Growth engineering connects people with the value a product already offers, then widens that value over time. In practice it means working across product, engineering and user needs, judging work by user and business impact rather than by simply shipping an assigned task.

Why does testing matter so much for growth?

Testing many ideas, especially around new-user activation and friction, is presented as the route to the largest wins. An early friction-reduction experiment that lifted retention is given as the foundational example, with later work building on those fundamentals.

Why is feature education important?

Because daily internal use can make it hard to see the product as a newcomer does. Teaching features through in-product tips, push notifications, email and other channels helps new users discover value they would otherwise miss.