There are two approaches to growing a product.
It’s a no-brainer. Your growth efforts will be much more effective if you establish a continuous, consistent cadence of experimentation to identify the leaks in your funnel and come up with test ideas based on multiple sources of data.
Peep Laja uses a great metaphor: “Would you rather have a doctor operate on you based on an opinion, or careful examination and tests?” You’re like a growth doctor, and your product is your patient.
When you focus on tactics first, you run into three core problems:
Tactics are important. But instead of focusing on them first, focus on establishing a systematic and repeatable experimentation process. This will lead you to discover the combination of tactics that result in sustainable growth for your product.
Your growth efforts will be more productive and successful once you move away from testing random tactics and start approaching it as the scientific process it is:
The first step in the growth process is about collecting quantitative behavioral data and qualitative user insights to identify the biggest issues your customers and potential customers are experiencing—and then using those findings to guide your experiments.
Fixing these problems will help you meet your customer’s needs and expectations, craft an experience they’ll love, and improve your growth curve along the way.
Start by gathering quantitative data that shows you where the problem is—where the biggest dropoffs are and where your funnel is leaking. Once you know where the issues are happening, you can gather qualitative insight to understand why. What’s causing people to have doubts, uncertainties, and hesitations?
And once you know the source of the problem, you can come up with hypotheses to test about what you think would remove the friction.
Here are 11 data sources you can use to generate data-driven growth experiments. You don’t have to use every single one—choose a combination of three to five quantitative and qualitative sources that make the most sense for what you’re trying to learn. As you do your research, document all the issues you identify and test ideas you come up with in your backlog.
Identify specific pages and steps in your product flow where you’re losing customers and potential customers.
Identify annoying cross-device and cross-browser issues that are hurting your conversion rates. Fix issues if the added value is greater than the value of the time it will take your developers to identify and fix them.
Know exactly which form fields people hesitate the most to fill out, which fields they leave blank even though they are required, and which ones cause the most error messages.
Anonymously record video of everything people do as they interact with your product. Watch how people respond to your product while risking their real money or personal information.
Place surveys on low-performing pages and ask people why they aren’t converting. Chat transcripts give you insight into common frustrations and where people get confused.
Observe people while they use your product and speak their thoughts out loud. Hear and see where people get stuck, confused, and frustrated.
Use click maps, attention maps, and scroll maps to record what people do on your product pages with their mouse or fingers.
Hour-long team exercise. Review your product page by page with your team and identify where you can make the experience more relevant, clear, and value-adding—and where you can reduce friction and distraction.
Twenty-minute team exercise. Everyone picks one or two products from your competitive and noncompetitive space that they use actively. Walk through their product flow and discuss what they do well, what they could do better, and how you can adapt it to your own product and audience.
Talk to other growth professionals on the phone on a regular basis. Exchange ideas, share experiments, and discuss what worked, what didn’t, and why you think you got the results you did. Adapt ideas to your own product.
Hour-long team exercise. Spend the first 20 minutes asking nothing but “why,” “what if,” and “what about,” questions. No discussion or answers. Write your question on a sticky note, announce it to the team, and put it on the whiteboard. This reveals what you don’t know and generates discussion.
As you gather and analyze the data you collect, you should be dumping all the issues you identify and experiment ideas you come up with into your backlog. The next step in the process is to translate those findings into a prioritized pipeline of hypotheses to test.
If you want to learn how to:
Then click the button below to download the product manager’s guide to customer-centered growth for free.
Get our best human insight resources delivered right to your inbox every month. As a bonus, we'll send you our latest industry report: When business is human, insights drive innovation.