20Growth: Three Growth Lessons Scaling Whatsapp from 0-100M, Why You Should Hire a Head of Growth Sooner Than You Think & The Biggest Mistakes Founders Make When Hiring for Growth with Ryan Wiggins, Head of Growth @ Mercury

19 May 2023 · 47 min

Ask about this episode

Ask anything about it. ChatGPT or Claude reads this page and answers with the times it was said.

Connect VO and ask about every podcast you hear, including the moments you saved. Add to ChatGPT · Add to Claude

In short

Podcast Summary: The Twenty Minute VC (20VC) - Episode with Ryan Wiggins

Episode Overview Title: 20Growth: Three Growth Lessons Scaling WhatsApp from 0-100M Guest: Ryan Wiggins, VP of Growth and Analytics at Mercury Host: Harry Stebbings Release Date: Not specified

Description In this episode, Harry Stebbings interviews Ryan Wiggins, who has played pivotal roles in scaling growth teams at major tech companies like WhatsApp and Facebook. The conversation revolves around crucial growth strategies, hiring practices for growth teams, and insights derived from Ryan's unique experiences in the tech industry.

Key Topics Discussed

  1. Career Path to Growth
  2. Initial Steps:
  3. Ryan began his career at Facebook in customer support.
  4. A pivotal moment was taking a SQL class that changed his career trajectory towards growth.
  5. Transition to Growth Roles:
  6. He worked at Facebook before moving to WhatsApp, where he contributed to growing WhatsApp Business from 0 to 100 million users.
  1. Building and Hiring Growth Teams
  2. When to Hire for Growth:
  3. Importance of having product-market fit and a reliable user acquisition channel before hiring growth personnel.
  4. Profile of the First Growth Hire:
  5. Should be a growth leader capable of architecting a growth system rather than a jack-of-all-trades.
  1. Hiring Process Insights
  2. Interview Structure:
  3. Assess candidates’ ability to understand customer behavior, execute analyses, and contribute to team dynamics.
  4. Case Studies:
  5. Preferably use generic case studies rather than ones from current companies to avoid biases.
  1. Effective Onboarding Strategies
  2. First 30, 60, 90 Days:
  3. Initial focus on understanding team dynamics and product processes.
  4. By month three, new hires should start to form opinions and contribute to strategic growth initiatives.
  1. Common Mistakes in Growth Hiring
  2. Key Errors:
  3. Assuming a single hire will drive growth without understanding the need for a systematic approach.
  4. Overlooking the importance of customer feedback and product experience in growth strategies.
  1. Growth Execution and Experimentation
  2. Importance of Speed:
  3. Growth teams should operate in an exploratory mode to validate hypotheses quickly and iterate on successful strategies.
  4. Handling Data:
  5. Ryan emphasizes understanding input metrics that lead to successful growth outcomes rather than just focusing on outputs.
  1. Lessons from WhatsApp's Growth
  2. Key Takeaways:
  3. WhatsApp’s initial growth was driven by product-market fit and simplicity rather than extensive data analysis.
  4. Understanding customer journeys and addressing drop-off points are critical for driving user retention.
  1. Future of Growth
  2. Evolution of Growth Strategies:
  3. The need to focus on sustainable product experiences as ad platforms become more expensive and competitive.

Key Takeaways

  • Curiosity and Value Addition: Always pursue what you are curious about to add value to your team.
  • Holistic Growth Approach: Look at the entire customer journey rather than focusing solely on acquisition.
  • Red Flags in Hiring: Watch for self-centeredness, unsustainable quick wins, and lack of receptiveness to feedback during onboarding.
  • The Role of Growth Teams: Should be a sustained investment; growth is a system requiring constant evaluation and adaptation.

Conclusion This episode provides valuable insights for startup founders and growth leaders on the importance of strategic hiring, effective onboarding, and understanding customer needs in achieving sustainable growth. Ryan Wiggins shares his journey and lessons learned from his experiences at WhatsApp and Mercury, making it a must-listen for those in the tech and startup space.

Written by AI. May contain mistakes. Listen to the episode to check what was said.

Hear the part that matters, and keep it.Open this episode in VO. Double tap your headphones to save a moment as you listen.
Get VO free

Transcript

Automatic transcript. May contain errors.

0:00This is 20 growth with me, Harry Stabrings. This is the monthly show where we sit down with the best growth leaders to unpack their tips, tactics and strategies to scale in growth themes and state, which are joined by Ryan Wiggins, VP of Growth and Analytics of Mercury, where he oversees a growth theme and founded the analytics function. Prior to this, Ryan built growth themes at WhatsApp, where he helped grow WhatsApp business from 0 to 100 million users, workplace and Facebook ads. And if that was enough, Ryan's also an extremely active angel ambassador. But before we dive into the show's day, and I'm really excited about this net sponsor, because a few of my portfolio companies use it and love it.

0:36So do you know the impact of your marketing efforts? It's more important this year than ever to know the impact. Or how much you've spent so far this month, and what you've got as a result. You're not alone in not knowing these answers, even though marketing is now all about the data, most companies still use manual spreadsheets for reporting an analysis. But if you want a supercharged gross, spreadsheets just won't cut it. Funnel is the world's first and only marketing data hub that takes all the manual effort out of data collection and lets you blend data from different platforms to unlock new, deeper insights.

1:09And the best part is this can all be achieved without writing a single line of code. I can hear your sigh of relief. That's why it's used by more than 2000 of the world's top brands and media agencies, including Samsung, Adidas, Sony and have As media. Start your own free trial by visiting funnel .io slash 20vc. That's funnel .io slash 20vc. And finally we've all been there but nothing is quite so depleting as the blinking cursor on an empty page reminds me of law school. You're sitting there trying to come up with ad copy or hypothetically a set of interview questions for a podcast you run obviously personal and it's just staring back at you like a brick wall.

1:48This moment of frustration amid growing content amounts is probably why I'm hearing about Jasper non -stop these days. Jasper is an AI assistant for business that helps mark his sales reps and other creators, accelerate their writing process and repackage content into different formats, languages and tones. Online broad use AI tools, Jasper was built for business and this makes a big difference. In Incorporate's SEO, a plagiarism checker, and a browser extension, so you can call up Jasper in pretty much any text box or platform you use online. Visit jasper .ai for slash 20VC for a demo. Your burnt out team will thank you.

