Go back

Decoding what’s behind the most admired business cultures in the world.

from Impact Leaders

52m 19s

Decoding what’s behind the most admired business cultures in the world.

Christine Dodge, Director of Product Innovation at Netflix, emphasizes the power of "dream teams" over individual leaders like Jeff Bezos or Elon Musk. She argues that high-performing organizations thrive not on personal charisma but on shared ownership, trust, and cross-functional collaboration. Effective teamwork requires humility, curiosity, and psychological safety—especially in remote or hybrid settings where personal connections are harder to build. She highlights how transparent, data-driven decision-making through experimentation (e.g., AB testing) helps validate hypotheses and deliver user-centered outcomes. Radical candor is not about aggression but about trust; it emerges when leaders consistently solicit and act on feedback. At Netflix, autonomy is paired with accountability, where teams share goals, test ideas, and openly report results—creating a culture of collective learning. Dodge stresses that technology like AI and machine learning only succeeds when embedded in a culture that values transparency and human-informed decision-making. She warns that without cultural shifts—such as embracing direction over precision and empowering teams to take risks—technology will remain underutilized. Ultimately, the future of innovation depends not on tools, but on leadership that fosters trust, transparency, and shared responsibility.

Transcription

9000 Words, 49900 Characters

English
We talk about like the Jeff Bezos, say like Elon Musk and Steve Jobs, and we talk about like these like individual people as leaders, but I would like to see more stories about like the dream teams, the bar self, Guardiola, where you're not just like valuing like one individual, but like how do they all work together to like accomplish those goals? (upbeat music) - Hi, good day to you all. You are listening to Impact Laders, a podcast in which actual well-gift sports to leaders who are challenging everything that needs to be transformed in this world to make it change happen. Ideas, conversations, and actions about the future of work, exponential change, the digital twins, and human interconnections. I'm Jonathan Escobar. Today, I am with Christine Dodge, Director of Product for Personalized Experiences and Netflix. (upbeat music) (upbeat music) - Welcome, Christine. - Thank you, Jonathan. - I believe in our audience wants to know who Christine Dodge is, and how you have become a director in one of the most well-known companies in the world now. Christine, let us know a bit more about you. - Well, where do I start? So I'm currently the Director of Product Innovation for Personalized Experiences and Netflix. I've been at the intersection of product and data science for like a number of years now, and I've worked in many industries, including energy manufacturing, banking and now entertainment with Netflix. And in my past role, I started at a startup that's also pretty well known in the data science community called Anaconda, which helps data scientists do their work. And you know, with growing from when I started like, you know, 20 employees to now over like 200, and prior to that, I'm an engineer, industrial engineer by background from the, I got my degree in the University of Polytechnica, Catalonia in Barcelona, and I've been living in the US for the past nine years. - What an amazing career, Christine. What an amazing career. I have a question and a first question. What does a director of product for personalized experiences do? - I believe this is a question that most of the people listening to us today has. - Great, that's a great question. So I'm responsible for product innovation at the intersection of user experiences and personalization. So anything in the Netflix experience that is related to making better recommendations of content, new applications of personalization and machine learning and data science, getting user feedback to improve their experience, all of those are in this like area that I lead. And Netflix, we're organized functionally, but the product leaders are kind of the cross-functional leaders of like an area. So I work with engineers, the liners, data scientists to like make this like innovations possible. And we, you know, ideate, build tests and then launch these features in the Netflix TV experience. - Amazing, you're a data scientist in a top leadership position. What is needed to build great teamwork around data? - That's a great question. I think it doesn't happen if there's no alignment with like the executive team. It starts like the top, right? Of having a culture that values learning, values like curiosity and values like humbleness. And the trust autonomous team to like make the independent decisions following like those guidelines. So, you know, everyone on the leadership team has to like switch to think more as like a scientist than someone that's like right all the time and needs to push like their ideas through the organization. So, you know, as you know, you switch this mindset to like being more like a scientist, you need to embrace learning as you go. You need to make sure that you don't believe you have all the answers that you're gonna learn the answers as you like, you know, work with the teams. And like the teams can like figure out some of those answers for you. So, you know, it starts by switching from like making a plan that you think it's gonna work to like one where you're just like testing hypothesis and raising like different ideas, being open to test things that you might not believe yourself and looking to validate those ideas, you know, looking at the data, looking at the insights that your team can provide to make a decision and being data informed when making those decisions versus just like intuition based or like using your own judgment or just going with like the loudest voice in your room. So, you know, any switch from, you know, like a mentality of I know best, I'm the expert to one where I'm like, I'm curious to learn what is best. - I learned it together with your teams, huh? Because in the end, it's not, you know, about one single person is about building dream teams, isn't it? - Exactly, I think that's a very interesting point. I think we're still in like the business, you know, industry to focus on individual people. So, you know, we talk about like the Jeff Bezos and like Elon Musk and Steve Jobs and we talk about like this like individual people as leaders, but I would like to see more stories about like the dream teams and like, you know, the bar self, Guardiola equivalent and like the business setting where you're not just like valuing like one individual, it's like how do they all work together to like accomplish those goals? So, I think we still have a ways to go. I think we're still really ego based, you know, like of the like, you know, big personalities and you know, a lot of us kind of like looking up to them and I think when you switch that paradigm to looking up more to like those great teams that are out there doing amazing work. - I love your example about the Guardiola's team. I do, you know that I do agree with this. (upbeat music) From your perspective and experience and you have, have you explained before an extensive and massive experience in many organizations and high performing organizations? What sets a dream team, a high performing team apart from others? - There's multiple things. One is ownership, you know, like people on the team need to feel like responsible and accountable for the results of the entire team. That's why, you know, it's like a team sport, it's not an individual sport. So I think like people that have like embraced kind of like being a team player and feeling kind of like, you know, that they matter on the team and they have like a contribution to make and that the outcome is also the result of their work and the and feeling kind of that really strong ownership on the outcomes of what we're working on together. I think it's also very important to like be a good team player but not only within your function. I think it's easy to be good team player within your function. If you're an engineer, it's relatively easy to get along with other engineers because you have the same context. You've gone to similar schools. You have like similar knowledge. You know, you can't like disagree sometimes but those are not hard disagreements because you have a very, you know, shared context of, you know, the, and you can think like one option might be better than another one. But I think what is key is being like a good team player cross functionally of when you don't have all the knowledge, when you don't, when you're not the expert, where you're missing a lot of that context of like what another team does, right, if you're an engineer working with a designer and still like being able to like communicate effectively, be curious about the contribution of that role within the team and what they're bringing instead of like trying to like, you know, pinpoint what they're doing wrong. I think it's easy to like sometimes like have this animosity across different functions. And very often it's just because like, we don't know as much. We're lacking kind of that context. And so it's easy to like pinpoint and say, oh, they're, you know, not doing this right or I don't know, you know, instead of like focusing on like your own lack of knowledge of that domain or that function, you know, it ends up being kind of like, like a pointing fingers. So I think that good team players that can have that curiosity and that humbleness of like everyone, all the functions within the team are contributing to make this like a reality, like whatever we're working together. And they have the ability to create those relationships and that trust so people feel like welcome and appreciate it within the function and the what they're bringing to the team. I think it's very important. And then communication, right? Being candid, willing to speak up, willing to provide feedback. It's all related to like that ownership and being a good team player, right? That because you feel like you have something at stake on the game that, you know, you're gonna say something when you disagree. You're gonna say something when you think that the team is not working at its best or it's not the most efficient that it could be. - How many great insights? And I'm curious about something. Do you believe that does all these change in remote or hybrid work situations? So is there a difference of this before it copied when we were in 2019 or how it will be now when we are back in some months to an a hybrid or full remote situation? Do you think there is any major difference? - There have been major differences And, you know, and Netflix, I've-- been remote for now over two years and I think I've been once back to the office in this like two years. So we are still learning, you know, it has been like a change. We don't have all the answers yet, but it does have an impact and we need to adapt and we need to figure out how how to adapt this change. I think first of all, we need to acknowledge that it is harder. It is harder in this remote and hybrid area to build those like trusting relationships with your teams. You know, we've had people, you know, being hired that I haven't met in person in these like two years. And we are social animals and we interact, we learn, we know how to interact in person. Like we read each other, our, you know, it's not only facial expression, but our movements, you know, we, there's a lot of moments in person of like getting a coffee or just staying high on the hallway or being in an elevator together that kind of like gets allowed you to like learn more about that person outside of work as well as like, you know, whether they had like a good, you know, weekend or, you know, what they're going to do that afternoon or following up on something you know about their, their kids or their family. And it's harder to create those relationships in like a virtual environment because you have to create those spaces explicitly. They don't come for free. When you come in a meeting, you know, like we're all kind of like getting to work, you miss out on all of that, that transition that happens in an office in person setting that is more informal that allows you to build that relationship and that trust so that you can work more effectively. So the first thing is creating those spaces. How do you create those dedicated spaces so that people within the team and within yourself, you know, yourself and like the team can know each other, can like trust each other, can build that empathy. And it's not easy, right? And without building those like relationships, it's very hard to build a high-performing team because you need that relationship to like have, you know, candor, to have trust, to like feel that ownership, to make sure that like you can make people like responsible and accountable for like decisions. So, you know, we, you know, we're still learning and like we're adapting as we go. But I think that is one of the most important things of like how do we create those spaces to build relationships? Christine, we had actually global see now a very common practice that we don't like at all. That is with this hybrid patterns of ways of working. Some companies are designing that, you know, their people will be in the office kind of two or three days per week and normally they decide to do this by functions. So, I mean, it's the finance department, you know, they will be one day in the office and then, you know, the supply department and the product department, you know, like they go to the office but they they go in the, you know, within the departments, that for us doesn't make absolutely no sense. Because I mean, we know that in reality, it doesn't matter. People is working, you know, across the organization. So, it doesn't make any sense to build a hybrid way of working in which people go, you know, to their offices within their departments. It's still creating silos in the hybrid way of working. And I would like to hear what do you think about this, your opinion about this, because we are building a completely different pattern in hybrid, we are building a pattern in which cross-functional teams or high-performing teams that, you know, integrate people from different departments, they get together in monthly to define their OCRs and to iterate their plans but always in this cross-functional teams and not in the functions. What is your opinion about this? Yeah, I mean, I completely agree. I don't think it would make any sense, you know, within my team to just go to the office on a live-function basis. And the most impact an organization can have is when those cross-functional teams are working together, they're realizing that to really drive initiatives that are impactful to the business, you need people with different skill sets and with different functionality. And you need to like allow them to like work autonomously, trust them to like make decisions to like drive those like initiatives forward. And so, you know, I think that is where most of like the day-to-day work happens. And like, you know, my organization, I think that's the most effective way to like organize ourselves is like within this like, you know, some organizations call them like virtual pods, cross-functional teams, you know, areas of innovation. And those are, you know, horizontal teams. And so, it would make a little bit more sense to me if you organized horizontally by by area rather than like functionally. Still, I think that if you set up, you know, the right way, you can still give a lot of freedom to people to decide, when to come into the office and like, when not to come to the office, when what types of meetings really value to like that in-person setup and which types of work, you know, can be more productive from out working from home situation, working remotely. I'm happy to hear this from, you know, from someone working in the, you know, in one of the companies that we respect more in terms of way of working. Now, thanks for sharing this, you know, your opinion and your view on this, because I believe there is a place where a lot of companies are right now experimenting. And I believe there will be a lot of iterations and a lot of changes in the next, you know, few months, few years, you know, as organizations realize that it doesn't make any sense to make people go to their offices, you know, twice or three per day's in a specific pattern rather than enabling them to self-organize across their squads or across their multifunctional teams or, as you said, their innovation, bots or virtual pods or whatever, each company calls it. You also mentioned before candidate communication and we know honest feedback is a fundamental characteristic of any great company. From, again, from your perspective and your experience, what does it take to make radical candor the sound of an organization? Yeah, that's a good question. And I think sometimes like radical candor is positioned as something kind of like aggressive, maybe like from the word radical, you know, it can come across as like, oh, like it did like a very aggressive tactic, you know, very competitive. And I think that's really far from the truth. I think, you know, in my experience, if you've built those relationships, if like you have a trip, a high performing team that trust each other, that feels like ownership, you know, that wants to accomplish the goal that you've set up. People have the best interest at heart, right? So you go into those conversations of radical candor, not from a point of like being aggressive, being right or trying to like put someone down or like, you know, say all the thing that they're doing wrong because, you know, you don't like them. You're going into those conversations thing like, how can I best improve this team and this team's outcome? And because you've built that relationship, the next trust, you know, like people know that they can be very honest. And they know that no one's going to take offense for this agreeing, which, which happened in like situation where like, there's no such trust in like the team, right? Then people starting like, oh, someone doesn't like me. They're trying to like, you know, get me fired or they're trying to like, you know, you know, take me off of the team or there's going to be some type of like repercussion for, you know, if I disagree with like the leader or like the boss for being honest and direct. So I think, you know, for me, the key part is like building that relationship and that trust within the team so that everyone feels that they can speak up, say what it's on their their head to make with the goal to make the team and each of us individuals like better. So in the end, it all comes down to building this common trust. And we also agree that this is somehow a missing part in radical country because you know, a lot of people just focus on the honesty part, which is important. Of course, it's important, but you cannot be honest if you have not built, you know, safe connection with the other person or with the team and with you have this. And I think this is missing and deliberately missing in some organizations and in some teams. And how do you make it happen on a daily basis? Because that's the key part. How do you, how, how would this radical kind of look like in, you know, in a common day, huh? Yeah. So I think you, you know, it starts also with the leaders setting an example because I think very often, you know, what I've seen as someone saying like, oh, we want to do radical candor and you push it down to like your employees, but oh, you have to like give each other feedback and we'll have this sessions and like, you know, you kind of like need to be very, very honest. And but then you go to like a meeting and there's no one giving feedback to the leader, you know, like, and the leader takes that either very personally. If someone like disagrees with them in a meeting or they never change their mind, no matter what feedback is given. So I think it all starts by setting a good example. And you can set that example in any of like the meetings that you lead as a leader of like asking openly for feedback in a meeting with you know, how many people are there. And not only having that people being able to like raise and give you like feedback on like decisions that you're making in the moment. So for example, you can like come up with a plan and say, hey, here's the plan. I want feedback from the team on this plan. And not only welcome the feedback, but actually like listen to the feedback. Listen to the feedback and being willing to like change directions if they're like enough feedback. You know, if there's like valid feedback that makes you like resync the approach that you were taking. So there's a lot of ways to like model it in your day to day. And then when you're having, you know, in my one-on-ones, we set up regular one-on-ones where we call it like a feedback session. And you give some time for people to prepare. I, you know, you intentionally as a leader, ask for someone else for like feedback on how you're doing. And sometimes like, you know, your other people on your team, I ask you to do the same. You know, and it can be like two ways. Sometimes it's just like, you know, I just want to feedback for myself. But, you know, I'm not gonna, if you haven't asked for the feedback for you, maybe it's not the right time, not the right moment. So you don't always have to do it, right? Like you can also ask for it. You can also tell someone, hey, I've noticed this thing that happened in the meeting that I think you could have done differently. So it's making a pilot like making it more like a habit than just sometimes I see that we create this dedicated moments and spaces to give that feedback versus making it a daily habit of just like, how do we interact with each other and create kind of those moments of like, you know, modeling, asking directly for feedback to give you as a leader. And then, you know, as things happen in the moment, giving it timely as well. 'Cause I think another thing that happens is like, you know, there might be like some processes within the organization that HR organizes, you know, once a year, kind of feedback review. And then everyone's holding, kind of writing down, you know, like the checklist of all the things you want to tell that person that day. And that's like too, you know, too late. You know, you have to like give it in the moment, in the context where it matters so that they can make those changes, you know, with their everyday decision making versus like, once a year now you have this like long list, I think that no one told you. So you haven't been able to like act on it. And, you know, and change some of those things and grow because they just been waiting to like that moment that everyone said, "Oh, this is the moment to give, to give that feedback." - Fully agree, fully agree. We always say that actual global, that we believe that performance management systems today are mainly broken, you know, and are mainly broken because of what you are mentioning right now, that's because I mean, there is one, you know, once per year, even twice per year, or four times per year, it doesn't matter. But then you're listening to a list of things, you know, that in 90 days you, no one told you. And in the specific, in the specific situation or the specific moments where it happened, you know, so, and also when it comes to radical candor, we always talk about the flywheel of radical candor and what moves the flywheel of radical candor is leaders asking for feedback, listening to the feedback, and actually making a difference with that feedback. Because as you said, it's not only listening to, asking for feedback because if you ask for it, but then you don't listen to what people are saying, or you don't really make a change, or at least explain why you are not going to make a change after the point that, you know, that you got from your people, then you don't move the flywheel. And that's from our experience also, what really moves the flywheel of radical candor. And we see a lot of organizations trying again to push this, you know, the training of radical candor to, you know, to the people on the floor, and just, you know. - You're not applying it to themselves. - Exactly, exactly. - Yeah, and they're just, you know, they wish that, you know, this book will become the culture, but you have the leaders not asking for it, not, you know, using it, not, you know, showing the example and we know that that would mix the difference. Oh, it's a, thank you very much for sharing this because this is cool, huh? For all the people that will be listening to you to us today. Let's turn a bit into experimentation, huh? Because experimentation is one of these words that are often used, but less practice, huh? What does experimentation really mean in high performing organizations? - Well, the way I see experimentation, it's like one of many methodologies and approaches to building this like data-informed culture, right? So like when you're building a data-informed culture, data can come from like a lot of different places. And you can have a lot of different methodologies to like evaluate, you know, like the ideas that you want to test, like the, you know, testing like the hypothesis. You know, and so, you know, if we look, we take a step back as like we develop and, you know, product experiences. You know, if there's a lot of work having done, being done in like user research, right? Where there's like, you know, we've done, you know, people like to like surveys, focus groups. There's like interviews. All of those things are also data, you know? Also data that can help make an informed decision. Experimentation is yet another methodology that kind of goes all the beyond that because it has this like dialogue with your users of, you know, your product, you know, through observing their behaviors and how they're interacting with these like new features that you hypothesize that they're gonna make a difference in, you know, the engagement of the product in like the, you know, the impact to the member experience. So, you know, when we talk about experimentation like the kind of gold standard is kind of like AB testing, which is very similar to like random mice control trials and how do we learn whether, you know, a vaccine or a drug is effective to like, you know, prevent or treat an illness by like, because you want to know like that, the intervention that you're making, it's like the cause of like the improvement. And so that's what really experimentation tells you is like, I made this change and this changed cause this, you know, improved experience for my members or my users. Without experimentation, you know, you might make a change and you might see like, you know, after you wrote that feature, something changed, but it's very hard to know whether that was like, causally, you know, like if that was like the cause and effect versus just like by chance, you know, roll out on a day where like there was more traffic because it was like holiday and you, you know, you're not sure whether the new feature made the difference to your members or not. So, you know, as a data, you know, data team and data science team, you know, at Netflix, we do have like this very robust experimentation platform that allows a lot of these like product areas to launch new features, see how users react to them and compare them to like the current experience without the feature. And we can say, yeah, this feature really made a difference to accomplish the goals that we were trying to like accomplish and therefore should be rolled out. And some other ideas, you know, you realize this feature actually was not helpful to your members and you can see that through like the behaviors within the experience and then say, we shouldn't roll this out because it didn't help members, it didn't help your users. So, don't launch it, right? And I think there's, if you don't have an experimentation within your, you know, process of, you know, launching new digital feature digital products, you don't know, right? You keep launching things, you never know whether what made a difference, whether it made a difference, whether it actually went in the opposite direction that what you pretended to happen. - So, what you're describing is really understanding your users' desires, isn't it? - Yeah, yeah, for us, experimentation is a way to like, really learn from our users. So, when I was saying like, you know, you have to change your mindset to be more of like a scientist, right? It's kind of like that, that's how experimentation helps you because you start testing ideas. You're not launching features, you're testing those ideas and letting the users tell you whether that was a good idea or a bad idea and you have to be willing to be open to like, you know, changing your preconceived notion of whether an idea is working or not working because you're seeing users directly on like how their engagement, engaging with that feature and then deciding, you know, yes, let's go for it or no, let's not go for it. And you have to be okay, you know, that's where the humbleness also comes as a leader. It's like, I was wrong, right? Like, I thought this was gonna be a great feature and then you see your users not using it, you know, or being less engaged with your service, you know, you have to say, I was wrong, you know, I thought this was gonna happen and it didn't, right? And so, without this humbleness and this curiosity, you know, you can't make an effective, you know, data-informed, you know, culture and high performance that is really customer-centric, right? And really listening to that customer, making decisions based on how the users are behaving and interacting with your service to make it better. - Doesn't this mean that user is boss? - Yeah, yeah, user is boss. I think that's the way to see it with experimentation. Like, the user, the one that decides which features get actually launched. - What about freedom and responsibility? Because, I mean, would you are describing requests, high doses of freedom, you know, and the teams are working in a safe environment, you know, the day, there to experiment and to launch features with a hypothesis of what, you know, of the behavior that they expect to see in users, but at the same time, a lot of responsibility, you know, as you said that. they look at the data, they really understand if the user is really valuing that feature and making the decision autonomously not to either to roll out or not this feature. What does it mean to be highly autonomous but accountable in a high-performing organization, like Netflix or others that you have worked for? Yeah, so I think like those two have to go hand in hand, right? You can't do like half freedom, give freedom without the responsibility part. You have to like, yes, I'm going to be free to like make decisions, but I also need to be responsible for, you know, making those decisions. And the way we create kind of that freedom and responsibility model and like the product innovation is also being very transparent with the rest of the organization about our learnings, our strategy, our, you know, the ideas that we test, the results of those ideas, and presenting them in a very broad forum where everyone can, you know, see the, you know, freedom choices that we've made, but also see like the accountability part of like, we tested this idea, it worked, it didn't work, this is why, this is what we learned. And so that you give back kind of all of those learnings back to like the company of our transparent and are willing to like say, here we were, right, you know, we were right or we were wrong. And you know, it's not like a successor failure if you're right or wrong, but like when you test like an idea, it's about like the learning process. Like what did you learn about that idea that you went in thinking that it was going to work some way and worked in a different way? Because like every, for every idea that doesn't work, it inspires other type of work that is going to be potentially like effective. So really focusing on those learnings and sharing those learnings broadly across like the company. So the team, you know, it's having both. It's like being able to like, you know, run the ideas that they want, have the freedom to set up like the strategy and the test and, you know, in the way we think it's best, but then coming back to the organization and being transparent and open of like, he's like, what we did here were like to learn the results and being open to that feedback that we were talking, right? Like the radical candor is not to like an individual, right? It's also to the team. That's where the team is important. So like hearing from like the rest of the organizations from leaders of like, you know, what, what we've done and getting kind of that feedback and where we should go next, you know, what's our strategy, what's our roadmap and having everyone be able to like give input into that to shape it and make it better, right? That's how you manage to have for the executive team to like give that freedom and responsibility to like the autonomous cross-functional team. It's because you're providing also that visibility and that transparency and you're also open to like feedback on the other way. I learned this practice from you some years ago. And since then, we are, you know, rolling it out also to many other companies because I think it's amazing, you know, the idea of the teams setting up a, don't know, their plan for the year with their goals, with their OCRs or whatever, you know, method they're using doesn't matter with their outcomes, with their hypotheses, their, their road maps, you know, sharing this with the whole organization in a transparent way. And having a session open to everyone in which they can get feedback from anyone in the organization about their goals, strategies, tactics and the way the way to achieve this. I think this is one of the most amazing practices we have put in practice in organizations. It's giving us a lot of power, you know, to build these data-informed cultures, to build these radical transparent cultures. And thanks because to be honest, I learned this from you and I've been, you know, amazed about this practice from years. And does it really work for everyone at Netflix or other high performing organizations that you described? I've only seen it really happen at Netflix and I think it's like a great form. I was, I was really impressed. It was like one of the things that impressed me the most when I joined Netflix like now four years ago and I wasn't one of those forums. And at Netflix, those meeting rooms actually had kind of like a, kind of a Coliseum kind of Gladiator structure, like we're like a circle. And everyone's there like the, you know, presenter kind of presents the, you know, the world map. Usually there's also like a very memorable driven culture, like a very written down. Like, you know, when you write down your plans, it's very different than just creating like a slide deck, right? You have to go to like a very, you know, level of like detail that allows for that feedback, right? Because like if you say you have very high level, you know, generally people can like agree. It's hard for people to like give a lot of feedback when they don't have all of the context on like how do you arrive to that conclusion, right? Like how did you make that decision? What, what things did you evaluate like the pros and cons? So, you know, we, we were a very memorable driven culture, which means like writing down that plan and having pre read. So before going to a meeting, you have that shared context. People have read the document, have been able to like give leave comments. And like, you know, we, we, you like a gold dog can leave comments in the document. You know, and then like also give feedback life in the, in the session. And I think it's like, you know, as for me as a leader, I get so much value out of that session and define in helping, you know, redefine or define like this strategy of like our area, our, you know, test plans, the learning then take away like next steps. I think it's like great form to like seek kind of this broad diversity of voices. And sometimes like, you know, you have, we all have, you know, areas where like we're not as strong or like that we're missing some context. Having all those things being like filled in for you because you're like having that, oh, you know, big net off of feedback. I think it's, it's incredible. One of like the best things I find of like working at a network is in that form. So it's no slight that culture, at least to make decisions and to build this collective intelligence. And something that I was really impressed also is, for instance, when you want to get feedback from others, you are not using a complicated tool to just using a, you know, a Google doc or whatever, not other tool and just, you know, getting the free, the feedback at open document for everyone and just getting the feedback from people. So not complicated, super simple tools, just focusing on good matters the most. You know, not a story, not a lot of, you know, storytelling, just to the point. You know, what is, why we believe we need to do this? What are our hypotheses? What are our, the plans, the test plans we need to do and just letting everyone, you know, give feedback with Google comments in a collaborative way. So it's, it's amazing. Everyone will think that the company like Netflix is, you know, using complicated tools to get this feedback and you are making it very simple. Yeah, yeah, you definitely don't need complicated tools. I think, you know, just being able to like write down, you know, any, you know, you know, in a document like Google Docs where you do like a write down share, write comments like iterate, make suggestions, make improvements, you know, see kind of like the version control to like go back and see like how, how the document evolved over time. Yeah, it's, it's very simple. And sometimes, you know, you, you have a feedback session and you didn't, you know, write it down, you can, you know, you can just like voice it, right? Like something, you don't necessarily like any tool to log it to create a culture, right? Those are things that are set up to, you know, do something like try to kind of like control the process, but in this like freedom and, you know, and responsibility, like sometimes like you don't need that that control to like create the culture. You just need things to happen, right? And if in a moment you need to give that feedback just like through like zoom, just just do it, right? Just, you don't have to go through the process. The process is doing it itself, right? And whatever, you know, mechanism tool you find to be the most effective for you, that's the way to go. I just like say that, you know, I'm, you know, we're not anti-slides. They are also like some forms where like, you know, presenting things in like a more storytelling, you know, presentation for like a broad company audience. Maybe, you know, people that don't need or want so much level of detail is also great. You know, it helps kind of like align and share information in different ways. But I think when you're wanting to make product decisions, I find like writing down, you know, documents, providing all that context to the reader so that people can also decide, you know, it's part of freedom and responsibility. You know, there's going to be people that want to get to a lot of level of detail, having that level of detail prepared for them so that they can give you like valuable feedback. Because if you don't, you know, if you don't provide that context, it's also hard for people to like give you meaningful, safe meaningful things to contribute to make it better because they don't understand, you know, why you made that decision or like what data did you use to inform it, et cetera. You know, I would just stay with you hours and hours and now I was talking to you with this culture. And you know, we share, we share this passion. [MUSIC] Christine, in order to build this data in foreign cultures, we had actually global, you know, we have a fundamental value, impact over activity. How important is it, according to your experience, the prior desires, initiatives, goals, with the results. with well-defined goals and designed them to achieve measurable, substantive outcomes? How is it? How important is this? I would say it's very important, as I said, like, you know, you can't have an experimentation kind of like culture with, you know, we have enough things of, you know, testing all of these, like, hypothesis and learning from our members and they be here, you're just like, what works and what doesn't work to decide what to launch, you know, you can't do that if there's not an aligned goal and a line metric that we're all trying to like move forward. And if you don't define the success criteria upfront, you can't make a decision, right? And, you know, that's not how making a, you know, experimentation-based decision work. You have to like define your experiment, your success criteria, your decision framework upfront, and then, you know, once you see the results fall through. So yeah, I think it's really crucial that you define what you're trying to accomplish, what metrics you're going to be using to determine success or failure. But maybe one thing that I would like to say is that one thing that I observe is that in innovation teams, sometimes like what I see is that we over-emphasize precision and, you know, and we should be more comfortable with direction. So what I mean by that is, you know, we try to be very precise with the exact number. It's like, oh, this quarter, this team wants to like grow by this much. And we, you know, debate and we spend a lot of cycles coming up with very precise numbers. And I think we waste a lot of time, you know, fuzzy thinking that we're being accurate. But in reality, I think those, you know, those goals should be more of a direction, right? Like, it's more of like, you know, we're going with our compass and we want to go north, right? And if you want to go north, you want to, you want to go as far north as possible, right? And when you start putting constraints and you say like, oh, we want to just go two kilometers north, you know, that doesn't help innovation. Because then people are take less risk, are less willing to like, you know, kind of push the boundaries, like take bigger risks and swings to learn, they take less, less bigger bets. Because like, if you know that you're just going to go two kilometers and it's very, and the communications that it's very important to like meet that number exactly, I think generally people end up being very conservative in what they try and the idea that they try. But as if you say to the team, we want to not go north and we want to go north as far, as far north as we can, you know, you, you get surprises of like, the team is able to like go beyond what you expect, initially expected, right? So maybe, you know, they spend some time, you know, building a motorcycle to like go together 20 kilometers, right? And maybe they fail to build that first motorcycle and then they, they build a bike and then they can go 10 kilometers, right? But if you just have told them, oh no, we need to make two kilometers, then everyone starts walking, you know, and yeah, it's, you know, it's reliable, you might get there, but you could have maybe gone a lot further if you just had given them a direction versus like a precise number to accomplish. Yeah, and that is moving away with all my respects also to this finance, sometimes driven culture, this dashboard driven culture, where, you know, everyone wants to be safe and just, you know, heat a specific number in order to report it, you know, but people is not willing to go further, you know, they are not using this, as you said, this direction, you know, as, you know, as a way to move forward and to move as fast as possible and to move together and also learning in the process and how they can move increasingly faster, because that's also the part, as you move in a direction, how do you learn to move increasingly faster? Yeah, exactly. That's amazing. We like to say impact delivered, future created. Let's talk now about the future. What is next in data science, in AI, in ML, what can we expect in the next five years in all these fields? I still think that data science in ML is still pretty in its infancy and in organizations, even, you know, at a company like Netflix, which it has been like from the start, you know, it has been like one of the pioneers of using, you know, machine learning to, like, do recommendations, content recommendations. As a field, it's still relatively recent, and so I think there's still a lot of, like, adoption that needs to happen in organizations of those capabilities and technology to shift that this culture might have been more like data informed and bringing experimentation other data science, you know, in machine learning capabilities like personalization and really making it core of your product experience and learning how it can help build, you know, better product experiences, but also helping make better business decisions. I still think that we're, you know, globally pretty far away from making that happen, you know, across like all of our organizations. And I think it's how those methodologies and those capabilities can be embedded within the different functions to make those better decisions in each of, you know, in each of the roles that we have and how they help you make more like effective and efficient decisions. So I'm really excited about like areas where we're bringing AI and machine learning, for example, Netflix, like an area that I led for a while was helping creators in the creative process of cutting trailers of, you know, you know, deciding posters, you know, and like, what's the best asset or image to use to present a show to our members, there's still a lot of like those creative decisions that are like based on intuition and best practices which are great, but I think like we can like super power all of those like functions by bringing these capabilities into their workflows so that they can like leverage the data that we have, like how our members, how are like users interacting with that creative, you know, that you're doing, you're producing back to help you make better, even better decisions that, you know, you as a, us as like humans, we can't, you know, process because we can't process all of this information, all this data so that you can make better data in from decisions based on like what members, what viewers, you know, whoever your customer is once, versus just like what you believe they want. I was discussing this week with AI company in Silicon Valley, and we hit a strong discussion because they thought that the technology would make the difference. I didn't agree with them, you see, the technology will make the difference, but if we don't build this, you know, data driven cultures and the organizations, the technology will be there, the data will be there, you know, the dashboard will be there, your technology will be, you know, telling exactly what you have to do. But if we don't build transparent cultures where this information is available for everyone, where there are the rituals, how they have it, as we describe, you describe, you know, with this moment in Netflix where, you know, people are sharing all the information and it's getting collective feedback from others. If you don't build this cultures, the data will be there, the information will be there, but in the end there will be, there will be no relationships, not culture to use these data effectively, to, you know, to build better products, to build, or to have a, you know, a more powerful impact in the planet, because we also need a lot of this to make, you know, to change things in this planet. Exactly. I think like if you don't act, you know, you don't have to build a culture where people act on that data, act on that information, there's no impact. And will that change in 10 years? That would be exactly the same, huh? Doesn't matter if the technology is, you know, much more powerful, it would be exactly the same problem, don't you? Exactly. If we haven't changed kind of like the culture and like the mindset in organizations to, you know, and, you know, embrace this technology and help us make decisions differently, you know, it's not going to make a difference. I think that it's important, you know, just like speaking from like another side and another perspective, is that sometimes also that technology is not built with the humans in mind, right? Like there's like some direction that is just like about automating processes, rather than like enhancing existing processes with the humans that are the experts. So I think that there's also like a part where, you know, the technology also has to realize that the way to make an impact is by augmenting and making, you know, processes where there's like humans and experts, like even more effective and efficient with them in mind, right? It's not about just like automating, it's about like augmenting, you know, the human capabilities and like the our ability to make better informed decisions in our jobs and in our processes. So I think it's also important for like that side that the technologist to think about that and not just like, oh. we're going to automate and reduce cost by this much. I think there's an upside of all this technology of making better decisions, being more like effective at our job, and going to a next level of the things that we can create using them. >> Simple, amazing. Christine, thank you very much for your friendship. Thank you very much for this talk. We always learn a lot from you at actual global. Thank you for accepting the invitation to talk with us in impact leaders. It's an absolute privilege. We feel very honoured to have you today here. We know you are very busy, executive leader at Netflix and thanks for your time and being so humble, and being shedding all your knowledge with all of us. Thank you very much for this. >> Thank you. Thank you for the invite. Thank you for having me. It's been a lot of fun. >> Thank you very much. To all of you who listen to us at the other end, remember that you can continue the conversation with us on the actual global website, actualglobal.com, on our social media profiles, Instagram, Twitter, LinkedIn, and YouTube, through their profile at actual global. And don't miss a single chapter of this podcast by following us on any of these platforms. Spotify, Amazon Music, Apple Podcast, Google Podcast, IBOX, or Podimo. See you soon for the next impact leaders by actual global. Impact delivered, future created. [MUSIC]

