Bonus Episode 8 – Structure Of A CRO Team
11 Nov 2022 · 1 min
Khalid Saleh and Simba break down how to structure a CRO team, covering the key roles: strategist, UX designer, developer, project manager, QA, and analytics. They walk through how ideas get presented and reviewed, plus the processes that make A/B testing and experimentation programs actually work.
My name is Khalil Slade and I love to talk about conversion rate optimization.
I'm Simba and I love asking questions about conversion optimization.
This is CRO Live Hour, a show all about a B testing, experimentation and conversion rate optimization.
Each episode, Khaled amazes me, answering some of the difficult CRO questions, dropping insights like it's no big deal, while pretty.
Much every episode will take on a new set of conversion rate optimization questions that are not easy. We will talk strategies, we will talk process, and we will talk tactics. Simba will be bringing all the questions.
Oh, man. I bring tough questions like, do a B testing results fade over time? How do you go from low to high testing velocity? How do you measure the success of a conversion funnel? And how do you align your CRO program with a growth strategy? Yeah, Khalid, these are very, very tough questions.
Yes, they are. But we always answer them here. And if you love conversion optimization like we do, and certainly like Simba does, subscribe to the CRO Live Hour podcast today. Wherever you listen to your podcast.
What we have right now is we've switched into a pod system. So in a pod, fundamentally you have a CRO strategist or senior CRO strategist. You have a UX designer and you have a developer. Most of the people that work with us are seniors. They have at least 5 years experience. More than that. That's the core team. That's the core pod. Each pod is also supported by a project manager. So the product manager ensures that we are delivering on time. We're making sure our project plans are done correctly. Each pod is also supported by a COR, quality control or quality assurance engineer. Last thing you want is to develop an AB test and that a B test has a bug in it. Which means that instead of helping a company improve conversion rates, you reduce their revenue. Your project manager and your quality assurance or quality control engineer, they're usually two resources that support two pods. You have usually an analytics person that also supports two pods. Iat the CRO queen, usually for us, oversees everything IAT brings strategy. She's done so many A B tests, she's talked to so many companies, she's not going to be involved in the day to day, hour to hour. You don't want her to do that. She's our subject matter expert, where all of our CROs go back to her, have discussions with her, present different ideas. One thing that we do is all of our pods have multiple meetings throughout the week where they present ideas to other pods and they say, hey, here's the idea that I have. Here's the data behind why I had this idea. Here's the solution. It's a very lively discussion where people ask questions. They say, hey, why do you think about this? Did you consider that? One thing I would like to get to which we are not there yet. If you have any ideas, prepare all your presentations. Send them on a Friday. Allow people a chance to digest them over the weekend. On a Monday and then Tuesday, instead of you presenting your ideas, it moves right away into a Q and A session, because the team should have actually studied your ideas and your analysis. We're not there yet, but that's kind of where we're heading into.
More from Khalid
Unlocking Website Conversion Secrets Through Data-Driven Testing | Khalid Saleh from Invesp
Unlock the Power of Post-click Experience: Roadmap to Convert Leads into Customers