2:32Ryan,

2:36I am so excited for this, my friend. I spoke to Alex Shulls, I spoke to Kourtynia, I spoke to Sachin, I know so much about you, but thank you for joining me. Hey, Eric, excited to be here. I'm really excited to get to chat. I would love to start with a little bit on you. So first question is how did you make your way into the world of startups? And then secondarily how did you make your way to Mercury today? I started my career in a customer support role at Facebook right out of college. I didn't really know what I wanted to do, but one day someone offered a sequel class and I took that class and it basically changed my life.

3:07I used that in my support job. I tried to basically figure out why I was getting yelled at so much and tried to improve what we were doing with customer support. Then a couple years later when I was looking for a new job, it turns out that I was doing the whole time was growth. That got me connected to Alex Schultz and a team at Facebook, known as growth marketing that sits at the intersection of data, product and marketing. And I spent six years there helping grow different products across Facebook, things like Facebook ads, workplace, and WhatsApp, where I spent about three years really going deep on how we grow some products.

3:38At some point, I wanted to go explore some earlier stage problems and so start to look and stumble across Mercury. How I ended up with Mercury was that I started some conversations and then took a look at the product and immediately knew that I wanted to join. For those in your audience who aren't aware, Mercury is banking for startups. We offer a product that helps startups solve all their banking needs and it's such a better banking experience than anything else I had experienced. And since then, about two years in, we've scaled to over 100 ,000 startups. We have established a super strong product -led growth motion and I've gotten the opportunity to help build a world -class analytics team.

4:12So I meet this with respect. You don't have the Harvard Stanford Facebook growth team, like LinkedIn profile, like Brian Hale and like many other grace. My question to you is, do you think we placed too much emphasis on these logos? And what do you advise people who are navigating their careers and maybe quite you didn't always know that this was what you'd ultimately do in the end? And what would you advise them? Yeah, I started my career and been pretty humble backgrounds. And the thing that's interesting is that growth wasn't even really a job when I started. Basically my entire career has been unplanned, but there have been two guiding principles that have guided a lot of my career that have come in the form of advice.

4:52And the two kind of things that come up is that first at the end of the day you have to pursue things that you're really curious about and you have to use those curiosities as a way to add value to the team you're on. I always had this saying which is that you should blossom where you're planted. I've tried to do that as much as I can and when I've done that it creates options for where I can go. Second, someone once gave me the advice that you should try to pick a role in a person you want to be and try to understand your skill gap to that role. And then once you find opportunities to apply that skill gap, you try to make progress in that.

5:20And you can re -evaluate over time, but if you're pointing in a direction trying to make progress in that, you'll grow in ways that you didn't expect. But I found that those two principles have helped me and helped guide my career and giving me opportunities that I wouldn't have ever expected. Let's be keep growing in ways he didn't expect. A Facebook and WhatsApp are to meet your growth case studies over the last 10 years. I'm just fascinated when you review those years that you spend at both organizations or within the organization there. What a once to the biggest takeaways for you Ryan from seeing first -hand the hypergrowth there.

5:52And how did that impact your mindsets? I enjoyed WhatsApp in 2017. WhatsApp was very different than everything I had learned at Facebook. And for six years at Facebook, the thing I had learned was that data is core to everything. and you understand funnels, you instrument things, you don't make a decision without having some data to the table. But when I joined WhatsApp, it had a billion and a half users. And it really only had about one product manager, about two to three data people working on it. So what I learned about WhatsApp and how WhatsApp grew was really kind of three things. First, it was the right product for the right market.

6:23If you look at the market at the time when WhatsApp launched, the app stores and smartphones were just launching. SMS prices across the world were about 10 cents a message. And the second thing is that WhatsApp built a product that was really simple and it was reliable. They focused ruthlessly on the core things you should do, which is be able to send a message and it go through. And it always worked. In the four years I worked on WhatsApp, it never went down. But then the kind of third thing was that they added fuel to the fire and found what was working and tried to enhance that. In particular, there was some partnership deals early on in the lifecycle of WhatsApp, where they partnered with carriers to offer free data packs.

6:56This kind of aligned incentives with WhatsApp and the carriers because carriers wanted people to buy the data packs and those users would then buy the data packs and use WhatsApp. So it was kind of a protruding cycle up growth. That led to a product that just took off and became a fuel for a lot of growth. I just dive in and ask when you look at the gross of WhatsApp, did it ever not go up into the right? Was that ever a corsa where it was flat or where it wasn't meteoric? So I think that WhatsApp hit S curves along the way throughout. And when you look at an overall WhatsApp growth, the thing that it looks like is a straight upwards trend in the coming online and reaching around 600 million smartphones over the course of the last 10 years has been just a huge boon to WhatsApp's growth and has been something that always adds incremental numbers and it's become a really saturated product in that market.

7:45But there are some markets where WhatsApp wasn't as big in the United States, as a country where WhatsApp has some adoption but hasn't quite reached a scale, total growth and it's sometimes it's been flat and sometimes even negative over that course of time. The thing that I kind of found was that, okay, so what's up grew basically without the Facebook data -driven approach. That doesn't mean that data doesn't have any value. And so core to the lessons that I learned are things that, first, you need a great product, second, you need to have a deep understanding of your customers, and that can come through data or just true customer empathy.

8:16But then third, you have to have an incredible growth execution loop. And when you combine all those things, you get a product like WhatsApp that is truly something that has taken over the world. What is an incredible growth executionally? It comes to understanding the dynamics behind a product and what will help poor fuel on the fire. And when I think about what makes growth really work, is the intersection of product experiences, marketing, and partnerships and sales that kind of fuel the fire. But that has to be built on top of a product that is fundamentally attentive in something that provides value and people really want.