Podcast Summary

Key Points:

  1. Christine Dodge leads product innovation in personalized experiences at Netflix, blending data science, user experience, and cross-functional teamwork to drive product improvements.
  2. High-performing teams are built on shared ownership, cross-functional collaboration, curiosity, humility, and trust, not individual heroism or ego-driven leadership.
  3. Remote and hybrid work challenge trust and relationship-building, requiring intentional creation of informal, empathetic spaces to foster connection and collaboration.
  4. Cross-functional, autonomous teams are more effective than functionally siloed ones, enabling better innovation, agility, and alignment with business goals.
  5. Radical candor requires trust and psychological safety—rooted in leaders’ openness to feedback and consistent modeling of vulnerability—rather than aggressive or one-time criticism.
  6. Experimentation, especially through AB testing, is essential for data-informed decisions, allowing teams to validate hypotheses and understand true cause-and-effect impacts.
  7. Freedom and responsibility go hand-in-hand
  8. Organizations must shift from precise, rigid goals to directional goals to encourage innovation, risk-taking, and learning—enabling faster progress and unexpected breakthroughs.

Summary:

Christine Dodge, Director of Product Innovation at Netflix, emphasizes the power of "dream teams" over individual leaders like Jeff Bezos or Elon Musk. She argues that high-performing organizations thrive not on personal charisma but on shared ownership, trust, and cross-functional collaboration. Effective teamwork requires humility, curiosity, and psychological safety—especially in remote or hybrid settings where personal connections are harder to build.