8:47And so when you have that for a product, then you have that three rocket boosters of growth product, marketing, and sales and partnerships, that is the combination that really wins. Growth is a system. And often when I get asked to come in and grow something, what most people actually think they're asking about is growing acquisition. But I actually think that's where it's totally wrong. Because often, if you look at the kind of growth journey from acquisition, getting in front of someone to conversion, someone going through a funnel, to then activation and retention, there are often problems that exist in that bottom funnel that make it such that if you or just to go try to do acquisition, you wouldn't reach kind of a scale that you need to.

9:23And so you have to think about that kind of full customer journey and then think about the levers that you didn't pull in that journey and sequencing matters a ton for how you actually drive an impact that is kind of at scale. When you say sequencing matters at the time, what does that mean and how do people get sequencing wrong? Often I found that when someone is asking me about trying to grow something, they want acquisition, but what they actually have is conversion and retention problem. You have to look at the full funnel of that experience and understand is there drop -off. One example of this with WhatsApp Business when we launched Pretty Early On is when we had a product that was starting to get really strong adoption, Team really wanted to go do some acquisition.

9:57But when I went through this growth system, the thing that I found was that retention was dropping off in an enormous scale. It was something that was actually really concerning some of the lowest retention I've seen. And as we dug into that a lot further and we started to doctor customers, one of the things that we found was the transition from the WhatsApp consumer app to the WhatsApp that business app was broken. It was some technology that didn't exist. You lost some chats along the way. But if you're a business starting a new app, losing chats is actually the most critical thing. And you could just switch back to the consumer app and get going.

10:25And so one of the things that we started to do before we actually focused on pouring fuel on the fire with acquisition was we fixed initial transition that the common customer is going through. That basically doubled retention and was an angle change in growth. And then when we added in acquisition, we grew at a rate that was totally different. It wasn't just a step change. it was an angle change and I think that's ultimately what I'm looking for in growth is trying to find what's fundamentally broken in the system and then when we pour fuel in it how do we really get that kind of fire going? If we think about that holistic picture of growth being what most leaders get wrong about growth in terms of what gross people get wrong about growth what a gross people get wrong about growth.

11:02I think ultimately is that the product experience matters. I see far too many growth leaders jump to notifications upsells or things like that but in my experience there's usually one thing that drives most the results and people get too bogged down and trying 100 growth hacks to actually move a number. But really you have to find the right thing. I'll give you like one classic example from WhatsApp that we used a lot and the kind of the consumer experience, which is that as we talked about in France and the United States or some of those markets, WhatsApp isn't used by everyone. But in those markets, people still sign up for WhatsApp.

11:31And it turns out when you sign up for WhatsApp and you have no one to talk to on WhatsApp, you don't use WhatsApp. And so what we were doing was we were looking at inviting as a mechanism for how we could increase utility WhatsApp in these markets that WhatsApp wasn't working. And we tried a bunch of different entry points throughout the product to invite people, but the thing that we found was that an entry point when you're searching for someone that doesn't have WhatsApp was the top entry point. It became 10x bigger than any other entry point. And it makes sense because the context of what you're trying to do in that app was met by that entry point.

12:00If you're trying to search from someone and talk to them, they don't have WhatsApp, so adding a little invite to an entry point makes it so that you actually want to invite that person gets a WhatsApp and you're more likely to use WhatsApp. That one thing was better than the 20 different things that we tried. To me, it's really about thinking about what is the right thing at the right place at the right time for someone. That kind of is the most important thing about growth. And I think sometimes we're too caught up and oh, we just need to send another notification. We just need to like add an upsell.

12:25But actually, it's really thinking about a core product experience. What's the user problem and how do we actually go solve that with a product experience that leads to growth? How do you define what is a successful user? I think this is the hardest question that not enough people actually get right in their own business. But you think about WhatsApp, it could be the number of messages that are today, it could be the number of times you return to the app on a daily basis, it could be the number of contacts you have that you use it, how do you advise founders on the right metric that determines user success?

12:56At the end of the day, there's a reason people use a product and stick around it. And one of the most common analyses I do when I start on a growth problem is think about What is the retention curve? So up the percent of people that start, what percent of people stick around. And basically try to correlate that with actions people take early on. For WhatsApp, if you look at that, one of the things that matters a lot is having people to talk to. And so the more people you have to talk to, the more likely you are to stick around on using WhatsApp. But actually that's not the thing that matters. What matters is the one person that you want to talk to.

13:23And we can't necessarily know that one person, but we know that if you have more people, you're more likely to have the one person. And so you have to think about what's kind of the core dynamic of that, what's the value the user receives, And then what's the thing that helps represent the actions that people take that lead to that? An example of that is the Facebook 10 friends and 14 days. It really is about having kind of connections on the app that make it so that you have content that you can see and experience the core value of the product. Then the growth effort is how you drive that action that leads to the retentive behavior.

13:51You said about that one action is much more helpful in a lot of cases than like a hundred middle actions or hacks. How do you think about speed of execution and the importance and success of growth teams? I'm kind of growth experiments. I think speed is what are actually the most important parts of a growth team. And I think it's something that differentiates a growth team from just a core product team. And really, I think there's kind of two dimensions of speed that really matter. What is having really tightly scoped projects that validate a hypothesis? And two is getting like quick impact for results.

14:20And so to break those out a little bit more, one, I think that growth teams should constantly be in an explorer, then exploit mode, where they're placing quick bets, getting quick results, and then doubling down when something's working. And I think that's kind of a iteration loop that can happen in a matter of days or weeks, not months. And so a growth team should constantly be in that dynamic. The second thing is that I think sometimes teams aim too small. If you're an early stage company, if you're an early stage product, you're looking for something that clearly impacts top line growth. You're not looking for 1 % wins.

14:48Sometimes not getting a clear signal is a signal in itself. And I think that sometimes people get lost and, oh, maybe this is going to improve by 10%. No, we're not looking for 10 % wins. We're looking for 50 % or things that kind of double behavior that's going to lead to a different outcome and I think that those things are really important when you think about speed of execution. How long do you wait? How much signal is enough signal? And I just see people try things and I like, we need more time. A week isn't enough. How do you determine when enough data is enough to decide whether to continue or to cut something?

15:19There's actually a science to this, which is that when you run an experiment, you can measure the measurable impact of an experiment and the sample size you need to be able to affect that experiment. And so there's some online calculators. If you just go Google sample size calculator for an experiment, this is something I use all the time because basically if you're trying to make a 1 % change, you need a huge audience. If you're trying to make a really big change, you need a small audience. And so the things I think about are like, what's the size of impact we actually expect to change? How quick can we measure that and how many people are going through an experience?

15:49And if you can't measure an experiment with the kind of sample size that you have, it's not even worth running big experiment. And if that's one of the science pieces of this, the other thing is I think sometimes you have to look at the input metrics. Maybe there's a downstream action like messaging someone that is going to take a little bit, but does someone have contacts? Do they import their contacts? Do they invite someone? Those are actions that lead to an output. And so thinking about the difference in input metrics versus output metrics is one dimension that I think actually helps teams understand.

16:16Are we seeing the positive actions and the income? Are they input met before we're seeing an output metrics? And you can feel confident that maybe there should be more time if there's a lift in the input metrics. But if you're not seeing input metrics, you're never going to see the output metric as well. We've jumped to step there, which is really the assumption that this can all be done by an initial team. When we think about the teams that actually work on this day to day, how do you advise founders on what is the right time to really start thinking about higher your growth team? The thing that I think is the moment that you're looking for is that the product has a core product market fit and at least one channel is working for bringing in some new users.

16:50It doesn't have to be huge, but it has to be consistent and reliable and safe. If it's not there, to me, the company is the growth team and the CEO is the growth PM. It should have to be core to building and can't bring in a growth team to create growth out of nothing. It has to be about doubling down what's working and scaling out to new channels. You know, the growth has to be fundamental to what the product experience is today. And I see a lot of sometimes founders come to this problem and say, oh, I want a growth team. And what they're actually asking for is someone to run marketing to get people in the door.

17:20And that can work. but that's not a growth team. That's a marketer that is bringing people into the door. And so I think you really have to think about how is the product working and is something hitting there and then it's time to pour fuel on the fire. I'm an early sage founder Ryan and I'm thinking about adding my first growth hire. Should it be a growth leader who can hire their growth team or should it be a jack of all trades growth person who is much more versatile? How do I think about that profile type leader or more junior? I think that there can be some early rules around setting up infrastructure from an engineering perspective or from a marketing standpoint where you're getting the measurement of your product or the conversion tracking set up.

17:58But I think you should bring in a growth leader pretty early once I understand that it's time to grow because you want that person to basically architect the system of growth that you're building for your company. And I think that's like a pretty critical aspect of this. And so how I think about this is lace of early foundation get to know that it's working. But then pretty quickly bring in a journalist's growth leader that can start to think about, you know Where do we want to take this and how to maximize what we have? Okay, so we do that say we are the first person in the growth organ company as Hypothetically speaking someone actually hired me.

18:28What should they be? How should they do it? What test should we run? What advice you have for that is the first growth person in the rule I think that this has been the niche that I have found myself in my career And it's something that I truly love and enjoy doing and so I have a couple of different things that I think are really important early on in the journey of a growth leader at a company, I think there are a couple things that should really happen. First, I think that growth leaders should go through the customer journey from discovering the product and becoming an active customer. Go through it like a customer would end in, take screenshots of every step, aggregate that and share that back with the team.

19:0299 % of the time that I've done this, I found that the team hasn't actually looked at that experience in a while because it gets lost in the changes. So taking a fresh set of eyes at this problem is something that is kind of really important for setting a good foundation. The second thing is I think there are a couple of analyses that are really critical to run. First, I think you have to understand where you're used to come from and how has that changed over time. That can give you an insight into what are the dynamics that are driving growth of this business. Second, I think you have to think about what's the funnel from someone's showing intent to becoming an active customer.

19:31Where are the drop -off points? What are the friction points? What's working and what is not working? And then by this thing that we've briefly talked about, but the key actions that lead someone to becoming highly active, Is there people that become successful? And what did they do early on in their life stage that made it so that they become successful? And so that's maybe foundation of understanding. Then I think as a growth leader, one of the things you have to do is you just have to try to ship something. I think it's important to think about what is the process of going from an idea to actually implementing something?

19:59Who's willing to step up, whether friction points, what is kind of the engineering systems that are involved with that, or the business processes that exist around that? And so you're gonna have to start from a place of curiosity, but then quickly shift into being someone who gets something done and trying to understand How can we do that in a repeatable motion? It can ask you in terms of building the team around us You said before before we jumped to hire in this full growth theme You said that building with the minimum number of people it possible is actually maybe better Why do you think it may be better to have less people and what are the advantages of that lean a team?

20:31I think at some level I strongly believe in the principle of mechast law. And for those of you who aren't aware, the mechast law is the notion of in a communication system the number of nodes in a communication system mean that the complexity and the value of that communication system grows exponentially. And so when you think about that if you have a huge team, it is more complex to get anything done because you're having to coordinate across a bunch of people. And so the thing that I look for is there one to four people that can get something done and trying to keep things as small as possible to iterate as quick as possible, keep the communication loops tight, keep the alignment tight, and it helps prioritize.

Read the full transcript

21:07It helps you think about what is the most important thing to do, and how can we go execute on that very quickly? And so I usually start very small, and as you start to do that kind of explore or the exploit mindset, that is the fundamental principle of explorer. But at some point you do need to scale it up, and you need to start adding more resources to help take things bigger. But it has to come from something that's working, much the product has to actually be working before you bring in a growth team, I think a growth team has to be working before you scale a growth team as well. Do you think founders really know when it's working?

21:35And what I mean by that is do you think we can trick ourselves into thinking, ah we're at 50 km or hour, this is real customer demand, but actually it's forced, it's founder -led sales maybe, they may not be churning, we don't have enough data to know about retention. Do you think founders actually understand where they really are? The thing that is important is is it repeatable, right? And when When you say founder let sales, the thing that I often think about is that if founders haven't make every call, it's not repeatable. Because there's a lot of things to do when you're building a company and the founder having to be able to sell every deal is not the thing that is repeatable.