, AB testing) helps validate hypotheses and deliver user-centered outcomes. Radical candor is not about aggression but about trust; it emerges when leaders consistently solicit and act on feedback. At Netflix, autonomy is paired with accountability, where teams share goals, test ideas, and openly report results—creating a culture of collective learning.

Dodge stresses that technology like AI and machine learning only succeeds when embedded in a culture that values transparency and human-informed decision-making. She warns that without cultural shifts—such as embracing direction over precision and empowering teams to take risks—technology will remain underutilized. Ultimately, the future of innovation depends not on tools, but on leadership that fosters trust, transparency, and shared responsibility.

FAQs

They lead product innovation at the intersection of user experiences and personalization, focusing on improving content recommendations and leveraging data science to enhance user engagement through machine learning and feedback loops.

Dream teams are defined by ownership, cross-functional collaboration, and trust. Members feel accountable for collective outcomes, communicate openly, and act with humility, ensuring all functions contribute to shared goals.

Remote work makes it harder to build trust and rapport through informal interactions. Deliberate efforts are needed to create spaces for connection, as in-person interactions help foster empathy and understanding that are essential for effective collaboration.

Radical candor requires trust—team members must feel safe giving and receiving honest feedback. Without trust, feedback is perceived as criticism, leading to defensiveness. Trust enables open dialogue focused on improving outcomes, not blaming individuals.

Experimentation, like A/B testing, allows teams to test hypotheses with real user behavior data. It establishes causality, helping organizations know whether changes truly improve user experiences or are merely coincidental.

Teams are given freedom to make decisions but must also be accountable for outcomes. This balance is supported by transparency, where results and learnings are shared openly, enabling collective growth and trust across the organization.

Chat with AI

Loading...

Pro features

Go deeper with this episode

Unlock creator-grade tools that turn any transcript into show notes and subtitle files.