22:07And I think at that stage, definitely not. I think what I'm looking for is actually like, has it scaled beyond the founder or one other kind of test that I think about is if you stop that activity, if you like back off, if you're running ad campaigns, if you turn them off, what happens? And if it totally goes to zero, you actually don't have something that's working because you're not certain to see that organic adoption is happening. And I think that it's very rare that a product exists totally through just direct sales only or marketing only or other things like that. You tend to see something is happening when you do one of those, is other channels start to take off as well.

22:40And so to me, you actually need to see that something is working when you pull back your effort or lower your level of investment. As a growth leader, here's the channels that we're using. Do you want to take a channel that is working and make it better or take a channel that is not working and trying to make it work. I think that when you have something working, is the first priority to make that thing work as well as a camp. So I always start with how can you maximize what is working and accelerate it? But ultimately you start to face this question of when should you stop working on a lever or when is there bigger upside elsewhere?

23:10And so I think a lot about when do you hit diminishing returns and when is there opportunity cost? And so when I'm looking forward as a constant evaluation of what do we think we can gain? What do we kind of have a friend of us in this channel? What else could we be working on? and how do we make that tradeoff of impact cost and excitement about those different options? See, we now know that we need to build out the growth theme more. We want to embark on that process, and so we're going to start hiring Ryan. We are hiring for our growth theme, but also we're aware that Canada's often for startups are non -obvious and underappreciated, often the obvious bunny or the biggest company is earning the biggest salaries.

23:45Where do you find great, non -obvious talent and growth talent? And what I really look for is the change agents, particularly in operational roles. And some of this comes from the bias of my journey into this role, but where I started in the Facebook Austin office, which is an operational team that handled customer support operations for some different Facebook teams. The people that stood out in that where they could get things done both kind of within the teams that they're working on, but then actually impacting kind of the core product of Facebook are the people that you want to be looking for as untapped talent that is not yet being reached.

24:17And so I think a lot about who are the people that are being able to make changes from difficult positions or places that you wouldn't expect change to be happening from? In those roles you learn a level of scrappyness, you learn Kessa Rambathy, you learn humility, that sets you up for success in a bunch of ways that like the traditional PM that has started right out of college doesn't necessarily have and so I look for someone that has been making some changes and been able to affect that change. I have Mercury one of the best PMs I've worked with with someone that came from the customer support.

24:44She taught herself how to code and she was able to like just learn all these small little tasks that helped her do her job better But then created a skill set that was very well rounded admit that she could just get shit done And that's what I look for is the person can get stuff done even when it's tough because I think that that's what you're ultimately looking for Is a diverse skill set able to go through walls and build things that last which you ever high someone who hasn't done growth before It depends because I think many things can look like growth But if I go back to what is my definition of growth, I think growth is a system of optimization and being able to understand a problem in the system and change that system towards positive outcomes.

25:21It doesn't have to be called growth for me to be down with that to hire for that, but I do need to see that how the ability to understand the system make changes and then that change have an impact. That is the core line that goes throughout that skill set. Okay, so say we have this camber pool in mind. We now need to run a process and run. I've never hired for a growth team before or growth higher before But in terms of the light structure, how should we literally structure the process for growth higher? I think the fundamental things you're looking for are really three things one I think you're looking for some background examples of being able to get things done and ship impact Can they get stuff done beyond their position or what they would have beyond the system of the company that they were in?

26:01If you just sail with the wind behind your back, you're not a great sailor you have to be able to go through the difficult times as well. Second, you're looking for the ability to understand customer behavior and do analysis. Can they break down problems into actionable insights, go from an idea to actually what would you do to execute on that idea? I think that's something that's really critical and what you're looking for is someone that isn't going to be blocked by other people and need to pull a bunch of resources. They need to be someone that can generate value without needing to pull as much from other people.

26:29And the last thing I think is product sense and can they make decisions that are gonna fit within this broader kind of company perspective. So those are the three dimensions that I look for, and I think there are many configurations of what you can actually screen for, and how you can set up the interview process. But those are the three pieces that I'm really looking for when I hire someone that is a growth leader. Just want me to, again, I'm the first time found a hiring my first growth eyes, interview, case study, deep, that how do we structure that process? So the first interview is an interview about their background and kind of what led them to here.

27:00What I'm really looking for is take me through the journey of your career, why did you choose things that you worked on? What are some example projects that you helped guide? And how did you guide that? I really love going through examples of what people have worked on asking them to break down why things worked the way they did and how they would have gotten more impact out of it if they could. Now what are the best and what are the worst that? What are the green flags and how they describe those experiences and what are the red flags? The thing that I'm really looking for is the ability to understand the system behind what's happening.

27:28Can they understand that it's not just about adding an entry point but actually there's a value that matters for a person at a given drop off and that they can understand that there's something broader beyond just the one change they made and find consistent wins or break it down into like how could you take that and maximize something. Those are some of the dimensions that I'm really looking for in that background is it can they think broader than just the example about their kind of role and how they entered that. Great people I find are people that are able to a problem which is like how do we get more people to sign up break it down into composable pieces and then figure out the seven things that you should try.

28:02And then this one works, oh, let's take that one thing that works. And 10X it. That is often the thing that I'm looking for in that kind of background thing. And the worst case is the thing that I see is someone that is just running a play, but someone that is just doing the thing that either their company would do or we could find on a blog or things like that. To me, you have to be curious. You have to be trying to understand how the dynamic of the product is actually working, not just what's the change. In terms of case studies, how do you think by using case studies, do you think they should be your own company or company that the person's experienced and what with before.

28:34So they have more natural domain knowledge coming in. One of the things that I try to get away from interviews is biasing based on the kind of prior context of a given problem. And so if I'm using an example that they went through, I actually think that it's about the work that they did. But I don't think it's like worthwhile of going much deeper on a case study for their kind of prior company. But there's a lot of inherent knowledge that you understand in that problem space that it's going to be difficult to communicate in a new interview. I also think that you can't quite use the problems of my company as the problems of the day because it ends up making the Canada feel like they're providing free work for you or you have biases around what your solution would be.

29:09And so the thing that I think about is there a problem that is generic enough or not a problem of the day that helps establish the framework for thinking and lets you kind of go deep on a couple of different dimensions. And so case studies are critical, but I try to think about can it be about the more general problem of what the case study gets at verse something that would be influenced by my thinking of the day. Who do you bring in on the decision process? Who's the people who should be on the hiring committee that say yes, we should hide this growth person? I think that it should be the leadership team should be core to it and the people that are going to make decisions about the future of the company.

29:43I think the cross -functional partners they work with is going to be critical. So the team they work directly with, if it's marketers, if it's engineers, if it's partnerships folks, you've got I get those people working together and understand can they work as peers and then if there's going to be kind of reports You need to get some reports signal as well and management skills too And so the thing I think you're looking for is 360 overview of how does that person work with other people as a think that the Analysis part is critical and so if your company doesn't yet have an analytics team Understand how you can try to build that kind of skill set or bring in external advisors because I think that fundamental to growth is Analysis and you have to add that skill set into it How much do I pay them?

30:21What does that count package at like Ron? I think Commentation Barries by Location and the kind of seniority of the role. But one dimension that I think is really important for a growth role, it is slightly different than maybe some other roles is that you really want skin in the game so that the growth person has equity upside in the problem. And the thing that I would look for is what is the kind of combination of salary that kind of fits their needs, but that equity that has meaningful contribution such that if that person succeeds, they would have reasonable upside. And that is a combination of things that I'm looking for.

30:50It's good to give a sliding scale of that. Presented offer, but say, if you want more equity, or if you want more cash, like we can talk about that, but I think you do have to think about that balance of reasonable cash, sizable equity, and then trying to find that is important. The other thing correlated with that is, you have to be pretty critical about if it's working or not. You don't want someone to have a huge equity package and just be sitting, resting, investing. You want them to like, how know that they're gonna be evaluated by their performance and they will be compensated as such, then if you do well, you're gonna have to use up side, but this isn't going well, we're gonna call it.

31:21And so I think that's an important aspect too. First growth hire, I'm, I dig now my friend, I've been doing many shows. It's an order senior hire, it's a 28 year old, to 35 year old, but it's a first growth hire, it's not a growth leader. What's that range in terms of salary? I think in the United States, I think it's a reasonable assumption that 150 to 250 cash, and then some sizeable equity packages is the range that you're looking for. that kind of various buy seniority and skill set and ability to kind of manage or build a team and experience But I think that you're looking for that you don't want to try to match some of the big companies that can offer a huge salary and equity packages You do want someone to be scrappy and to understand that their upside is gonna come from the growth And so we've we've hired the person fantastic.

32:05We've done it rhyme well done They're joining our company. Woohoo. Now we need to onboard them that kind of segment of the hiring process, which is continuously fucked up. So what is the right way to onboard gross talent? What does that optimal onboarding process look like? To me, month one is about getting to know the people, the product, and the kind of processes. When I really look for when I'm onboarding someone is an exponential growth trajectory for themselves as being the person that role. And so in that first month, the thing that I'm really trying to get them in is all the context that we can possibly have.

32:37Do they have the right relationships? Do they understand the problem in the customer journey and do they understand how they can get stuff shipped? And that first month, actually, you may not see much progress. But by month three, when I expect to someone to be starting to form opinions and starting to make changes that are having clear input into a successful trajectory. And so what I'm looking for there is are they finding unique insights? Are they making changes and helping ship things that wouldn't have otherwise been shipped? Are they bringing clarity with strategy and kind of the tactics that we're building and helping bring people along in the communication of what they're doing.

33:10And that's all I think about it is that one month and then three month timeframes and I think that it varies by the person, but that's essentially the path. What are the biggest red flags for you if you have someone join at first 30 to 60 days where you're like, it's not working out. What are the big red flags as to why that would be? Three things that I really love for is red flags. One is high -not team. Are they thinking more about themselves in their position than how the team operates? And the broader kind of mission of the company, you really want to see someone that is adopting and adapting to the company that you're working on?

33:42Second, are they thinking about sustainability and systems? If someone's just coming in and launching a new notification in their first month, you're probably looking for the quick wins that kind of show that they're making progress, but not things that are actually going to lead to long -term success. And what's the sustainability of what they're doing? And will it be something that is a repeatable pattern? or is it kind of behaviors that are quick wins that may be annoying to customers, but you may not see that annoyance early on. And the last one is ignoring feedback. I think early in this kind of first month to three month period, the thing that you want to do is have a really good feedback cycle with the leadership and cross -functional peers.

34:15And if someone is not taking feedback about, hey, you might want to focus on this rather than this. That's a huge red flag to me and something that we've got to act on super quick, because being a leader means that you take feedback. You said act on super quick there. I think we're both recognized that people are generally too slow to let people go if it's not working out well If it's not going to plan how long should we give a head of growth and a growth higher and they may be different there to Prove their worth and prove their value. I think in most cases you can understand Three to six months if someone is working out or not and that doesn't mean that they have to be totally changing the directory of your company in in three to six months.

34:51But the question is, are they leading to a quality of work that is the kind of understanding, choosing of smart bets and showing that they can execute on problems that is leading to any success? It is it has to be focused on the inputs and the quality of those inputs. And sometimes the output takes a while. For some of the roles that I've taken and taken me six months to 12 months to actually see a win. But that kind of early inputs of how they're interacting with the team, how they're coming to conclusions and then what they're building is, I think enough to be able to tell This is going to be successful or it's not.

35:21And then you have to have a hard conversation and understand can they change that trajectory? And if they can't, then it's time to let it go. But the thing I found about letting people go is that you're always happier when you do than you ever would expect. What are the biggest fuck -ups you've made in hiring? Mine's like I've hired logos that give me confidence and then actually they weren't very good and they didn't play the role I thought they did. And it was like, ah, what do you think yours are? I remember once we hired someone that in the interview the thing that we felt that was that they were super -heared They just presented themselves as like the expert and the perfect person for the job and we all picked up on it in the interview But we decided oh this person's got a bunch of skills and so we should do it The thing is that people show you who they are in the interviews and the things that you see that our red flags are the on tend to be Problems that kind of grow over time and people don't kind of change their core behavior And so the red flags for me are one taking the red flags I saw in the interview process seriously and two thinking about Did we hire someone because the system around them at their previous company made it to they were successful or were they uniquely successful?

36:22Ultimately, in a higher thing I'm looking for is can they drive an incremental difference in a new scenario and they should have some example of being able to do that previously. Speaking of determining levels of success, on a project basis, how often do you do post mortems as a growth team? How do you structure them? Who's in vices? How do you think through post mortems effectively? Maybe a controversy will take, but I don't really believe much in doing plus mortems for growth change. I think that there should be a process in which you understand what you're going to do, you understand how that went, and why you made the decisions you made, and where you should go from there.

36:55And that should be a regular process, even something that happens monthly. But I think that it's very toxic for a growth team to get in naval gazing of micro -managing basically every small change that happens. If something breaks, you should evaluate it and figure out where to go forward. But it's constantly about that evaluation of what should we change, and where should Should we go forward and what are the themes of what we're learning? Rather than, oh no, we launched this thing and it didn't work, but it's like spend a full day on it or even a couple of hours on it. I think that you have to be able to make a lot of changes and see what the themes of those are, evaluate what happened, and then figure out where you go from there.

37:27And I think that's a model that I'm really looking for rather than a media postmortem, which to me speaks to like, taking mid -step assessment of how things are. I have to ask on review when you think about growth decisions that you've made. It told me about a growth decision you made without data to back it up. How did it go and what was some takeaways for you? Mercury, there were a ton of these, especially early on because we were a pretty small company at the time and we didn't have a ton of data to inform what we were doing. But one example of this is the experience that I had when I joined Mercury was the product is the differentiated experience.

37:57And so one idea we had was maybe we should build a product demo so people can see our product. But we thought about how to do that in a Mercury way. And we went and booked out at other demos they either didn't exist or they think about the value for the company They tried to extract an email they tried to walk you through these really annoying steps You can't actually explore the product and so what we built was a product demo where we just remove all the friction You can see the product you can go to demo .mercury .com And we added a little open account button at the top and we just put it out We didn't know if it would work, but it was found an experiment let people see the product to play around with it And if they want they can decide to use it the reception has been like wild from them over a thousand accounts have signed up we've had some huge deposits, basically sales -sized deposits have come in without talking to anyone.

38:39It's become a huge growth lever and it even helps with things like recruiting because employees see that and they're like, oh, that's a really cool product. I want to go work there. That to me is the classic example of part of the lead growth and doing that explore versus exploit mindset was that we just launched something, put it out quickly, tried to see what would happen, and then we've gone back to that for a bunch of wins, and it's turned out to be something that's hugely successful, but at that precipice, It was really just a hypothesis that like people want to see a product before they sign up for it Let's do it in the way that we think we should do it and it turned out to be hugely successful To talk to me about a b -testing WhatsApp.

39:11What's the story there? I got told I had to ask this one So one of the craziest funbacks about WhatsApp is that WhatsApp got to a billion and a half users without running any a b -test They didn't even have a framework that could run a b -test But when I joined a 2017 we were starting to think about some business features that we were going to have And in particular, one of the things that the team was most concerned about was the negative impacts of those business features. That if someone starts to get business messages, they might react negatively and turn off the app. But at WhatsApp scale, it's very hard to see that.

39:39And because it's a network effects product, that if you do start to see it, it's actually too late. And so one of the things that we decided to do was to build an A .B. testing system to understand the negative impacts of some of the features we were introducing. We ran that. We built that. Worked with some great engineers to build it in a privacy safe way. We built that, we ran the experiments, and we found that there were no negative impacts we didn't prove that no hypothesis. And we were able to launch that product and feel good about what we launched. And that A .B. testing framework has become thin for all that is run for a lot of other things in WhatsApp.

40:07But so interesting to me that so much of WhatsApp had been built without that, and then when it does get introduced, it's more to think about the downsides rather than the upsides of the kind of quick wins that often A .B. testing is thought about. What about Cori Thinfrance? Well, story there. For what's after some markets where what's up is not the main messaging app that exists in the market and it comes down to a lot of Competition in the places in France is one of those and we were looking at the growth of what we could do to grow what's up consumer We thought about what are the markets in which we can help accelerate towards true network effect that becomes the main messaging app and so in France What we did was we basically took that playbook of finding the product Marketing and partnerships that we could build to go accelerate our growth and we execute that playbook over the course of a year where we worked on things like inviting in the product to make it so that people had the people that they wanted to talk to.

40:55We worked on marketing campaigns that WhatsApp had never run to bring in consumers to WhatsApp. And it turns out that people responded really well to that. We found some pretty novel partnerships as well in that space. And through that kind of combination of those three tactics, we were able to accelerate growth in France and see that we were actually increasing our market share of WhatsApp and put that on a trajectory to start to win. And it was one of the best successes we saw and growing the WhatsApp consumer up. And the interesting thing was that it wasn't about trying to grow in India, that market is already one, but trying to find the right markets in the right places and that classic Playbook of growth is something that you can kind of pull from.

41:30Ryan, I want to dive into a quick fire. I've basically just pelted you with questions for most of the show, but I'm going to do a quick fire where it's 60 seconds per one, and then we rock and roll through them. How does that sound? Sounds great. What type of texting growth have not changed over the last five years? Building an experience that connects users with key actions that are going to make it so they stick around in your product is something that hasn't changed and is never going to change. It's something that is going to always work and I think it's going to mean that I always have some sort of job in the space.

41:59What tactics have died a death on the flip side? I think that email and push notifications are something that has been so overused that it actually has led to channel blindness. No one's excited about them. They die a quick death and win someone, you actually like annoy someone to the degree that they turn it off. You lose a channel forever. And so I think that the tactics of let's just send another notification on its way out and hopefully that is the case but something that I don't take work so well. What would you say the biggest mistakes found is make when hiring growth themes? I think it's just one thing that I think a growth team has to be a system and a sustained investment.

42:35Just because you try once doesn't mean that it's going to work. You have to actually go at it and you have to understand the problems, making incremental progress and see that it's working, and then when it's working, you double down, but you can't just expect someone's going to come in, run the best marketing campaign, heaven, history, and that it's just going to take off. It has to be a lot more than that. What would you buy something to change about the world of growth? I think people need to talk to more customers. One of the things that I came up in was that a lot of growth people think about data and they think about the experience without actually putting products in front of people and asking them what the problems they experience are or what they feel about the growth tech of this being introduced.

43:10And so I think talking to customers is something that I would love to see growth, the growth practice, spend a lot more time on. How do you see the function of growth evolving over time? Does it look different in five or 10 years? I think it's about building a better product experience. I think that it just comes back to that fundamental of what is sustainable for a product and what is native to that product. And I think that that tactic is going to be something that I see continuing to evolve and be important. But I think on the flip side, the thing that I see is ad platforms are always getting more expensive.

43:39They're always more constrained. And if you particularly look at some of the trends that are happening with moving to richer formats like TikTok, it's just more expensive to create basic content. And so I think that it's always going to be more expensive to run ads. But if you can think about what are the sustainable kind of product experiences, that's really where you find a lot of graph die. Final one, my friend, when you look at the landscape of great product experiences, other than mercury, what one product to experience company, growth strategy have even most impressed by recently. One that I really love is SubStack.

44:08SubStack is a product that has built an incredible platform for a very targeted customer subset and provided a ton of value with them. But then as they've gone through the journey of building that initial product that provides value to writers, they started to add on things that they can uniquely do because they have a network. They've added ways to recommend newsletters between different writers. They've added a mobile app that is quite compelling and has these features. They just launched a new kind of network effects product. And I think to me, the interesting thing about Substack is they're lining their incentives behind their core customer.

44:41And when you see that happen, the world is their oyster. And it's something I'm really stoked about and really excited to see how they've taken all. Ryan, as I said, I had so many good things before. I love the blend of WhatsApp code stories. I love the blend of Mercury's Day. And then also Super -Ash will advise. Thank you so much for joining me and also for putting up with me, moving slightly off schedule. Thanks, Harry, really presented. The thing I love about these shows is just how tactical and granular they are and if you want to see the full video you can check it out on YouTube by searching for 20BC but before we leave you today, I'm really excited about this net sponsor because a few of my portfolio companies use it and love it so do you know the impact of your marketing efforts?

45:20It's more important this year than ever to know the impact or how much you've spent so far this month and what you've got as a result. you're not alone in not knowing these answers, even though marketing is now all about the data, most companies still use manual spreadsheets for reporting an analysis. But if you want a super charge gross, spreadsheets just won't cut it. Funnel is the world's first and only marketing data hub that takes all the manual effort out of data collection and lets you blend data from different platforms to unlock new, deeper insights and the best part is this can all be achieved without writing a single line of code.

45:55I can hear your sigh of relief. That's why it's used by more than 2000 of the world's top brands and media agencies, including Samsung, Adidas, Sony and have Asmedia. Start your own free trial by visiting funnel .io -20VC. That's funnel .io -20VC. And finally we've all been there, but nothing is quite so depleting as the blinking cursor on an empty page. Reminds me of law school. You're sitting there, trying to come up with ad copy or hypothetically a set of interview questions for a podcast you run, obviously personal, and is just staring back at you like a brick wall. This moment of frustration amid growing content amounts is probably why I'm hearing about Jasper nonstop these days.

46:36Jasper is an AI assistant for business that helps marketers, sales reps and other creators, accelerate their writing process and repackage content into different formats, languages and tones. Online Broad Use AI tools, Jasper was built for business and this makes a big difference. In Corporate SCO, a plagiarism checker, and a browser extension, so you can cool up Jasper in pretty much any tech spots or platform use online. Visit Jasper .ai -4 -2 -0 -VC for a demo. Your burnt out team will thank you. As always I so appreciate your support and stay tuned for an incredible set of episodes this coming week.

From the publisher

Ryan Wiggins is the VP of Growth and Analytics at Mercury where he oversees a Growth team and founded the Analytics function. Prior to this, Ryan built Growth teams at WhatsApp, where he helped grow WhatsApp Business from 0->100M users, Workplace, and Facebook Ads. If that was not enough, Ryan is also an active angel investor.

In Today's Episode with Ryan Wiggins We Discuss:

1.) From US Department of Commerce to Leading Growth Teams:

  • How Ryan made his initial foray into the world of growth with Facebook and Whatsapp?
  • What does Ryan know now that he wishes he had known when he made the entry into growth?
  • What advice does Ryan have for people who want to change their career but are not sure what they want to do?

2. ) Who and When: Building the Team:

  • Should we hire a Head of Growth or a more junior growth hire first?
  • What are the different profiles of growth hires? How do they change with business model?
  • When is the right time to hire your first growth hire?
  • What are the single biggest mistakes founders make on the timing of growth hires?

3.) How to Hire: The Process:

  • Structurally, what is the right way to hire for a growth team? What does the interview process look like? What do you want to get out of each meeting?
  • Should case studies be used, if so, should they be used for the company hiring or of the company where the candidate is from?
  • What does the comp package look like for different growth hires?
  • Who should be brought into the growth hiring process? What stage should they be involved?

4.) Onboarding: Setting Growth Up for Success:

  • What is the ideal first 30,60 and 90 days for new growth hires?
  • What can leaders do to ensure they are set up for the maximum chance of success?
  • What are three of the biggest red flags bad growth hires show in the first 30 days?
  • What are the biggest mistakes founders make in the onboarding process of growth hires?

More from The Twenty Minute VC (20VC): Venture Capital | Startup Funding | The Pitch

All 520 episodes
20Growth: Three Growth Lessons Scaling Whatsapp from 0-100M, Why You Should Hire a Head of Growth Sooner Than You Think & The Biggest Mistakes Founders Make When Hiring for Growth with Ryan Wiggins, Head of Growth @ MercuryThe Twenty Minute VC (20VC): Venture Capital | Startup Funding | The Pitch · 47 min
Listen in VO