Category: Le Podcast – Season Four

  • Optimizing for the Unexpected – Insights from Gojko Adzic on Lizard Optimization

    Optimizing for the Unexpected – Insights from Gojko Adzic on Lizard Optimization

    ome of the most valuable product signals do not come from your roadmap, your user interviews, or your strategy workshops.

    They come from the weird stuff. The edge cases. The misuses that look irrational at first glance.

    In this episode of Le Podcast on Emerging Leadership, I welcomed back Gojko Adzic, one of the most influential voices in modern software development, named an AWS Serverless Hero (2019) and author of Impact Mapping, Specification by Example, and his latest book Lizard Optimization.

    Gojko’s core idea is simple and powerful: pay attention to unexpected behavior, because it often reveals hidden opportunities.

    He calls these unexpected users “lizards”.

    Not because they are wrong, but because their behavior looks non rational from the perspective of the product team.

    And that is exactly why they matter.


    Lizards are not a problem

    They are a signal

    A key story from our conversation comes from the early days of PayPal.

    The founders built a PalmPilot based solution and expected the product to live there. Users, however, started using a rough web demo in a different way. Product managers initially fought the “misuse”. Eventually, the numbers made the truth unavoidable: the web path had massive adoption compared to the PalmPilot path.

    The lesson is sharp:
    If you fight users to protect your original vision, you might miss the market that is trying to adopt your product.

    This is what Gojko means by lizard optimization:
    Identify misuse, then decide whether it is a threat to block or an opportunity to amplify.


    The LZRD loop

    A practical method to work with the unexpected

    Gojko describes a four step approach that is easy to remember because it spells LZRD.

    Learn
    Observe and collect unusual behavior. Not with judgment, with curiosity.

    Zoom in
    Most weird signals are noise. Some are gold. Pick one behavior that is meaningful enough to explore.

    Remove obstacles
    Users often “misuse” a product because the product blocks the outcome they want. Remove friction that prevents valuable usage.

    Detect unintended impacts
    Even good fixes can create new problems. Watch what happens after changes, and be ready to adjust.

    What I like about this loop is that it complements user research. It helps you discover unknown unknowns. Things you would not think to ask about.


    Two examples that make it real

    Subtitle files in a text to speech product
    Gojko noticed users uploading subtitle files. That looked odd until he understood the job to be done: creating synchronized audio tracks for video content without manual editing. A small change unlocked a valuable use case for a specific segment of customers and delivered outsized business impact.

    VAT number friction and unintended impact
    Gojko tried to remove a payment obstacle by changing where VAT information was collected. The result was fewer payments. The fix made sense logically, but broke expectations for a subset of users. The mismatch reduced conversion.

    This is why the last step, Detect unintended impacts, is not optional.


    Mismatch beats blame

    A concept that fits extremely well with lizard optimization comes from Kat Holmes’ book Mismatch.

    Instead of saying “users are stupid”, treat issues as a mismatch between:

    • the user’s situation, expectations, or capabilities
    • and the product’s design

    This framing keeps teams humble and productive. It also opens the door to solutions that improve the product for many users, not only for the one strange case.

    Solve for one, expand to many.


    From products to organizations

    Watch the desire lines

    Gojko connects this to a broader idea: desire lines.

    In physical spaces, desire lines are the paths people naturally take across the grass when the official paths do not match how they actually move.

    In organizations, desire lines show up when:

    • teams route around processes
    • workarounds become common
    • people find unofficial paths to get work done

    As a leader, these are not annoyances to punish by default. They are signals to examine:
    What obstacle are we creating
    Is it intentional
    If not, what would it take to remove it


    The humbling truth

    Most ideas do not create value

    Gojko ends with a message that is both uncomfortable and liberating.

    Data from large scale experimentation at companies like Google and Microsoft suggests that a majority of changes do not create measurable value. Many ideas fail.

    That is not a reason to stop innovating. It is a reason to test, learn, and stop bad ideas earlier.

    The competitive advantage is not having more ideas.
    It is discovering faster which ideas work.


    A question to take with you

    Where are your lizards today

    In your product, your customer journey, your team, your organization

    What looks like irrational behavior might be the clearest signal you have.

    Listen to the episode here or on your favorite platform.

    References Mentioned

    1. “Build a Product with Gojko Adzic” – An episode of Le Podcast on Emerging Leadership
    2. “Founders at Work” by Jessica Livingston – Stories of Startups’ Early Days
    3. Lizard Optimization by Gojko Adzic – Learn how to transform unexpected product usage into growth opportunities.
    4. Trustworthy Online Controlled Experiments by Ron Kohavi et al. – A foundational guide on using experiments to discover what truly works for users.
    5. Mismatch by Kat Holmes – Explore inclusive design and learn to recognize mismatches in user needs versus product design.

    Here is the transcript of the episode

    Alexis: [00:00:00] Welcome to Le Podcast on Emerging Leadership. I’m your host, Alexis Monville. And today, we are joined once again by a very special guest, Gojko Adjik. Gojko is a renowned author, speaker, and recognized leader in the world of software development. He’s been celebrated as one of the 2019 AWS Serverless Heroes, the winner of multiple prestigious awards, and the mind behind several influential books, including Impact Mapping and Specification by Example. In our last conversation, we dove deep into how to build a perfect product, how to avoid waste in software development, and explore the principles of impact mapping.

    Today, we are excited to discuss his latest book, Lizard Optimization. We’ll be unpacking the core ideas in the book, how they apply to modern software development, and what it means [00:01:00] for leadership in an evolving technological landscape. Welcome back to Le Podcast on Emerging Leadership, Gojko. How do you typically introduce yourself to someone you just met?

    Well, I say I’m Gojko, it’s like Beyonce, you know, it’s.

    Does it work really well? 

    Gojko: Oh, I guess so. I don’t know. I’ve never been in a situation where it doesn’t work because maybe people try to be polite to me. I’m a developer. I kind of build my own products. Now I write books mostly as a way of. Doing a brain dump so I can leave more space for other things. I stole that one from Henry Kniberg.

    He said, kind of, he likes to do a brain dump to free up shorter memory. I think upgrading RAM in my head would be really expensive. It’s cheaper to write a book. 

    Alexis: I love the way it’s said. I have to agree with that. When you try to write something, could be read by not [00:02:00] only you, but also by other people.

    It’s really good to help you structure your own ideas. 

    Gojko: Yeah, and it gets you to clarify things that might not be perfectly clear. It’s always fun. While I was writing this, my most recent ninth book, I was trying to hunt down some quotes in exact way, the way they were said. And I’ve realized that for years I’ve been doing conference presentations and quoting some people completely wrong.

    I misremembered it the way I read in the book, but then read actually what they said and kind of, the meaning is there. I, I didn’t misremember the meaning, but Really shame on me for misquoting people. So yes, you get to consolidate your thinking and really verify that it’s still correct. 

    Alexis: You spoke briefly about your latest book.

    The latest book is Lizard Optimization. I would probably not have picked that book on a shelf. I don’t know anything about lizards. I’m not [00:03:00] really keen to optimize any lizard. That’s 

    Gojko: your mistake as a leader. I think your job needs to be to watch out for lizards and support your product teams in optimizing for lizards.

    That’s incredibly important. 

    Alexis: So now you need to explain a little bit. You need to tell me what inspired you to write the book and what does that lizard mean? So what inspired me to write the book is 

    Gojko: a really crazy growth phase for one of my products where the usage increased by about 500 times in a space of 11 months.

    So that means that things that were weird edge cases that would happen once every two years now start happening every day. And the whole 11 months was a bit crazy and firefighting and things like that. But I’ve learned a lot and I wanted to pass on what I learned [00:04:00] to other people and maybe inspire them to investigate these things on their own.

    And a lizard optimization is in a sentence, figuring out how people are misusing your product. And then figuring out whether you want to support that kind of misuse in a more systematic way, whether that should be done, or whether you want to block it and prevent it. And both of these things are valuable.

    The one example I really like that’s not from my product, but I read this in a book called Founders at Work by Jessica Livingston. Was from a company where in late nineties, the company was started because some super, super smart people built some incredibly efficient cryptography algorithms. And they had a solution, but they didn’t have a problem.

    We built this now what then somebody said, well, these are incredibly efficient algorithms, so they [00:05:00] can run on low power devices because they’re efficient. They’re not going to spend battery too much. And PalmPilot was a popular low power device there. So they said, well, let’s run something on PalmPilot.

    What do you need encryption on a PalmPilot for? And they said, well, encryption brings security. You need security when, I don’t know, you’re transferring money. And then they build a system where you take your PalmPilot out of your pocket. I take mine and we bump it together. And money goes from my PalmPilot to yours.

    That was wonderful. That was magic. And it was all insane. They had trouble getting people to know about the mobile application and to use it. Late 90s was a time where web was becoming popular and they built a website to promote the Pornpilot app. So as a way of getting people to try it easily and experiment, they had this really horrible, very rough demo thing where you could use the website to transfer money to somebody’s Pornpilot account.

    And, [00:06:00] What people started doing is they were using the website not to transfer the money to somebody’s PalmPilot account, but to transfer the money to an account and opening it even without having PalmPilot devices. The product management was really furious with that because somebody was misusing their system.

    They were not using it for PalmPilots. They had nothing to do with their brilliant app, nothing to do with These efficient cryptographic algorithms that were running on low power devices, because it was all running through the website. And people even started using the trademarks and the names on forums, like, Oh, send me money, buy this or something like that.

    It kept fighting it. The product people kept fighting it. They were going in these forums and saying, you’re not allowed to use our name. We’ll sue you and fighting with the users. At some point, somebody looked at the numbers. The website had 1. 5 million active users and 12, 000 PalmPilot app installations.

    And somebody who can do mathematics basically said, well, [00:07:00] this PalmPilot thing is really not as popular as the website. So they kind of killed the PalmPilot app and the web app became PayPal. That today is known as PayPal. PalmPilot no longer exists. And we do have. Low power devices and things like that.

    And PayPal runs on mobile phones. And of course, you know, you can, I don’t know if you can transfer money by pumping it, I think that’s like a weird gimmick, but it’s used to transfer money all over the world by doing this PayPal pilot bump, you have to be next to somebody and you, now you can use PayPal to transfer money somewhere, halfway around the world in a different time zone.

    And I think that the really interesting lesson there is that the product managers fought against users for a very long time. They fought against this misuse. They fought against people actually trying to benefit from the product in a different way because it wasn’t consistent with their vision that they were trying to stay true to the vision, not true to solving the problem.

    And I think this is where people fall in love with the solution, not with [00:08:00] the problem. And, and I think that’s kind of one of the biggest issues product companies have. So I think as a leader of a company and your, uh, listen as a leaders. Helping your product, people like focus on solving the problem. Not loving the solution is really, really important and noticing when people are misusing your product.

    It becomes important both for unlocking growth and for understanding where the market wants this product to grow, because it opens up some incredible growth opportunities. If the PayPal stayed on the Palm Pilot app, they would have had 12, 000 users and that’s it. They would have never made a kind of a decent company out of it.

    And I think this is what becomes really interesting. Lizards in this terminology are people who do things that you can’t logically explain. It looks like it was done by somebody who’s not a rational human. They’re doing something you didn’t expect. They’re doing something you don’t want, but they are effectively misusing the system.

    Now they might be [00:09:00] misusing the system or trying to misuse the system in a good way or a bad way, but kind of figuring that out becomes, I think, critical for good product management. 

    Alexis: This is very interesting because yeah, you, you take the examples of product managers fighting against misuse of the product.

    Just noticing that something is going on is already something important. And I, when I read the book, I was there and was looking at that to say, Oh, I don’t know if I would have noticed that. And the example of that video that is blank. How would 

    Gojko: you even know? And that’s really an interesting thing. So, for example, one of the products built allows people to upload different types of documents and create an audio file using text to speech.

    So, when users do something unexpected, like trying to upload an unsupported file type, they will get a decent error message. I set a number of people every day that try to upload MP3 files into a text to [00:10:00] speech system. I don’t understand why you would do that, what you expect, how that would even work.

    Converting audio to audio, you’re not converting text to speech. It’s weird. There are people who try to upload Android package files every day. I, I don’t understand how you would do that, but occasionally there’s somebody who kind of does something potentially useful. Now, with the error message that people get, Oh, you know, you’re, you’re uploading something that is not text.

    We can’t read that. In addition to showing the user an error message, I get a message. I get a log message that I can expect that somebody did something I didn’t expect. Now, I started noticing a pattern, uh, about a year ago where people were trying to upload subtitle files. Subtitle files come with video files, they are subtitles for a movie or, or something like that.

    And, um, they’re text files, they’re not images, they’re not Android packages, they’re not [00:11:00] music, they are text files. So I thought, well, I didn’t expect this extension, but why not? I can just enable that extension in addition to txt and I enable that and then I started getting complaints from people saying that, uh, the system also reads the timestamps.

    Subtitle file said timestamps when to show certain text. Yeah, you’ve uploaded a file with timestamps. What the fuck did you expect? It’s, it’s kind of reading the timestamps. It reads the content. But yeah, I wasn’t expecting it to read the timestamps. I was only expecting it to read the kind of voiceover.

    I said, well, I can understand that. So it took me five minutes to just skip over the timestamps. And then people were complaining that it reads the text too slowly. It’s like, what do you mean too slowly? It is the text at the speed of it reading the text. I mean, and then I realized talking to people what they were trying to do actually, you know, in the jobs to be done category is they were trying not to just convert text to speech a step there.

    But what they were trying to do [00:12:00] is to create an alternate audio track for their presentation video. And instead of creating lots of short clips and then aligning them themselves, what they were hoping to do with the subtitle file is to get the whole thing synchronized. Now, it was, you know, logical. I see the value in doing that.

    It was a very tiny percentage of users doing it, but it was a small change. It was a technical challenge. It was interesting to do. So I did it. So in total, you know, we’re talking about two days of work in total, building on top, by far the most profitable thing I’ve ever done. By far, what happened later is that these features were discovered.

    Like there’s an American mega church where they have these sermons, religious lectures, whatever. And then they want to have them in all the languages on earth. And they’re using my system to. [00:13:00] Somebody types over the subtitles or I don’t know how they produce them, but then they just use the subtitles to create alternate audio tracks for the priests kind of preaching.

    There’s an enterprise software company that’s using this thing for all their instructional videos. To basically automatically get an alternate. So if you’re a, if you’re a video content editor, usually what you would have to do with this is either try to record your voice or get somebody to record short clips and then suffer through hours of placing the clip at the right place in the video, where with this thing, you get it almost instantly.

    And it saves you hours and hours and hours of time. And if you save somebody hours and hours and hours of time, they’re willing to give you some money for it. Especially if it’s automated, then they can do it at scale. So although this feature is used by like a tiny percentage of my users, it’s probably contributing a decent percentage of the revenue where the most kind of profitable customers we have on the tool are actually using it for that.

    [00:14:00] So that’s the value of. Lizard optimization. I would have never guessed this without monitoring for weird file types that people are uploading. And I would not have done it in user research because I would not be doing that kind of research. I would be interviewing people who need something else done.

    And I think lizard optimization is a wonderful way to complement customer research and user research and discover the unknown unknowns. You know, you can discover through customer interviews and user research, you can discover known unknowns. You kind of, you know what people want to do, but you don’t know the details and how important something is or what, but this is really helping us deal with the unknown unknowns.

    And this is really interesting because it can open up a completely new market segment. It can show you that people want to go in a totally different direction. And maybe you don’t know that. And you need to consider it. And I think that’s why I think this is [00:15:00] such a powerful method to use. 

    Alexis: It’s interesting because we can apply that in a lot of different things.

    So of course, when you’re building a product, it’s kind of obvious, but my temptation was to say, okay, how can I learn that someone is doing something unexpected? Because as you said, in user research, you’re coming with your own assumptions about what is going on and you’re asking questions, you try to validate your assumption, but there it’s way more powerful because basically you’re trying to be on the lookout on what is going on and what are those things that you can brush saying, Oh, those users are completely idiot or maybe they just have a brilliant thing that I can solve in two days of work.

    That’s very interesting. How do you see that? Do you have a, do you have a kind of structure to help people understand how it works? 

    Gojko: So I think the process itself, I’ve kind of nailed it down to four steps to use myself. And the four steps are easy to remember because they start with the letters LZRD, like lizard, [00:16:00] The first step is to learn how people are misusing your product.

    That’s the L, learn. Then the second step is to zoom in on one behavior change. You can’t change everything. And when you start looking for weird stuff, there’s a range of incredibly weird. We’ll never understand it to this kind of makes sense. And it’s going to be a lot of noise and we need to figure out the signal in that noise.

    The zooming in is the second step. The third step is to remove obstacles from users. And the, the software is placing obstacles in front of users and not letting them do something they wanted to do or the product. And that’s why they’re misusing it. Some obstacles need to be removed for them to be able to do that.

    And then the last step, the D. Is to detect unintended impacts because these people follow their own logic. They don’t necessarily follow my logic or your logic and our assumptions about how we’re going to fix the problem aren’t necessarily true. Like I said, my first idea was, okay, just [00:17:00] support the file.

    That’s okay. But then there was an unintended impact where people were starting to complain and we increased support because we were reading all the timestamps and things like that, lots and lots of times where I thought this is going to be a good idea. didn’t turn out to be spectacularly good. 

    Alexis: Can 

    Gojko: you 

    Alexis: give me an example about that?

    Gojko: Yeah, like in European Union, kind of, there’s like VAT numbers. So with VAT numbers, uh, you need to enter a VAT number for the receipt. And with the digital product, If you’re selling things to individuals, you have to charge VAT in the country where the individual is. If you’re selling to companies, you don’t charge VAT.

    They have to account for that using reverse charge magic and things like that. Now, without going too much into the accounting details, companies want to put their, or people purchasing for business, want to put their VAT number in. If they put a VAT number in and they’re doing it with domestic transaction, they’ll usually just put the number.

    But if they’re doing it in a foreign [00:18:00] context, they’ll put the country prefix. So FR 12345 is for France. And the payment processor I use is done by an American company. They don’t understand all of that. It’s too complicated for them. And they’re trying to validate these numbers. But very often they, even if you selected France and you entered one, two, three, four, five, it’s obviously the French one, two, three, four, five number.

    What they’ll tell you is, Oh, this is an invalid VAT number. It’s not, it just, you’re not storing it correctly. And I can’t do too much about their validation. It’s their validation. It’s third party product. But what happens is I had a percentage of a good percentage of people. People that go try to purchase, they enter 4, 5, this thing tells them it’s an invalid number, and they think it’s the card number, not the VAT number.

    So then they added the card number, it fails, it fails again, and, and, and, so a ridiculous number of people from European Union end up selecting Russia as their country because Russian VAT numbers don’t have a prefix. It is, it is ridiculous just to enter the thing to, like, [00:19:00] I’m placing an obstacle in front of them trying to pay me.

    This is idiotic. So I thought, well, you know, let’s solve this and all that can’t control the validation on, on the form. It’s done by the payment provider. I can remove the field altogether. And then when they pay, I can say, okay, now to get an invoice, give me a VAT number. And then I can say, well, you’re in France, obviously the prefix is FR.

    I did that. And then I measured where the people are paying me more. And it turns out people are paying me less. 

    Alexis: Uh, 

    Gojko: Uh, yeah, so unintended impact. So what had happened is I thought I’m going to solve it, but actually people that wanted to pay for the company, they go to the form where they couldn’t put in a VAT number and then they didn’t pay.

    They were confused. They, they expected a place to put a VAT number in, and the number of payments dropped significantly. So I had to kind of go back and, and, and do some other stuff there. So that’s kind of an example of an unintended impact where [00:20:00] something that’s, you know, to me as a maker sounds perfectly logical to a user might not, or to a user of a certain type might not.

    And this is where I absolutely love, you said users are not that smart and things like, I absolutely love this book by Kat Holmes called mismatch. Because she rephrased this whole thing. It’s not that the users are stupid or smart or whatever. It’s kind of, there’s a mismatch between the user’s capability and the software.

    Now, that mismatch might be something we want to do something about or not, but we need to understand it as a mismatch. There’s, uh, people that, Expect the VAT field to be there and the VAT field is not there. It’s a mismatch of expectations. People that the user interface is very complicated, a developer can use it, but a regular person who’s not a trained developer doesn’t follow that logic.

    You can blame the user for being stupid, or you can say there’s a mismatch between what the user is expecting, their experience, the software. [00:21:00] Likewise, there could be a mismatch. Like. Visual capabilities. You might have somebody who’s vision impaired. They can’t read small letters, or you might have somebody who’s sitting on a beach under direct sunlight, and there’s not enough contrast on the screen.

    There’s a mismatch between the user situation and the app and the solution. And I think identifying these mismatches allows us to then talk about Do we want to solve it? Do we not want to solve it? Do we care about it or not? I mean, I, maybe I can’t build an app that works fully for blind people, but I can make an app that works well with somebody who’s elderly and has bad vision.

    And if I do that, I will also make it so that people on the beach can read it or, or, you know, if they were in a dark environment or something like that. And, and, and Kat Holmes talks about how You don’t necessarily follow each of these really difficult edge cases because that economically doesn’t make sense, but you figure out how to solve that and at the same time improve the product for everybody.

    Alexis: [00:22:00] You have a small population of users that could be affected by that if you look at it from one angle, but in reality it will help a large group of your users. 

    Gojko: And you just think, yeah, you make a better product. Like, for example, a couple of years ago, we had a bug report for MindMap. MindMap is one of my products.

    It’s a collaborative diagramming mind mapping tool, and we had a bug report that it does not work well on a refrigerator. Okay, well, I mean, it doesn’t work well if you put it on a microwave as well. It’s not intended for that. It’s intended for computers, not for kitchen utensils. You have these weird things where people play Doom on a microwave screen or something like that.

    How did you get my software to run on fridge? That’s the first question. A woman who stayed home in the mornings to take care of her children, this was before COVID and work from home and things like that. Because our software requires a large screen, it’s kind of a [00:23:00] diagramming thing, uh, running it on a phone is not really an option, but keeping a laptop opening the kitchen when you’re cooking is also not necessarily the safest thing to do.

    You can damage quite expensive equipment doing that. So she actually had an Android screen on the fridge that had a browser, but you don’t load it up there, but the software just did not work without the keyboard. It required the keyboard to work. So it didn’t work that the problem is not that it didn’t work on a fridge.

    The problem is it was useless without the keyboard, really, because we never really thought about people using it without a keyboard. Or a pointer device or something like that. So instead of making it run on a fridge, which was pointless, one user in 10 years complained about that. We thought about, well, maybe there’s a whole class of people who are not at the keyboard at the moment.

    Maybe there’s a whole class of people who just need to observe rather than Participate, because she wanted to observe the collaboration that her colleagues were doing. Maybe [00:24:00] there’s some stuff we can do, like changing it from a floating toolbar with really small buttons to a really large toolbar with big buttons that you can control and things like that.

    So we iterated on that. And I think we came up with a much, much better UX design for the app in general, not just making it work a better on a fridge. So it works better, even if you have a laptop and a keyboard and a mouse, it still works better for you because we challenged ourselves to improve the UX.

    Alexis: Yeah, it’s, it’s very interesting. So that was one person trying to do something, but as a result, because you observe that very carefully, you realize that could affect and improve the product for basically all the users. It’s very interesting. It’s not only discovering new use cases or probably new personalized or new possibilities of development for the product.

    It’s really improving the product overall. So there’s, that’s another class of, uh, 

    Gojko: Kat Holmes has this principle in her book talks about solve for one, expand to many. And that’s really important [00:25:00] because especially if you look at kind of lizard behavior, these are like really, really weird things that go on, but solving and doing things for such weird edge cases, it’s never going to be economically justifiable.

    I mean, you can look at a product manager, looks at the weird edge cases. Well, this is like, 0. 1 percent of our users. I can’t spend time doing this. I have to spend time doing what 80 percent of the users expect, but it’s not about helping that 0. 1%. It’s about using that as signals that your software is placing obstacles in front of people and then figuring out, well, maybe there are some obstacles in front of other groups of people as well.

    Alexis: I love it. How would you translate that into other things than software development or building products? You have a leader or an emerging leader. How would you translate that in the realm of an organization or a team? 

    Gojko: Well, that’s an interesting question. You know, I think, uh, quite a related concept from outside of software is those kind of [00:26:00] desire lines, desire lines are from usability research and things that where you try to figure out, I think there was a story about this university where they built a new campus instead of trying to figure out where to put the.

    Walk paths and, and the roads, they just planted grass and let students walk around stepping on the grass. Then they figured where the grass was stepped on and built the pathways there instead of trying to predict where the pathways are going to go. I think from an organizational perspective, that’s something that we can figure out.

    What do we want? our employees to do? How do we want to support them? How as a leader can I support people in what they want to do, not what necessarily we think they want to do? I remember one kind of really weird case, maybe it fits into this, maybe it doesn’t, when I was working with hedge funds or small investment banks.

    Small in this case means about 3000 people. So not [00:27:00] massive international giant, but not a small company as well. And they had a couple of hundred developers and we were trying to help them improve the software process, but whatever we suggested, it wasn’t improving productivity because the bottleneck was somewhere else from the systems thinking perspective, the bottleneck was somewhere else.

    And then we’ve done a kind of figuring out where people feel that they’re wasting time. One of the things where lots of people felt they were wasting time was waiting for virtual machines to start. The morning, everybody comes at the same time and they had this recent policy where for business continuity reasons, they were not allowed to keep any data on their physical machines.

    Everybody had to use a virtual kind of remote Citrix. So everybody comes in at the same time. They kind of, you know, start logging on to this. They didn’t have enough capacity and they were waiting for something ridiculous, like 40 minutes in average for access to these things because it was new and imposed, people were complaining, but they were just getting shut down because it’s for [00:28:00] whatever, for reasons.

    The leadership introduced it and we realized, well, the introducing things like continuous delivery, test driven development, whatever, it doesn’t matter really, because your bottleneck is virtual machines and they were limited by the amount of hardware they had. But developers time in a financial institution in central London is quite expensive if you think about just in salaries.

    So we added up the money. We went to the CIO and we said, look. You are spending this amount of money every month on people just waiting for virtual machines to start. With this amount of money, you know how much hardware you can buy. Can we please use some of that money and buy more hardware for virtual machines?

    And then he said, of course we can, it’s logical, but why are people waiting for virtual machines to start? Like, why are developers doing that? So, there was a company wide policy, everybody has to use virtual machines, business [00:29:00] continuity. And he said, yes, everybody, like traders and not developers, like developers don’t store data on their machines anyway, it’s in version control.

    Okay. So you want to do, I said, well, it’s idiotic. Why are you just killing productivity from people? So there’s like a totally different desire line there. There’s a different path. And I think this is an example of the company misusing its own people. I guess because when they said everybody, they didn’t mean developers.

    So I think as a leader, it’s important to kind of figure out Both when misuse is happening in one way or another way, and where if you have people that are trying to treat the system in some way, do we want to actually support that or not support that? How do we figure this thing out? And if we’re placing obstacles in front of people, are those obstacles intentionally there because sometimes they are.

    Or those obstacles are [00:30:00] intentionally there and then they should be removed like this policy where basically, yeah, if you have version control, you don’t have to use a virtual machine. Makes total sense. 

    Alexis: So lastly, what would be the one advice you would give to your younger self? 

    Gojko: One advice I would give to my younger self, I think that would be in terms of just product building, not to trust that things I do actually have value.

    And to try to validate it. I think I’ve spent far too long in my career trusting that the things I do are actually good ideas. And very often they’re not. I’m not alone. I love Ron Kojavi’s latest book called Trustworthy Online Controlled Experiments. Here’s data from companies like Microsoft, Google, Slack, Netflix.

    The data says that kind of between one 10th and one third of things they do actually [00:31:00] delivers value. 

    Alexis: That’s okay. After that, you need to be a little bit more humble. Okay. 

    Gojko: That means that these people who are supposed to be industry leaders kind of Between seven out of 10 times, things that they think are good ideas are not necessarily good ideas.

    Alexis: Okay. 

    Gojko: They don’t, they don’t improve the product in a measurable way. And with something like that, I guess it’s really interesting to think as a leader or as a, as a product manager and executive supporting product managers, what brings value to the market so we can capture some of that value, uh, back because If we’re not delivering value to the market, then we can’t really capture the value back from the users.

    And if we can’t figure that out, then we can run circles around the competition because the bad news for most listeners that have never thought about this is that, well, I’m just going to stick the range in half there. So eight out of 10 things you do make no sense. But the good news is that eight out of [00:32:00] things your competitors do.

    If you can figure that out faster than the competition, you can create a much better product. And I think that’s why these companies are winning in the market, because they can figure that out and they can understand that they can measure it. They can stop bad ideas from progressing too far. 

    Alexis: This is very insightful.

    for sharing that. 

    Gojko: Trustworthy online control experiments. Wonderful book. Wonderful book. 

    Alexis: I will add the references in the companion blog post. Thank you very much for having joined the podcast, Gojko. 

    Gojko: Thank you!

  • Leadership as First-Time Founders: People First, Focus Always

    Leadership as First-Time Founders: People First, Focus Always

    Leadership looks different when you’re a first-time founder.

    There’s no handbook for the moments that matter most — the ones where you have to show up as a human, make a decision as a leader, and keep the company alive at the same time.

    In this episode of Le Podcast on Emerging Leadership, I welcomed Héloïse Rozès and Nikolai Fomm, co-founders of Corma, a startup helping companies regain control over their software tools and licenses. Corma’s mission is deeply practical: bring clarity to the SaaS “black box”, improve employee experience, and help IT teams manage access, cost, and risk — especially as new tools (including AI tools) keep multiplying.

    What I loved in this conversation is that it’s not theory. It’s leadership learned in motion.

    Here are a few ideas that stayed with me.


    Communication is not one skill — it’s many

    Héloïse describes communication as her biggest challenge — not because she dislikes it, but because it constantly changes depending on who is in front of you.

    Co-founders. Employees. Interns. Freelancers. Investors. Clients. People you meet at an event.

    Same company. Same reality. Different language every time.

    And as Nikolai adds, the CEO role amplifies this even more: you’re often “the voice” externally, and the internal team watches how you represent the company outside.

    Leadership forces an uncomfortable question:
    are we consistent across all the rooms we enter?


    People are the challenge — and the point

    Both founders put people at the top of the leadership challenge list.

    Not in an abstract way. In a very real, operational way.

    Héloïse shares a moment many founders face for the first time: an employee announcing a maternity leave. The human reaction is joy. The leadership reaction is also: how do we adapt?

    The tension is real and constant: you can be empathetic and still compute the consequences. That doesn’t make you less human. It makes you responsible.

    I appreciated how they name it clearly: balancing care and survival is part of the job.


    Prioritization is the art of saying “no”

    One of the most concrete leadership lessons Nikolai shares is the difficulty of saying “no”.

    In startups, ideas are everywhere — especially with creative, ambitious people. Many ideas are good. The problem is that resources are limited.

    If you do everything, you do nothing.

    Saying no is not rejecting creativity. It’s protecting focus.

    And Héloïse adds an important filter she uses: if an idea doesn’t connect to market value and impact (including revenue), it may be interesting — but not now.

    That clarity is leadership.


    Culture doesn’t happen — it is built

    Héloïse and Nikolai insist on something many teams forget: culture is not a poster. It is practice.

    They talk about culture in very concrete ways:

    • being on time (or even early)
    • being available to talk when someone needs it
    • celebrating small wins
    • avoiding “two companies” inside one (sales vs tech)
    • intentionally creating cohesion

    They also created a program called Cormacolindor — an ambassador-style ritual inspired by the origin story of “Corma” (a nod to the One Ring), designed to help new hires collaborate, build spirit, and shine individually.

    I like this because it’s not vague. It’s designed.


    Radical Candor: avoid ruinous empathy

    They use Radical Candor (Kim Scott) as a feedback foundation.

    And Nikolai makes a point that is worth repeating: for teams that genuinely care about each other, the biggest risk is not aggression — it’s ruinous empathy.

    When you care personally, you might hesitate to challenge directly.

    But not giving the feedback doesn’t protect the person. It delays the learning and increases the cost.

    Leadership is not being nice. Leadership is being helpful.


    Advice for first-time founders: don’t do it alone

    Their closing advice is simple and strong.

    You don’t learn leadership from a textbook. You learn it by doing — and by talking to people who have done it before.

    Héloïse suggests a practical move: list the leaders you admire and reach out. Nikolai adds that many experienced leaders are surprisingly generous with their time when the request is genuine.

    This is a great reminder: mentorship is often closer than we think.

    Listen to the Full Episode

    Tune in to learn more about the Corma journey, leadership insights, and practical advice for emerging leaders.

    Here is the transcript of the episode


    Alexis: [00:00:00] Welcome to the podcast on Emerging Leadership. I’m your host, Alexis Monville. Today, we have both Héloïse Rosas and Nikolai Faume on the show. They are both co founders of Corma, and they will explain a little bit what it is. Héloïse and Nikolai, it’s great to have you both on the show. Let’s start with some introductions.

    How do you typically introduce yourself to someone you just met? It’s 

    Héloïse: a good question. When I meet someone. So if this is like in an informal setting, I’m going to say, hi, my name is Héloïse. I’m working in Paris as a, as a founder. And then I’ll just see if the person is in a startup ecosystem or not before knowing how to introduce myself better.

    Alexis: Okay. Nikolai, how about you? 

    Nikolai: Yeah. So I would say that I’m also Nikolai, one of the founders of Corma and then yeah, maybe say a little [00:01:00] bit more about what I’m doing in life or at the company. And then usually it gets quite quickly to what we’re doing as a company. But yeah, I do it a bit like Héloïse, see a little bit, who do I have in front of me, so I don’t give like a minute monologue that the other person doesn’t really understand 

    Alexis: or wants to know. 

    Let’s say now I’m interested and I’m saying, okay, what is Corma about? What would you say? To keep it 

    Nikolai: short and spicy. I mean, usually people work with a lot of different software tools nowadays and it’s become so many, I mean, just think of all the new AI tools that are coming in. It’s becoming a mess for all the employees to understand, okay, where do I have access?

    How do I get access to a new tool? But it’s It’s messy for the company who needs to make sure you don’t pay for seats. Nobody is using your people are not signing up to dangerous AI tools and load up their entire company secret data to some weird AI company in China. It’s also a mess for the it team.

    And basically as Karma, we want to solve that by bringing everything together in one place, [00:02:00] providing a great employee experience. And at the same time, making the life easier for the company. 

    Alexis: Excellent. I love it. Héloïse, can you do it better? Just to check that, can you make it shorter just to put some competition between the two of you?

    Héloïse: Good. I mean, I’m lucky I got a bit of time to think about the question. Corma is the co pilot of your IT for handling licenses. So that’s how I put it in a sentence. People are like, okay, but what does it really mean? I simply tell them you’re a head of IT of 1000 people. You have to manage computers, Wi Fi, VPNs, and the little mouse of the, of the computers too, but also the softwares and what’s happening in the cloud.

    But when you look at the application park, that’s your software stack represents. It represents a budget of three million dollars. It’s a black box where you don’t know what the ROI is, and you have no clue of who has access to what at what hour and if it complains. So Corma solves that problem by being the cockpit of truth of your licenses.

    Alexis: Excellent. I love it. So [00:03:00] your boss, co founders, if I understood well, there’s a third one who is not in the room. 

    Nikolai: Yeah, it’s CTO. You know, they don’t like to talk to people too much. No, but he’s, it’s, it’s, no, that’s not true. It’s he’s called Samuel. He’s also very nice and sociable, but actually right now he’s on his well deserved honeymoon.

    So we try to leave him as much alone as possible. That’s why it’s only the two of us. 

    Héloïse: And 

    Nikolai:

    Alexis: love that you’re taking care of that and you’re, you’re paying attention to that. And that’s, that’s very cool. Okay. Your first time founders, how do you experience leadership? Nikolai, could you share your perspective?

    For me, it 

    Nikolai: was interesting because before I worked for two and a half years. in another startup and saw like some good growth there. And I always look at the founder, like whenever I didn’t know something, you obviously ask the founder and expect it’s like a bit of a wizard who knows the answer to everything and know that I I’m in this position myself.

    I know this is not necessarily true. So I see it as a challenge that you need to figure stuff [00:04:00] out that nobody did before you. Obviously you have advisors, but in the end, You are the founder or you are free founders. You can ask each other. This already, this already helps at the start. And it still is a big challenge that a lot of people rely on you.

    And obviously yourself, you might have some doubts. Of course you have your vision, but you might doubt it at some times. It’s a process as well to become a founder. Then you never did it before in your life. 

    Alexis: Okay. And Héloïse, I’d love to hear your thoughts as well. 

    Héloïse: So to be a leader in a, as, as a young founder in a startup, I think is absolutely thrilling.

    I’ve always looked at leaders by leading by example, and I hope I share a good example with what I’m doing in my day and, and how I act in my life. But I think the biggest challenge for me is communication because we have so much information in our heads. We have to communicate it in one way to our co founders.

    We have to not communicate some things as well because we don’t want to disturb them at some times of the day where we’re focused on deep work, but then you have to [00:05:00] communicate at different times. You start to communicate differently to employees, to interns and to freelancers, but also to investors, clients, prospects, and people you just meet at a random cocktail for networking events.

    Communication for me is very, very important, and it’s a challenge that I’m not ready to have completely tackled yet, for sure. I think it gets even tougher when you go. 

    Nikolai: To jump in immediately and you have the extra challenge that you are the CEO, so you’re also by role in charge of the communication with the external world.

    I mean, you mentioned investors, but like people will always look to you first. So it’s. Internal different types of communications and then the whole external world. And obviously the employees see what you say outside your investors have some insights into the company as well. So I think it’s already also interesting to balance those different types of requirements of communication where you are in the spotlight.

    Alexis: What I observed so far, you are doing really [00:06:00] great. So I would say, don’t be too worried about that. Maybe that you are doing great, but I’m glad you’re taking care of that. And you’re, you’re finding that very important. So That’s very cool. There’s always challenges in early stage startups. Can you tell me what are the typical leadership challenges you face?

    Héloïse, do 

    Héloïse: you want to take that first? Yes. The first challenge is people. Okay. And I think it’s the most important challenge of all, because a company is laughing about its team. The main challenge, for example, that one of us, we had to face was our first maternity leave. It was happened during, uh, the life of a startup.

    It was a surprise for everyone, the person included. And we’re all very happy that it’s, it’s happening. It’s going well. However, it’s of course like, no one tells you as a young founder, how to react when your employee tells you that we’re going to go on maternity leave in the next six months. And you have to react to the right words in a culture setting that’s very international and with [00:07:00] an age gap that’s quite present.

    So yeah, there’s a lot of key elements to put into context for your first reaction to this type of news, which for me was quite naturally because I think Life is a Miracle was very warm. But at the end of the day, it’s also a challenge for the whole team to make sure that everything goes well for everyone professionally.

    Alexis: I have to admit that the first time it happened to me, I believe my face showed something completely different from what I wanted to say. And I saw the person, the face of the person in front of me. And I realized that my face was telling off what we will do now. And what I wanted to say is, of course, congratulations, because that’s what you want to say.

    But I was already starting to compute what, what we will do. That’s an important person. And when I saw the face of the person in front of me. [00:08:00] I 

    Nikolai: think this can summarize many things quite up. You have like really happy moments and still lots of concerns at the same time. So you obviously, we are very happy for her, but still, we still feel the responsibility as a founder, because this person also has a leadership role, you think, okay, who will cover that?

    Okay, we also have a CTO who goes on maternity leave on his honeymoon. At the same time, you have someone who has a visa needs to travel for it. So we always have A lot of things in the back of our head that we need to consider. And just because we consider, I don’t think that makes us less humane. I would say we try to be very empathetic, but still we also need to make sure that the company survives because in the end that’s the goal here.

    So I think yeah, balancing those thoughts is quite important. And then maybe to add to your point, so I would agree people challenge at the top. For me, It is the challenge of challenges because [00:09:00] there’s always so much stuff happening at the same time and you need to prioritize stuff. And this means, which I find quite difficult is sometimes you have to say no.

    Like we, by definition, a startup has very limited resources. So people will have ideas. That might be great, but still, sometimes you have to say, no, you need to prioritize because if you do everything at once, you do nothing. And that’s quite important to set like a clear guideline for yourself, for the founding team, but also for the employees.

    Héloïse: I completely agree. Especially in a tech startup where people are like tech wizards, project geniuses, call it whatever you want, but people are very creative. They always have this cool idea to do this new research or that cool new feature. But at the end of the day, maybe it’s my stage hat, but I have me.

    For me, if it doesn’t go on the front line and there’s no impact on the revenue, it’s not a good idea. It’s not good. If I cannot see where it’s going to bring more value to the market that we’re addressing. 

    Nikolai: And sometimes it’s a bit brutal. And like, because, you know, you don’t want to be [00:10:00] the no person. And I mean, we don’t say no most of the time, but it happens.

    And it can be kind of like, because you know, you want people to have ideas because maybe the idea is actually something nobody thought about and it sparks something great. But I mean, the minimum we have to do is like really challenge it. And then, yeah, sometimes we have to be a bit tough and say, yeah, okay, cool.

    But honestly, Maybe in two years, if everything goes well and that’s not always easy. 

    Héloïse: And actually the challenge to make sure that we, uh, not just challenge that, but channel that we channel the energy of the people that joined the team by creating this a new ambassador program. That’s called the Cormacolindor.

    It’s literally, so, you know, the name Corma comes from the name, the ring, where the sass of sass, so one ring from the Lord of the Rings, basically. And, um, uh, Cormacolindor is literally an elfish. Yeah. The ring bearer, the person that bears the ring, because like Frodo, when you’re Corma, you’re a Cormacollindor in Elvish.

    So we did this program quite [00:11:00] recently with the new hires to help them step by step collaborate with each other to reach the objective key results, make sure that they do things outside of work that build up the team, uh, team spirits and make sure that individually they shine because everyone is unique.

    Everyone can not, no, They cannot be replaced, someone cannot, because you’re not here, I replace you. So it’s really a very interesting program to show that, to really leverage also and make them shine as people. Because it’s not just the challenge, it’s also the main channel of how Corma is going to do great.

    Alexis: I love it. That’s very, very interesting. So you put people first as a challenge, and I can see that you are really taking care of I’ll People contribute to the company, but also how they develop themselves, how they grow into their role and grow with each other. So that’s very cool. Are there other challenges as managing people as young founders?

    I mean, 

    Nikolai: for like an important thing, it’s people, but [00:12:00] you know, as a startup, you’re in survival mode all the time until you get I mean, technically every company is survival mode, but I would say in startups is the strongest because they are young, they didn’t prove themselves yet. They don’t have as much money as they want.

    They don’t have like their product market fit yet. That’s generating profitable revenues every month. So, so it’s really. Tough also on the, on the commercial side to manage people and data founders are obviously heavily involved as well because we have investors, we have some funding, but we need to show to get revenue to prove obviously that our product, that our idea is needed, but at the same time it also pays our bills.

    And I think balancing a little bit of this financial need to just push on the commercial expansion, but at the same time, not get lost. On it. And remember, you try to sell your product because you believe in it. And if you have more clients, you get more user [00:13:00] feedback. It’s a bit difficult to balance this sometimes the need for commercial expansion or with the internal need to understand what you actually want to bid.

    If the client asks you, okay, can you do this? You say, obviously yes. And if, if it’s. Not there at all. You say it’s on the roadmap and if you know, it’s like humanly technically impossible to do it. You say, okay, we’re going to look into it for the next quarter. But obviously this has a limit. You cannot oversell all the time and you need to take a step back then and know how to balance this.

    I would say this is also a challenge. 

    Alexis: Hmm. Very good point. So when the leadership team embodies the values and principles they want to see in the organization, then I believe the organization can scale, can grow and can become something very beautiful. Do you agree with that statement? 

    Héloïse: Yeah. Culture eats strategy for breakfast.

    So like, it’s a very basic sentence to say, but really summarizes the whole feeling that we see, not [00:14:00] just at Corma as a company that has, is very strong in the values that it upheld, but also within Station F, we see the startups that are very united. Where the people are already, the cement of the whole building, of the, basically the cathedral that they’re going to build.

    It beats any competition. It goes, it just shines quick pass. 

    Alexis: So what are you doing to create such a culture? 

    Nikolai: You mentioned it’s a lot of leadership by example. You need to lift the company values and I think it’s also something we learned. You need to actively nurture it. Like, okay, people. Probably have the tendency to copy behavior, but you need to encourage it.

    And it was something that was not always super easy because sometimes people feel the founder has their unique role and they always share direction. But you know, it’s part of our DNA that we want people to lead the way as well. So there’s sometimes you need to actively encourage fine programs. Like, for example, what you said with this ambassador program, but it can be [00:15:00] small stuff to how you give praise, how you give feedback.

    So for example, this radical Canada methodology, we follow it, tried to implement it and how we do feedback and how we do development and like personal career development. It’s an active process. It takes active management. Even if we try to. Live as the best example. I think it’s still, yeah, we still need to be active to do it.

    Héloïse: Yeah. Some examples are typically by your life on time, if not on time, like this in advance, being on time is always being late. It being present for the others. Like if someone wants to talk about something, they can pick a lunch for you very easily as a founder is something that you do. I mean, sometimes it’s a career coaching.

    Sometimes I, and we talk about other things than work, which is like, what is like next five years, you know, how, how can we, how can we get you there? It’s about creating an alumni, uh, alumni group. And the alumni also inspire the current people that are present at Cuomo. And so they are inspired together and it’s about giving them the voice to be heard so that they [00:16:00] embody this leadership position that Nikolai was just explaining now.

    It’s part of not just the Ambassador program, which is. Basically setting a more formal setting to what was happening before it’s really just a mix of how you celebrate the little wins or you close the deal. That’s really, really good. Okay. How can I help you close your deal today? Collaboration on different topics and putting everyone in the same team, like there’s not a tech team and a safety mask on my team.

    That’s just one. That’s just not possible to not talk to each other. Even if you don’t understand what JavaScript is, at some point, you’re going to have 

    Alexis: to. I love what you’re saying there. So you mentioned Radical Condor for the audience. The idea, if I summarize it, is if you care personally about people, then you can challenge them directly.

    So that’s the important part of it. If people can feel that you care about them, then you can challenge them. basically give a feedback. If you don’t feel you care about them, it’s like if you were trying to put a big truck on a rope [00:17:00] bridge. It will not really work. Your feedback will not go through. So that’s basically useless.

    Is it a good summary? I think 

    Nikolai: like the other thing is even more dangerous that because you care to, because I would say we all care deeply about the, the, the team, the humans, the people behind it, that you, because of that don’t challenge directly. I think in the concept it’s called ruinous empathy, and I think it’s a big risk that you’re trying to be too nice, too cushy.

    You know, it’s like a bit of the example after lunch, you have some food stuck in your face. You don’t want to tell the person because you don’t want to embarrass them, but imagine then they go off and spend all their day with food in their face and they would have been so much more grateful to have this.

    uncomfortable moment where you say, yes, sorry, maybe clean your mouth a little bit. There will be so much that you were created this little uncomfortable moment, but overall, because you care personally, you gave some, yeah, let’s say negative or in the sense, constructive criticism. This is better. Like, so for me, just being like toxic, not caring about [00:18:00] people giving meaning.

    Feedback. Obviously there are toxic people. I don’t think we are at risk of it. So for me, it’s more the thing to avoid the ruinous empathy and to challenge directly because we have the best intention behind it. 

    Alexis: I love it. Thank you for the example. That will make it very clear to people. They will all try to look if they don’t have anything left.

    So lastly, what advice would you like to share with our audience, especially those who are aspiring leaders or early stage founders? 

    Héloïse: That’s a good question. 

    Nikolai: I think there are a lot of answers to 

    Héloïse: it. Yeah, there’s so many. I mean, it depends on what context you’re in, but do you want to start or? 

    Nikolai: I mean, for me, there are some basic things.

    You throw yourself into the cold water. I know some people that hesitated away from leadership positions because they are scared to manage others, be it because they’re still a bit young. They’re a bit shy. You have to do it to learn it. It’s not something you learn in the textbooks. So you. First, you have to bring yourself in the position to [00:19:00] lead.

    And then the next thing is you will see, you don’t need to figure everything on your own. Find yourself some mentors, find yourself some friends. Ideally. I mean, we have us three co founders, I would say we are really, really tightly linked. Then you can like with people that have similar experiences or similar learnings.

    Try to like, once you bring yourself out there, try to exchange with people that live in the same or lived in the past in the same situation and try to learn from there what worked for them, from what doesn’t. And for me, something that I usually do, like try to follow your intuition. If you feel something doesn’t feel right, maybe, yeah, reflect if it’s good.

    And if you have a good feeling of something, you also need to have to act, like have the courage to act. Don’t be like too scared in moments, even if it might seem a bit scary. Like sometimes you have to push yourself a little. I think that’s the uncomfortable part of the leadership. Sometimes you need to do things that are not super pleasant, but you have to do it because nobody else will.

    Héloïse: I mean, I can [00:20:00] only second what Nicolas just said. One thing in addition came into my mind. So when you’re young as a founder, there’s a lot of topics. But you’re going to realize that exists first in life, like managing new employees, like having a specific type of client to manage or stuff like that. It’s called like zones of hurtful ignorance that are very difficult to not difficult to observe because they’re quite come quite fast, but very difficult to, you know, on your own, if you really isolate yourself, it’s going to be a harsh on you, on your life, on your mental health.

    To actually overcome and because you, you have like 15, uh, ignorance bits to, to master at the same time. Like, uh, it’s like, just life gets in the way. What I really would recommend to a young founder, how founder starting out is you just get your phone, build out a list of the top 50 people. And so maybe five in every category, or 10 in every category that you most admire in the world.

    in your region, in your industry, and get [00:21:00] them on the phone, book a meeting with them. It might take you a year, but at the end of the day, you’re going to make it happen. Actually, I would disagree. 

    Nikolai: It won’t take you a year. Like one thing that surprised me, how happy many leaders are actually are to share their knowledge.

    I mean, if you think of some people that we spoke, like we, I mean, yeah, it’s, We’re not out of school for that long and the amount of senior people we speak to just because we reach out because, okay, they maybe get spammed by sales people, but just people asking for like founder to founder advice. They are usually really happy to share.

    So like really go out there and try to get some advice, some mentorship. I would say it’s easier than you think. I don’t think you need a year for it, but it’s super valuable to do that. 

    Alexis: I love that. That’s really beautiful. Thank you for being here. Join the podcast today. I’m sure it will be already uploaded.

    Héloïse: Thank [00:22:00] you.

  • The Future of User Experience Is Not Artificial — It’s Human

    The Future of User Experience Is Not Artificial — It’s Human

    When we talk about the future of User Experience, the conversation often jumps straight to AI models, automation, and performance.

    But what if the real challenge isn’t prediction — but judgment?

    In this episode of Le Podcast on Emerging Leadership, I had the pleasure of discussing this question with Sebastian Cao, a UX and technology leader who has worked at Red Hat and Tesla, and who recently taught a Stanford course on the future of User Experience.

    His perspective is refreshingly clear:
    technology only creates value when it strengthens human capability.


    Prediction is easy. Judgment is human.

    Sebastian draws a crucial distinction between two forms of intelligence:

    • Prediction, where machines excel by identifying patterns in massive datasets
    • Judgment, where humans rely on experience, context, and intuition

    At Tesla, this distinction became very concrete. Machine learning models could predict likely failures based on historical data. But technicians — by touching, seeing, and sensing the vehicle — often detected signals no model could capture.

    The best systems were not fully automated.
    They were guided systems, where AI informed decisions, but humans remained accountable.


    From automation to augmentation

    One of Sebastian’s most telling stories is surprisingly simple.

    When his team was called Service Automation, frontline technicians immediately feared job loss. The name alone created resistance.

    Renaming the team Service Augmentation changed everything.

    Words matter.
    Framing matters.

    By explicitly positioning AI as a tool to amplify human skill, rather than replace it, adoption became possible. Productivity improved, trust increased, and the technology actually delivered value.


    The “ghost in the machine” problem

    Sebastian uses the metaphor of the ghost in the machine to describe what happens when AI systems behave like black boxes.

    When users don’t understand:

    • where data comes from
    • how predictions are made
    • how confident the system really is

    they stop trusting the tool — or actively work against it.

    Transparency is not a “nice to have” UX feature.
    It is the foundation of trust.

    Explaining reasoning, showing confidence levels, and making decision logic visible turns AI from something magical and frightening into something usable and credible.


    Empathy is not optional anymore

    One of the strongest messages of the episode is that empathy has become an engineering requirement.

    Designing AI-driven systems without understanding:

    • user incentives
    • fears around automation
    • real-world decision-making

    almost guarantees failure.

    Sebastian insists on something deceptively simple:
    go where users work, observe them, and learn how decisions are really made.

    No amount of code can replace that.


    Open source, ethics, and trust

    Finally, Sebastian makes a strong case for openness.

    When AI systems influence frontline decisions — impacting customers, safety, or livelihoods — leaders must be able to explain who built the model, how it was trained, and what biases may exist.

    For him, open source is not an ideology.
    It is a practical condition for trust and accountability.


    Leadership in a human-centered AI world

    Sebastian’s advice to leaders is clear:

    Understand the technology.
    But never forget the human on the other side.

    The future of User Experience will not be decided by the biggest model or the fastest deployment.
    It will be shaped by leaders who combine technical literacy, empathy, and responsibility.

    That is where Emerging Leadership truly begins.

    Here is the transcript of the episode

    Alexis: [00:00:00] Welcome to the podcast on emerging leadership. I’m your host, Alexis Monville. Today, we have a fascinating conversation with our guest, Sebastian Cao. Sebastian is a visionary leader with a wealth of experience at the intersection of technology and user experience, having held pivotal roles at Red Hat, Tesla, among others.

    He recently delivered an insightful course at Stanford on the future of user experience, where he explored critical topics like AI’s role in augmenting human capabilities. So we are thrilled to dive into these topics with him today. Sebastian, welcome to the podcast. How do you typically introduce yourself to someone you just met?

    Sebastian: Thank you Alexis.  I love to be here. I usually speak that I’m an engineer that can talk about [00:01:00] Problems that could be solved with technology. I like to talk about problems. that are worth to be solved, like real problems talking about as a species worldwide, globally, problems that we have and what are good options and good ideas to solve with technology.

    So that’s my, how I introduce myself. 

    Alexis: I love those kinds of introduction where I need to ask more questions to know a little bit more about your background and all those things. But we will go through that at some point. You did a Stanford course. about the future of user experiences, and you emphasize the balance between prediction and judgment.

    Can you tell us more about that? Because I’m very curious about that thing. 

    Sebastian: Yeah, as I mentioned, I’m an engineer, computer science engineer, but I’m certainly not the kind of guy that would go and hack and make a model, an LLM model better, or just make a little bit more incremental performance out of a model.

    I’m more [00:02:00] concerned and interested about how that model could really solve human problems. We can go into that and move into Silicon Valley, like a few years ago. And you always read about all this story and the heritage around this area. And you see all this company, but it’s still a really engineering led culture.

    So everyone right now is like competing about it’s an arms race, right? Who has the biggest, boldest, more expensive model in a way. But I was concerned and we can certainly touch into that. My experience of 2 years at Tesla about how we can solve real human everyday problems for frontline workers that.

    So, when I was discussing that we engineers that were getting coding these big models back inside Tesla, we’re always. Computers will always be better than us and doing prediction made by that we mean getting a huge amount of data historical data and see patterns things that [00:03:00] are repetitive over there and say, OK, this is with a high.

    That’s a probability, right? With a high degree of a chance, 90 percent 80%. So this will happen because data show us that happened before. And that’s great. We shouldn’t be doing that. So in the case of a car company, any company, you get all the historical repairs and you know that certain type of cars in certain weather, when driven by certain patterns, you usually break this part of this subsystem X amount of kilometers or miles or whatever.

    So that’s great. We were doing that. We predicted diagnostic to Manchell learning. What I wanted to add to the equation, because it’s the part that’s easy to forget is What about the judgment? What about the human judgment? The mechanic or technician will see the car coming, and we might see by touching it, by feeling, by looking at the car, might see that something else is off.

    Maybe there was a, I don’t know, heartbreak or there was actually a crash or something that happened before that we’re getting all [00:04:00] this data and all these signals coming from the car that might also come into play. And that’s what we humans are good at. We remember seeing that before. We made a decision back in the day that the outcome was a particular outcome, and that kind of is part of your knowledge base and your experience.

    So how we can merge both how we can merge the cold data coming from the car in this case, but leaving the opportunity for the technician to make. a judgment call. So I was pushing not for a automated kind of result, but like a guided, guided diagnosis process where the machine will provide all the probabilities looking at the car and getting all the data coming from the sensor.

    But the technician will actually use that to make their own judgment and say, yes, I will do that. Or maybe now we’ll do the other thing. So I think that is a, that’s a great concept that I’ve been talking and I’m In love right now, and I think it’s really important because we’re seeing this much development in a it’s [00:05:00] thinking about a not only as artificial intelligence, not even as artificial intelligence, but more like augmented intelligent or amplify intelligent where we make humans better, they can do more because we’re feeding them with data pre analyze data with a lot of prediction by your living room for judgment.

    Alexis: Okay, so a large place for human, but not only human, the experience they have in a particular field, and that could be any field. 

    Sebastian: In this case, we’re talking about mechanics technicians, people that do wrenches, they take wrenches, I mean, with their hands, they’re not coding, they’re not engineer, they don’t care about at all about machine learning.

    How you can give them More especially there for example compensated and then we get into compensation and kind of incentives that’s a cold economical kind of analysis and there’s a lot of research about that they were incentivized by the number of cars so why don’t we tell them a story that they [00:06:00] will be able to use him.

    Augmented. Tools or machine learning or whatever, it’s not about machine learning. They can actually go through more cars through the day, through the week. So they’re more productive. They get a better paycheck. So we’re all happy. But sometimes I feel as an industry coming from any, again, as a software engineer all my life, and we met in a software company, we tend to fail to explain that we go into, okay, this is cool.

    This is the latest, this is the latest model. LLMs, but we understand who is the customer who’s on the other side consuming that technology, how they’re incentivized and what is that they’re trying to solve. And we certainly fail at telling that story sometimes. 

    Alexis: I feel there’s something deeper that we can grasp there.

    And so AI is not a replacement for human intelligence and definitely human intelligence, their experience and how they understand the world is something important. So they could be augmented. How do you do that? Practically. 

    Sebastian: [00:07:00] That’s where I learned a lot and made a lot of mistakes doing that. And I think that’s what I’m looking at.

    What is the company or yeah, a company, a software provider actually going to crack that code. I think right now everyone is fighting about releasing the biggest model and spending a lot of billions of dollars in training, but no one is certainly there might be companies doing that. But we haven’t seen that and the headlines and the stories in the media.

    It’s all about the biggest model and the competition between the providers. No one is okay. This model, whether it’s the biggest or not, it’s actually increasing productivity for it. Frontline workers, technicians, insurance clerks, customer support operators, airlines, whatever, we’re still not seeing that because we’re failing at deploying those models along human beings, working side to side, the whole copilot idea, whatever we would like to call it.

    So when I’m seeing failings first, as an engineer, we tend to, it’s too [00:08:00] complicated. We throw a lot of technology in a lot of. Explanation and a lot of, we tend to use automation and artificial intelligence a lot. And if on the other side you have someone that doesn’t come from our industry, the first thing that comes to mind is, okay, this is automation, this is going to replace me.

    No matter your intention is the first, because it’s the human reaction to that. One of the first things that I did at Tesla’s team that I inherited when I joined was called service automation. And we were supposedly, we were tasked to, okay, let’s create more tools. For internal customers to employees, more tools for them to be become better.

    I say, okay, the first thing I want you to change is the name because every time I present myself as service automation, they say, okay, you’re coming for my job. So it was super quick and everyone say, okay, that’s cool. That’s a good idea. So we change it to service augmentation and I started sharing a lot of like research, not papers, but just.

    Headlines and professors kind of [00:09:00] analysis at both sides of the aisle, as they say here in the US, both the engineers are building the software and the consumers on the other side, the technicians say, Hey, this is what we’re trying to build. We’re trying to build something that will help you go through your day that are going to augment you.

    Augmentation is still like a 20 word. As I say here, it’s like too complicated. Maybe the amplification. But just change the name because words carry a lot of weight. Right now in the media, it’s much more interesting to publish. story about automation or AI taking out jobs than talking about AI making people better.

    Alexis: It’s very interesting how we oscillate between a 1 world and 5, 000 world, and we are mixing them in one sentence and it’s scaring everybody. 

    Sebastian: It’s a human behavior and we go from, this is going to be a great feature, to Skynet and Terminator and we’re going all like the matrix. So, and that sells. So I think it’s for people like us, like you to understand the technology, but I think you need to [00:10:00] go further and explain the technology, explain what’s going on, explain why you’re using 

    Alexis: it.

    And it’s a very good point. You need to care about the users themselves, the people who will really use the technology and go a little bit further in understanding how they work and what they are trying to achieve. And it’s not a game about feature or that’s not only that it’s really about. what they need to accomplish, even if they don’t really know what kind of feature they would need on pantyhose with users, I feel is very important.

    Absolutely. You picked an example about the ghost in the machine. And I was very curious about that because yeah, I’m probably old enough to know about that album from a police, uh, from the police, 

    Sebastian: 1981 great songs that I was doing, but I always heard, I mean, I always listened to music that is. Yeah, but yeah, I got a t shirt and I used that t shirt that’s about that album that is called the policy of ghost in the machine.

    And I used that t shirt when I went to a meeting that I want to explain the [00:11:00] concept and say, the ghost in the machine is that idea. It’s a phrase that had been going on forever. It’s just. You can also talk about the Turing test and all that. Okay. If it is a machine, if it is new enough or strange enough, and I think most people got that experience with JGPD like two years ago, you do feel that there’s something else about a program there.

    That is the ghost. There’s a soul, there’s a human touch. At the end of the day now, if you delve into it and you get into the research and you do, you understand the transformer model and all that, okay, it’s a pretty big program choosing what’s the next word to use. But at the beginning, it feels magical.

    I think that is the idea is people will tend to think, okay, this is actually sentient. This is actually thinking by itself. So with the ghost in the machine, I tell the people, if we don’t explain them what’s going on, if it is a black box, that is a concept that we also use a lot in software, you’re not explaining where’s the data coming from for you to make the decision, the prediction, where it’s coming from, who selected the data, [00:12:00] who labeled the data, and then you don’t explain how you use that data to make a decision.

    And then you explain. In simple terms, kind of the, like the confidence interval, I say, okay, we’re pretty sure up to 80 percent you don’t need to use percentage worth. I was pushing a lot for like graphical representation, easy to understand that this is a recommendation based on all this data. I think we also need to get better at that with sending all these models that you ask a question, you get a response, but there’s nothing that will explain you.

    How that response got constructed, how that response came to be, and then we get into a lot of and we all we saw that already a lot of crazy stuff on really dangerous stuff about labeling and who’s bias data and all that. So I think that is an also an important concept. We’re dealing with a frontline workers say sharing with them.

    Okay, we’re giving you this recommendation because A, B and C or D happened before in my case, I was pushing, but it was a pretty simple concept to fix [00:13:00] an issue. You’re relying on millions and millions of rows of data, lines of data coming from previous repairs. The repairs, historical repairs you have done 10 years of experience, those repairs were done by other technicians just by sharing to the technicians.

    Hey, this is actually recommending you what to do, but it’s trained in a way or based on what your peers have done in the past. It’s like this shared knowledge of all your peers that you look up to. It’s not a machine that the machine is just sorting the data and just going through that really fast.

    That was a good example of how I was pushing for the ghost in the machine. We will need to explain because they will embrace it much. There will be much more open. That is just again, a black box. They’ll say, Hey, the machine is telling you to do this. Then they will know, you know what I’m doing the other way around.

    Alexis: What I really like there, it’s not just trying to explain how the feature work, but basically showing the work that is done, explaining all the reasoning [00:14:00] that got us to the conclusion. So you need to explain a few things. You did it very well to say, okay, that’s basically the model is just trying to predict what is the right word to use after the previous one based on historical data.

    That’s probably a rough explanation, but that’s pretty cool because then, okay, I understand that this is the data, this is how it works, and I can trust. that thing. In addition to that, I have a kind of confidence level that is shown to me. I can really rely on it or I can say, ah, okay, the confidence is very low.

    There’s maybe not a lot of historical data on my current situation. You probably need to pay attention a little bit more. That’s very interesting, I 

    Sebastian: feel. It’s spot on, and you mentioned such a key word, Alexis, that is trust. And the other word that I kept on using in all my meetings with product managers and engineers is empathy, too.

    You need to increase the empathy for them to say, Hey, this is actually helping me. And [00:15:00] I’m actually rooting for the software, rooting for this solution because it becomes better, the solution becomes better or machine learning, whatever the AI becomes better, I become better. We’re all peers. We’re all partners.

    If I think you’re trying to replace me, then I will do all my best to actually hijack and just kill your project. 

    Alexis: You have quite a fascinating career trajectory funding companies in Latin America, working with RADAT in Latin America and in the U. S., working in the Silicon Valley for Tesla. How do you see the role of technology in customer experience?

    in the future. And how have you seen that evolve? And how do you see that for the, in the future? 

    Sebastian: That’s a good question. You know, Alex, one thing that I keep repeating myself, just not to forget, and I keep telling friends that I have in Latin America, they go, okay, Tesla, Silicon Valley is great. And you can relate to that being in France is at the end of the [00:16:00] day here, you will see probably bigger, Ammunition, bigger weapons, or bigger things that they’re building for a global scale, we’re solving the same kind of problems.

    Cultural change, resistance to change, human behavior is the same in Silicon Valley, in Paris or France, in Buenos Aires, in Argentina, in Brazil, or in Africa. This problem of, let’s say, for Tesla, but if you’re throwing a fully automation machine learning, whatever, diagnostic to a technician. In Tesla and Silicon Valley, without explanation, they will resist to it.

    You do that in France, they will resist to it. Also, you do that in Turkey, they will resist to it. And the same in Latin America. That’s again, that was an insight that was a realization for me. I finally understood that, okay, I’m here because you get exposed to global scale of solving problems. You probably have bigger resources and tools to solve that problem.

    But at the end of the day, the problem that you’re solving is still a human problem that is the same, no [00:17:00] matter what language you speak or the color of your skin or whatever, to be honest, this is amazing because even with everything that we’re discussing about AI and all that, at the end of the day, human beings at the core, we are still the same and we fear the same things and we need the same kind of help.

    So that’s probably what I think it’s the biggest. Outcome of my journey so far, but yeah, as I mentioned here in Silicon Valley, you see that we go really fast and sometimes too fast. So I like being here and seeing everything that’s going on with AI and everything that we’re thinking about building at the same time.

    I’m super interested in how we are going to build all of that with a good adoption and with empathy. So this is a great 

    Alexis: place to try all of that. So that’s the right balance of technology and human touch. That’s the empathy that you build with the users and to foster the adoption of technology or foster the idea of innovation itself.

    Sebastian: I read as many psychology books as [00:18:00] Coding or AI machine learning algorithm books. I think we need both, especially with AI right now. Any, any you on your, what you’re working on your consultancy and we need people that talk technical because you’re going to be exposed to technical discussion or code or a solution or diagram.

    Okay. This is what we’re building, but I think we need more people that can understand, okay, we build this and we ship this product. This is going to happen. And if you don’t know, at least you’re going to, Catching a bus or a taxi and you go there with your user and you sit with them, you sit with them and see them in action.

    In my case, it was going to the Places where they were actually branching car and working with them. You have to work with them, understand what they’re doing. So if you’re just shipping code, pushing code into production without ever talking and touching and feeling your customers, it’s going to be hard.

    Alexis: I had a, I had a conversation with a really high performing team. I was looking at what they were doing every week to have a sense of what they are, the [00:19:00] things that were important to them. I noticed that. All the team members had user, real users, interviews every week. Not all of them. Every week there was a contact with a user.

    at least one. And that was different people on the team. And they had a user interview guide that was constantly evolving because they were testing their assumption with different users. And I was looking at it and say, Oh, okay. So probably a successful team needs to be in contact in touch with their users at least weekly that showed up in their work.

    Of course, 

    Sebastian: I agree with you. I think they’re really successful like B2C consumer companies. The product management team had been doing the, they know that, and they’ve been doing for AI, we’re trying to hopefully not replace, but augment decision. It’s even more that you need to be there and understand how that person is making decisions.

    If [00:20:00] you trying to build something. That person was going to use on their day to day. Now you end up with Clippy from office in the 90s. They’ll say, Hey, what do you need to do? Do you need to print? Hopefully we’ll become better than that. 

    Alexis: Yeah. That’s the first question everybody asked was how to turn off that thing.

    Absolutely. Finally, as a leader who worked in different high tech environments, what advice would you give to a new leader who want to effectively evolve in that world? 

    Sebastian: Advice. Okay. For leaders, I would say maybe what we’ve been discussing, it’s, I think today you need to have exposure to the technical part of things, understand everything that is going on, how it’s been created, why it’s been created and by who, and there’s a lot of, we know.

    Political things at stake and companies competing against each other. So you need to understand them. We probably need another podcast to discuss open source versus closed source for [00:21:00] things like AI and all that. But you need to understand where everything is coming from. But those again, those are tools in your tool belt.

    What I would like leaders. I think it’s very important. We’ve been discussing, understand, be empathetic, understand who’s on the other side. Who’s your customer? Who’s consuming that? It’s a B2C, it’s a B2B. Are your users experienced with AI or whatever technology you’re using, or they are not? Do they trust it or not?

    And if not, and if you’d make those questions and you get answers, work with those answers, I think one thing that I see a lot here is, again, we are shipping code without asking any questions and we think that code is the best and that option will follow. And I think we need a little more human touch on that.

    So that will be my recommendation for leaders. Again, human touch and empathy. 

    Alexis: Excellent. Oh, I cannot resist. People will not see that on video. I can see it on your wrist. You have an interesting message. Tell me more about that. 

    Sebastian: All right. Yeah, I am. I just I was it was lying around. [00:22:00] This is a wristband that I got from one of my favorite places in the U.

    S. That is the Air and Space Museum in Washington, D. C. That you have all these. Historical planes and the Apollo mission, all that. And this is a wristband that says failure is not an option. And there was a wristband that was created for the Apollo team before sending someone to the moon. And then you see how much was achieved in collaboration between private and public sector, different political views and all that, how much was achieved in like six years, that’s amazing.

    Alexis: I like the story, I like the message and at the same time you mentioned open source a second ago, so don’t we say fail often, fail fast or something like that? 

    Sebastian: Oh, you got me there. Okay, we have another hour and a half to keep the discussion. I don’t like the idea of with AI and everything that’s going on that fail often, fail fast.

    I mean, just releasing whatever it is because now this is something that is talking at you and many people are making decisions based on the responses that [00:23:00] they got, the answers that they have. So if it’s not curated, if it’s biased, a lot of things can go wrong. And we have seen examples. So I think for the ethos of just move fast and break things, I’ve never liked that much.

    And especially here right now with AI. And the other part that you asked me, we share that background together is I think there’s need to be a much more open source involved. And again, ghosting the machine and the black box. If that model is answering me questions, I want to understand who built the model and who made those initial training, initial answers.

    And that’s what I love. What a lot of companies are doing in France are taking the more human approach and they’re mostly based in open source. If we go and this is a personal opinion, so I don’t know, I don’t care about all the comments that we may have. This is handled by one big corporation with all the data and it’s closed.

    We have seen that before, and it’s never a good story. So I will push for [00:24:00] maybe we have seen you and I were competing against other companies. Maybe you have your closed source. That’s good. And you have your open source of that is good enough to and it kind of the similar. It’s your choice, but at least you have an open source choice.

    I wouldn’t trust my frontline workers to make decisions that will affect customers based on a model that I don’t know exactly how it was built. Personal opinion, 120%. 

    Alexis: Totally agree. And that we are back to the trust aspect and transparency is the foundation to build trust. So I love that. I’m happy that I asked the question about failure.

    Thank you for joining the podcast, Sebastian. Thank Alex. You have been great. Let’s do this. 

    Sebastian: Once again, in the future, okay? Pleasure. Take 

    care.

  • Career Conversations Are Not a Retention Trick — They’re a Leadership Responsibility

    Career Conversations Are Not a Retention Trick — They’re a Leadership Responsibility

    Many managers hesitate to talk about careers with their team members.

    Two objections come up again and again:

    • “People don’t really know what they want. Why would I open that conversation?”
    • “If I help them think about their long-term future, won’t I just help them leave?”

    In this episode of Le Podcast on Emerging Leadership, I discussed these questions with Russ Laraway — former leader at Google and Twitter, co-founder and former COO of Candor Inc., and author of When They Win, You Win.

    What emerged from our conversation is both simple and counterintuitive:
    career conversations, when done seriously, increase commitment rather than reduce it.


    People usually know more than we think

    One of the most persistent myths in management is that people have no idea what they want to become.

    Russ’s experience — working with thousands of leaders and teams — shows the opposite. Most people do have a sense of direction. What they often lack is a safe space and a skilled manager to help articulate it.

    When managers invest time and attention in these conversations, people don’t suddenly become disloyal. They become clearer.


    Retention at all costs is a losing strategy

    Russ shared a strong conviction, shaped by both experience and data:
    retention at all costs puts the company first — not the human.

    He tells stories of sitting down with team members to evaluate external offers together. Sometimes the right decision is to stay. Sometimes it is to leave. What matters is that the decision is aligned with the person’s long-term vision.

    Ironically, managers who behave this way tend to retain people longer. Trust grows when people feel their manager is genuinely invested in their future — not just their output.


    Career conversations reduce the “grass is greener” effect

    Many people leave not because their current role is bad, but because they believe the next one will magically be better.

    Career conversations change that dynamic.

    By working with a long-term vision and a concrete career action plan, managers can often make small but meaningful adjustments in the current role: exposure to budgeting, collaboration with another function, or responsibilities aligned with future aspirations.

    Suddenly, the present becomes a place to grow — not something to escape.


    Leadership behaviors can be measured — and that matters

    One of the most powerful aspects of Russ’s work comes from his time at Candor Inc. and later at Qualtrics.

    There, leadership was treated as an independent variable:
    direction, coaching, and career behaviors were measured directly by employees and correlated with engagement and business outcomes.

    This rigor matters because many organizations suffer from leadership overload:
    too many frameworks, too little coherence, and no clear connection between selection, training, assessment, and coaching.

    When managers don’t know what truly matters, they guess. And guessing is expensive.


    Investing in people is demanding — and that’s why it works

    Real career conversations take time.
    They require effort, listening, and humility.

    They force managers to see people not as resources to retain, but as humans to support.

    And that is precisely why they work.

    When people feel genuinely invested in, they take more responsibility, stay engaged longer, and deliver more meaningful impact — not because they are controlled, but because they are trusted.

    That, ultimately, is what Emerging Leadership looks like in practice.

    References:

    Russ’s insights provide a fresh perspective on leadership, emphasizing the importance of measurable behaviors, meaningful career conversations, and prioritization. Tune in to the full episode of Le Podcast on Emerging Leadership to explore these concepts and learn how to implement them in your organization.

    Here is the transcript:

    Alexis: Welcome to Le Podcast on Emerging Leadership. I’m your host, Alexis Monville. In today’s episode, we are honored to have Russ Laraway, an accomplished leader with 30 years of operational experience. Russ has held significant roles, from being a company commander in the Marine Corps to managing positions at Google and Twitter. He co-founded Candor, Inc. with best-selling author Kim Scott, and has served as Chief People Officer at Qualtrics. Russ is also the author of the insightful book “When They Win, You Win: Being a Great Manager Is Simpler Than You Think.”

    Welcome to “Le Podcast on Emerging Leadership,” Russ! How do you typically introduce yourself to someone you’ve just met?

    Russ: Yeah, that’s a wild question. I just say my name at this point. I don’t really say anything else. And I, and I have some reasons for that. I [00:01:00] think, Alexis, what you’ll gather from me over the next several minutes together is I’m a very intentional human being in, Ways that I think are perhaps uncommon and might seem a little bit nutty to people.

    This is one such example I realized that what’s common Is that we often introduce ourselves and we sort of lead with our really our professional identity our title and company or whatever And that’s not even probably in my top five identities. I’m a dad, I’m a husband, I’m a friend.

    And so I started to just become really conscious about that. Additionally, I kind of have to say that as my career has transpired, I’ve had some really, really good jobs that are, I don’t know, I think you might say objectively one might say.

    They’re kind of impressive. Then I get into this problem where, gosh, I don’t want to sound like I’m bragging ever either. And so I really started to sort of subordinate [00:02:00] the professional identity in introing myself and just kind of wait. And if someone wants to talk about what do you do, I’m happy to, happy to talk about that.

    Alexis: And what happens when you do that?

    Russ: We have this house here in Utah in the United States. And it’s a very unusual house. It’s really neat, but it’s unusual. And when we show people the house and take them through, because. You know, some of the features and because of the size, it’s very common.

    People, people think they’re being slick, but this has happened now like a hundred times, somebody will say, so what do you do? Because they’re looking at this house and they’re like, how the heck, you know, that kind of thing. And it’s funny, the first couple of times I realized, well, I finally, it took me a minute.

    I’m a little slow sometimes to realize what people were, they were trying to triangulate. Like some version of how can you afford this? Right. So then that makes me even want to sort of subordinate the professional identity even more. And then I just generally will say I’ve been, I’ve been an executive in tech. So that’s kind of what I’ll say. Because that [00:03:00] is really, I know what they’re really asking and that helps explain, you know, this house. So I don’t know. It’s a really wild question. I’ve been very intentional about it over the last several years where. I’ll just let someone else, if they want to peel that onion and they want to find out what I’ve really done and ask questions out of genuine curiosity, I’ll go there with them.

    But generally I just say my name and let other people kind of take the lead and see where our introductions take us. I don’t know. What do you, what do you think about that?

    Alexis: That really resonates with me. For years, I introduced myself to anybody, regardless of the context, by stating what I was doing for a living. Sometimes, people were impressed, and sometimes not, but it always led the conversation to professional stuff.

    While I would have loved to discuss something else. I am an avid book reader of fiction and non-fiction. I would love to hear about that or anything you are interested in, and necessarily what you are doing for a living.

    In short, it really resonates with me!

    Russ: Well, glad to hear that. It’s also it’s been frankly a mouthful the past few years. You know, I’m, I go from chief people officer at Qualtrics to chief people officer at Goodwater. By the way, wrote a book sort of in between those two. So I’m an author. Then switched over to operating partner at Goodwater.

    So that’s kind of two titles in a little over two years and author and chief people officer of culture. And by the way, now I’m, I’m actually with some buddies. I’m writing a screenplay.

    Alexis: Oh 

    Russ: and, and so, you know, you just, it’s just tough to, it’s tough to fit it all, you know, say, say my name and see where it goes.

     I’m way more proud of, my sons and my marriage and my,, that I’m a good friend to people, I’m just way more proud of those things than anything else. So yeah, cool. Fun question. Great question. I’ve done a bunch of podcasts, I think, as you know, and that is the first time I’ve been asked that question and that’s really fun.

    Alexis: I love it! My friend Michael Doyle, who is a great coach and a great communicator and also the co-author of my second book, wrote that question for me. I love that you liked it!
    Your book, “When They Win, You Win,” proposes that being a great manager is simpler than one might think. Can you tell us more?

    Russ: Yeah. Why I wrote the book, maybe I’ll start with why I wrote the book. It’s a really simple idea. I believe people deserve to be led well. You know, stop, you know, sort of that’s that idea itself is, can be unpacked for months, but the problem that I have seen and measured, by the way, is that actually people are not being led well and this is kind of hard to believe, in fact, measurably managers have not improved in 30 years.

    This is like, you start to combine stuff from Gallup and some other like Qualtrics, other employee experience [00:06:00] companies, and you start to see a pattern that managers are really flailing in the world big time. I have a lot of rigor behind these statements, mathematical rigor behind these statements, as you know, in the intro and part one of the book. And then I thought, well, gee, how can that be? How can we be standing here? Employee engagement is a measurement that’s been around for 30 years. It comes from the field of IO psychology. And it is explained, by the tune of like 70 percent of employee engagement is explained by manager quality.

    And employee engagement itself predicts business results. And so you’ve got this really interesting relationship, manager quality, employee engagement, business results, and engagement has not improved in 30 years. Managers have not improved in 30 years. How can that be when I can’t walk 10 steps outside without tripping over another book or podcast or article in HBR about how to be a better leader?

    Like, How, how, could it possibly [00:07:00] be the case managers aren’t getting better when there’s a pile of content that’s taller than Mount Everest out there trying to help them be better. So I dug in on, on that and I had this realization. I learned this in my time at Radical Candor this probably my biggest insight I have from my time with Kim there, which I think might be on our agenda to talk about a little later.

    So I can come back to that, but I had this realization that One of the reasons managers are failing is because all this content out there, including their training programs in their company, there’s too much stuff. That’s number number one problem is too much. We’re asking managers to pay attention to too many things.

    It does not hang together, so there’s not a common system. Let’s say that is pervasive. There’s a lot of like, well, what worked for me, the problem with that is the person you’re learning from isn’t necessarily conscious of exactly why that worked. What was their business context? What was the team context?

    What were their executive relationships? Like, what are the things that [00:08:00] contributed to you having success with that leadership advice you’re giving? By the way, worse, the manager who’s receiving the advice is extremely biased in what they choose to opt into or not. They grab for the things that sound familiar, the things there may be even already good at things that sound perhaps easier.

    So there’s too much stuff. It doesn’t hang together. And worst of all, none of it is held to measurable account, like whatever leadership, you know, prescription you’re offering. What’s your proof that it’s worth paying attention to? There isn’t any out there. So I said, you know, there’s no wonder people aren’t being led well, systematically or the managers have not improved.

    And by the way, like you’ve heard the cliches, people don’t leave bad jobs. They leave bad managers. Like I’m not exactly saying the most controversial idea in the planet. I just was, I was just like, how is it possible? They haven’t actually improved. That seems impossible. Well, that’s how too much stuff doesn’t hang together.

    held a measurable account. And so I realized, Oh, you know, the world does not need another person’s opinion about what it [00:09:00] takes to be a great manager. What we need is to measure, measure a set of leadership behaviors, small in number, ideally, that measurably and predictably lead to more engaged employees and better business outcome.

    And so my really talented team of quants at Qualtrics and I set about running that. Experiment, you know, we were lucky Qualtrics has an employee experience platform that, you know, it was very natural for us to measure a number of these aspects of the employee experience. And all it took was some cleverness from our people analytics team to mix these things together in a giant stats package with things like ratings and quota attainment and contract renewal rate and in engineering, like lines of code checked in, like any measurement you could find that would indicate business performance.

    We could measure the frequency with which managers were showing these behaviors. And of course we could measure employee engagement. And by the way, several other aspects of the employee experience. And so we were able to tease out about a dozen or so. Leadership behaviors that predicted [00:10:00] engaged employees and better business outcomes.

    That’s extraordinary. That’s never existed before. That’s the book I wrote and why I wrote it in the books organized by the way, direction, coaching, career. Those are the three buckets, let’s say. Of behaviors direction is a set of behaviors, set of behaviors, their coaching, set of behaviors, career, set of behaviors.

    So that’s kind of why I wrote it. That’s the impact we’re hoping to have is let’s demystify this. Let’s take out a bunch of the bias. And let’s focus on a really small number of behaviors that actually work that matter. And, and by the way, in almost any context that these behaviors work.

    Alexis: So you are telling us that the leadership behaviors you organized into the three buckets, direction, coaching, and career, are direct predictors of employee engagement and business performance. I have to admit, I’m a big fan of your career conversation approach, and I’ve used it more than a hundred times in coaching or mentoring session.

    Could you explain this concept to our audience and share why it’s so [00:11:00] effective in managing and developing teams? 

    Russ: Yeah, yeah, absolutely. So part four of the book career this is something very original in the book. A model that I’ve invented over, got to be coming up on 20 years now, invented and refined. It’s called career conversations. And it’s three distinct conversations.

    The first conversation is called the life story conversation, which is really about having people tell you their life story and then really taking the time to understand their pivots. Even at young ages, by the way, the pivots they’ve made and why they’ve made them. And through that process you learn sort of what people deeply value in their work.

    It’s fascinating. And it’s important, I think, to do it just that way, rather than just to ask them what they value, because I think people accidentally frequently lie. They don’t mean to but they’re not actually generally conscious of what they value. But when you start, when you have them tell you their life story, And you help them probe the pivots that they’ve made.

    You learn actually sort of a show don’t tell [00:12:00] version of learning what they value. So that’s the first conversation. And that really helps me understand things that in the, that are subsequent in the subsequent two conversations, things we should do, things we shouldn’t do, because we know what this person values.

    The second conversation, which is the most important by far, is helping to get to what I call a career vision statement, which is basically like, what’s your dream job? What do you want to be when you grow up? And a lot of people, by the way, have skepticism that this is feasible for our young Gen Z employees or whatever, you know, like, People our age will say things like, I don’t even know what I want to be when I grow up.

    I’m just going to tell you like, and I give a really strong prescription in the book for how to do this well, because it’s, it’s not, most people are kind of come into the room convinced they’re not sure. But you can facilitate them into the vision, and I teach how to do that in the book. I won’t get into it here.

    It takes a little, a minute. And I’ll say for myself, I’ve done, I’ve done this a thousand times [00:13:00] and I have successfully facilitated every single one of those people into a, into a working vision statement. The reason this is so important is because it puts someone’s development into the context of what they want to be.

    And by the way, those vision statements will generally be, and should be outside the four walls of this company. And this is one of the first powerful ideas is I have just acknowledged that you are a human being with a life well beyond. What we’re doing here in this office right now. And I’m interested in that.

    And I think it’s my job to participate in your growth and development toward that. But perhaps more important is, you know, you know, question I’ve been asked Alexis a million times is should I get an MBA?

    I’m like, man, I don’t know. What do you want to be? What do you, like, if you want to be the CFO at Disney as your, one of your, your career visions, then yeah, you better get one and you better get it from like three places, you know, that kind of thing.

    But if you want to be a you know, if you ultimately want to write a screenplay. No, don’t do not go get an MBA. It won’t help you at all. The people who finance movies, I think [00:14:00] oftentimes wouldn’t recognize. A good financial discipline if it fell out of the sky and hit him on the head. And then last is the last conversation is really about the career action plan, which is now that we know what you want to be when you grow up conversation to now that we know what you deeply value, let’s put together a short term plan that helps you take tangible steps toward the longterm vision right now.

    Let’s take some steps right now. You want CFO at Disney. Clearly I cannot make that happen, but I can help you think about ways to that you can take small steps in that direction and that creation plans it’s four parts. There’s four discrete aspects will follow we’ll set up action items who will do what by when that’s how you know, you have a, a good action item.

    And so and now this employee and I are both actively working on their long term career vision, what they want to be when they grow up together while they’re reporting to me, it doesn’t mean. We don’t focus on the day to day work that has to get done. It doesn’t mean any of that. And, you know, it’s funny, one of the most [00:15:00] common push, I get to two sources of pushback most often.

    One is people don’t know what they want to be when they grow up. So why would I bother with this? That’s. I’m telling you, they do. You just have to make it safe and skillfully facilitate that conversation. And the second is, wait a minute. Why on this company’s dime, should I be helping a person think about their longterm?

    Am I not just lose, am I just greasing the skids for them to leave? And what’s fascinating about this model, and I give retentive. People tend to stay with a manager who invests in them like this for longer for a number of reasons. One is they’re saying, well, this is unusual. I’ve never had a manager invest in me this way.

    I think I’ll hang out here for a bit. The other is like a lot of people leave a current job because they have this grass is greener problem. They think the next job is better. And what you learn. Is that you can potentially make small [00:16:00] adjustments to your job right now in your career action plan. The first thing we do is evaluate what can we change in your current role, given your longterm vision.

    So for example, if you want to be the CFO at Disney, I can have you run my team’s budget. Now that might seem a little silly or trite. But, you work with FP& A now, and you see, you start to see from the inside, what does the CFO’s organization look like, right? It’s, it’s actually powerful. So now you’re not necessarily as inclined to say the grass is greener because we make small adjustments that are in my, as your manager, within my power to make.

    We can make small changes to your current role. We can chart a next job for you. That’s maybe on my team or maybe on another team inside this company that makes sense, given your long term vision. Right. We bring to bear and people in our networks that can help inform and influence these decisions you need to make.

    That’s a part of the career action plan. So it’s robust and it really helps a person feel invested in, in a very unique way. And [00:17:00] so counter intuitively. Whereas it feels like you’re greasing the skids for somebody to go sliding out the door. The reality is they tend to stay longer when the manager goes through the full career action plan model with them.

     At the end of the day, I think a person that you’re working with on this feels invested in uniquely and in a way that contemplates their humanity. Not just their sort of economic value to this company. And that’s, that just doesn’t happen. I don’t care. You know, it’s hard to pull off actually, as a manager, it’s hard to find those moments to invest in a person like that.

    Given the core nature of our job is manager directs employee, Employer, you know, so I think that’s why it’s so powerful. I think that’s maybe, I mean, you could tell me you’re the one who says you love it. You could tell me why you think it’s powerful, but I, but I feel like maybe those are a couple of the reasons.

    Would you, would you add or subtract anything

    Alexis: That’s exactly what I believe. When we truly invest in people, and I’m truly that, like you say, I’m truly investing in you, we [00:18:00] take the time to make it work. And it’s a lot of effort. It sounds very simple. Yeah, there are three big conversations, but please don’t believe you will be done in half an hour.

    It’s, it’s not true. That requires a lot more work, a little bit from you and a lot from the other person, by the way. That’s very powerful. And I had people targeted by recruiters outside of the companies. And sometimes you have people who are leaving or taking a new job in another company and you realize that, yeah, you basically were not there at the right time.

    And when they are back in your company two years later, okay that means they should have stayed maybe, or probably they were not taken care of at that moment. That was a big mistake. And what I realized is once you have those conversations, they listen to the recruiter or even not listen to the recruiter, because those arguments don’t resonate with them because they have their development plan.

    They have their action plan. Those things don’t fit their action plan. They don’t care. [00:19:00] They have a plan. They are working towards it. And that’s very cool.

    Russ: That’s right. Yeah. A woman who worked for me at Twitter named Anne I had gone through the career conversations model with her and I knew what her vision was. And she had come to me one day with an external offer. This is exactly what you’re describing. And we sat down and we evaluated the offer together.

    And we’ve reached the conclusion together that this wasn’t it. This isn’t the right move for you. I appreciate that. Maybe there’s a couple of things that might be missing here for you now. I get it. We’ll change. What would I change? We can, there’s things we can’t change. She was an all star, you know, she was going places and she has gone places, she’s the CEO now of Gretchen Rubin media.

    Like she’s, she’s an all star. I’ve heard of Gretchen Rubin. And what’s, what’s interesting about that is given her. Long term vision , we were able to say objectively wrong step. Nine months later, she came in with another offer. And I was like, yo, you got to take this one.

    And I, you know, so retention at [00:20:00] all costs is a bad practice. It’s not, it doesn’t put the human first. It puts the company first. And people feel that I had, I had a manager one time who. She talked me into staying at Google. I had a pretty good offer to leave my manager. She talked me into staying. I highly regarded this manager and the company that I was going to join ended up getting bought by Google would have been not only a huge payday.

    I would ended up back at Google in a, in a good role, you know, and After it happened, I actually, when the announcement happened that we were buying this company, I happened to be in the air traveling to Asia Pacific, and I landed and I saw this news and it was, I dunno, it was a little bit of a gut punch, you know?

    Because yeah, I was still trying to make a, a career here and I care about my financial outcomes like anybody. And when I got back to the states, she, our one-on-one, all she did was apologize because, she just tried to keep me on her team. She wasn’t really thinking about what was best for me.

    I forgave [00:21:00] her, you know, in fact, that person’s Kim Scott, actually, who wrote Radical Candor, like, I forgave her so much, I’ve worked with her again, and this is what makes her amazing, she probably lost a lot of sleep that weekend, waiting for me to come in Monday, to put that one on one on the first calendar, first thing in the morning, so she could apologize, so I know what it feels like, when someone engages in retention at all costs and it feels bad, like don’t do it, you know, and it put our relationship in jeopardy for a minute.

     I don’t have a better relationship maybe anywhere in my work life. And she’s a friend, but you know, retention, all costs of losing strategy. So with, with Ann, we hung on to her because things she was thinking about, like you said, it was the wrong thing when the right thing came, I was like, Hey, Like Sting says, you know, if you love someone, set them free.

    And so we did, we set her free and she’s had this, she became a CMO. She became a COO after that. And now she’s a CEO she’s so good. And she’s earned all of this. But we were able to help make sure she took the right next step given her vision.

    Alexis: I love the All Stars story, but I definitely love the story of [00:22:00] retention at All Costs. I was about to interrupt you to mention that the manager was very good at realizing that they made a mistake and needed to apologize. And then you mentioned Kim Scott, the author of Radical Candor.

    I love that book and I did an episode about the four quadrants of Radical Candor. Co founding Candor Inc with Kim Scott must have been a remarkable experience. What key insights did you gain from that venture? 

    Russ: Yeah, I don’t mean to make everything about my book, but by a, by a mile, the theory for my book came from my time at Candor Inc. So let me explain that. So Kim and I co founded the company and, and basically I took on all of our go to market activities. We had a ton of demand for just what can you do for us with radical candor?

    You know, like we had so much demand. The job was really about keeping out things that would waste our time. On the phone, I talked to like, I’m not even, this is not an exaggeration, a thousand [00:23:00] companies. 

    As the chief operating officer, and, you know, basically that meant I managed our marketing person, Elise, who was amazing. And I handled all of the, all of the market based calls. I was selling our stuff, you know, workshops or talks and stuff like that. And so I would get on the phone and I would always start with a simple discovery question.

    It was either or both, what problem are you trying to solve? And, or how do you think we can be helpful? And honestly, I’m just trying to get off the phone as quickly as possible if we can’t be helpful. If they want something we don’t do, you know? And so what I heard though, from a thousand companies was.

    An alarmingly similar answer that I’ll summarize almost nobody said these exact words, but everybody said this exact idea, which was, we have an engagement problem related to low manager skill. Now, one group did say that specifically. And I [00:24:00] said, that’s the headline that everyone’s been telling me anyway.

    So, so, and what they were looking for from us was some radical candor coaching stuff. That’s what they wanted, you know, cause radical candor. You know, direction, coaching, career, coaching is really, Radical Candor is really about improvement coaching more than anything else, right? Chapter 8, I think, of my book. And so, when people would say to me, we have an engagement problem related to low manager skill, I asked, To further clarify, if we were a fit for them, I asked, what’s the nature of your manager’s skill gap?

    Alexis: Hmm.

    Russ: And so they, they said a lot of things, but you know, you’ve seen a word cloud before.

    So imagine a word cloud of all the words they said to me, but three jumped out in the center of the page, three words. Direction, coaching and career. And so that those are part two, part three and part four of my book. [00:25:00] Now that wasn’t sufficient. That was not real research. It was, you know, it was a back of the napkin research, but I took that research and I created a theory that we took, I took to Qualtrics and we measured.

    Whether those were the right groupings or whether those were the most pervasive groupings. And I think that’s important because one of the questions I get asked a lot about this leadership prescription is, is that just for tech? Well, no, our customers at radical candor came from every industry, including by the way, government, including education, including finance, consulting, you name it.

    I mean, I talked to every kind of company on the planet, big, small, it didn’t matter. And they all had the same exact problem with their managers. That’s a, that’s shocking to me. I mean, I couldn’t believe it. Like it didn’t, it’s almost when I tell the story, I bet listeners are like, boy, that sounds lucky.

    But we, so then anyway, we took that theory and we tested it, tested it over four years, rigorously, measurably. And that’s how we just, we learned that these direction coaching and [00:26:00] career, they break down into about a dozen or so behaviors that when managers regularly practice them as measured. By their employees saying that they regularly demonstrate those behaviors, we saw that then employees became more engaged and delivered better business outcomes.

    And so by a mile. The most important thing I learned is, Oh, everybody still has the same problems. Nobody who’s out there running their jib about or, you know, yapping about what leaders should be doing. No one’s listened to one customer on the planet because otherwise it’s the answer is so obvious.

    And then I was able to kind of take that and study that very rigorously over four years. And learn that, Oh my gosh, these behaviors strongly, the marketplace was correct, these behaviors do strongly correlate with happier employees and better business results.

    Alexis: Yeah, that’s very impressive. Reading about your experience, measuring precisely the impact of leadership behaviors in the book convinced me [00:27:00] to try the approach you outlined. By the way, thank you for the tools that are available online. That’s very convenient, very cool, and thank you for that. I should put a link to those.

    I can see that And there were some things that I was doing and others that I was absolutely not doing. For example, I was not doing the live conversation. I was trying to get people to tell me about their values, but I was not doing that by listening to their stories. 

    And that suddenly changed everything because, first, I needed to pay a lot of attention and do a lot of work to really try to extract that.

    And, uh, and the first time it was very difficult. I learned to discover people that I, thought I knew, and I did not. 

    Russ: I knew almost nothing about what they really care about. I thought, and I think the super human, I’m like a human leader. I, I try to know my people. I ask about what they do on weekends. I ask about their families. I ask about their health. You know, I, I do these activities that [00:28:00] we’ve been.

    Incorrectly taught help us know someone and we don’t know him in a way that really is helps us to help, to help them grow in a, in a relevant way. It’s the big insight. Yeah, for sure. Yeah. You know, by the way, I just, I’ll say if I did, if I had to offer one criticism of the book, one thing I noticed is you’re probably an anomaly.

    In that you’ve clearly read the book quite carefully. That’s just not common. And I’m not just for my book. I could tell I’d go do a radical candor talk back in the day. This is one of the most popular business books in the last decade. Right. And I would ask people who read the book and, you know, every hand would go up and then, then I’d get to Q and a, and based on the Q and a, I could tell.

    That I’d been lied to because if you’d really read the book carefully, you wouldn’t have been asking the question you just asked me. Right. Same’s true of my book. And so the criticism that I have is I have noticed [00:29:00] that with a lot of people listening, not maybe carefully, let’s say you’re listening on two X speed and you’re, that’s during your commute or two X speed while you’re gardening, you know, let’s just say like that. What has happened is a lot of people have missed part one that talks about the rigor of the model. You know, it’s important to me to give the why, and part one gives the why. Most people that have the books, the book, it’s 4. 0, you know, it’s highly rated book. I’m not, but like people tend to be very appreciative of the how and what of parts two, three, and four, and they skip, they skip the the why.

    And what’s, what’s extraordinary about that is that’s what, that’s what I actually invented that in career conversations in part four is fully, but the rest of it is a little bit kind of just cobbled together behaviors that help to bring the wider life and the actual invention. Is leadership as an independent variable statistically in a regression model, like the math of this leadership’s an independent [00:30:00] variable with engagement.

    And business results as dependent variables. Nobody has ever done that before. Like it’s not that I’d like even want credit or something for it. It’s just like the reason you should pay attention to this book is because it’s the only book that has bothered to try to measure how leadership behaviors produce what we want.

    Happier employees that stick around when they should and better business outcomes, which is all point. We’re all in the job to do, you know? So anyway, just a little, little bit on that, that I’ve noticed now a couple of years out regularly gets missed. Even, even among very intellectual types who I, you know, I thought, boy, boy, the intellectual types I know from Silicon Valley are going to love this.

    You know, a lot of people miss it. A lot of people miss it because they’re not really reading it carefully. So I wish I wrote it a little better. To make that idea more obvious or make it more accessible for people with contemplating that people don’t read books very carefully. Very often. Does that make [00:31:00] sense?

    Alexis: Yeah, it is very funny. If you ask people what they need, they need results. And for a lot of them, they understood that people engagement, employee engagement is linked to results. I usually describe this with impact and satisfaction. You cannot have one without the other, at least sustainably. And they have some common sense or street wisdom about how the manager role is important and related to employee engagement.

    But when asked what they are doing about that, they tell you about incentives, without any proof that it’s working. 

    Russ: Always. Yeah. Yeah. And then on top of that, you know, what leadership approach we follow suffers badly from like chief executive officer flavor of the month. I went to this thing with other CEOs and they were talking about, you know, I don’t know, situational leadership. And so now that’s what we’re doing.

    And what ends up happening is then the people who do leadership development in some company. Now have [00:32:00] to pay attention. This is a new thing they teach their managers with, with, by the way, and I don’t mean, I’m not picking on situational leadership. It’s very popular for a reason, but I also can say it’s not been held to any rigor now we’re telling managers to focus on this thing and then the CMO, let’s say, or the CFO goes to some conference and they come back with some new leadership idea, framework, and they say to the, And then there’s the chief human research and nevermind what the leadership development person learned in their PhD and everybody wants that to get into the leadership model.

    None of it has any rigor. It’s too much stuff. It doesn’t hang together and none of it has held a measurable count. Now our managers are confused about what they’re supposed to do. And, and, and on and on it goes over and over. And you mentioned like proof. The most important thing that that we did at Qualtrics to learn that this, to prove this was the model we used, I call STAC, select, teach, assess, [00:33:00] coach, all with that leadership standard.

    The same leadership standard and the assessment was the key, a measurement for every manager in the company from their employees on whether they’re demonstrating these behaviors, not 360, not from the boss, the boss gets plenty of opportunity to assess that manager in other ways, you know, and so now managers even who thought they were demonstrating certain behaviors, their employees were saying, we didn’t see it, you know, and it had confidentiality, so they didn’t know who said what, you know, we had a very Because of who we were, people, the managers were inclined to look at these measurements and pay attention to them.

    And so suddenly we could show a manager every quarter how their team was experiencing their leadership. We didn’t use a punitively. That’s the fastest way to get employees to stop telling the truth. You fire someone. We used it to coach, assess, coach, assess, coach, assess. Every quarter, a manager got an assessment from their employees [00:34:00] anonymously that was by the way.

    Organized and prioritized around the things that were correlating very strongly with employee engagement on their team. So it was custom what they should focus on. And we gave them measurements of why they should focus on, you know, nobody’s doing that. And that’s why managers. They, they pick and choose what they’re going to focus on based on, I don’t know what way the wind’s blowing half the time.

    There’s, you know, and, and the, what companies choose to teach, select, teach, assess, cause they’re teaching too many things and they’re confusing their managers. What should you focus on is not a question a manager can answer. Managers are, what I think I should focus on is they don’t know because they don’t have any sort of connection between the teaching and the assessment.

    And there’s no connection between the selection for the job. The teaching, the assessment and the coaching, the coaching should, they should all be done around a coherent, concise leadership standard that we know works measurably predictably leads to more engagement and [00:35:00] better business outcomes.

    Alexis: Yeah, I love it. I have one last question that I like to ask. Looking back at your career, what is the one piece of advice you would give to your younger self?

    Russ: say, Hey, you had a good instinct. It was well executed. Do that again. And here’s what it was. I was in the U S Marines and I loved it. I really loved it. There’s a number of things in that culture that I miss. I’ve never seen again in corporate America, probably do another whole episode on that someday, but I loved it.

    But I got out after four years because I realized that the tempo. Of the Marine Corps, the deployment schedule, for example, was not conducive to me being the kind of husband and father I would one day want to be. I wasn’t married yet. I had a couple other small complaints about the Marines too, but this was probably biggest for me.

    We deployed a number of times. And I saw how it wreaked havoc on my, you [00:36:00] know, my Marines and other officers and things like that. So that’s the first time. Then when I was graduating business school, so, you know, let’s, I think I’m 33, 20 years ago. I was interviewing with like McKinsey and Bain and, you know, big, big consulting houses. And I came home one night and my wife said, and I had two sons already. I eventually had a third. I came home one night and my wife said, you know, She goes with like sarcastic air quotes. She goes, you know, now that you’re getting this fancy degree, does this mean you’re going to get a job where we’ll never see you anymore?

    Alexis: Hmm

    Russ: You know? And I, and so we sat down and talked that through and I made a promise and the promise was that I would never allow my career to get to a point where I was no longer being a good dad or a good husband and further agreed that she and the kids were the ones who got to evaluate that, not me, it was, you know, they’re the ones who are receiving.

    My husband ship [00:37:00] receiving my fatherhood. It’s very similar to the assessment of the manager. I don’t really care what the manager’s manager thinks about how that manager’s leading. I care what the employees think people are fighting to attract, develop and retain my opinion of how good of a father I am or how good, you know, I got to look myself in the mirror, but I really want to know what my wife thinks about that and what my kids think.

    Right. So we, we sort of stacked hands and said, Never let, never let the career get in the way of being a good dad. Good husband. What’s interesting about that, by the way, is I, as a result, I became a really good prioritizer. And, and I, you’ve heard, you know, I know you’ve read the book. I say the book prioritization is an exercise in subtraction, not addition, but it’s, it’s like, it’s like one of the most misused words in business.

    I think only strategic is more misused than, than prioritization. People think it means a task list. It doesn’t. And so what I became very, very good at. Is subtracting work. It’s, it’s way easier to say than do by the way. And and [00:38:00] so when I subtracted work, that meant I tended to have usually a better work life balance, but you know, like I want people sometimes hear that and they think, oh, don’t work hard, you know, I won an award at Google for being a great manager.

    You, the way you win that is one, you have to be. Not a dick, you know, so your employees are the ones who recommend you. And so if you’re a dick, you’ll never get recommended. And then you get chosen by the CEO’s team and they don’t pick people who don’t have like a reputation or track record of getting meaningful things done.

    So I’m, I’m by far most proud of that award for that reason. So I say that just cause sometimes when I say I became good at managing my time, I became good at prioritization. I became good at subtracting work. Sometimes people hear the wrong thing. Sometimes when people hear work life balance, mine tended to be pretty good sometimes people hear doesn’t work hard.

    And that’s just wrong. That’s a bad conclusion to reach. So anyway, what I would go back to my younger self and say is, this instinct that you had, [00:39:00] that you weren’t sure about, that by the way shows up again, In another 10 years in your early thirties when you’re graduating business school go with that What when you’re at the end of your career, which by the way, I pretty much am now.

    I just i’m retired I do some speaking. I do some coaching when you’re at the end of the career All that will matter is you’re looking at your three sons you know, you’re looking at, you look at your wife, are we still happily married? Yes, we are. You’re looking at your three sons, how they doing? Do you know about them?

    Do you know about their lives? Are you involved in their lives? And that I can’t, I can’t think of one other thing that gets anywhere near as important in my career as those things. So I would go back and encourage myself to follow that instinct that I, that I had. And, and maybe especially graduating Wharton wasn’t totally sure about it was, it was the right, it was the right instinct.

    Alexis: I love it. And, , and thank you for sharing that. I hope it will inspire a lot of people to think and reflect on what they are currently doing. [00:40:00] Thank you very much for joining the podcast. I hope we will have another opportunity to discuss all the other things that we were not able to discuss today. 

    Russ: Anytime you want, anytime you want. Thank you so much for having me. 

  • Agile Conversations: Why Trust Comes Before Why

    Agile Conversations: Why Trust Comes Before Why

    Some episodes give you a framework.
    This one gives you a practice.

    I sat down with Jeffrey Fredrick, VP of Engineering at Ion Analytics and co-author of Agile Conversations, to explore what happens in the moments that matter: when tension rises, stakes feel high, and the conversation goes off the rails.

    What struck me is that Jeffrey does not talk about communication as “soft skills”. He talks about it as deliberate practice.

    The moment that changed everything: “You’re good at advocacy, but where is your inquiry?”

    Jeffrey traces the origin of his journey to a conversation at CitCon. Someone he had just met told him something precise and unsettling: he sounded skilled at making the case for his ideas, but not very curious about others’ reasoning.

    That single observation pointed him toward Chris Argyris’ models:

    • Unilateral control: I’m right, the answer is obvious, and my job is to make my idea win
    • Mutual learning: I share my reasoning and I’m genuinely curious about yours, so we can learn our way to a better decision

    The key move is deceptively simple: balance advocacy and inquiry.

    The Four Rs: a method to practice, not just understand

    Jeffrey introduces a simple cycle that turns good intentions into actual behavior:

    1. Record the conversation (in a two-column format)
    2. Reflect using a model (Argyris, NVC, LEAP, etc.)
    3. Revise by writing an improved version
    4. Role play to make the new behavior real, out loud

    What matters is not the elegance of the model. It’s the repetition.

    Jeffrey’s point is sharp: these ideas make so much sense that we assume we already do them. Recording exposes the gap between what we value and what we actually do under pressure.

    Why we can’t recall what we said

    One of the most useful insights is about memory.

    Jeffrey explains that we don’t remember the exact words we used because we’re not hearing our own “tapping”. We’re hearing the “music in our head”. In other words, our internal story is richer than the actual signals we send.

    That gap is exactly why deliberate practice matters. If you can’t accurately perceive your behavior, you can’t reliably improve it.

    Trust first, fear second, then why

    Jeffrey challenges a popular leadership reflex: starting with purpose.

    He argues the sequence often needs to be:

    1. Build trust
    2. Surface fear
    3. Then talk about why and direction

    Why? Because without trust, “why” becomes a debate weapon. And without acknowledging fear, teams act out of loss aversion while pretending they’re being rational.

    I especially liked one framing: if you hide your concerns, you’re not being neutral. You’re withholding relevant information. That changes the emotional meaning of vulnerability. It becomes part of doing the work well.

    Triggers, tells, twitches: spotting your patterns

    Over time, practicing the Four Rs helps you identify repeat patterns in yourself:

    • what situations trigger you
    • what your “tells” look like
    • what your body does (“twitches”) when you’re about to slip into control mode

    Then you can do the adult thing: plan your moves in advance, instead of improvising under stress.

    Can this work at scale?

    Jeffrey has seen it spread in organizations in two ways:

    • explicitly, through shared practice and vocabulary
    • implicitly, by embedding mutual learning into rituals like incident reviews and postmortems

    His reminder is both hopeful and pragmatic: it spreads one person at a time. You don’t need everyone trained for the conversation to improve. But when more people practice together, everything accelerates.

    The simplest takeaway

    If I had to keep one idea from this episode, it would be this:

    When stakes rise, stop trying to “win”.
    Return to mutual learning: be transparent about your reasoning and curious about others’.

    It’s not a slogan. It’s a practice.

    Transcript:

    Alexis: [00:00:00] Welcome to Le Podcast on Emerging Leadership. I’m your host, Alexis Monville. Today, we are diving into the world of agile leadership with a special guest, Jeffrey Fredrick. Jeffrey is the Vice President of Engineering at Ion Analytics and the co author of the book Agile Conversations. With a wealth of experience in the tech industry, Jeffrey has a unique perspective on how agile can transform teams and drive innovation.

    Welcome Welcome to the podcast, Jeffrey. How do you typically introduce yourself to someone you just met? 

    Jeffrey: Well, I had lots of practice that last couple weekends being at a couple of conferences. So I got to refine my pitch of it. The usual way that I put it is I work four days a week as a software executive, currently VP of engineering and then one day a week as an executive coach, both to individuals and to executive teams.

    Alexis: Wow, that’s a perfect pitch. I love it. And I [00:01:00] like the balance between the four days a week doing the job for real and one day a week helping others do it. That reminds me something. You are also the, the co-author of the book Agile Conversations. Can you tell us about the pivotal moment that led you to the book?

    Jeffrey: Oh, well, in a sense, I think the pivotal moment came for me actually at a, at a different conference, at CitCon, the conference that I organized and have organized for the past 19 years. I was there and I was talking to someone who I just met, a gentleman named Benjamin Mitchell, and we were talking and he said to me, something very strange.

    I didn’t understand what he meant at first. He said well, you seem very, very familiar. Practice very skilled making the case. For what you’re saying, you know, he says you’re, you’re very good at advocacy, but I’m not hearing much inquiry. And I was very confused by what he said. He clearly meant something very particular but I didn’t know what it [00:02:00] was, and that really was my very, very first taste of the model from Chris Argyris what he would call model one and model two where it’s easily understood as the unilateral control model and.

    The mutual learning model and the idea. One of the one of the ideas in it is that you should be balancing advocacy inquiry. There’s you should be both making the case for what you believe and sharing the reasons why you believe it. And you should also be curious about the other person’s beliefs and why they believe what they do.

    it was, so it was actually that conversation that ended up setting me down the path that led to the book. The gap between that conversation and the book was about nine years. So it wasn’t a quick path, but it was actually fairly direct.

    Alexis: I love the story about it and I can understand why in a way, in our current timeframe or mindset [00:03:00] it could seem long, but at the same time When I read the book I was thinking, okay, it sounds very simple at first. And you’re talking about the four R’s and I will ask you to explain that a little bit, but if you want to practice it, suddenly you’ll realize that you will need a lot of practice, but can you give us a taste of what the four R’s are?

    Jeffrey: Sure. The four Rs actually came about from trying to teach other this model and w what happened is we, we, I started learning Chris Argyris material. I started practicing it myself and I was very fortunate to be in a study group with aforementioned Benjamin Mitchell, Douglas Squirrel, my co author.

    And we would have long weekly sessions where we would study it. And then I tried to bring the same material into the workplace and have other people learn it as well. We weren’t though going to be able to have multi hour [00:04:00] conversations. So what I needed was a format that would allow us to get the same, a lot of the same value of practice, but in a shorter timeframe.

    And so what the four R’s are is a, process for studying really any kind of conversational technique that nice. And I make this point because there are lots of different models of what good communication looks like. There’s the Chris Argyris model that we just, we’re discussing the mutual learning model, but there’s also models like nonviolent communication.

    Xavier Armador’s leap model. Many different types of things that people might want to check to see if they’re doing and the four Rs in a sense is kind of separate from all of those. It’s a process really of studying conversations and it’s the four steps involved are first you record Your conversation, you do this in a, in a two column format and the two column part is important and you write it down and this is important.

    We can come back to why. [00:05:00] So there’s the record. And then once you have it written down, then you reflect. This is where you bring whatever model you’re using to bear. You evaluate your conversation that you’ve recorded according to the model you have in mind. And then having reflected. On it and seeing some things that you might improve.

    You then revise, you, you try creating an alternate version of the conversation. And this, these two steps are really where the practice is, you know, up until now, you’ve been kind of evaluating what you’ve done, but it’s really in the work of trying to improve as the element of deliberate practice. And once you’ve written down a version of the dialogue that you.

    Prefer then you can go to the, the final step of practice, which is to role play which is to actually say things out loud that you have written down and and having done this of course, there’s kind of a loop here. You’re, you might not like your first revision. You might not like it, what it sounds like when you role play.

    And that’s the point is that you will then revise or repeat rather, you’ll go back and re [00:06:00] revise and re reflect and come up with better versions. And even In the role play, you might change sides with the person you’re practicing with, and that’s role reversal. 

    Alexis: It’s very powerful. And just the recording phase is very interesting. I usually take. notes when I have a conversation with people but I realized when I was reading the book that I usually take notes about what the other person says, not so much about what I say. And when I recall the conversation, usually I don’t really remember what I said.

    There’s a few things that I note, but it,, that’s basically things that I want to remember. I said that to that person. I give that advice or I asked for a particular thing, but all the rest I am, I forget about it and I am able to remember it. And, and I was stunned by that. That’s, I, I, I just can’t is it something you observed? 

    Jeffrey: Absolutely. it’s [00:07:00] not surprising that we don’t. Remember what we said exactly because in practice, actually, we aren’t aware of what we say in a conversation this is kind of why people have difficulty improving their conversational skills without this kind of deliberate practice and writing things down.

    Now, when I say we don’t know what we see in the conversation, this may sound , hyperbolic, but it’s, but it’s actually true that one of the, one of my favorite experiments about this is they asked a number of people to tap out a tune, one that was very familiar, that everyone would know.

    And so for example, the song, happy birthday to you. Right? So they would tap on the table, you know, tap, tap, tap, tap, tap, you know, and then, and then they would ask the people, what are the odds that the person listening to it will be able to guess what it was that you were tapping out. Right.

    And, and, and and when they ask people, and I’ve done this many times, I’ve done this. And when I, if I’m doing [00:08:00] in person, I will tap it out and, you know, ask people, you know, what do you think? How often people they guess? And people give a whole range. They, you know, some people say 40%. Other people are much more.

    Cautious, maybe 20 percent or even 10%, but actually it’s much smaller than that. Even it was something like less than 5 percent of the people could guess what was being tapped. So there’s huge discrepancy between what people guess, what people will be able to guess and the actual number of people can guess.

    Now, why is that? And it comes down to this. The person doing the tapping isn’t hearing the tapping. They’re hearing the song playing in their head. They’re hearing the music in their head. And that’s what we are like in our conversations. We aren’t hearing the words we say. We’re hearing the music in our head.

     So there’s like, actually two completely different conversations happening. There’s what we’re hearing in our head, and the person we’re talking to, and all they hear is the tapping. And that’s the [00:09:00] that’s that gap explains a lot of our conversational differences and what the four Rs do in the recording format by having one column where you write down your thoughts and feelings and one column where you write down the actual dialogue.

    Well, it makes that difference clear. So that’s that idea that we can’t remember is when you have this mental model is less surprising because what remember is the music, you know, that in our head, not the tapping that we’re making. Right.

    Alexis: Mm, I, love the analogy and I’m I’m eager to try the experiment. . I’m pretty sure that all listeners Start With Why. And still, I tend to agree with you that it’s not really where to start.

    Why are you saying that?

    Jeffrey: it’s worth perhaps saying that , in the book when we lay out conversations that we believe , that team should be having it really comes down to what we value more than why, why is still important, but we put it third. , we, what we say is before you start getting into why.

    What you’re doing, [00:10:00] the first place, the place to start is to start with trust. Because this is the, what’s going to be, what is the foundation for how you are able to improve going forward? You know, if you, if you don’t have trust, then . The future conversations are not going to bear any fruit.

     That’s our place to start is that is doing things that build trust. Now that the idea of how you build trust generically I’ve only come across one way to do it, which is in some sense to be vulnerable. The idea of being vulnerable means, in this case, it might mean, you know, sharing are really comes out of sharing our thoughts and feelings and being interested in the thoughts and feelings of other people.

    And this way of, of being vulnerable is a very common thread that I’ve seen through all the different types of discussions of trust. Now, this is not the kind of trust or being vulnerable that you might have with a [00:11:00] traditional leadership game of, you know, maybe doing trust falls where you’ve leaned back and someone tries to catch you.

    This is something that’s a little bit more high stakes. This is sort of like being willing to, to share differences of opinion and where You’re not sure when it’s going to agree but the idea is , that there’s not another approach to really building the relationships with your colleagues, other than to be able to be honest about Your thoughts and feelings.

    I could say more about this. It’s not that you you need to be blunt. I can tell people when when they’re doing these kind of exercises, you might have the inner thought that says, That’s the stupidest idea I ever heard. And building trust doesn’t mean therefore saying, Wow, that was the stupidest idea ever heard.

    If you if you say something, like, Well, I look, I have some concerns, great, you have full marks. But if you just say, Oh, Okay, then clearly you’re withholding relevant information. And so, that’s the low [00:12:00] trust building approach. And very often people are nervous about how people react.

    So they’re nervous about sharing their differences and getting that point where you can say, I have some concerns. And we talk a bit more about how to do that in that chapter. So that’s why we don’t start with why is because we think building trust is essential. And the next thing we get into.

    So our second. Conversation we think is important is having the fear conversation. That is, is a sense an extension of the idea , of building trust, because if we’re not sharing our fears, then we’re not really being vulnerable, we’re not sharing important elements to it, but fear is such a large element and actually can be a way to.

    For people to better understand us when they understand a lot of our motivations are coming about from what things that we’re concerned about and what we’re concerned about is not going to be the same as other people. That idea that our, our inner fears and thoughts are not going to be different from other people’s actually a really important idea.

     One of the big [00:13:00] barriers to good conversations is something called naive realism. Which is a cognitive bias that works like this. It says, I see the world as it is. And so do you we’re both, and we’re both looking at the same objective reality. And therefore we have the same information.

    And and of course I’m, what I’m seeing is correct. You know, the right thing. is obvious by just examining reality. So if I can see this thing, you can see it also. And so if you don’t agree with me, well, then you must be confused. In which case, my job is to explain to you how you’re confused or that you’re doing something sort of disingenuous or malicious.

    You can see the truth. You’re just choosing not to share it. And in that world, we don’t need to talk about our fears because they’re obvious. And so if we, if we leave that, that mistaken world of naive realism and realism that we’re seeing different worlds, then the need to actually explain our fears become more apparent.

    And we, and we start [00:14:00] with fears because people are, tend to have a negativity bias. People tend to have loss aversion, negative emotions and negative feelings have a stronger influence on us than positive ones. And therefore. We think addressing those hidden concerns, surfacing them is important first step before you start getting to the more positive side, which is why and you know what what we hope to address what we have to achieve going forward.

    So. why is still very important we just don’t start there.

    Alexis: Yeah. And I, and I love it. And I, I really love the way you are framing it about withholding information. I feel it’s very powerful because If you ask me to be vulnerable, I, there’s some discomfort with that. And now if you’re telling me, Oh, but if you want to make progress in that relationship, if you want to make progress in that conversation, you cannot keep [00:15:00] information to yourself.

    You have to open up a little bit to help the other person. See what you think, see what you, Or see what you fear. I, believe it’s very, very powerful to frame it this way.

    Jeffrey: yes. I’m glad that resonates with you. And one thing I’ll say is it resonates resonates with a lot of people. One of the dangers that our book is actually trying to address is that when you read these types of ideas, they all make sense. The challenge is that they make so much sense to people that people think that they not only do they agree with it, but they believe they actually are already doing it. And if we go back to the four Rs, the purpose of the four Rs, the purpose of writing things down is to allow us to observe the fact that we don’t. Behave the way that we espouse the way that we value we think that because we believe this to be true We believe it to be the best way to communicate that therefore that must be how we [00:16:00] communicate But when we look at the evidence unless we’ve done some very deliberate practice What we’ll find is that’s not the way we we actually behave by default.

    We we are More strategic we fall into what? Chris Argerys is called, you know, model one or the unilateral control model. And we ended up withholding this information, not by deliberate strategy, but because it’s in a sense of the way we’ve been trained and the way that feels natural.

    Alexis: Yeah, and I love the idea of identifying the triggers. Because they are derailing completely the conversation. It’s very interesting to reflect on that and say, okay, okay, let’s, let’s pause for a second on that one. let’s avoid reaction the, the hundred percent hundred percent reaction mode and

    Jeffrey: Yeah,

    Alexis: spend a little bit more time on that

    Jeffrey: that’s right. That’s the triggers that we talk about triggers, tells and twitches, which are three types of patterns we can learn about ourselves through [00:17:00] doing multiple conversation analysis, right? So we use that four Rs for conversation analysis. If we do it multiple times, we’ll tend to spot these patterns and realizing the way we often behave.

    And then the idea is that having discovered that we come up with preplanned strategies. Things that we’ve decided in advance that agree with our values rather than trying to improvise in the moment under pressure, in which case we’re likely to go fall back to those default model one strategies.

    Alexis: So, you are VP of engineering at ION Analytics. 

    Jeffrey: Yes.

    Alexis: ,are you really able to use that in your day-to-Day? Life and how your teams maybe are using it if they are. 

    Jeffrey: Would say this is in this scenario, not all of the teams are I use it all the time. I if nothing else, I, I do a workshop every month at a meetup where I have a meetup, the agile conversations meetup, and that we do a it’s open, it’s free to [00:18:00] everyone. And so once a month I will do the four Rs practice along with everyone else.

    So minimally I actually do. this practice minimal once a month. Now I actually did something like this. Four or five times in the past week leading different workshops at the conference and quote unquote, summer camp between them at these conferences. So I’ve I’m you’re you’re catching me in a moment where I where I look especially virtuous in practice. So, but I will definitely use this techniques of practice, even though I’ve been doing it for 10 years. It’s still very valuable to keep practicing. Oh, 10 years. It’s much more now. Isn’t it? Time flies more more like 12 or 13 years. Yeah. But it’s not I’m not in it. The thing about these skills that we talked about here, these conversations is there are things that you can initiate.

    These are practices you can do on your own without needing to get everyone’s buy in that these, these are things that you can do. These ideas of being more transparent of being more curious , [00:19:00] these are things that work whether or not other people are, have practiced them as well. And I think part of it is because goes back to what I said before, these ideas make a lot of sense to people and Generally, what we’re saying here is take those, those ideas that we would all agree are the best way to make decisions and then actually behave that way.

    But, but the important part here is we’re not, we’re not trying to do something wild and crazy. And I often illustrate this in my. Group sessions when I’m doing a workshop, I’ll ask people and I’ll say something like if, if I was going to put you in charge of coming up with a process, we’re going to make a decision and I’ll choose something trivial.

    Let’s say you’re going to choose what ice cream we ordered tonight for the group. How would you suggest we go about making the decision? And it’s generally some variation of, well, I would ask everyone. For their idea what they would suggest. Cool. And then I asked you. So you’d be curious. Huh.

    Now, would you also share your own [00:20:00] ideas? I feel like, well, yes. Okay. So you’d be transparent because everyone agrees that we’re going to make a decision together. We want all the information. So we should be curious about what everyone else knows and what they believe. And we should be transparent about what we know and what we believe. And we all agree that that’s the best way to make a decision, but it’s not the way people act in practice. I should be, I should clarify this. It’s not the way people act in practice. If they think something important is at stake, if they, if they think this, the question is trivial and they’re, they’re not concerned about it.

    Or, and this is why, for example, people make great facilitators for other people’s problems because they don’t care. And when they don’t care, they. Naturally act in a way that’s very productive, which is they say, well, let’s get all the information on the table. Look, I don’t really know about this dispute.

    Let’s hear from both sides. Let’s bring in all the, all the facts. And once we have all the facts, then we can decide. That’s what we, we know in really deeply [00:21:00] believe this is the best way to make decisions, but. If we think there’s something important at stake, suddenly we don’t behave that way. And the reason is because we come up with our own ideas about what we think is best.

    And once we have our own idea of what’s best, now, suddenly we want it to win. We’re no longer trying to make the best decision. We’re trying to have the best. Our decision be the decision that approach of how do I get my ideas to win? It just leads to a completely different set of behaviors.

    And I don’t think this is a conscious choice people are making. It’s just a function of how our cognition works. It kind of goes back to that fallacy of like the naive realism, like look, the, the right answer is obvious. Therefore, since everyone has the same information, there’s no need to be curious and there’s no need to be transparent.

    It’s just a question of being logical. And so I will try to reason people, I will bludgeon them with reason until my way is victorious. And, [00:22:00] and that going along with this is the idea that this is the right thing to do. I should be trying to get my idea to win because my idea is best. And and this is an important decision.

    This is consequential. If something else were to happen other than my best idea, well, that would be a loss for all of us. And it’s that fear of loss that I think generates these kinds of behaviors in us. It’s not that people are ill motivated, but the, the way our cognition works gets us caught in this trap, and this is why.

    It’s really valuable to have people go and practice this other way of being and practice this other approach of saying, you know, rather than trying to focus on having our idea win, how can we focus on mutual learning? How can I focus on learning what other people believe and sharing what I believe? Now at the end, maybe we won’t agree.

    On the best thing to do, but at least in our disagreement, we’ll have all available information. That’s why I think this [00:23:00] works without having other people be trained in it, because if I come to you and I say, look, we have this decision to make, but I really want to understand, Alexis, what is it that you believe and can you tell me what you saw and how you got there?

    You’re happy to tell me you’re not going to say like, well, look, I, I think you should, my idea should win, but I’m not going to tell you why I got there. No, no. You’re quite happy to like share your chain of reasoning because you’ll be persuasive. And if having done that, I say, well, look, let me share.

    What I’ve seen and how I got there, then people are generally are happy to listen after they’ve had their chance to talk, right? So this kind of reciprocation. So when we’ve done the practice and we can behave this way, we make the whole conversation better for everyone.

    Because we’re not trying to mislead people where we’re actually taking them back to what they believe would be the right way to work and and the way that they would behave. If it was something they were designing in advance. It’s only something we fall out [00:24:00] of doing in the moment, in the heat of the moment.

    Alexis: Yeah, that’s very interesting. So do you believe that drive way the teams are organized on, on the way the team works because you and probably others start to behave that way, engaging people and their interactions. Excellent.

    Jeffrey: What, well, I mean the, the, the conversation I’m part of, I can bring these skills to better, and I’d also would say the more people who’ve done the practice, the better I’m. At ion via a series or a short series of acquisitions when I first was learning this, I was CTO and head of product at a much smaller company called Tim group and at Tim group.

    We actually did bring this these, this material in, and we did have everyone in the company practice, and it was very effective to have everyone learn these skills because you start having the kind of jargon and it really did [00:25:00] accelerate things when you could be much more transparent about what your thoughts were in the sense of the metathoughts of saying, well, let’s make sure that we’re using mutual learning here.

    You know, there was keywords people would apply and not only that, but people would do practice sessions together. We would have a weekly and then fort later fortnightly practice session where people would bring their conversations for group discussion. It was very valuable to have people to talk through their differences.

    It’d be really interesting when two people would bring their own conversational analysis of the same conversation. What we found was that people consistently realize that if they’d been more transparent, more curious earlier in their conversations, the things would have gone better. they often were bringing cases where, they had these long, Debates with each other before eventually settling on something.

    So in one sense, they didn’t really need the skills. They would work things out eventually, but having the skills, having done the practice, what would have been maybe three [00:26:00] hours of discussion became 10 minutes. So, and people felt better. So there was definite wins for having done this as a group. It’s not that there isn’t value, but it’s not.

    It’s not required to develop it. But it is an accelerant if you have more people on board doing the practice.

    Alexis: Excellent. What, what is the size of the, of ion analytics and ion group in general?

    Jeffrey: I, Ion group is tens of thousands of people. Ion analytics, is a a couple thousand within engineering we’re talking 300 to 250, 300 ish. So that’s a, a much larger whereas at Tim Group, when I started there was 120 people. We’re now doing this much larger organization than when I was, was at Tim.

    Alexis: Yeah, that gives a sense that we are not talking about 10 people or even 100. It’s way larger than that. And you can still see the impact of having better [00:27:00] conversations in the, in the organization. Is it something that can spread to , the other part of the group, or is it only in your area?

    Jeffrey: I think it spreads individual by individual. So even if I think back at to Tim group, it it started very much within engineering. It was it was people within engineering who were practicing these things and then, and then product and then people in data science and then until it’s kind of all of the sort of technology side, and then it spread over to the executive team.

    Actually, and then the executive team then wanted to instill it in the rest of the company and then took it to sales. So it it, it, it did spread bit by bit through Tim group. It did so because you had people who were explicitly championing it within the context of. Analytics, it’s something that I focus more on using than teaching.

     I have done some classes, [00:28:00] but we don’t have the same at the moment, same kind of weekly study group. It’s there for people who like it. And I do think there is an element to which it spreads on the other hand, even though there’s no training , if I’m with a group of people and. We practice the idea of being transparent and curious, then they begin developing those patterns and it comes out in some of even some of the ritualized elements.

    So, for example, we’re focused a lot right now on post mortems or root cause analysis. And bringing in the idea of, look we’re going to focus here on first creating a timeline. We want to head of shared facts that we’re discussing before we then go and try to make meaning from those facts. And we’re going to move stepwise and have multiple people involved to sharing their perspective.

    We’re kind of embedding in the process, this mutual learning model. And so in that sense, there’s an element which it spreads through experience rather than [00:29:00] through, you know a shared mental model of what’s happening. I do think that does spread in part because if we go back to, we said before about the need to build trust when we have built trust with other people and when we have psychological safety, then we are more likely to behave in the way that we believe is correct.

    We’re more likely to share, be vulnerable and share those thoughts and differences. And we’re more likely. Having built trust and respect, we’re more likely to then be curious about what other people say. So there’s an element which the practice leads people into behaving in this fashion.

    Alexis: I love it. Thank you very much, Jeffrey. Maybe one last question. What would be one advice you would give to your younger self?

    Jeffrey: Well,, the advice I’d give to my younger self is to start this earlier. I’m now 54. I came to this in my forties and it would have made a massive difference to me if I had started this in my [00:30:00] twenties. I could have learned a lot more, a lot faster. I could have been much more.

    Persuasive I could have been much of much more help to the groups. I was dealing with if I had learned these Skills earlier. I definitely was a Kind of person who would try to persuade other people about why my position was right and so I think that since Benjamin Mitchell was correct in his analysis when he said I was well practice at advocacy, that was true.

    I had a couple decades of serious practice going back to actually the high school. So maybe three decades I had been on the speech and debate team. And so I had learned a lot in practice, a lot of persuasion. I think I would have benefited from a lot more curiosity. That’s my younger self that would be.

    You know, become more balanced, learn the value of listening first and to understand that listening is not a weakness. It’s a strength. I think there’s that element of if I, if I’m [00:31:00] curious, then it makes it that I’m somehow losing ground. And that’s just simply not true. I’m, I’m adding value to everyone by being curious.

    And then I’ll have my opportunity to be transparent. That’s, that’s advice I could have used a couple decades before I learned it. Thank

    Alexis: I love it, Jeffrey. Thank you very much for having joined me on the podcast.

    Jeffrey: Thank you for having me. 

  • Exploring Leadership and Open Source with Maria Bracho

    Exploring Leadership and Open Source with Maria Bracho

    Some leadership environments reward authority.
    Open source rewards influence.

    That is the quiet power behind my conversation with Maria Bracho, CTO for LATAM at Red Hat. Her story is not only about technology. It is about what leadership becomes when you cannot force outcomes and must instead create conditions where people choose to build together.

    Open source explained through ramen

    Maria offers one of the most tangible explanations of open source I have heard, and it starts in Japan.

    She tells the story of instant noodles and the decision to share a method with competitors so an entire ecosystem could move forward. Companies could still compete on flavors, but they standardized the foundation. The result was not only industry growth, but global adoption.

    This is the open source logic in plain sight:

    • share the foundations so everyone can build
    • collaborate on the hard common problems
    • compete on what makes you unique

    In software, that foundation can look like Linux. The toppings can look like products, services, packaging, and the experience you deliver.

    Leadership across geographies shapes the leader

    Maria has led in multiple regions, and her lived experience shows in the way she describes leadership.

    She contrasts the directness and energy of Latin American communication with the subtlety and collective orientation of Japan. She also points out something important: culture is not only what people say. It is what the language allows and what the environment encourages.

    For leaders working across geographies, this is not a “nice-to-have” insight. It changes how you listen, how you build trust, and how you create alignment.

    Taking on the hard problems

    There is a pattern I recognize in Maria’s career: she takes on work that many people avoid.

    Her explanation is surprisingly grounded. It is not a heroic narrative. It is a mix of perspective and appetite:

    • perspective from where she started, which makes “hard” feel worth attempting
    • appetite for the satisfaction of moving something difficult forward
    • a belief in persistence, learning, and collaboration

    I also noticed a subtle leadership trait here: she does not let the full size of the challenge paralyze the first step. She moves, learns, adapts, pivots, and keeps going.

    Product leadership without authority

    One of the most practical parts of the episode is when Maria describes her transition as a product manager.

    Before Red Hat, she could write documents that said “the system shall do X, Y, Z” and expect engineering to execute. In open source, that model collapses immediately.

    Instead, she had to learn to:

    • influence communities rather than command teams
    • co-create with customers and partners
    • collaborate with competitors and coopetitors
    • iterate in public until the outcome is good enough to ship

    Her conclusion is sharp: the ego-based model is expensive and slow. The collaborative model is hard work, but the outcome reaches production faster and fits reality better.

    This is a leadership lesson many product leaders need:
    If you struggle with engineers, it may not be a communication problem. It may be an authority mindset in a system that requires influence.

    Recruiting as a leadership responsibility

    Maria treats recruitment as part of her job, not as a task delegated to HR.

    She designs the hiring process intentionally:

    • aligning the future direction of the team with the profiles she seeks
    • involving a strong panel that challenges candidates and challenges assumptions
    • seeking diversity of perspectives to strengthen the team, not just fill a seat

    Her standard is simple: the time spent recruiting pays back when the team becomes stronger, more cohesive, and more catalytic.

    AI, the Red Hat way

    Maria does not avoid the AI topic. She embraces it with a clear framing: Red Hat’s approach must be authentic to its mission.

    She highlights RHEL AI and InstructLab as signals of a serious commitment to AI through openness, community, and access. The emphasis is not only on features, but on democratizing the ability to work with models, adapt them, and keep control of where data lives.

    Whether you agree with every detail or not, the leadership principle is consistent:
    new technology becomes durable when the ecosystem can participate.

    The closing advice: work hard, stay authentic, keep learning

    Maria’s advice to her younger self mirrors the way she leads:
    work hard, stay true to what you believe, stay open to feedback, and keep learning.

    It is not glamorous.
    It is also how influence is built over time.

    References for you!

    Here is the Transcript!

    Alexis: Welcome to another episode of Le Podcast on Emerging Leadership. I’m your host, Alexis Monville, and today I’m thrilled to welcome Maria Bracho, Chief Technology Officer at Red Hat LATAM. Maria brings over two decades of experience in steering multinational technology initiatives and mastering the art of leveraging cutting edge technology to drive business growth. Maria, it’s wonderful to have you here. Could you start by sharing how you typically introduce yourself in professional settings?

    Maria: Hi, Alexis. It’s a pleasure to be in your podcast. I am Maria Bracho. My role at Red Hat is as Chief Technology Officer for Latin America. And I partner with our customers, communities, and our teams to create better experiences. And shape the vision of Red Hat both [00:01:00] in as our technology, but also with communities and move the world forward, hopefully with open source technologies.

    Alexis: Hmm, Maria, for many, Red Hat is synonymous with open source, but there are also many in our audience who may not be familiar with either open source or Red Hat. Could you explain what open source is and perhaps share a bit about Red Hat?

    Maria: Sure. Absolutely. In the context of software, open source not only means having your code available for others, but it means sharing it in a way that others can also use, modify depending on open source licenses, but also create it with open source communities for open collaboration and definition of the goals that you want to pursue together And, and also be able to listen to multiple ideas that move the technology [00:02:00] forward.

    Alexis: Would you have something to explain that in more, I don’t know, more tangible way for our audience? Thank you.

    Maria: Yes, absolutely. So I have a few examples from personal experience, as you know, I have lived in different places, but I’ve also worked in these different countries that I’ve lived. And more recently I lived in Japan for the last four years. And. It’s fascinating to me to going to a new place, but also live, work, share the customs especially the food as well.

    And I came across this example by going to the Cup of Noodle Museum in Yokohama. That’s the city I lived in. And this was one of like the highest rated places. Places to go for newcomers and visitors. And of course we never went because we just thought it was a tourist trap and we didn’t feel like tourists, but we had time for a family to come visit.

    [00:03:00] And we went there as I was listening to the story of ramen, it really felt very familiar the way we. Talk about open source software. Have you ever had ramen? Alexis,

    Alexis: I had some, yeah, of course. And yeah, I’m, I’m very curious about how, how some sort of noodles would speak about open source, the way you spoke about open source just before. So yeah, yeah. Enlighten me, please.

    Maria: so I’m not talking about the ramen. So you go sit at a fancy restaurant and they come in hot and ready for you. I’m talking about the workhorse of ramen. The ramen that are hard and that are essential. staple for university students, anybody with an end of the day or after party snack, middle of the night hunger pangs, et cetera.

    These are the flash [00:04:00] fried. Ramen noodles that you can then rehydrate using hot water. So it’s the simplest form of, of cooking a super delicious and satisfying meal. Again, not necessarily the Michelin star experience, although there are some Michelin star ramen cup of noodles in Japan. So anyway, the story starts with Momofuku Ando who like post war Japan was sitting in with many looking at lines and lines of people trying to get this hot cup off of ramen and understanding that in the provinces or inside of the country, it was hard to get access to food.

    And wheat had become one of the new crops to come into Japan. So noodles was a new thing that, that was coming. But access to food was problematic. So he didn’t want people to sort of stand in line hours to get food. He wanted to devise a method to preserve the noodles, to have those [00:05:00] noodles be more accessible.

    And here’s the part where the invention may have come from him or may have come from someone else. But he was sharing this problem with his wife as she was cooking tempura shrimp. So she was flash frying the battered shrimp to come up with a delicious meal. She told him that what happens with when you flash fry Shrimps is that it takes out all the moisture from the batter, and then it makes it a little bit more shelf stable.

    So she was able to get the shrimps ready and then get them, let them last for hours, if not days. And then you put the flash fried tempura noodle. back into a soup, it will reabsorb some of the water and rehydrate and made it delicious to eat. Obviously, if you let it soak for a long time, it won’t be delicious.

    But anyway, the whole point was this flash frying method. And after trying many other methods to [00:06:00] preserve the noodles some of that were not effective causing some stomach intoxication and food poisoning because they wouldn’t. Last that long, Momofuku Ando try this particular method, and he was very, very effective with it.

    So he noticed that this allowed the noodles to remain shape shelf stable for months, and it would preserve them and all you have to do then later before eating was to rehydrate it with hot water. So access to hot water was a lot easier than just to have an entire kitchen to to prepare meals. So this game this gaming clutch, he started being very, very famous for it, his business started to grow.

    There was a lot of interest and then he was looking at his competitors. And seeing them sort of stumble into problem after problem to try to get to the perfect way of preserving the noodles. And he had this, this thought that [00:07:00] it wasn’t just about him or his business, but it was more about Japan and saving the people and helping feed the country.

    So what he did next was sort of an odd move even for a collective thought society like Japan. So he met with all his competitors and started sharing the recipe. He said, Hey, this is how you should preserve the noodles. Japan is huge on on food regulation and sanitary procedures to preserve food as well as other multiple processes.

    So they were sort of eager to get this new method going and they would still compete on the flavor that you add to the soup, but sharing how to preserve the noodle. was something that helped them all move forward. It also helped them standardize on other partners and vendors that would help bring more flavor [00:08:00] to the cup.

    So they would partner with a company that made the size of the cup. So regardless of the noodle that you were selling, everybody had the same cup. So the cups became cheaper to acquire and then to resell. And then. It also made it possible for vendors that would serve other packet flavorings and MSG and other you know dried shrimps are added or dried corn or other toppings that are added to the mix.

    So all of that lower the price and increase the accessibility to the point that you can find this type of ramen. anywhere in the world. So even though his ambitions were for the collective of Japan, it ended up

    influencing it globally to the point where you can have the same noodles today and they are curry flavored.

    They have specific flavors for different regions. If you go to Thailand, you’ll find them with like lemongrass and other things. So the idea was starting small, thinking about the [00:09:00] good and the collective and moving a whole industry forward and then seeing where you can get. So I guess Momofuku Ando

    Alexis: last

    Maria: didn’t even think that that he was going to be able to, to influence so widely and his influence lasted even to NASA because the space program also has these noodles in space.

    So that made me think about. Our influence in the work that Red Hat has done with Linux. And it was a little bit about not just the improvement or moving one company or one technology, but it was more about being the right way to share and think about the collective and the power of what can we all accomplish together and and move us forward.

    You know, we have RHEL now in space as well. So right along with the noodles. So that’s what made me think about parallelisms with open source and the places that I’ve traveled.

    Alexis: That’s a very beautiful way [00:10:00] to explain open source and explain the benefits of it. And explain also why competitors can collaborate on something that even becomes a standard like Linux that can run everywhere, even at Microsoft. And, that’s something very exciting for people.

    So I hope it will help people understand role of open source. in an ecosystem and why competitors can absolutely cooperate on building the community, the future standard, but still compete on the toppings. Maybe even a little bit more of that. So Maria, you are, you have an impressive background with leadership role in different geographies, and you said it, Japan, but you worked in the U.

    S. and now Latin America. How have these experiences shaped your leadership style and what unique challenges and insights could you share with us? ,

    Wait, 

    Maria: Yeah, I also spend time in France. [00:11:00] So well, some of the things unintentionally, my career has sort of been that way. I have found that not only being in different geos, but actually living there understanding the language, the culture, the way of work. Also. It has influenced myself.

    So I also think that have left a mark on me.

    Alexis: wait, wait, wait. You lived four years in Japan and you’re telling us that you speak Japanese?

    Maria: I am not by any approach of the imagination fluent in Japanese. No way, even though I have given it my best efforts. I’m absolutely not fluent, but there’s a lot more of the culture that is. That is the language. And if you think of, I mean, coming, from Latin America where it’s a different way of communicating or sharing information, of collaborating it in itself is very direct and open and exciting and somewhat loud in Japan [00:12:00] is very more.

    Very much more. It’s quiet. It’s subtle. It is a lot more thinking about the collective rather than the individual. And that has been a great sort of compare and contrast and two different two different forms of the spectrum. And then in North America, that’s really where the bulk of my career has been.

    So corporate America has been sort of the staple of how I have moved. Working at Red Hat has been the space where we think more global in terms of community and collaboration and the power of open source. So that’s how I feel much more at home at Red Hat with open source communities because it does think about the The power and the good of the collective but also being very direct at proposing ideas and also sort of challenge each other and, and challenge the status quo.

    That may be [00:13:00] very French with et cetera. And and so, so I find that that that has been a great, a great space to use all of all of what I have learned in different spaces. And yeah, I’m very, very happy to be here. Sort of back in Latin America, where where I started my my career and my preparation in a region that is growing sort of year after year, not just for Red Hat, but for many other companies, a region that can benefit very much so from open source and the innovation that happens elsewhere, but also that happens in LATAM.

    A geo that has many challenges, both political economical challenges, but has a lot of people willing and able to try. A lot of the spirit of the underdog and a lot of the spirit of trying new things and not being afraid and sort of like there’s nothing to lose kind of way. So I love being in that space.

    If you think about it, [00:14:00] Latin America is sort of the startup of the, the rest of the GEOs, where, where North America and Europe would be like the most established. And, and then APAC comes in with very niche offerings and then take over spirit of taking over the rest. Latam is very much the startup where, or incubator where many ideas happen.

    Alexis: It’s very interesting. I’ve observed you working on topics that probably nobody wanted to take. Nobody wanted to take that challenges. And and it seems after sometimes people were realizing that, yeah, you were doing really great. Can you explain how it works? Can you explain how you are doing those things?

    Maria: Well, I have, I have been for a long time with an attitude of both being naive to the challenge, but also I’m just happy to be here. So I started my career in Venezuela very much a third world country [00:15:00] where it was really, really hard to get into, into very competitive university and have access to collaboration with.

    Research into institutes all over the world. So I was very lucky to be in one of those. And then anytime that I look back to, to where I was and the place where I’m from, no longer exists as I knew it. So I think anything extra is, is gain. So I usually do take on the hard, difficult assignments because I have found so much The reward of getting something done that was very hard or complicated.

    There’s nothing like it. So I’m usually chasing that that thing or that same feeling of, wow, we moved, we really moved the needle. We really made an imprint here and we changed it for the better, left it better than [00:16:00] when I did it. Came in and then I also selfishly I learned a lot. I learned a lot and I learned that I could do it.

    So I’m more emboldened the next time. So, and I’m still naive to the next challenges that I that I take. So, but I know that persistence and hard work. And collaboration and, and the spirit of learning from others really moved, moved me forward. So I’m happy to do that.

    Alexis: Yeah, but there’s something with that idea of being naive that I have trouble to understand. Can you tell me more? What, what happens to people that they start really working with each other, collaborating really well that’s not, I have trouble connecting that, connecting that with being naive. So tell me more about that.

    Maria: Well, maybe the, the exact word is not just naive, but it’s not letting the big challenge stop you. Because, and not [00:17:00] letting, not seeing the full picture also stop you, but understanding that And this is very true with open source. Understanding that if you influence And collaborate with a collective and you continue to move forward, you can help shape the innovation.

    You can help shape the future. And that is that is very consistent, even if the beginning, you don’t know exactly how hard it’s going to be or how long it’s going to take or how difficult the challenges, the external challenges are going are going to be. But understanding that through being open and persistent and open to learning and growing and changing direction, pivoting as well.

    Hard work pays off.

    Alexis: Yeah, it’s a, it’s, it’s very interesting because I have I’ve, I’ve heard over the years, a lot of product managers [00:18:00] in tech, having troubles to interact with engineering teams and getting what they wanted and and now you work in open source and of course you cannot tell open source or the open source communities to do what you want so it seems that it sounds like a no problem for you so tell me more about that maybe other product managers can use that

    Maria: No, that, that was a lesson hard learned. I think that my first few months at Red Hat, so I joined over nine years ago as a product manager, and I was a product manager at another company where I just created PRDs and MRDs and product managers wouldn’t know what that is. But it’s basically a document that says the system shall do X, Y, Z.

    And that’s really what I focused on, understanding the market, talking to customers and then I would give that to my engineering team and wait [00:19:00] until they tell me they need any clarifications and just give me a timeline of when it will be done based on a timeline that I gave them. So the ego was quite big Alexi, and then landing in an open source company where, you know, that would be read.

    And it’s like, well, this is. This is a nice looking document. Yeah, we’re not doing that right now. You need to go talk to the communities, et cetera, et cetera. So I was like, what I need to, I need to influence outside my own company. You mean these are not, these walls are not really walls. These are more like lines in the sand that I can cross at any time, embed myself into other customer problems, really work with them, co engineer, figure out exactly their use case.

    And then also collaborate with competitors and coopetitors To again, together, understand the problem and come up with a solution and then [00:20:00] iterate and iterate on this. That was new for me. It felt like an enormous amount of work. It felt like nothing I had done before. It felt like my ego was nowhere to be seen, and I was just in the mud wrestling to get going.

    However, the outcome after that. Is that the piece of code, the design, the documentation, whatever outcome that we had created and co created and co engineered together, went to market kind of right away, it made it to production in that moment. A new sense of, wow, this is the way kind of became upon me and I don’t think I can go back.

    I mean, I’m not interested in the ego of thinking that whatever I said goes, because I also frankly had a lot of situations where whatever I said And then I had to pay a third party to [00:21:00] try my product and tell me the feedback. And then even with that feedback that I had to pay to get, it didn’t actually resonate with customers the way that I wanted it to resonate.

    So. I’m not ready to have that feeling ever again. That was a huge waste of time. So I, if I have to work hard, iterate with communities, wrestle with competitors, competitors, partners, customers, To to really move technology forward and move entire industries forward. That’s a hard work that I am grateful to have because the outcome and the feeling of accomplishment is It’s, it’s unlike anything I had ever experienced before.

    Alexis: I love it. And I can see how it led you to, to, to become a chief technology officer for, for that, that geography you are in because yeah, you’re able to be a very comfortable with the [00:22:00] technology, talking directly with engineers. Inside your company and outside of it, and and really wrestling with different customers or competitors or to finally agree on the size of the cup, the noodle cup.

    That’s pretty cool. I love it. Could you share a little bit about Your approach to recruitment and what strategy you find most effective to, for assembling a team.

    Maria: Wow. This is, this is great because I just recently had two recent hires that I’m extremely proud of of having found them. I think I take recruiting with, you know, this is my job, not just outsourcing it to the, to the HR team or the talent acquisition team or another recruiting firm or whatnot.

    I think that understanding. Where I would like a team to, to be and fit and to see if those folks [00:23:00] are also going to be great fit for the current and existing team and whether they’re also going to come and catalyze the team and sort of bringing new perspectives based on where we want to go is also very, very important.

    And so I, I reach out to, I think like anybody else does like to my network. I reach out within the company, outside of the company. And then I usually try to find a diverse group of folks to help me with a, with a strong panel that can not only challenge, the applicants, but also challenge me in, in what they expect my team to be.

    So I also try to bring them in, in the recruiting phase. If we’re going to, to be collaborating in the future, because, because of this specific thing that I shared before, like we’re bringing somebody in, we want, we want them to feel valued, but also add value and help them grow. So I, I invite the rest of the team and I was happy to say that I also tasked them with with the opportunity to recruit or just to [00:24:00] bring and help shape the positions that we’re in.

    So I take more time than I would want, I think recruiting, but I think it usually pays off. I’m very happy about the team I’m putting together.

    Alexis: I hope they will listen to the episode to, to hear that you’re saying it out loud to the world. That’s pretty cool. Looking at what, what are some of the key areas of focus for you and your team at Red Hat.

    Maria: I’m in the field. So as a CTO I’m still part of the engineering organization. So what we are looking for are moments to, to co engineer with customers. So beyond just. The products that we have today, the communities of open source that we engage with today, just find and understand use cases of where the industry is going.

    Whether it’s, I don’t know, telco, FSI financial services, or, or even communities focusing where other, other industries are, are engaging with health and sciences [00:25:00] or insurance companies, et cetera. We try to. Come together and be a trusted partner where this new technologies, they can understand this new technologies and how it can affect or move the needle for their business and then creating spaces or other sometimes they’re competitors, sometimes not competitors, but they’re in the same sort of vertical.

    for customers to come together and see how they’re using our technologies and other technologies in addition to that. Because that way they don’t feel so sort of lonely or alone following their own technical trajectories, but they can build a roadmap that aligns, not just with their business, but understanding other adjacent business.

    And so, And we help create that community between customers as well. Because we know this is sharing ideas in this way is, is the way to move, to move things forward. And now selfishly that also helps us validate and [00:26:00] understand the, where Red Hat is going, where we should be investing, where we see spaces, where it makes sense for us to invest more maybe or, or ways in where, in which we can, we can be effective to, to other businesses.

    Alexis: Hmm. And you are a CTO and will you, will you say anything about AI or, we are in, in the midst of the hype of ai, so there is, there’s nothing you are doing about it.

    Maria: I have been planting seeds about that since the very beginning. So even with the ramen story, I, I also planted the seed and made a allusions to, this is pretty much how Linux started. And you know, we made recent announcements just last week. We had Red Hat summit in Denver. We have some of those presentations up in YouTube that release some new, some new cool products and, and others that are in sort of tech preview, but One of the, one of the big announcements was RHEL AI, which [00:27:00] naming a product as a product manager is one of the hardest things to do.

    But for us to name RHEL AI, RHEL AI, it could have been another name, right? But for us to call it. Red Hat Enterprise Linux AI and attach AI to that known and trusted brand means that we’re very serious about moving into the AI space. And I think we’re doing it in the most Red Hat way in some in a way that is very authentic to the mission and vision of the company.

    Of being catalyst in, in communities of customers, partners, collaborators to, to move it forward using open source. So we also made an announcement around an, a new invention called instruct lab, which helps modify large language models, which is a, which is really a novelty because any other technique to train a model has been done like rag, for example.

    at the inference stage, [00:28:00] but having the ability to influence a model itself to change the actual model is something that was not accessible to regular humans. You needed a data scientist to, to be able to do that. So I really love that we’re democratizing the access to, to models were influencing I think in this case, IBM to open sort the granite family of large language models that, that is huge.

    And then having a way. For anyone to modify a model a from their computer. Like you have a laptop. You can do this. This is something that if we see the current models available, even if they have open in the name you don’t really know what’s in there. Having the ability to have a models where the code is available Openly cited with the data that it was trained on.

    So you know exactly what it was trained on and the ability for you to use it, modify, train it with your data [00:29:00] and keep all of that private is is very, very interesting and compelling. So we’re really hoping to catalyze this industry and really excited to. to what’s to come. Kind of same as the beginning, like Momofuku Ando just trying to preserve a noodle.

    We’re starting small and we are eager to see where this can go. Understanding and being not a hundred percent naive, but a little naive to what it would, where that would go, like how far it can go. And all we have going for us is, It’s just the experience that we’ve had with Linux. So that’s really, really exciting, Alexei.

    I think we’re at an inflection point here and I’m, and I’m happy to be part of it.

    Alexis: I love it, Maria. And that will be my last question. What advice would you give your younger self?

    Maria: Wow. [00:30:00] Ah, you know, I have a 16 year old daughter that I give advice to. And she looks just like me and likes things just like me. And sometimes I wish she wasn’t so like me, but the, the advice that I tell her is sort of the same thing that I, that I did is just work hard, continue to be authentic to, to who you are and what you believe and.

    And then be open to be open to feedback, open to learning. You will find places where you can continue to, to shine and places where you can continue to learn. And hopefully that will be leading you to a fulfilling and happy life.

    Alexis: I love that. I continue to explore. That’s beautiful. Thank you, Maria, for having joined the podcast today.

    Maria: Thank you. It’s a pleasure. [00:31:00] 

  • Engineering Leadership at Scale: Navigating Complexity and Change with Tamar Bercovici

    Engineering Leadership at Scale: Navigating Complexity and Change with Tamar Bercovici

    When engineering systems grow large enough, leadership stops being about control.

    That is one of the strongest messages from my conversation with Tamar Bercovici, VP of Engineering at Box. Her team supports a platform used by tens of millions of users and stores massive amounts of enterprise content. At that scale, leadership becomes a different discipline.

    From individual contributor to organizational leader

    Tamar describes two major transitions in her career.

    The first was moving from individual contributor to manager. Like many engineers, she found the transition awkward at first. The work changed. The definition of success changed. The challenge was no longer writing great code, but enabling others to do so.

    The second transition was even bigger: moving from managing teams to managing organizations. At that point, leadership is no longer about direct influence. It is about creating the conditions where many teams can succeed simultaneously.

    Each step required Tamar to rethink what she was accountable for and how she measured her own impact.

    Scale changes the leadership game

    One striking aspect of the conversation is the ratio between scale and team size.

    Tamar leads a core platform organization of under 200 engineers supporting one of the largest content stores on the web. That reality forces a very specific leadership approach: you cannot control everything, and you should not try.

    Instead, leadership becomes about context. If engineers understand why something matters and what outcome they are aiming for, they can make good local decisions without constant oversight.

    Change is the job

    Large-scale engineering leadership, as Tamar puts it, is largely about leading through change.

    Infrastructure migrations, cloud adoption, evolving customer needs, new technologies like generative AI – none of these are static problems. They require continuous adaptation.

    Tamar emphasizes three principles when leading change:

    • Make the change your own, even if it was not your decision
    • Be transparent about why the change is necessary
    • Avoid both sugarcoating and venting

    Leaders must own difficult messages while still providing a credible path forward.

    Clarity beats control

    One of Tamar’s most practical insights is deceptively simple.

    If you stop someone in the hallway and ask them what the next milestone is, they should know the answer.

    That level of clarity allows leadership to scale. It enables teams to move independently while still rowing in the same direction. Without it, leaders are forced into constant intervention, which quickly becomes impossible at scale.

    Risk is not the problem

    Another powerful reframing Tamar offers is about risk.

    Risk is not a sign that an initiative is wrong. Anything meaningful carries risk. The real leadership work is to name the risks explicitly and then de-risk early and continuously.

    That can mean prototypes, pilots, staged rollouts, load tests, or customer design partners. Whatever the form, the goal is the same: reduce uncertainty before it becomes failure.

    This mindset turns large programs from fragile plans into adaptive systems.

    Innovation on top of foundations

    After completing a full cloud migration, Tamar’s teams are now focused on optimizing and innovating on top of a more consistent platform. The emergence of generative AI is a natural fit for Box’s role as a content platform.

    What stood out was Tamar’s realism. AI is both hype and substance. The technology is moving fast, best practices are still forming, and customer expectations are evolving in real time. Leadership here is not about having all the answers, but about learning faster than the environment changes.

    Advice worth remembering

    When asked what advice she would give her younger self, Tamar did not point to a specific career move. Instead, she spoke about reducing the emotional weight of decisions.

    Careers, like software, are iterative. Choices are rarely irreversible. What matters is making a choice, committing to learning from it, and adjusting when needed.

    At scale, leadership is not about perfection. It is about intentional progress.

    Here is the transcript of the episode

    Alexis: Welcome to Le Podcast on Emerging Leadership. I’m your host, Alexis Monville. In today’s episode with Tamar Bercovici, we’re diving into the art of leadership within the tech industry. Tamar, VP of Engineering at Box, has led her team through groundbreaking transformations, bleeding the art of building high performing teams with the science of developing innovative technologies.

    Join us as Tamar shares her journey from a software engineer to a visionary leader at Box, revealing her strategies for building teams and steering her team towards continuous innovation. 

    Welcome Tamar. Could you share how you typically introduce yourself?

    Tamar: Hi, it’s wonderful to be here. My name is Tamar Bercovici. I’m a VP engineering at Box where I lead the core platform. So at Box we’re building out the, the content layer for the enterprise and the core platform is [00:01:00] the underpinning of our product. So a lot of Distributed systems type challenges high scale challenges, but also the backbone for the product.

    So thinking about what the right abstraction layers are been at box for 13 years. Yeah, that’s me.

    Alexis: Excellent. So what drives your passion for technology and leadership?

    Tamar: I think the technology space is just fun. You know, it’s a really unique combination of, hard, interesting, intellectually challenging problems combined with a lot of customer empathy and, and human empathy and, and a lot of creativity. So I think there’s just a really unique mix that we get to, to think about problems from a lot of different angles and a lot of different perspectives.

    And then leadership is something that I, You know, at some point in my career, I shifted into a managerial position and sort of as an experiment, but I think I learned [00:02:00] that there’s something very compelling about teams and how you bring people together and align their energies and their passions and their talents to accomplish a goal together.

    Like there’s, there’s, it’s, it’s a really unique type of challenge in and of itself, how you do that. But then there’s also something very. I think gratifying of working in that way. It’s something that I like. So you know, being in a leadership position is enables me to create that for myself and for my team.

    And it’s something that I’ve really enjoyed over the past years.

    Alexis: So me a, give me a sense of the scale of what we are talking about. That’s what are, what is the size of your team? And on the other side of how many users do you, do you have? How many customers are we talking about?

    Tamar: So, so box focuses primarily on enterprises on businesses. And we have, you know, businesses all over the world as customers all different industries, all different sizes from, you know, very small companies to. [00:03:00] Some of the largest organizations that we have and and then the users are the employees at that in those companies that have seats at box, plus, you know, individual users, of course, as well.

    And so in terms of the scale of users, it’s in the tens of millions, but some of the interesting elements of box platform specifically is that is the scale of of content that we store on the platform. So we’re probably leading one of the largest just content stores on the web and that has a lot of interesting challenges just It’s straight up in the, in the storage itself and uploads and downloads and managing copies and encryptions.

    And it’s just a, a very sort of unique challenge in and of itself, but then also the system and the product and the, the, the metadata around that, that enables the product experiences an interesting scale challenge as well. 

    Alexis: With users in the tens of millions what is the size of the team managing that core platform?[00:04:00] 

    Tamar: so we, we run a relatively lean engineering team, I think, for the scale of the company. My team specifically on the core platform is just under 200. And that’s again for Sort of all of those core parts of our infrastructure, the storage infrastructure that I mentioned our data stores eventing systems search index metadata stores and then kind of the, that core backbone business logic layer.

    So recently AI platform thrown in there as well. So a lot of those, those sort of fundamental components and then within box engineering more broadly, we have. Teams that are focused on just kind of the pure infrastructure layer to make sure we have the right environment to operate our systems.

    As well as of course, all the teams that build out the product experiences themselves.

    Alexis: I still find that incredible that that’s, that’s a very small team compared to the challenges. But yeah, that that’s perfect. That’s really good. Tell me more about your, your transition from an individual contributor [00:05:00] to a management role and the.

    pivotal moment in the decisions to do that.

    Tamar: I joined box as an engineer and I was actually coming off of finishing up a PhD in theoretical computer science and my goal at the time had just been to, you know, To kind of get back into industry, get back into a startup environment. I had a previous experience working at a startup company before, and I really like that sort of somewhat more chaotic and flexible and dynamic experience, and then also just being.

    Very connected to the business and the customer and what we were trying to build. So that was sort of what I was looking for. And I specifically wanted to get into web, like box is actually the first web company that I worked at. And after joining as an engineer, my first biggish Project was around building out the initial scalability layer for a database infrastructure.

    And one of the interesting things that you go through in an early stage company, you sort of shift from [00:06:00] very generalized roles to incrementally sort of more specificity in, in what you own. So I joined a, a six person backend engineering team that kind of owned all of it. So, you know, at any given time you had one person who happened to be working on the storage infrastructure, one person who was working on databases.

    Right. But it wasn’t like, There was a lot of specialization there and it was fine. It was appropriate because it was a much simpler stack. But then as the company was scaling and we had to scale out the, the infrastructure to support that you’re now building more complex systems. There is more value in investing in those systems, but then also as you make those investments, you increase the complexity.

    You now need people who specialize in the system. So you sort of go through this process of all of a sudden having differentiated teams. And I have a team that owns storage and a team that owns databases and so forth. And so again, I had kind of Thank you. Been a part of that, that database project that [00:07:00] shifted it from very simple, single database to a somewhat more complex infrastructure.

    And I was faced with that decision point of staying on the technical track or, or, or trying my hand at management. And I debated it a fair amount. And I, I feel like actually it was hard to get good advice on this. It It felt more consequential at some level than it should have, because honestly, this is the kind of decision that you can undo.

    Like I’ve, I’ve I’ve had multiple people who sort of shifted into management and then decided at some point that that was no longer the path they wanted. They went back to being individual contributors, but that experience actually gained them a lot of, I think, insight and perspective on what it takes to, To lead an engineering team to have a healthy engineering team.

    And so it enabled them to be better engineers, I think. And then there was also a lot of muddiness in the conversation around is engineering management, a technical role or not. And I wanted to stay in a [00:08:00] technical role, but at the end of all of that debate I decided that management was going to be a bigger departure from what I had done thus far.

    And I was curious. I wanted to try it out. And I think that initial transition is awkward for almost everyone that, that I have ever either talked to or, or, or managed who was going through that. And definitely for myself, it, you need to redefine what it is that your job is and how you. Assess your success or failure in your job.

    I think it becomes a little difficult to separate yourself from the people on the team that are doing the work. So it took a little bit of time. But I think once I wrap my head around that, I found that I really enjoyed it because again, it let me. Look at the same set of problems, but from a more kind of well rounded, multiple angle type perspective.

    And I just I like that. And so I, I [00:09:00] really enjoyed it. I felt like I was learning and growing and decided that this was the right path for me. And I think that that was sort of the first big transition. And then I think that the second big transition is sort of further on when you shift from managing teams to managing organizations.

    And again, understanding what that requires and how you need to shift what you do and what you hold yourself accountable. It’s again, to some degree, a different role. So I’d say those were sort of the two big, big moments.

    Alexis: Excellent. Thank you. Thank you for that. Can you discuss some strategies you’ve employed to foster a thriving engineering culture?

    Tamar: I think. This is the 1st thing is you have to work at a company as a leader in particular. If you’re not the CEO who’s sort of setting this tone for everyone, if assuming you’re working. You know, for someone, I think it’s important to find a place that your values [00:10:00] align with that, that, that the culture aligns for you, because as a leader, it’s a, it’s really important that you are modeling and reinforcing that culture and those values.

    And so finding a good place to work is, is I think key so that the investments that you’re making are synergetic with what’s happening more broadly within the company. And then I think a lot of it is. At the end of the day, all of us, no matter what our role is, I think good employees, like what do we want?

    We want to be challenged and have opportunities to grow. We want to work with a good group of people and we want to make sure that we’re having impact, that our work matters, right? People, if you’re working at a company, then, then, then generally you want, you want that to, to be somehow contributing to what’s important.

    You want to understand why, what you’re doing is important. But by the way, because any job has. Sort of the less interesting parts, like any job, every, every single role, every single job has the exciting bits, the challenging bits, the, the, the, the flashy [00:11:00] ones. And then the more run the business aspects or the more the, the less exciting aspects.

    And so you have to be somehow motivated by the importance of what you’re trying to accomplish. And so as a leader, Yes, making sure that it’s, it’s sort of that good, good cultural DNA and that you’re reinforcing that within the team and setting that tone from, from yourself, but then making sure that the team has a, a compelling thing.

    Goal or set of goals to strive for and that people really understand how what they’re doing fits in with what we’re trying to accomplish as a business and have that context. I think that’s how you get engineers or whatever role they’re in at the company that understand what we’re trying to accomplish and can hence.

    Make better localized decisions, feel more empowered, be more engaged and actually deliver better results. So fundamentally that alignment of what we’re doing to business impact, it [00:12:00] sounds sort of straightforward, but I think it’s, it’s very foundational to having a healthy culture and engaged engineers.

    Alexis: And so I assume that as a, as a lot of people managing through through changes is can be challenging. Do you have examples that you can share that, and that were really challenging and what have you learned through those, those examples? Hmm.

    Tamar: I think a lot of leadership is. Chain leading through change, right? You know, our organizations are very rarely stagnant, right? There, there’s an evolution of what we’re trying to solve for, what our goals are, what’s challenging, what isn’t you know, ups and downs in the business that you need to contextualize as well as just, you know massive challenging projects that you need to lead the team through that, that cause big shifts.

    So it, whether it’s sort of a. More of a like corporate context or a people, [00:13:00] HR or process or technology at some level, a lot of that is what we do as leaders. And I think there are some commonalities for all of those, which is you have to understand whether it’s you sort of driving, like you’re making the decision and causing the change or whether you are.

    You know, you have to make it your own, you have to understand why it is that we’re doing what we’re doing, why do we need to make this change? And what are we solving for so that you can be very transparent with the team? Again, change is always uncomfortable, we all have a little bit of that reaction of like, oh, you know, what’s happening?

    I feel unsettled. I don’t know where this is going. But having that context on why we are dealing with this problem and, and what we are. What we are hoping to accomplish sort of transparency, even if it’s about the challenging things is really important, but then in particular, if it’s challenging.

    You know, striking that balance of making sure that you’re, you’re not sugar coating and kind of glossing over [00:14:00] the critical parts, but then that you’re not over almost like over empathizing with the negative and effectively like venting or ranting to your team. Like you have to, you have to own the difficult message if it is difficult and then you have to.

    Show sort of why are you optimistic that we are going to navigate this change successfully? What do we need to do to make this work? What are your expectations of the team? And then everyone kind of understands, understands that context and knows how to approach it. I think specifically in the context of, of sort of, I’ve had the opportunity at Box for, for whatever reason to.

    To lead us through several sort of big infrastructure migrations, which are, you know, think, you know, very large scale efforts we had some that were sort of shifting. Between various on prem data center environments, which is still a quite complex endeavor to shift your entire infrastructure from one place to another.

    And then more recently, [00:15:00] we completed a sort of a full migration from all the workloads that we had on prem into the cloud. And that’s something where. You need everyone across all of their different services and, and, and, and tool sets and libraries and, and, um, corpuses to, to, to figure out sort of the right set of things to do localized while also having it be part of that, like overall migration cadence and how do you wrangle something like that?

    And so again, it’s, it has to start first and foremost with a. With a ruthless clarity of goal. Like everyone needs to know what we’re trying to accomplish and why. So that as they’re making localized decisions, they make them in a way that’s synergetic with the overall goal. There’s no way that you can go control every little last thing that, you know, hundreds of people are doing.

    Even 30 people, I don’t think that’s feasible. So definitely not a whole organization. And [00:16:00] so having that clarity of goal and then having even clarity of like, what are, if there are any sort of interim milestones that we’re trying to hit as a team, like really making sure that those are simplified to the point that people, if you ask them, if you stop them in the hallway and you ask them like, Hey, what’s the next milestone we’re working towards, they’ll know what that is.

    And that can give you the confidence that because we trust that we’re building a a high performing team across, across the, the, the floor, if people know. what they need to solve for, they’re more likely to be able to make those good localized decisions. And then it all kind of like connects together and you’re able to steer that, that unwieldy process to a successful conclusion.

    Alexis: Yeah. I like, I really like. How you framed it. It’s very interesting there’s the need to understand why we are doing something and to own it and to make it your own. That’s not, even if the changes is pushed on you in some ways at some point you need to make it your own. And and you need to make [00:17:00] sure that finally everybody knows why we are doing something and what we are aiming at.

    And there’s those intermediate milestones that we’re aiming for. That will really enable decisions by the people who are, who are doing the work. And I, I feel there’s a lot of things to connect there that are really important. I am capturing all of that.

    Tamar: Yes. Yeah. Yeah. That was a a great recap. I think it’s, you want to increase the chances that all the decisions that are being made, you know, you scale out by enabling people to make good localized decisions. And you do that through context and, and through that sort of drum, like the high level drumbeat and through a lot of communication.

    And then, you know, Of course, there’s, there’s more to this, right? You need to have some, some signals that you’re rolling up to tell you how things are going so that you know if a particular area is falling behind and maybe you need to dive in more like it’s, it’s never as simple as it sounds in, in the podcast.

    [00:18:00] But, but I do think that sometimes we almost like, Jump over that 1st part and start diving into the hard problems that we know exist. But then if you, if you do that too quickly, and you don’t take the time to set that overall context for everyone, you’ll, you’ll have more problems as you go along. I think maybe 1 more thing that I would call out in the context of any.

    And he’s sort of large scale change. They’re always risky in some way, right? Like there’s, there’s some element of risk on will we be able to successfully make this change and will it have the impact that we expect it to have? And I think sometimes people interpret the risk as a sign. That this is a bad idea, or that maybe we shouldn’t do this or they sort of make plans that assume no risk and then say, but this plan is at risk because there’s a lot that we don’t know.

    There’s sort of this kind of Handling of risk that’s maybe not what it [00:19:00] needs to be. And I think it’s important. And this is something you can do as a leader as well, again, to sort of frame that for everyone to take a step back and say, there’s nothing of value that is without risk. So the fact that there is risk is not a problem because we know that this is risky.

    We have to ask ourselves concretely, what are the risks that we’re concerned about? Right. And then once you’ve called out the risk, you make a plan to de risk. So it’s not about knowing everything. You sort of assume that as you’re going through this process, there’s an ongoing level of risk that you’re managing.

    But managing the risk is not just acknowledging that it’s there, but rather figuring out it. It’s usually about de risking as soon as you can, right? So is there a POC that I can do? Is there an initial test? Is there a load validation? Is there an integration point? What can I do to, is there a customer? A user study, a customer test, a design partner, like depending on whatever the project is, it [00:20:00] doesn’t matter if I’m rolling out a new process change, can I roll it out with an individual team to help them iron out the kinks?

    Like what is the risk of the thing you’re trying to take on? What are the ways it could fail? Actually spelling those out and then putting in place actions that help you reduce the risk of that happening. And at some level, that’s how you manage the program. And so if you have clarity of goal. And you have clarity of everyone within their own areas, de risking towards that goal.

    That is the best way that I know of to increase the chances of successfully hitting that, that outcome that you were hoping for.

    Alexis: I really love that that idea that there’s things that, you know, that’s good. You need to make sure that, you know, why, why you know them and there’s things that you don’t know, and then you need to conduct experiment and so that, you know, a little bit better, those areas you don’t know. I really love that.

    That’s that’s perfect. Thank you very much. Looking ahead What are some, some of the key areas of focus for you and your [00:21:00] team, and how do you plan to continue innovating 

    Tamar: I think there are some areas that are almost a constant, but that is a good thing. If you’re running any kind of large scale infrastructure platform system, you’re, you’re always thinking about, you know, Performance availability, efficiency, you know, all of those kind of fundamental foundational components.

    And the reason hopefully you’re always thinking about them is because the scale of the business is growing. The scale of the customers is growing that the types of. Especially in an enterprise context, the type of work they’re trying to do on top of your platform is becoming more sophisticated, more critical, and hence their demands of you are growing.

    So all of these are good signals. Like if you constantly feel like you have a More to do to, to keep kind of ahead of the business needs in terms of the scale at which you can operate, then that’s a [00:22:00] good sign. And so that is often and always a key focus area for us. I think in this year, in particular, after.

    Completing our cloud migration. There’s obviously a lot of optimizations and, and improvements that we’re now able to make by having everything in sort of this more consistent modern environment. So we have a lot of focus there. And then at the product level, we’re at a really exciting inflection point at the company with a lot of interesting momentum coming together, both from kind of macro trends, as well as just things that have been building up within box to, to really.

    Enable our users to leverage, to, to get value out of the content that they have on our platform in new ways. The whole sort of AI generative AI hype cycle that, that we’ve been in, it is a hype cycle on the one hand, but on the other hand, it’s, it’s It’s a real sort of kind of suite of technological.

    It’s [00:23:00] technologies that are building up for years, but they’ve sort of gotten to that point of capabilities as well as kind of market recognition where all of a sudden, it’s really compelling. And, and if you think about it, they’re, they’re very good with unstructured Content with, with, with human text.

    And what is, what is box, if not the platform where you put all of that data. So, you know, when this, when this was kind of exploding you know, around a little over a year ago, we were kind of, you know, we were all just as, you know, anyone who’s a technologist and following the field is like, wow, this is, this is so exciting.

     I didn’t think that we’d so quickly get to the point that, you know, things like the Turing test maybe need to be rethought in terms of what they mean. But then at the same time, we realized how relevant this was to our product and to our users and really thinking about how to completely shift the paradigm around what type of value you can get from the content that you have on Box.

    And it’s, It’s really interesting to try to [00:24:00] connect like the technological capabilities to solving real customer problems and delivering real value in a space that’s so emerging, right? There isn’t a paved path of here’s what, you know, successful use of this looks like. Here’s what the customer expectations are.

    You’re, it’s kind of, you’re figuring out all layers of it all at once. The, the underlying, excuse me, the underlying technology is, is just. Shifting so quickly and then the best practices on how to leverage that and how to build product from that are shifting so quickly. And then, and then what the customer wants and even how to price it like the whole thing is in a state of flux.

    And so it’s just been really fascinating this past year building out the foundation for that. And then looking forward, I think we just have a few really exciting ways in which we’re going to Continue layering intelligence through our platform to really enable new and compelling use cases.

    Alexis: Excellent. I love it. [00:25:00] So to close what advice would you give to your younger self?

    Tamar: it’s always hard for me to answer those questions because at some level, I’m a bit of an optimist and so I think even the challenges and the bad decisions that we make or, you know, the places where we derail a bit, I see the value of the learning from each of them. But maybe at some level, that is the advice to not.

    I think sometimes when you’re at the beginning of your career, a lot of decisions feel very consequential. It’s like, I’m now making this choice and this is like, this is going to be the trajectory of my life. And it feels. the emotional burden of that can, can feel high. And it’s true that , when you’re further through and you look back, you understand how each and every one of those choices built to where you are today.

    But that’s not to say that had you made different choices, you would not have Similarly, been able to have a [00:26:00] compelling path. So I think just like software development is a very incremental process, right? We’ve we’ve sort of collectively as an industry with the advent of web learned this process of iteration and making small changes and and getting it Data validation and then tweaking and adapting and adjusting.

    And at some level, our careers are no different, make a choice and then optimize for whatever choice you made. And if at some point it feels like that’s not the right thing, you know, make the next choice, but you’ve, you’ve learned something and get, as long as you’re intentional about what you’re doing and you.

    Apply your energy and you stretch yourself to learn and grow sort of with every phase then that even the ones that don’t go so well, I think end up adding another rung in your ladder to wherever that ladder is leading. So I think that the advice would be to not be too worried about those things and just make a choice and move forward and see where it takes you.

    Alexis: I love it. That’s a very [00:27:00] beautiful one. Thank you very much for having joined Tamar.

    Tamar: Thank you. Thank you for having me. This is great. 

    Photo de Jeremy Bishop

  • Trust, Excellence, Customer Delight

    Trust, Excellence, Customer Delight

    Engineering leadership lessons from Bruce Wang (Netflix)

    Some leadership philosophies sound good on a slide and collapse the moment reality arrives.

    Bruce Wang’s doesn’t. It is simple, grounded, and demanding. In our conversation, Bruce, Director of Engineering at Netflix, describes the three pillars he tries to balance every day:

    • build a trusting team
    • seek excellence and mastery
    • drive customer delight and value

    The tension is the point. You cannot maximize all three at once. Leadership is the ongoing practice of balancing them without drifting into extremes.

    Trust is not given, even inside the same company

    Bruce joins a new team at Netflix and starts with a clear assumption: people will not automatically trust him.

    Yes, reputation helps. But trust still has to be earned. He talks about building what he calls vulnerability-based trust: showing you are a person, not a role, and creating space for honest questions and challenge.

    One practice I loved: asking people who worked with him before to share “what’s wrong with Bruce” in front of the new team. It is a direct way to make psychological safety concrete. Not as a slogan, but as a lived behavior.

    Vision first, then structure

    Bruce describes a sequence that is easy to underestimate.

    First, get clear on what the team is here to do. Not the tech. The purpose. The customer value. The essence.

    Then, and only then, decide the team structure: the balance of managers and ICs, the domains, the diversity of the group, the shape needed for where you are going.

    If you start with structure before direction, you end up optimizing for today and paying for it later.

    The leader’s growth edge: letting go

    Bruce makes a point that shows up again and again when leaders scale.

    At first, you lead individual contributors. You are close to the work. You can shape direction through direct interaction.

    Then you grow managers. And that changes everything. You have to scale yourself through others. The hard part is emotional, not intellectual: letting go of being the center of the system you helped build.

    In his words: sometimes growing the team means letting go.

    Process is not the enemy

    Netflix is famous for “people over process,” and Bruce names a subtle trap: teams sometimes treat process like a dirty word.

    But deploying code is a process. Offsites are a process. Coordination is a process. The real question is not “process or no process.” It is: what is the lightest structure that helps the team do better work?

    Bruce’s approach is principle-based. Try something. Keep what works. Throw away what doesn’t. Do not force a framework just because it is fashionable, or because another successful company used it.

    He adds a useful warning: copying Netflix practices without Netflix context is risky. What works in one environment may fail completely in another.

    A failure mode worth remembering: the shortcut that breaks trust

    Near the end, Bruce answers the question I wish more leaders asked themselves: what are your failure modes?

    He shares a clear example: he moved too fast to present a vision, collaborating with one strong supporter but not building shared alignment across the broader senior engineering group. The result: pushback, confusion, and a hit to trust.

    The lesson is sharp: speed can look like leadership, but shortcuts often bypass the very collaboration that makes strategy real.

    If you take one line from this episode, let it be this: before you go fast, check whether what you are doing is a shortcut.

    Leadership as a humble gardener

    Bruce references Team of Teams and the image of the leader as a “humble gardener.”

    It fits this conversation perfectly. The job is not to be the hero. It is to cultivate the conditions where people can grow, do excellent work, and deliver customer value.

    Humility, curiosity, and continuous learning are not soft traits. They are operational requirements.


    References mentioned in the episode

    • Winning Now, Winning Later by David M. Cote
    • Team of Teams by Stanley McChrystal

    Here is the transcript of the episode:

    Alexis: [00:00:00] Welcome to the podcast on emerging leadership. I’m your host, Alexis Monville. Today, we are diving into the art of leadership in tech, building and sustaining excellence with our distinguished guest, Bruce Wang, director of engineering at Netflix. Bruce brings a wealth of experience from the intersection of tech, business, and team culture.

    His journey from a hands on developer to a leader focused on people leadership, culture cultivation, and mentoring offers invaluable insights into the evolving landscape of tech leadership.

    Welcome to Le Podcast on Emerging Leadership Bruce.How do o you typically introduce yourself to someone you just 

    Bruce: I’ll probably just say, Hey, I’m Bruce Wang. I’ve been an engineering leader for about 20 plus years two time founder. And currently I’m a director at Netflix.

    Alexis: Excellent. Thank you. can you tell me about your key principles [00:01:00] and how they are essential to, to build an engineering 

    culture? 

    Bruce: Yeah, I have sort of this guiding leadership philosophy, right? I call it trusting team seeking excellence, driving customer delight. And so what I’m trying to kind of convey is sort of these three pillars for that. That every leader needs to balance, right? So how do you build a trusting team? How do you seek excellence and drive mastery? And how do you make sure you’re delivering customer value, right? And usually the challenges of engineering is keeping those in balance, right? And what I’ve learned over time as a leader is it’s all about the balance. You can’t get all of everything. You got to figure out how do you balance between these three?

    Because sometimes maybe like you would break trust with a team if you have to do something on the seeking excellence side. Right. And so how do you balance that and make sure that you’re doing it well. And so all of [00:02:00] my sort of sub values and things I think about is under that principle.

    Alexis: can you share your approach growing? A team of really starting something and, and help that team grow. 

    Bruce: Yeah. You know, it’s funny. Cause I was like trying to think, do I have a formula and you know, it’s, and it’s interesting because just so you know, I’m actually taking on a new team in a week. And so I’m switching roles

    and so I’m trying to think like, what do I do? Right. So this is, so I used to run a team called product platform systems. I’m sure by the time this releases, I will have the new job, which is a games platform and you know, it’s within Netflix, but it’s a totally different group. Right. And so I’ve been thinking about like, how do I, what do I do with this new team? Right? Like people know me but you know, not everyone right on the team. And so I think the first one I typically do with any team is. Set a vision first for [00:03:00] myself. So what what is this thing? I’m leading like what does this team do? What’s the essence their core, right? I think a lot of people think oh, this is the technology we build It’s like no no, but what’s the thing we’re driving at this goes back to the customer delight, right? Are we here for? Like our purpose, right? And 

    I actually wrote this memo for myself to figure out Why are we doing what we do? And in this particular team right in the games platform team, right and it’s a newer team You know, I don’t I don’t know if people know but netflix actually have games and that’s a growth area for us, you know over the next several years. And so it’s very Interesting. Kind of a little bit like a startup, right? And so I think for me, it starts with sort of that vision of what the team is and could be. And then from that, the next is who do you have? Who’s there? What are you building? Like, [00:04:00] what’s your team structure, right? The other anchor point you know, building trusting teams is really around the makeup and diversity of your team. Who do you have? Do you have the right parts? Do I have enough managers? Do I have enough ICs? Are they focused on the right areas? And so here’s the thing is like, if you think about a leader, how do you decide the right team structure if you don’t know where you’re going? Right. And so that’s why for me, it’s like know where you’re going and then figure out the team makeup. Right. And then the last part,

    I think this is the seeking excellence piece, which is, all right, what do we need to do now and do well, right. To deliver value. Right. And so it’s kind of like the vision, the team structure and our goals, right? What are we trying to do? And for me, I have a philosophy that I’ve written in my github page. And this is from a book called when now, when later, but winning now, winning later, which is like, you have to do tactical as strategic at the same time. Right. And so the goals that we have set is like, we have to deliver on 2024 goals. [00:05:00] We also have to prepare. For 25 and 26 and beyond. And so I think that that’s like kind of the, for me to get a team in a good place, you’re kind of building those sort of three things together. Now underneath all of that, you know, foundation to everything is trust. How do you build trust with the team? How do they trust you as a leader? Right? All this stuff does not work without trust, right? So that’s why trusting teams is so, is the first thing for me, is because, you know, I think you know this, if you don’t have a trusting team the vision is not going to make sense, they’re not going to trust you, right? The goals, they’re not going to push, and definitely hiring and conveying what the team structure is they’re not going to believe you. So I think that’s So, you know, like underneath that is constantly building trust with the team.

    Alexis: help me understand that. So I’m a, I’m one of the engineers on your team, hypothetically, not I don’t know. You, you, you are the new [00:06:00] of that team. Do you believe, I will trust you like 

    this. 

    Bruce: So in this particular, no, you won’t, I have to earn your trust. Now I do have a slight advantage in the sense that I have been here for four years, so I’m not some random person coming in from the outside, you already have seen. Multiple outputs of what I do and how I think at the company. And, and so the good thing is my reputation precedes me. I hope in a good way. I think people, you know, I have team members who actually used to work for me who actually advocated for me. Which is always nice to hear. Honestly, as a leader, like that’s the only criteria, do they actually want to work with you again? And so that comes with some level of credibility, right?

    So I’m not starting from scratch. But I’m doing actually something very early. I believe in vulnerability based trust, right? And so here’s what I’m doing. One is, you know, setting that vision doc early is to say, Hey, I want to learn more about the business, right? And I want to learn and [00:07:00] define a future that’s exciting for all of us to pursue. But the second is, The day I start, I have a town hall where it’s about me, right? Like, Hey, learn about me, read, read my leadership philosophy doc. You know, here’s my intro to me as a person, right? I live in San Francisco, you know, I have wife and kids, but, you know, like these are the things I like. I love food, right?

    I love travel, all that stuff. Right. And then something I’m doing is have the people who used to work for me, that’s on that team now giving. Verbalize critical feedback. They’ve given me in the past. What’s wrong with Bruce? Right? And you now as a leader, you have to be careful because coming in new vulnerability also has to be earned over time, right?

    If you just be like, I don’t know anything that’s not going to instill confidence, right? And so you kind of balance the like, I know what I’m doing, I think, but also I’m not perfect. You know, [00:08:00] I’m not infallible. I have, you know, I have weaknesses just like anyone else. So that’s how I’m doing it is right away. Try to build through that closeness of, Hey, I’m a person. And you know, I have flaws and then ask any questions and actually. I continue to encourage people, ask the spicier question the better, challenge me, question why I’m in this role, question what are we doing here push me hard, because what I’m trying to convey to the team is, I want the openness to discuss problems, I want us to be open about where our challenges are, you know, inside the memo that I wrote, actually I list out all the things I heard that is difficult for us as a team, And just wrote it out, like verbalized it and said, yeah, I know it’s really hard to be a startup in this giant company who’s been around for 25 years. Let’s not underestimate how hard that is, right? So that’s an example of [00:09:00] like, this is a difficult thing to do. And so that’s kind of like tactically what I’m doing as well is just introducing myself, but not not just, oh, here’s who I am, but like, kind of learn a little more deeply about me. 

    Alexis: I have to admit I loved I, I would love to hear the segments wrong about Bruce. There are people that know you. I love the idea. I need to do that. The, the other thing is when you said you write the memo about the vision. Why are we doing what we do? That means you’re not doing that in isolation.

    You’re, you are interviewing a lot of people probably the team and in the 

    Bruce: well, and that’s the thing is I wanted to be careful, right? Because when I originally wrote when I started writing the doc It was for me to like write down what I thought this team was doing and I’m like, I don’t know enough so instead the memo became more like embrace hard mode It went from, like, specific, tactical, here’s the technologies we need to work on, to, [00:10:00] we need to embrace the challenges ahead of us.

    So it became more of an inspirational, yeah I know it’s hard, but we’re going to have to do it. Because if we want to do, you know, I wrote something in the memo, I said, if we want to do extraordinary things, we need to overcome extraordinary obstacles. So. Anything worth doing is hard, right? Like, that’s just how things are. And so, the memo became more like, let’s embrace the hardness. Not overwork, but just like, yeah, it’s difficult. You know, you’re trying to build a new system, trying to establish product market fit, but you still need to integrate with Netflix. So how do you do it well? Right? That’s not an easy thing, right?

    You got systems built for SVOD, not for games. How do you integrate with those systems? And there’s real technical challenge of that. And so I sort of shifted from like, here’s what I know what we want to do to like, I know how hard it is to be in the situation. [00:11:00] And then look, I still need to collect a bunch of feedback and, and figure out, you know, what’s wrong with it.

    And, you know, I’m, I readily admit, like, look, I don’t know what should be in this doc. You know, I just kind of wrote. My initial version. But the, the good thing is, you know, the first few people I shared it with were like, Oh, this really resonates. So then I’m like, okay, I’m on the right track. Right. At least I didn’t write something and people were like, this makes no sense.

    Why did you write it? Right. And so I think that’s also how I work too, is that I think a leader will put out a vision memo and they think it’s like written in stone, dude, we can completely change this however we want. Right. And actually more information I have will help us make this memo and this. Vision better, right? So that’s kind of how I’m thinking about it. And so yeah, definitely inviting people you know being transparent of what you’re trying to do. I think is really important You know, you kind of want to show I don’t know. I’m kind of like a show and doer at the same time You know what?

    I mean? Like I you know, I don’t want you to just trust [00:12:00] me that I Am a trusting leader. I want to be transparent. I want to be open I want to be vulnerable like i’m just gonna like, you know Do it, not just say it. Right. And so I think that’s also important as well.

    Alexis: Excellent. And the next question is also about doing and saying or doing and helping others. It’s about growing people. And I know growing people starts often with oneself. So help me understand how you. What is your philosophy about growing people?

    Bruce: Yeah, I I think everything is about growth mindset, right? Which is just the idea is just because you don’t know something now doesn’t mean you can’t learn it. Like, right. The idea that you can get better and be better. Right. And so I think you said you start with yourself, right? You realize where your challenges are. You realize is where, where you, maybe your weaknesses are. And, and you, you want to like get better, [00:13:00] but the second thing about growing, which is also recognizing what you’re really good at, what you’re like exceptional at, right? Like what’s my superpower and how do I like do that more? Right. So I’ll give you an example. One of my superpowers is like connecting with people and networking within the company. And one of the challenges of games is that it’s sort of insulated and ice, you know, isolated. And so my job is using the connections I already have to start doing road shows, right? So that’s an example of like, how do I also use my own strengths to my own advantage, right?

    And so that’s for me. And then, then about to the team, that’s where it goes back to earlier. I mentioned figuring out what you have, where the strengths are, you know, what can you push, right? Where can you help support and coach where there’s weakness or, or, you know, somewhere to improve. And so I think.

    Growing people, I like what you said earlier is like, first it starts with yourself, right? [00:14:00] You have to be humble enough to know that, you know, you don’t know everything. And then I think when you work with people then you, you got to figure out as they. Build that trust, then they can open up to, here’s what I’m good at, here’s what I’m not, here’s where I want to grow. Now, also as a leader, the challenge is that, you know, I’ve had the benefit of leading ICs, but as I build up the team, I don’t directly lead ICs anymore, right? And usually I have managers who then lead ICs, so then how do you grow people when you’re not directly interacting? With the ICs, right? And so you have to grow your leaders, right?

    You got to grow your people leaders and make sure your people leaders are reflecting sort of the vision and the ideals and pushing you as well, right? Cause my, my people managers pushed me all the time to get me to think, rethink and learn. And so I think that’s the other thing is as you move up, it’s really about scaling yourself, right?

    You can’t meet everyone. You need to make sure you’re building [00:15:00] the scalable structures. So that the, your managers and their managers can like build strong teams. Right. So I think the growing also is about scaling out beyond just you personally, you know, one on one growing someone.

    Alexis: Yeah, love that and it’s funny because I’m starting working with a new customer this week. And I always love when I’m able to meet with everybody on the team. And during the first call before we started, he told me, Okay, so there’s 800 developers on the team. And I said, okay, so that will not happen. I will not meet with all of them.

    That’s for sure. So now we need to have a really good strategy to scale myself because I will not have 800 meetings during the first week. That, that not even during the first year, 

    Track 1: it will probably not 

    Alexis: happen. So, yeah, I am saying, and it’s, it’s really different to be directly managing the team of individual contributors.

    And [00:16:00] starting to have managers will do that with you. ,

    Bruce: By the way, that’s actually a really great tactical example of growing my team. If you look at my previous team, I, when I led Netflix, first team I led at Netflix was API systems, right. And it was just ICS, right. And the whole point was me coming in

    to help. Establish like a team structure, but it was all ICs. And actually that was a real growth area for me is when I started getting, you know, man, engineering managers, it was this weird, like I had, you know, worked with a team to build out this vision, but then now I have managers who’s. Pushing that vision and changing the vision. How do I let go right? And so growing the team sometimes is letting you letting go Like you not being in it with you know, like because you feel like I felt obligation.

    I felt like hey This is my you know, this is the team we built together I don’t want to let go and actually growing the team sometimes means letting [00:17:00] go

    Alexis: Oh, I feel that’s important. Letting go. Okay. We’ll put bold at some point. So can, can you share a challenging project that really, really stretched your skills?

    Bruce: Oh, man, they’re all challenging I mean When I first started, so I always tell my story of when I started Netflix because it was the hardest job I’ve ever done in my life, right? Times two, because here’s what happened first. I come into a dream company. Right where you you know, i’ve been following the culture for years I’ve designed my engineering culture based on the culture So you have an aura like I have no idea how it really is in the company I’m, just like oh my god They must know everything and they must be right on everything and they must be the best company everywhere, right? So you already have that first off you have deep imposter syndrome coming in then you have a memo that says

    Keeper test dream team [00:18:00] a players, right? So then you’re always constantly worried. Am I gonna get fired like at any point? Right to then you come in and, you know, I’ve been mostly startup founder and, you know, worked at startups leading teams.

    And this is a order is multiple orders of magnitude, higher traffic, you know, services much more complicated systems architecture, right? The technology is way harder than I’ve ever seen before. Right? So you got that. And it mixed all that together. COVID hits in March of 2020, right? So I start Jan of 2020, I get two months in the office and then it’s locked down. So you also are facing with an existential crisis within the world and Netflix. Cause Netflix was built to be a in person company, right? I still remember early on attending meetings with you know, we had this major API migration project, [00:19:00] right. Dot next to edge pass. So NEXT is this, you know, API platform that we built over many, many years, and EdgePass was kind of the new GraphQL like graph language API, and it’s been already going on for multiple years, right? And in the check in meeting, everyone was in the room. Right. Like literally all the engineers and I’ve never seen that before. I was like, Oh my gosh, everyone’s here. This is amazing. I’ve never, you know, like mostly work for startups where it’s all remote and distributed. It’s like everyone’s in the room and we’re talking about this project. And so you go and lock down everyone’s remote. So you’re also dealing with like the companies aren’t even prepared for that, right? Like, like we’ve never done that before. And so to me, that combination of just, do I know what I’m doing? Am I going to get fired at any time? Plus. You know learning an environment that like, you know, everyone was dealing with right?

    Not just us was just super super hard and I don’t know how I got through it Honestly you know [00:20:00] i’m like I tell people it took me Nine months to really understand nine months to a year to really understand what the team did right? And then took me really two years to feel comfortable. And so that journey Here’s what’s interesting.

    It’s not one difficult thing, right? It’s like 10 20 difficult things. And actually what was really hard about that situation was even after I built up, you know, good rapport, I actually fell down like a year and a half in where it’s like, Oh, I felt good. And then like I made a huge mistake with the team and lost some trust. Right. And so like, you have to then rebuild that and figure out, Oh my gosh, what did I do wrong here? And so the building out API team to be this more scalable team So the vision that I came up with was hourglass to turbine So hourglass is what everyone tells API is right? It’s in the middle layer between two huge [00:21:00] groups like UI and back end teams So, you know, we’re the middle layer that like a hourglass right that that That choke point. And we want to become more of a turbine or engine for innovation. So it took many, many years to figure out how to do this thing, right? This really complicated piece of the ecosystem and moving it to a more scalable architecture and team structure. And not everyone was happy about the move. Right. And so it that’s another

    example of trusting teams and seeking excellence conflict with each other. Right. And so, so this journey was really a multi year journey that had come with many difficult up and down. Right. And so it’s not a single event that I can say, Oh, that one thing was really hard. It was just like the whole journey. Was really hard. 

    Alexis: I love it. And the context was definitely how say, interesting or really challenging. When when I listened to what you said [00:22:00] about your, your leadership philosophy, I was wondering how the, how the system, how the, I understand the organization is really important, but I owe the system, the processes, the tools, are they, are they important in what you are doing or?

    Let me understand how you you deal with that.

    Bruce: Yeah. So when you say systems tools, do you mean like technical tools or do you mean like pro like JIRAs and Kanban boards? Like, I’m just kind of curious, how do you mean?

    Alexis: I I mean everything I I want to leave it as much open That’s up. That’s all the things you you know that there’s a deming We’re saying always that a bad system will beat each time The system is really everything That people will interact with. And so I’m, I’m curious about what is in the system you and what you feel you are to 

    Bruce: Right. So, so here’s, what’s really interesting about Netflix is that Netflix is well known for a culture [00:23:00] aspect called people over process. Right. And so actually, we’re like very shall we say, like, not anti process, but just like, oh, process is bad. And like, that’s actually a culture meme we have to break, right?

    Like, process is not bad. I mean, deploying code, CICD, that’s a process, right? Like, you know, running offsite is a process. Like, you need processes, right? Like, and so you can’t treat it as a dirty word. And so actually, the thing I had to fight was how do we introduce some lightweight processes? Right. Can we just use Jira’s to track what we’re working on? Right. Can we have like a lightweight Kanban board, you know, to just see what the team was working on. So what’s interesting is what I’ve learned over time is that everything you learn, all the tools you learn, you have to apply for the situation and the problem on the ground that time. So what I had built before of like building Kanban, for instance, I, you know, [00:24:00] built Kanban processes.

    And I, I, I’m kind of like. That’s kind of a strength of mine is when I read something about a process, I can kind of synthesize it pretty quickly and get to the core of why you do it, like OKRs or Kanban boards or whatever, right? And so those are easy for me to implement in a good way. Like Kanban is all about limited WIP, right?

    Work in progress. Right. And you’re trying to stop the line when you’re having a problem, right? It’s not about filling it with a billion things. It’s about actually filling it with less things and

    doing Right. And so those things I can do and so implementing some lightweight process when there was no process or very little, because at Netflix process was actually considered bad. Right. And so that was actually, the challenge is that you have to kind of take into account the team you have, the org structure and culture you have. And then figure out how to like integrate into that. I actually got feedback early on. It’s like You [00:25:00] know, I was trying a bunch of different things I read and they were like, Oh, my team was worried.

    Like, Oh my God, this is some like guy who read a bunch of blogs and I was trying everything. And, and, and it was funny because, you know, I was doing that. That’s what I was doing. I was like, Oh, I read, this is a good structure. Let me try that. And it’s like, I had to adapt, right. And what happened, what helped. What helped the team realize is, look, I’m a startup person. If something’s not working, I’ll just throw it away. I’ll try a different thing. Right. I’m not going to try to force feed some process down your throat until I make it work. Right. And so that was my process is like seeing what worked with the team. Trying, what were the things that resonated? Didn’t, you know, I try to put stuff in air table. That didn’t work. Okay. Throw it away. Do Kanban boards. Okay. That worked. Cause we’re mostly using JIRA. We were doing sprint planning and we’re switching over. And so that’s the example of just. adapting to who you have and the company you’re in and being able to implement some things to put more structure [00:26:00] to just organize you know, the team a little bit.

    And so I think for me, it’s not about a set thing, like implement these 10 things and it will work. Right. It’s about like, it’s kind of like that growth mindset mentality of like, what are we trying to do right now? And how do we make it better? So it’s more of a philosophy of how we get better. That’s seeking excellence. Making the system work better rather than a specific thing. So I’m more principle based on that than like a formula of things.

    Alexis: I love it. I, I would love more people to answer that question with a more base. I just think that way would be more probably interesting for them to, to realize that implementing a framework or adopting best practices is not necessarily the best option they can pick. That really are reflecting on the core principles is probably 

    more important to adjust and adapt.[00:27:00] 

    The current 

    Bruce: Yeah. I’ll get, I’ll give you a quick example here. Is whether we like it or not, I think Netflix has influenced the industry on like graph QL, right? Because my team, my team’s actually wrote blogs about sort of our federation technology and stuff like that. And I always find it very interesting when teams say, Oh, Netflix is doing it.

    So we must do it, but why Netflix has very specific reasons why they’re doing it. You know it, it’s not just. Like because we want to you know, and I think that’s also very important like where I find it people like want to copy success Right, like oh this company’s doing this. Let’s just copy what they’re doing without recognizing what they actually need.

    Alexis: Yeah. It’s a very, very dangerous do. It’s harder to really understand the core principles. So it can be off. Ah, that’s a, that’s good. You, you went from being an individual contributor to a [00:28:00] higher level leader in a, in a new large organization. And as you said, a dream company what, what is your perspective of what makes, what makes a good, a good people leader?

    Bruce: Man, that’s so so there’s, there’s a book I read called Team of Teams by General McChrystal.

    And he, he had one of the best lines. He said he looks at himself as a humble gardener. And it’s like one of my favorite images. Is like being a humble gardener, right? So one is being humble. Like don’t assume, you know, everything and the gardener piece is more about for me It’s the image of in the dirt with the team figure out what needs to be done clearing the brushes Making the environment in which everyone can grow right?

    So I like that mentality of like Your job as a leader is to make sure everyone else grows and gets better [00:29:00] and sometimes it depends on what the situation sometimes you have to take a much more hands on approach Right given the you know the current team Structure or current experience of the team and other times you just need to let go and let let it shine Right, and so it’s it’s very dynamic, right?

    It’s based on the situation so I think those those two things really speak to me like if I think about what kind of leader I want to be. It’s that it’s like that humble gardener approach of like being, you know, able to work closely with the team, but also knowing what you don’t know. Right. And honestly, I think comes down to just curiosity as a leader. Like, you have a lot of experience, right? Great, but maybe you don’t know everything, and that’s okay, and being okay with not knowing everything, and learning, and that drive and thirst for learning, and being better, like just being wanting to learn more and [00:30:00] get better, incorporate more concepts. Don’t think you know everything I think is just like a key attribute of any leader whether you’re a people leader.

    IC leader

    Alexis: Yeah, I love that. I love that. And a really good reference. I love that book. And I was about to say that there’s a, there’s a lot about curiosity, but you said it. That’s perfect. I will put the link the comments we are about to, to be at the end the episode.

    What is the question I should have asked you?

    Bruce: Well, that’s a good question. you kind of addressed it which I think you could have pushed more is the failure modes Right? Like you asked, like, Hey, what was the hardest thing? So I think that was good. But maybe even digging deeper on like, what were the failure modes and like, what did you learn from them? Because I feel like it’s not about the success that defines us as a leader. It’s about how we dealt with the failures that defines us. And so I think if [00:31:00] like, maybe it’s more like drilling down into where are some of those points that you learn from a failure or some situation like, you know, I mentioned to you like I had a problem with the team that I thought I lost some trust.

    I had another one letting go right to my managers. I think those are always the, what I don’t like about the world of, you know, whatever you want to call influencing leadership, you know, talks is it’s, it paints too rosy of a picture sometimes, right. You’re, and you’re actually seeing a lot more practical discussions of like, what’s hard about leadership, not what’s easy everyone could talk about being a leader, but it’s actually pretty hard to actually be one.

    Right. And so I think that would probably be, you know, a good question is to drill down in some of the failures more deeply

    Alexis: do you want to, try the for us? 

    Bruce: Sure, sure, sure. Many. I can’t, I can’t even pick all the mistakes I made. Let, let, let’s [00:32:00] pick the failure mode where I think this one is important because this is where I had built some confidence with the team. So this is when I lost some trust with the team. I had already built some confidence on like knowing what I was doing. And that’s actually, it’s funny because that’s kind of where hubris kicks in, right, where as a leader, you’re not being humble anymore, and you’re sort of like, Oh, I know what I’m doing. I’m just gonna push forward. And so the situation was that we had a new VP and we want to present our strategy for Consumer Edge, right?

    So Consumer Edge was our new federated GraphQL API for the consumer product. We already established it for our internal enterprise within the studio applications. But we want to move towards consumer, which is the Netflix app, right? The product itself. And so I spent time with one IC who is a big proponent of that vision, right?

    And we wrote the vision doc together and it was great. And I actually even said, let’s write it without even using the word GraphQL in it. [00:33:00] Because what are we trying to do, right? The vision is unified API, democratized edge, right? So what that means is you unify all the APIs together. Because, you know, before we used to have like per UI based APIs. With BFS or backends for frontends. And we want to unify on a single GraphQL API, but then democratize in the way that it’s unified. But the people that own it are actually the domain owners, right? So the identity graph is owned by the identity team. Not managed by an API team. So really excited. And we presented to the VP and, you know, I think it went okay.

    And it was fine, but my team was like, what are you doing? Like, why are you talking about this? Like, we’re not even sure if this is going to work. And it was like, like multiple senior engineers in the team really pushed back on the concept. It’s like, we don’t even know if this thing will work. And why are you talking about this thing?

    And, [00:34:00] you know, what are you trying to do? Like, it was almost like, are you trying to like dismantle the team on this new vision? Right. And I was like, whoa, what, you know, because of my push for speed and push for like, Hey, I want to get this in front of this leader. Who’s new. I actually didn’t take the time, right.

    I used. My confidence hurt me here, right? I thought I built the trust of the team. I pushed fast and I didn’t collect enough information. And so when I presented it, it wasn’t a cohesive vision that the whole team supported, right? And then I had to go back and

    really work with you know, the more senior leaders to define a more cohe I mean, I remember, I even remember us, cause it was lockdown, and we had to like find a room outside to like meet the four of us, right? To just like talk through the vision and be like, okay, what is really underneath this? What’s the meat of it? How do we really make it happen? [00:35:00] Not just write a doc. Right. And I still remember sitting with the four of us like outside discussing, you know, in person, cause you know, it was also remote. Right.

    So that didn’t help. And we were like social distancing and trying to discuss this vision together. So that was, that was a key moment for me because I felt really bad and the team was just like, you know, we’re like, I’m really disappointed. You know, I was like, Oh my gosh, how did I mess up this bad? 

    Alexis: thank you for sharing because it’s, it’s very interesting and it shows the other face of that. spoke about the humility that is needed and I love the way you presented the vision doc and the fact that it was really a collaborative document that you refine each time you meet with someone.

    And then, yeah, you’re confident in that vision and you want to take a shortcut and Boom, doesn’t work. And it’s very interesting. Each time you, each time we take a shortcut, [00:36:00] should think a little bit about, is it worthwhile? Is it really a shortcut?

    Bruce: yeah,

    Alexis: And yeah, 

    Bruce: yeah, yeah, no, that’s a great one. Yeah, I liked that term. Is it a shortcut you took? And absolutely it was a shortcut because it was speed, right? Like I wanted to go fast and like present quickly. Right. 

    Alexis: Thank you very much, Bruce. Thank you for, for joining me on the podcast today. I really appreciate 

    Bruce: No, it was great. It was really fun. Yeah. We’ll do it again.

  • Outcome-Based Leadership Without the Bureaucracy

    Outcome-Based Leadership Without the Bureaucracy

    Outcome-based leadership is everywhere in theory. In practice, it often collapses into two familiar traps: goals become tasks, or goals become top-down control.

    In this episode, I spoke with Tim Beattie and Bella Bardswell, co-founders of Stellafai, about what it actually takes to build an outcome-focused culture that improves collaboration, increases autonomy, and keeps teams aligned without crushing initiative.

    Their perspective is shaped by decades of experience in consulting and transformation, and by the reality of building a product company from scratch.

    When OKRs trigger people, it is usually not about OKRs

    One of the most practical parts of our conversation is how Tim and Bella handle the strong reactions people have to OKRs.

    Many leaders say they “hate OKRs” because what they experienced looked more like classic management-by-objectives:

    • top-down cascading goals
    • pass-fail grading
    • goal setting as performance management
    • little room for experimentation
    • metrics used as pressure rather than learning

    Tim and Bella’s answer is not to defend a framework. It is to bring the conversation back to first principles:

    • clarity on the outcome we want
    • evidence that tells us whether we are getting there
    • experiments that help us learn what works
    • a shared rhythm that keeps outcomes alive

    And if the term OKR is a blocker, they change the language while preserving the mindset. Same approach, different words. Goals instead of objectives. Measures instead of key results. Experiments instead of tasks.

    Collaboration first, frameworks second

    Tim’s core message is simple: collaboration is the foundation.

    Before metrics, tooling, or structure, leaders need to create the conditions for real conversations:

    • between technical and business people
    • between teams that depend on each other
    • between leaders and the people closest to the work

    Getting people in a room, visualizing the work, and arguing about the words is not a distraction. It is the work. That is how shared understanding forms.

    This is also why tools like impact mapping can be powerful. Not because the artifact is magic, but because the mapping forces the conversation: actors, behaviors, impacts, and outcomes.

    The hidden cost of growth

    We also touch a pattern many leaders ignore: communication complexity rises sharply as teams grow.

    Add just a couple of people, split across rooms or locations, and suddenly alignment disappears. Nothing “important” changed, except everything did. Teams need systems that scale clarity and coordination, not just more meetings.

    This is where outcome rituals can help. Not big yearly launches. Not glossy presentations. Small, recurring check-ins where teams look at the measures and ask:

    • are we on track?
    • what do we change?
    • what should we stop?

    Over time, this becomes a way of working rather than a process.

    AI as a team member, not a replacement

    Stellafai’s use of AI is deliberately framed as supportive.

    Their aim is not to replace coaching or human interaction. It is to add an “extra team member” that helps teams start thinking:

    • suggesting measurement ideas
    • proposing experiments
    • nudging teams toward better options
    • reducing admin so time goes to the conversation that matters

    The value is in acceleration and better prompts, not in outsourcing leadership.

    Inclusion as a built-in practice

    Tim and Bella also share a clear stance: you cannot retrofit inclusion later.

    They treat diversity and inclusion as something you build into your values, your hiring, and your daily practices. Simple facilitation patterns (structured turn-taking, visible participation, safe ways to contribute) matter because they give people a real voice. Inclusion is not a statement. It is a set of habits.

    Advice for emerging leaders

    Their closing advice lands in three moves:

    • Collaborate: create the conditions for real conversations
    • Prioritize outcomes: narrow the focus and make it measurable
    • Make it enjoyable: leadership is a long game, build a culture that people want to be part of

    References

    Transcript:

    Alexis: [00:00:00] Welcome to Le Podcast on Emerging Leadership. I’m your host, Alexis Monville. Today, we are thrilled to have Tim Beattie and Bella Bardswell, the co founders of Stellafai, a company pioneering in outcome focused approaches to team collaboration and leadership in the tech industry. 

    Tim, with his deep expertise in agile and lean methodologies, and Bella, known for her transformative work in cultural change, bring a unique perspective to the table. We’ll explore their journey in co founding Stellafai. The challenges and triumphs of emerging leadership and their innovative strategies in the tech world. 

    Welcome to the podcast on emerging leadership. Could you each share a bit about yourself and what led you to cofound Stellafai? Maybe Tim you want to start?

    Tim: Yeah, sure. 

    Thanks Alexis. Thank you for having us on your podcast. My name’s Tim Beatty. I. Spent the majority of my career working in [00:01:00] consulting large consulting organizations including PWC, IBM, Deloitte a couple of smaller boutique consulting organizations.

    So I’ve always worked in the world of services and delivering professional services to clients. Most recently I worked for Red Hat where I met you, Alexis. And I was responsible for a part of Red Hat called Open Innovation Labs. Open Innovation Labs was a slightly different services model in that the focus was all around enablement.

    It was all about enabling customer teams to get the very best out of, in this case, red Hat technology. the focus on on successful enablement. It was all about ways of working, all about culture. Practices mindset a little bit about the technology, but you know, to technology is sometimes the easier part.

    It’s more about the ways of working around the technology. my time at Red Hat was very re rewarding. I loved learning more about open source and open organizations and it felt like a really good blend [00:02:00] to the work that I love, which, and I’m passionate about, which is all about business agility and lean and agile and, and frameworks like that. so I spent five years really switching away from being a delivery consultant into an enablement consultant. And that really I found very rewarding. I, I look back on the teams that I helped kickstart the organizations that I helped transform.

    And once I got a bite for that, that that felt like that’s, this is, this is the kind of world I want to, to, to live in. This is the kind of career I want to continue. So I co-founded Stellafai with Bella a little under two years ago. And again, that was building upon this idea of enablement. It was about how can we help organizations really achieve their outcomes, their measurable outcomes.

    And we’ve done that. We’ve, we, we had some great ideas when we, when we paired up on this of, of some software that could help with that of an alternative model to to [00:03:00] coaching in a more asynchronous, contextual way. And, and we wanted to leverage the, the work that we’d done in our previous 20 to 25 years.

    So we brought all of that together to form Stellafai. And I think we’ve come up with something really exciting and I, I love being a part of it.

    Alexis: Excellent. Thank you Tim. And I still remember the, the first time I really met you in person. That was, I believe at A gile New England, in Boston. And, see you showcase what was happening in an open innovation labs residencies. You showcased in a one hour long session what was happening in a whole week of engagement and even more than a week. So that there, that was very, a lot really a lot of fun. But before I, I recall my memories.

    Maybe Bella, you want to, to say a few words about yourself.

    Bella: Yes. So my, my background on, on a quick glance looks quite similar to Tim, but we’re actually, we’ve had very different, different experiences, which I think is why our partnership works so well. We were able to bring that together with the. Enough common [00:04:00] ground that took us in the sort of shared direction and vision.

    So I, most of my career was in IBM big, big digital transformation programs, and I’ve done most roles along that journey. So business analysis, business architecture, change management, business change program management, then the sort of leadership and sales sort of elements. But the sort of thread that’s gone through all of that is I did a lot, a lot of work in government and the thing that I didn’t realize at the time that made me love that so much is that real clarity over why it mattered.

    You could always, you were building software, but you knew why. What it, what the reason you were doing that for. And it was really tangible and it mattered and that was. Really, really motivating. And then I started, while I was at IBM, I became familiar with Agile and that amplifies that, you know, what’s the value of what you’re doing?

    What’s the why? But I often found that people were kind of somehow managing not to do that. And then I, I went from IBM to Google. And at Google, many people know [00:05:00] they’re really, really into this framework, OKRs objectives and key results. And that’s really about having a very, very clear why and then a way of measuring if you’re getting there.

    And there are lots of different goal setting methodologies and they all talk about. Measurement, but very, very often no one does it. And they don’t really, they, their goal’s actually a task. And, and I started to, you know, realize I’d built up these skills and these insights, but all I could ever do was help the client I was with.

    And I, I was really inspired what Tim was doing at, at Red Hat with the open innovation labs. And when we talked about it, the idea of using software to be able to. Scale us and our experience and what models could we use? Like Tim mentioned, the asynchronous model, but also bringing in AI and, and just generally technology making less admin and more visibility easier.

    I was thinking this is a way that we could start to scale ourselves and, and help profoundly more people. So that was, that was really the vision, help helping. [00:06:00] Get the power of the why, but also using tech to, and different, different ways of thinking to help many more people get the benefit of that way of working.

     The brilliance of understanding why you are there and why what you’re doing matters. And then also if you track things, you’re more likely to get there. So then the, the real buzz of actually achieving what you set out to is something that we wanted to help more people do. Yeah.

    Alexis: Yeah. I really love it because then it it give us a, a sense of why you are doing it and not really how you are doing it. There’s some mystery about that, that I, I really like it. And of course on the podcast, I had the pleasure to welcome a lot of different people, and some of them talk about OKR.

    There was Christina Wodtke w ho is the author of Radical Focus, for example or Gojko Adzic , who wrote impact mapping. And we had a discussion about OKRs. And that’s because of him that, I had a short video on OKR, on impact mapping because[00:07:00] we discussed it. We discussed impact mapping and I explained to goco, ah, that’s how I’m, I’m defining OKRs.

    And he looked at me to say, no. Explained that to me. ’cause I don’t understand what you say. I said, you are the author of Impact Mapping. You inspire me to do that. And he said, no, no. Explain that to me. And I explained it to him. Say, can you, can you record a short video? I would like to share that with my partner because we never thought of it this way.

    And for me it was so obvious that, that, that was really funny to, to connect the two.

    Bella: Yeah.

    Alexis: One of the guests, I welcome the podcast. I, I prompt her to speak about OKRs because I was all excited about it. And my surprise was she was very against OKRs on the approach of OKR. And that person is Radhika Dutt, she’s the author of the book Radical Product Thinking. A book I really like. When she spoke about OKRs, she said, oh, it’s setting big lofty goals. It’s not collaborative enough. It’s more [00:08:00] like an end of year exam that you pass or fail. And you don’t even test if the strategy really works. And I was listening to that and say, no, no. So, but tell me what you think about that.

    What, what would you answer to Radhika about OKRs?

    Bella: Something that Tim and I and, and this, we get this a lot, so OKRs, just like Scrum actually, we’ve noticed a lot of parallels. You get a big framework, someone writes a book like Measure what Matters or Radical Focus with Christina Watt, and suddenly you get the lovers and the haters. You know, it feels like you have to pick a side, but actually I think all these frameworks have.

    Elements that are valuable, and then elements that you have to like go, that’s not gonna work in our culture for where we’re at. Let’s think about what will work. And one of the, one of the patterns we’ve seen come up a lot with OKRs is people, people’s perception of OKRs is actually much more like what happened in the sixties.

    With management by objectives, which was Peter Drucker and then Andy Grove adapted them [00:09:00] to OKRs. But a lot of people go back to the principles of MBOs and management by objectives. So that means your managers tell you what your goals are. They’re very, the word cascade is used a lot. Top down your, you give them.

    You have to achieve a hundred percent and it’s linked to comp, and that has all sorts of unintended consequences. If you’re not involved in figuring out what you’re going to do, you’re not committed. You’re not engaged. You don’t have a say. You’re not getting the opportunity to help people. If you said a hundred percent.

    Goal, it creates pressure. There’s no space for experimentation. it’s stressful. And if you link it directly to compensation, you immediately eliminate the desire for anybody to collaborate or to do anything, but just to try and focus on what they need to do to get paid. that’s extremely damaging to culture.

    All of those things are the exact opposite thing that you want to have if you wanna build great products. So. I think OKRs are often done that way. You know, someone reads a book, a manager reads a book goes, right, okay, it’s gonna take too long to do lots of collaborative workshops. So I’m just [00:10:00] gonna, for the first time, just write them and give them to them.

    And then I’m not gonna think about how we’ll embed this idea of thinking and. Around outcomes into my organization. We’re not gonna use this as a way to communicate understanding and to track progress and to decide what we should do. We’re just gonna shove it in step back and expect everyone to deliver the goals.

    And yeah, that doesn’t work. So elements of that happen in, or pretty much all the implementations Tim and I have, have seen in the work we’ve done, and you don’t have to use OKRs, you can just take this concept of setting a goal. Being clear about the outcome you’re trying to achieve and then figuring out how you’re gonna measure whether you’re getting there.

    Coming back to impact mapping, which is why it’s so great a way to measure the impact of what you’re doing rather than just ticking off tasks, which may or may not help you get there. So I’ve drunk the Kool-Aid, I think done well. They’re brilliant, but they’re often not done well.

    And often people put a lot of effort up, up front and then we call it set and forget, and then they never go back to it. They don’t think about how to [00:11:00] build it into how they operate, but it’s as much as a way of working and a culture and a mindset as it is a, a framework. I mean, the framework’s pretty skinny,

    a lot of people that have negative feelings towards OKRs based on experiences they have are entirely justified. But often I think it’s what still worth taking a look and, and exploring what happened in the past and whether it could, some tweaks could be made where you could get this really incredible power of everyone understanding what you’re trying to do, caring about it, being focused, aligned, and then tracking progress together.

     When done well, it’s, it’s phenomenal. 

    Tim: Your experience Alexis with, with that lady reminded me of something that happened. Probably about a year ago I was doing some beta testing of the platform we built, and I had some time with a CTO and the CTO looked at it and he said, Tim, I can never show this to my CEO because he hates OKRs.

    He got burnt by them badly, tried them in a previous company and he’s just an anti OKR. [00:12:00] Your platform set has got objectives and key results. We tried a little experiment we built a little feature, only took a, a day or two to build where we could customize just for on a per user basis some of the terminology and the naming.

    And for his space alone, we changed it so that instead of creating objectives, he was creating goals. And instead of creating key results, he was creating measures. And instead of adding the activities or the tasks he was writing about experiments. So I showed him and he goes, oh, my CEO’s gonna love this, the goals, experiments, and measures.

    He’ll really get that. Now. The interesting thing was our mindset, what’s under the hood, haven’t changed. We were still thinking about what is the problem we are trying to solve? What is the opportunity we’re trying to grab? What are the pain points and how can we articulate that in a really well aligned and shared view, you know, and not our goal statement or objective statement, a smart goal.

    There’s lots of different ways you could do it, but in essence, [00:13:00] that’s what we were trying to do. Then we were trying to come up with a series of qualitative measures, so needles that we could see move that were going to tell us if we were making progress or not. And we were going to encourage the idea of trying different things out.

    Designing experiments to see if the needle would move or not. So whether we call them, you know, to me we were still doing OKRs, right? But I could hear that there was a negative perception to OKRs, and it’s a little bit of consulting 1 0 1 here,, when you go out and you consult with a client.

     You’ve got to meet them on the language that they’re comfortable about. And if there is language , which is triggering some real negative emotion, it’s okay to change that. What’s not okay is to change the mindset that we know is going to promote success and deliver success. So it’s a very interesting, and, and just as Bella says, we’ve seen it with many things over the years.

    With Agile, with DevOps, with design thinking, with lean, and I think, okay, anything that goes [00:14:00] mainstream starts to get that Marmite love-hate relationship, and therefore we tread carefully with what’s the best way to introduce that under change management to organizations.

    Alexis: That’s a very good point. So the language can influence the perception. We can change the language, but maintain the culture or the mindset that we want to have about the collaborative aspect of it. You both mentioned that. Top down effect of I’m setting goals.

    Not saying we, we will forget about them, but if it’s not integrated in our way of working, we’ll definitely forget. What do you want to say about that collaborative aspect? And finally there , you worked in Agile and lean, you have extensive experience on those topics.

    So I’m interested in how we can get people to be more autonomous, more independent, more able to take matters in their own hands, or basically make leadership to emerge in the organization. So I’m, I’m interested in what you have to say about, about that collaborative aspect.[00:15:00] 

    Tim: For, for me, this is all about collaboration. Collaboration is the number one focus. Whenever I’m doing coaching, what am I trying to do? I’m trying to get people to talk to each other. I’m trying to get technical people to collaborate with other technical people. I’m trying to get business people to collaborate with technical people.

    I’m trying to get users to collaborate and I’m trying to get shared understanding and alignment for me. The best way to achieve the best collaboration is in a room. It, it is bringing the energy, the physical energy together, the room, the walls, the sticky notes, the visualization. I feel it sets us up.

    It gives us the best chance for success. So to kickstart collaboration, getting people physically together. And reaching a point where everybody has really got that feeling of yes, that’s what we’re trying, that’s why we’re here. [00:16:00] That’s what we’re focusing on. That’s what we’re trying, that’s what we’re trying to achieve.

    And almost with our arms around each other, feeling passionate about that. So I think there’s, there’s a lot of excellent practices that, that really facilitate collaboration, facilitate conversation. You, you mentioned impact mapping. That’s why I love. Creating OKRs through impact mapping because just the act of putting up those, just, just the act of getting people to, to write a goal statement and align on it and argue about it, and challenge about it and change.

    Swap one word out for another word. That’s all. Collaboration and it’s achieving shared understanding and alignment, agreeing the actors and. What, what do we call those people? What do, what do we call our users? What, there’s lots of different types of users that conversation. It’s collaboration, the measurable impacts, and actually what we’re doing there, we are building OKRs.

    We don’t realize we’re doing it, but we are a we are coming up with a, an aligned goal and we’re coming up with [00:17:00] a well thought out, measurable impact that we’re trying to help to get us towards that goal. But we’re doing it through conversation and visualization and energy. To me starting these in, in the room is, is just such a key foundational ingredient.

    And then I think that it’s how do we maintain,, how do we not lose that? And I think that’s that’s where, the emerging leadership, you talk about Alexis, 

    it’s a very much a diverge, converge. Can we go away separately? Autonomously, can we come back at regular points to synchronize and, and bring that challenge back together?

    Can we provide, can we get access to the support, the right level of support where it isn’t someone doing the work for you, but enabling you and just challenging you to think. So I think it’s putting that environment in place, that’s what promotes that kind of. Continuous improvement and evolving leadership so that there is a self, self controlling, self-management [00:18:00] aspect to all of these things.

     I personally think that the most important thing that goals does is enable conversations and that is communication. I’ve just got so many stories and everyone I speak to sort of nods sort of slightly sort of, oh, wly when I, when I say this, but we’ve all been to those like start of the year kickoffs where all the leadership spent weeks, months figuring out strategy. And then there’s this big launch of your strategy and there’s glossy presentations and oh, this is gonna make such a huge difference to the set of the company and la, la la, and it’s all nice. Maybe there’s some wine if you are lucky enough to work to that kind of company.

    Bella: And then after you leave there, it’s very nice seeing everyone. You go back and you just carry on doing exactly what you were doing before. So that is an example of a strategy, which is not going to be executed anytime soon, perhaps ever. That’s crappy communications. Like it’s the message received and the action that’s taken off the back of it, not the one delivered.

     And I think it’s not just OKRs and Tim just [00:19:00] touched on lots of things. We’ve got to get better at finding ways for, for people actually to receive the message well enough that they can understand and apply it to the work they do. Strategy execution is a huge challenge for all leaders and every leader should be worried about that.

    Writing some really, really crisp, clear goals that break that down and can then be decomposed through the organization. All aligning can give you a pathway right down to every single person on every keyboard working in alignment to achieve the goal. And if they then every week have a little conversation about how are they doing against their goals, that keeps that goal front of mind, that present big presentation disappears quickly from your mind.

    If you are looking at the the measures every week, that’s keeping it front of mind and then you have a conversation like, we’re on track. Brilliant. What was going well? Or We’re not on track, what do we need to change up? And you are. To your point, you know, you are empowering people. You know what you need to do.

    I trust you. Go do it. Let me know if you [00:20:00] need me to unblock it, unblock something or, or help you. And I think that’s incredibly powerful. But the other thing you’re empowering people to do is to say, this has nothing to do with what we’re trying to achieve. I understand what we’re trying to achieve. I think we should maybe talk about whether we should stop that and the amount of waste of pet projects and work, which has drifted from the mission and no one realized ’cause the comms weren’t there, is huge.

    So that I think that empowerment and communication I. Combination that you mentioned in, in your question can make a huge, huge difference to, first of all, business success, but perhaps more importantly, all of our ability to feel connected to purpose and actually do something, actually deliver something that matters, which I think is super, super powerful.

    Alexis: Focus on outcomes. I saw that a lot in your communication. There’s also that thing about AI and I’m a bit curious about that because we spoke about communication between people empowering people getting people in the room getting them really aligned, really get to that [00:21:00] shared understanding what, what AI has to do with that.

    Tim: Let me tell you the story about why we put AI in, in the end of our company name. So we were drawn to the word stellify, S-T-E-L-L-I-F-Y, which means turn into a star or or place amongst the stars. There was a lot of thought behind that because we thought about outcomes in organizations are connected and particularly measurable outcomes.

    This idea of, if you’ve got, say, a platform engineering team working towards measurable outcomes, they’ve got these little needles, which should start to move and if they are moving it’s connected to maybe some product teams and their needles can start to move quicker because of that connection. And if that’s successful, then it’s helping a business line and it’s helping them achieve their measurable outcomes.

    And that’s helping the strategy. So we are, we’re joining the dots. We’re forming this kind of idea of a constellation of stars where, you know, there’s [00:22:00] lines and what we want is really bright stars really bright constellation lines because of those connected outcomes. And we want to be able to zoom into those stars and understand what the energy is.

    So we were really taken by this metaphor. And it goes many levels deeper than that as well. But when we looked into trademarks and domain names, of course it, you know, the guy who had stellify.com wanted a hundred grand for it or something like that. So we did what every startup did, and we invented a word.

     We liked Stellar ’cause Stella’s, you know, we want everyone to be stellar and our people to be stellar and our customers to be stellar. We still liked that stellify and then ai, we thought, well, AI’s coming and I’m sure AI will filter into our company at some point. We, we actually didn’t plan for it at the beginning, but we thought, well, that, let’s put it in and we landed on, on it.

    Then of course about a year ago, the world went AI mad and everybody was doing chatGPT and Bart and open ai. And so we invested a sprint one [00:23:00] week. I can remember it well, November before last. One of our guys basically just did a little bit of a, a spike, bit of a prototype just to see , how could this AI help us.

     It’s a great question because we have some strong beliefs. We don’t want the AI to replace coaches. We don’t want the AI to replace conversation, collaboration. What we want the AI to do is to help that. So we’d liken the, our ai, which we call Armstrong, named after Neil Armstrong.

    We’d like an Armstrong to be like the extra team member. Think about the team members who’s just always great at throwing out ideas. Suggestions, just gets people talking just by, just by getting you started. When you’re drawing a blank and you can’t think, oh, let’s get some ideas. And there’s always that one person who’s just really good at getting the troops talking and throwing some ideas out on the wall, and then everybody starts talking.

    That’s what AI can do. So we’ve built things like Hey, Armstrong, can you, can you suggest some ways to measure, provide measurements against this [00:24:00] goal or key results against the objective? And Armstrong won’t do that for you, but it’ll get you going. It’ll just throw out 10 ideas and people are, oh, okay.

    Oh, that’s what a key result is. Oh, let’s tick those two and now let’s talk about those and let’s dive deeper or. Hey Armstrong. We’ve got this key result, but are there some open practices that might help work? You know, we’ve trained Armstrong in, in the open practice library, great open source repository, and it will just, which is a bit overwhelming ’cause there’s so many, so much stuff out there.

    But Armstrong will just give you three ideas. You can take it or leave it, but hopefully it just elevates you on that little bit more. And I think. This is where Armstrong can help. It can just get you going in the right direction. It could. We don’t think individuals, we think teams should use ai in their conversations.

    Let’s see what Armstrong thinks and see if Armstrong can get, get us going in the right direction and hopefully you’ll get a better collaboration. You’ll more informed or point you in the right direction thanks to the training that we’ve been able to get to our ai.[00:25:00] 

    Bella: It’s become a little bit of a catch phrase, hasn’t it? Like AI won’t replace humans, but a ai humans that use AI will replace humans that don’t. That’s the exact approach we’ve taken. Tim was talking about it’s not gonna replace real coaches insights, that level of context, not for a while anyway, we need generalized AI for that.

    But it’s certainly, there are all sorts of ways, Tim’s given a few examples. There’s a heap of, we’ve been looking at research grants and things to go a whole load deeper about sort of some really, really fascinating kind of front edge stuff that could start to really help teams communicate and collaborate at another level with just nudges and assistance and help.

    So I’m very, very excited about. How it can help all the people that we’re working with, but also just help us be more efficient and do a better job. It’s an exciting, technological frontier we’re at, I think.

    Alexis: I really love that. And I tell you a story about. What happens when a team of developer really [00:26:00] work on that. I’m working with a team of, of developer , basically I’m coaching the manager of the team. We discussed, their new goals because they are really shifting where they are going with their product. And it’s very challenging for the product. It’s very challenging. For the team. And it’s also challenging for the people themselves because they will need to grow new skills.

    They will need to do things, they never did. They are really experienced developers and I’m discussing both the goals for the product and the developmental aspects for each individuals. And I’m telling the manager, you should have really career conversation with all of them so they can really think, at a at time period, that fit them. That could be five years, 10 years, 20 years. We don’t really care where they want to work, what kind of jobs they want to do, and what kind of size of company and work on that really career conversation really long term. And he, he is really excited about it.

     And he discussed with the first developer about that. [00:27:00] And the result was really interesting because the developer came back and listen, that was a fantastic conversation. I loved it. And look at that. I created a series of prompts because your questions were really good and I’m well thinking. Yeah, I know that. I know the questions are good. And so everybody in the team can do that following that series of prompts. And I looked at it and said, yeah, of course they are developers. They know how to talk to a machine. So of course he created really good prompts and he tested it and they all worked on that.

    And the manager told me that was very funny. I, I’m chatting with one. And then the 10 others are doing that work. And now the conversation I had with them are really fantastic because they have really inspiring things to say and. All about that. So I can see how, considering Armstrong as another team member that have of course, more experience and more knowledge, and that could be really inspiring for the other team members and really enabling them to go further.

    So[00:28:00] I feel that’s a very nice way to integrate AI in that context of aligning, getting people to really work with each other, collaborate with each other effectively.

    Bella: Yeah, that’s one. One of the things we looked into was, again, in, in relation to the sort of the grants, is could you, could you have an AI coach facilitate? Through a, like a, a, a check-in meeting. ’cause something we’ve noticed, a real anti-patent that seems to happen a lot is check-in meetings, become a group exercise where everyone watches everyone else update the numbers.

    And it’s like, yeah, but you could do that beforehand. The bit that counts is the, so what does that mean? And the discussion. So could you. Without the need to have a human, which is obviously expensive. And you have to book the human and arrange it all. You know, there’s, there’s logistics there. Could you have something that’s sort of just like you were describing, like nudging you through the conversation?

    And then the brilliant thing is it can then learn and respond depending on what [00:29:00] it is and, and goes. It, it’s not straightforward. But there’s, there’s some, some things there which could. Hugely increase the quality and the the outcomes that come just from a simple half hour meeting, but not just that afterwards.

    You’ve just had an AI listen to everything that happened. What was the subtext of that meeting? Were there any dynamics? Were certain people doing certain things they didn’t realize were having an impact because they were focused on the content? All that kind of stuff can be surfaced as insights afterwards potentially.

    And this is where the coaching comes in, with some suggestions about what you could do to fix it. I mean, these. Complex things to do, but I think they’re not out of reach with ai, but the, the benefit that it could have, it’s just enormous. It’s so exciting. So, yeah, I, yeah, we’ll have to see. But yeah,

    there’s a lot of good stuff to done

    Alexis: Excellent. So a question that I usually ask to all the people who are building a product for others do you use Stellafai to, to build Stellafai?.[00:30:00] 

    Tim: Absolutely. Absolutely. And it’s, we learn so much from adopting it ourselves. We are our own alpha testers. Not just Stelfy, but, but OKRs. In, in, in all honesty, I have not used OKRs brilliantly before Stelfy. I, I loved the idea of them. I love the principle of them. But I, like many other people, I have not seen them work terribly well even when I tried them at previous organization.

    I know, I know why I’ve learned a lot from Bella, who, who brought all of the goodness , from Google. And I can see that, that the mistakes we were making but the, the best way to learn is to do to do it on, on their own content. And as an example, we so, so we have a weekly check-in. It happens at 10 o’clock every Thursday morning.

    Honestly, if we don’t do the check-in on a Thursday morning at 10 o’clock, it feels like I haven’t brushed my teeth. It’s become a ritual. We’ve done it since the beginning of the company and, and we’ve evolved. So yes, we, we use our platform. We review our key [00:31:00] results. We update them. We have a conversation.

    But as Bella was saying in the last question we’ve learned actually, why are we wasting time in this, this precious time together as a team? We’ve only got 25 minutes. Why are we spending time trying to figure out the calculations and get the numbers right? We’ve, we’ve emerged from that and, we now entered before that meeting and actually something I’ve noticed just in the last few months is that the updates are happening during the week.

    ’cause we have a Slack integration,, we can see when anybody updates a key result or makes a comment, it, it fires out a message to the team. I think this is a transition we’ve gone through, that we’re now starting to think about what is the measure that we’re trying to move today.

    And when something happens that we know it’s moved, one of our measures, the first thing we wanna do is go and update it. So it’s become less of a, of a batch thing that we do once a week or a ritual and into a continuous thing that is just a part of our. Kind of cognitive way of [00:32:00] working. And I see this with other practices.

    It’s like going from fortnightly retrospectives to a realtime retrospective. You know, why? Why are we waiting two weeks to do a retrospective? We could just have a realtime one running all the time, or abandoning the daily standup because there’s such good collaborations, pairing and mobbing. You don’t need to stand up.

    And I think it’s a similar thing we have used OKRs with the ritual, with the guardrails, and now we’ve been using ’em for a couple of hours. I’m now seeing the team who are, who are just naturally thinking about what’s the key result that this, that, that I’m going to move today?

    And how is that gonna help achieve a goal? And what’s that goal connected to in terms of a bigger strategy? And that’s just becoming a part of default

    Bella: You are what, what you’re describing and, and it’s really interesting listening to you say this ’cause we haven’t had this conversation, but what, what you are describing is like another level of outcome obsession. It’s driving everything, every micro decision all the time. Is that gonna move one of our needles?

    And [00:33:00] yet, if you’ve got the needles right, which is why you need to put a bit effort into setting them, that’s

    Tim: got, we got them wrong at first. Remember our first quarter, we, we got, we got them wrong. So, so we, we’ve come through that journey as well. Yeah.

    Bella: Well, you let, I mean, part of that is we were new founders, so we didn’t know what we should and shouldn’t be doing, which is a whole nother podcast. But yeah, the, the yeah, like we’ve got so much better at figuring out what are the right OKRs for us. One of the things we’ve had from a lot of organizations is we’re too small for OKRs.

    Like it’s, it’s not gonna be valuable for us. It is true that you get to a, when you get to a certain size, and we reckon it’s about 2050 to 20 to 50, depending on the org from the people we’ve spoken to, you get a level of communication complexity with all of the interconnections. You know, it’s a great exponentially that suddenly you need a system to help you operate and stay aligned and communicate. And one of those systems could be OKRs, [00:34:00] but it doesn’t mean that it’s not profoundly valuable at a smaller scale, it’s just that it’s not critically needed to make sure you are still able to keep moving forward. So yeah, we, we 100% use them. . 

    Alexis: That aspect of complexity that comes with adding people to the team that usually we completely ignore. That’s very funny that suddenly people are highly frustrated because that doesn’t work anymore. When you look at it from the outside and you, and you lived it before, it’s so obvious.

    I was discussing with the founder of a company and he told me, I don’t understand why we just have two more people on the team and suddenly it seems nobody understand anything anymore and nothing changed. I told them, yeah, okay, good. Let’s look at that. Nothing changed. And they added the two people, but they took also another office because of course, two people in that previous office didn’t fit.

    So now they are spread into two offices.

    Look, that’s, so before it was annoying because[00:35:00] developers needed to work close to people who were on the phone calling customers, and that was very annoying. And now you split them in two rooms. And and you are surprised , that was so funny.

    And of course I cannot say it this way. I’m, I’m more gentle and I’m making it emerge more gently to avoid being thrown out of the window. But that’s, that’s very interesting to, to look at it. Yeah, that’s it. So putting in place a system that will enable people to do great work is really important.

    And what I like is you really thought that through and using it yourself makes, makes it better. So I really like that. I would like to touch on something slightly different. I’ve noticed you, you both have strong commitment. Diversity and inclusion and I would like to know how shape the, the culture and maybe even the strategic direction of 

    Tim: In our company we felt there are some principles that we have to start from the outset because it’s not [00:36:00] something you can retrofit in later. Diversity and inclusion is something, we were both passionate about. And Bella, I, I know from the work that she did at IBM , where we first met, I knew that this was going to be a really strong partnership in that.

    It was something that she would really drive and something that’s really important. And that was important for me when I was, you know, seeking a co-founder that I wanted to, to work with. We probably spent about four months before we even hired anyone to write code or build start building products and things like that.

    And a lot of that was about finding our why and our purpose. And we, we used practices on ourselves, like business model canvases, again, just to trigger the conversation and to get the alignment. But that was something from, from early on around around diversity and inclusion and also sustainability.

    You’ll notice in pictures of us, we have a, a, a lot of our own swag. We have a lot of our own t-shirts and hoodies and things like that. Our suppliers that we use for that , had [00:37:00] good sustainability metrics because we thought we could play the card that we are an early startup, we don’t have much money, let’s just go for the cheapest thing possible.

    Let’s not worry about where it’s made. But we thought that’s gonna be so hard to turn out. You know, it’s something we believe in. If you don’t follow your principles and your values from upfront, you’re lying to yourself. A lot of that comes around a, an alignment, again, alignment, shared understanding, communication, collaboration about what those principles are, and then figuring out then what, what are, what are the initiatives?

    What are, what are the acts that, that we, that we can then put in place? I think we, we’ve started I think there’s probably more like everyone that you’re never done with these things, but we started and, and, it’s, it’s something that you can continuously improve and continuously evolve in, in the next chapters and the next version of the, of the company.

    Bella: When we did our first sort of recruitment campaign, campaign might be too big a word. We’re only little, but we, one of the first things, so, so Tim and I do both care about this. So the very first version of our [00:38:00] website, I think I had like four pages, and one of those pages was a diversity statement and about just setting out our intent.

    But I was really interested when we put our first sort of ad out, we were looking for a a junior designer. We got you. All these things are benchmarked around how many, how many responses you typically get, and of, of like certain underrepresented, underrepresented groups and the applications.

    We got so many people that I spoke to often, women, maybe people that had a slightly different educational background and. Said when they, we asked them to write just an answer to two or three questions around what attracted them to Stellafai, and I’d say every single person that wasn’t like a young white male, came back with a, I was really, it was really cool to see the, the diversity statement that attracted me to your company and, and it’s a sort of.

    It’s a self-fulfilling prophecy. If you care about it, you’ll attract people that care about it. And then you’ll create [00:39:00] a more diverse and inclusive culture, which, you know exactly what Tim was saying. You have to do it from the get go. And we did. And then it’s also not just saying it, it’s doing it.

    There’s an awful lot of kind of they call it pride washing in pride month, where, you know, all these companies change their logos to pride. But if you look at their actual way in which they, the things they do, I mean, it’s. It’s the very minimum they can get away with. They don’t actually do, do any, their actions do not suggest they care, their actions suggest they want to cash in on looking like they care.

    Now, that’s not all companies, but, but like, you have to actually then do it in the organization. So the, the other thing mean, Tim and I are really lucky, like the experiences we’ve had and things like, you know, the open practice library and all these practices, design thinking, et cetera. So many of them, you know, dot voting for example, 1, 2, 4 all.

    These are all things that help give everyone a voice in a non-threatening way. And so it’s how you then operate and how you work. And then [00:40:00] that’s expanded out to our, our customers and our clients as well. And we talk to ’em about know. If you want people to be engaged, you need to make them feel like they have a voice and included, and, and this extends to the role you are doing as well as some of the more, you know, traditional DEI ERG, so employee resource groups and, and things like that.

    So we’ve tried to not only do it, I mean, we’re in a small company and Tim and I are pretty experienced, but we’re always learning. So we’ve tried to do all of those things, make sure that everyone has a voice, and we have lots of forums where we listen to that. But also in the work we’ve done externally, try and reinforce those values and those principles in how we run our workshops and how we advise and coach people do these things and here’s why.

     The business case for inclusivity and trying to bring in a diversity of voices is like a no-brainer. But sometimes people don’t know how to make that transition and they don’t realize it’s on a, it’s everyone’s responsibility in how you operate every day, not just. The, the HR group in your organization?

    We’ve seen the benefit of that in terms of [00:41:00] the talent we’ve had into organization and the diversity of people. We have 50 50 male, female, et cetera, et cetera. And but we’ve also tried to take that out and be ambassadors for those ways of working and those ways of thinking.

    It’s very cool to have a partner like Tim to do that way 

    Alexis: I love it. And people will not see that because there’s no video. But I was smiling and nodding as you were talking, because I believe it’s very inspiring and you gave really the, the right, things to inspire leaders to really do something about what, what they can control and to make it happen.

     To close , the session, what advice would you give to new leaders or aspiring leaders

    Tim: yeah. Wow. I would say simply collaborate. Get your people together. I. Get, ideally get, get your people into a room and get ’em [00:42:00] talking. That naturally giving it, it builds on several answers we’ve talked about today, but it’s, let’s get everybody talking to each other and I, you’ve, you’ve got something in common.

    You all work for the same organization. You are hopefully working towards a common mission. And if you’re not. By getting people talking, getting people communicating and collaborating. You will start to align. You will start to get shared view. You’ll start to identify where those slight nickles of misunderstanding are happening.

    That’s the starting point. Just just getting people to talk to each other. Then I would go level Steve about, well, you know, what are we trying to do? Why are we here? What, what, what are we gonna tackle? How are we gonna prioritize? Let’s prioritize, let’s measure. That can come all afterwards, but unless people are comfortable talking to each other, collaborating, challenging, ideating.

    Building upon you know, that is the foundation for success. So whatever it takes in a, to get those people into a [00:43:00] room. Good facilitation, good setup, good planning to to, to put that environment in place to facilitate collaboration. That’s what leaders should focus on doing right now at the beginning of the new year.

    Alexis: Excellent. Thank you.

    Bella: Predictably write some OKRs. Yeah, like that. Actually, let me rephrase that. Think about what outcomes you most want to achieve and narrow down that list till you’ve got like Warren Buffet gives us advice. He says like write your to-do list, and then scratch up everything that’s below number three. Like same thing, like lots of people say it in different ways, but, but you’ve gotta prioritize ’cause you can’t do it all.

    So prioritize and, but make it measurable. The biggest mistake I made when I first started moving into leadership roles is I tried to carry on doing everything that I’ve been doing before and then take on all the extra. And that just ended up with me being like, on this very fast moving hamster wheel and just like.

    Yeah, [00:44:00] it’s, it’s not a, it’s not a good place to have great insights and to be a good patient listening leader. So you’ve got to trust people to take things off you and to create time for you to reflect and think. And part of that reflection is figuring out what the priorities are and then making sure to Tim’s point that you are communicating and collaborating well to, to deliver them.

    And then the last thing. I think this is, you spend a lot of time at work, you’ve gotta make it fun, like find ways to enjoy yourself, to have a laugh. Like in Stellafai on the Friday standup, we always, we all pick a random filter on these Google filters, so we all turn up as like pirates and cowboys and astronauts floating in space.

    It’s a silly little thing, but find ways to make it. Make it fun. Like if you, if you know, you’re clear why you’re collaborating and you’re feeling engaged and connected, and then you are having fun as you do it, the [00:45:00] difference that makes to our working lives is pretty, pretty, pretty phenomenal. So, yeah, set OKRs, find time to reflect and stand still and, and lead , and have fun.

    Alexis: I love. Thank you to, to both of you for having joined the podcast today. Have a great one

    Bella: Thank you very much. It was great to do it. Thanks, Alexis 

  • Cloud Infrastructure Leadership: What Changes When You Lead the Platform

    Cloud Infrastructure Leadership: What Changes When You Lead the Platform

    Cloud infrastructure has changed radically in 20 years. We moved from standing in line to request hardware to provisioning global resources in minutes. Yet the leadership challenges didn’t disappear. They evolved.

    In this episode of Le Podcast on Emerging Leadership, I’m joined by Michael Galloway, a platform and infrastructure leader with experience at Yahoo, Netflix, and HashiCorp. We explore the evolution of infrastructure, but also the human side of platform engineering: trust, ownership, change, and the realities of operating systems at scale.

    From “tin” to cloud: speed increased, responsibility didn’t vanish

    Michael shares an early Yahoo story that captures the shift: the era of physical requests, committees, and scarce resources. Virtualization and cloud unlocked a new world, but they didn’t erase complexity. They moved it.

    The question is no longer “How do we get machines?”
    It becomes: “How do we design defaults, behaviors, and systems that make operations reliable?”

    “Don’t just use the interface”

    A key theme in our conversation is what happens when abstraction goes too far.

    Michael learned early in his career that using an interface without understanding what sits underneath limits your ability to solve real problems. The same applies to internal platforms and infrastructure products: if teams can’t see what’s under the hood, they can’t operate their services confidently in production.

    This matters for DevOps and full-cycle ownership. If the platform hides everything, it also centralizes responsibility again. And that’s exactly the anti-pattern many organizations are trying to escape.

    Setting the right defaults (instead of hiding complexity)

    Michael makes a distinction I find extremely useful:

    • Abstractions can help with the zero-to-one problem (get a service running fast).
    • But sustainable systems require teams to drill down, understand decisions, and troubleshoot effectively.

    His closing line on this topic is simple and sharp:
    Predictability is more valuable than velocity.

    A crisis story: ownership, outcomes, and early wins

    Shortly after joining HashiCorp, Michael faced a real incident: a workflow engine falling behind at scale, with work piling up and trust already eroded. The technical work mattered, but what stood out was the leadership sequence:

    1. Take ownership publicly
      People need to hear: “We own this, and we will fix it.”
    2. Form a durable team around the problem
      Not a temporary war room. A team with a mandate.
    3. Define outcomes that matter
      Not “deliver X,” but “stability,” “scalability,” and “confidence.”
    4. Deliver early wins
      Not a 24-month plan. Evidence now, then progress each week.

    That combination rebuilt credibility and made it possible to redesign the system properly.

    Change at scale: the lesson of urgency

    We also discuss a platform adoption challenge from Michael’s Netflix experience, and what he learned about change management: good ideas don’t spread by themselves.

    Two levers made a huge difference in later roles:

    • A real deadline (a cliff, not a wish)
    • Executive alignment to keep that deadline real

    Michael’s practical insight:
    A target like nine months is close enough to feel real, far enough that teams don’t immediately say no.

    Advice for emerging leaders

    Michael closes with three themes that translate well beyond infrastructure:

    • Understand your stakeholders deeply (including what isn’t said)
    • Deliver a meaningful win in the first 90 days to earn credibility
    • Define the purpose of your team so priorities become easier and autonomy grows

    Here are a few links:

    Here is the transcript:

    Alexis: [00:00:00] Welcome to Le Podcast on Emerging Leadership. I’m your host, Alexis Monville. In this episode, we are excited to welcome Michael Galloway, a visionary leader in the tech industry with over two decades of experience. Currently shaping the future of cloud infrastructure at HashiCorp, Michael brings a wealth of knowledge from his dynamic roles at companies like Yahoo and Netflix.

    Today, he shares his journey, insights on platform engineering and the evolving landscape of technology leadership.

    Welcome to the podcast on Emerging Leadership. Michael, how do you typically introduce yourself to someone you just met?

    Michael: Yes. Thank you for inviting me. Alexis. The way I think I typically introduce myself is I live in California. I’ve been working in the tech industry for about 20 years. Father of two rambunctious girls and husband to a wife of [00:01:00] almost 20 years now.

    Alexis: Wow. Wow, wow. I would love to unpack all those things, but maybe we’ll time for, for some of it. Let’s look at your, your journey in the tech industry. A fascinating journey. I’ve heard about your experiences both at Netflix and now at Hashicorp. Could you give us a, a snapshot of your trajectory and what drew you to that field of cloud infrastructure?

    Michael: Sure. Well, like I mentioned, I’ve been in the industry for more than 20 years. I was actually part of the early two thousands crew at Yahoo. Just before the Google IPO. So that was an interesting experience to start off my career. yeah, that was you know, everything, everything was possible.

    And some of the most brilliant minds that I have the opportunity to work with many years later in my career started there. In fact, my current boss at HashiCorp was also part of that crew back at Yahoo and And and, you know, it’s, [00:02:00] it’s, the Valley is ultimately very small from Yahoo. I went through a number of different ranges of companies.

    So I actually did a startup in the enterprise software space, which I was fortunate to sell. I would say it’s more of an Acqui-hire but it was a great experience to go through what is a startup life like in Silicon Valley. Eventually, I landed in Netflix around 2016. And moved into the platform engineering organization. From there I led a bunch of teams in Delivery Engineering. I think the most famous part of Netflix that people may know of is the Spinnaker product that was developed for the most part between Netflix and Google. And that’s what we evolved and, and worked on. After that, that was really where I fell in love with platform engineering as, as a concept.

    The whole concept of full cycle development and DevOps as we were pioneering it at Netflix was just fascinating and working with some of the greatest minds I I’ve had the opportunity to work in that space. I eventually moved to leading platform organizations [00:03:00] at mid-tier companies, and now I’m over at HashiCorp. Running the infrastructure part of the organization personally. you asked about infrastructure. Infrastructure specifically is a fascinating and evolving space. You know, I actually have experience going in front of David Filo, one of the founders of Yahoo, and making physical hardware requests.

    I remember standing in line a little anecdote there as I I was we all queued up at, at, at, at these hardware request committee meetings. And David Filo is one of several members. And I was right behind this gentleman. I had just started my job. Maybe I was a month, two months in. And the, the person in front of me was from Yahoo Photos, and he goes up to David Filo and he’s making requests for several multimillion dollar filer machines that we needed for the Yahoo Photos footprint. And they discussed and, and, you know, okay, we will ultimately approve. And then my number’s called, and I, I get up and. I said, I’m, I’m looking for $300 to buy a hard drive for one of our [00:04:00] machines. And Yeah. Philo had this look on his face of like, yeah, maybe this, maybe we can do, do some efficiency improvements for this meeting.

    Might not be the best use of everybody’s time. And I say, I, I really appreciated that he saw it that way. But you know, the, so I was, you know, I think a lot of us have experience with the actual tin, but now, but with the introduction of virtualization that really came out many years later, unlocked, you know, all kinds of, of capabilities like you know, immutable deployment patterns and, and real ephemeral infrastructure started to become a thing. And, and finally I think. So, so what we’re seeing is, is the outcome of those innovations and the, and the, this idea that you can allocate virtual global infrastructure in minutes. But I truly think that that’s actually just the beginning of where, where we’re headed as an industry. So it’s an exciting space to be.

    Alexis: Oh, whoa, whoa. Wait, that’s, that’s very [00:05:00] interesting because yeah, with, the introduction of virtualization, basically a lot of people thought, oh yeah, that you, you don’t need to care really about cloud infrastructure anymore, and.

    Michael: Right,

    Alexis: Anyway, everything will be fine with, that’s just infrastructure as code and, and let’s, let’s do everything.

    But that’s not really what happened. Even if we I don’t remember DevOps. It’s what, 2009? Something like that. We are still not there yet. Completely. In your, in your, during your talk at Plato Elevate you mentioned that. Cloud Infra was not about hiding complexities, but setting the right defaults.

    I would like to you to discuss that a little bit more, because that will maybe tell us what, what is coming, what, what the future looks like.

    Michael: Yeah. This is a very fascinating conversation. It’s, it’s something that we can quickly get into Modern applications and lose a sense of principles. So I [00:06:00] like to come at this more from a principles first approach than, than just you know, the common conversation that I hear in many platform organizations or many companies is, how do we become, should we present a Heroku environment? And I think that that’s missing some grounding. you’re talking about how to use it. As opposed to the philosophies of behavior that you want to encourage or support in an organization. So like everything else in software development, the answer is maybe The answer is nuanced, right? But let’s start with the an early, I’ll give you an early story that, that really grounded my thinking on this. It goes back to my Yahoo days actually. So I was a software engineer there and I worked on the Confabulator product. It was a Desktop Widgets product that worked on both Mac and Windows. Actually, the modern Apple widgets experience on the iPhones, as well as Netflix’s tv or Netflix’s video capabilities on tv. And, and all the modern TV [00:07:00] widgets all are actually born from some of the actual same humans that worked on Confabulator. I, I actually worked with some of those guys.

    One of ’em I actually hired into to Yahoo. So just a little short history there. So all things are connected, but I was working on this and I was around much smarter minds than mine. And one of the lead engineers in the group emphasized to me, he said, don’t just use the interfaces to these libraries that, that are, you know, available to us from the, the, the TVs or from the, the OSS systems that we’re trying to operate on.

    Don’t just use the interfaces. You said you need to understand What they do underneath, you need to understand those in order for you to be able to solve the real problems, the hard problems. And he was right. How often we end up grabbing a library and just using it without thought of how is it actually performing these actions.

    And when you do that, and we’ve seen this in software development all the time, where you have higher and higher level frameworks, and [00:08:00] the understanding of the magic underneath is ultimately .Limited to the few that actually care to try to introspect, and some of those frameworks actually actively try to encapsulate and block the ability for you to really understand what’s under the covers. Why does that matter? Is because if it fails to do the thing I need it to do, if my application calls into an interface and for whatever reason that interface has an unexpected side effect, I now have no ability other than to just abandon that interface. To solve that problem. And that becomes really a, a limiting factor. So if you take it from that perspective and you, you, you view software platforms and you view infrastructure platforms or platform engineering platforms, they’re all the same concept, right? They’re encapsulation their abstraction. There’s the same software principles. You start to get to the point where you realize, where do you want to put The responsibility for resolving and solving problems. In a true [00:09:00] DevOps world, you ideally want to enable application teams to ultimately have the ability to understand and operate their products in production. And if you don’t, don’t enable them to be able to see below the details for how something is being done. They have no ability to perform that task. They have to rely on a central team to do it. just like if I am, if I am the provider of a framework, but they can never see into the code of that framework. If that framework fails to do the thing they need to do, they’re going to abandon it or do something different, which will create heterogeneity in the environment and more complexity. So when I think about the right experience, what I look at is Not about hiding the complexity per se. I think you can follow abstraction or present a an interface facade if you want to simplify the zero to one problem that most of the time, this is what they’re talking about. I just wanna get my application out.

    I just wanna get a database. I that’s a zero [00:10:00] to one problem. Provide a simple facade. That’s where the abstraction actually can have value, but. It should be an abstraction that you can drill further down if you want to. You can go further and you can see what actually was done. How did how does this machine perform the actual instantiation of that database? What is the instance size? If it was, say, Amazon, of that database that was set up, I should be able to introspect these things because those can lead to me understanding why a failure occurred. In my production system or how better to architect. A good example of this is a situation that we just recently encountered you know in, in my current universe at HashiCorp, where one of our products has a stateful, it wants to perform in a very stateful way. Well, it is a stateful application. And stateful is a particularly tricky monster to, to from an infrastructure standpoint, right? We really, [00:11:00] very much on the infrastructure side, wanna see the world as I. As, as cattle they say not pets, right? That’s a common euphemism. And and so the idea that I can truly lose or blow away my infrastructure if I needed to and that the resiliency is actually supported both at the application tier as well as other parts of the infrastructure to support the idea that any virtual thing can fail. And the truth is, is that whether anybody likes to think of it or not, I have a lot of experience with yeah. Virtual things fail because physical things fail. So you very much need to have that. If you a stateful application doesn’t like to operate that way. It likes to believe that, that there is a permanence with the thing that it’s in. This is a really tricky problem with infrastructure systems to date. If we have a full abstraction of what is actually happening on the infrastructure tier, especially when we need to version the infrastructure underneath the covers, it can, [00:12:00] it can be a real problem for that, that application team, because they don’t understand why systems are periodically being disconnected or broken or having any predictability around it. So as a result of that, they have to offload all of the operation problems and all of the ops that are specific to their application universe, to the central and infrastructure, the central infrastructure team. And that is the anti-pattern that we all wanna avoid, that the whole point of DevOps was to move out of a central team operating applications in production as much as possible. So that was a long-winded answer. The short nugget here I would say is predictability is more valuable than velocity.

    Alexis: Mm. Yeah. , I guess that that summary helps really to to understand the, the whole thing. Could you tell us about a particular challenge you, you facedworking on that realm of cloud of platform at Corp and how you approached it.[00:13:00] 

    Michael: Yeah I’ll give you a different challenge ’cause life’s full of those. When I joined Hashi Corp let’s see, I joined December of 2022, so December last year. So I’m almost at my one year anniversary actually. About a month and a half in, I would say, so sometime in January all these alarms started going off. It was not my fault. I had just started. That’s okay. I don’t mind if it is. But it was not alarms are going off all these, you know, 3:00 AM things blown up. And so the issue was a big portion of our System relies on a workflow. It, it’s basically, it’s a workflow engine that, that a lot of our use cases require to be operating effectively.

    It’s a, it’s a, the engine’s cadence, it’s used, it’s pioneered by Uber. And temporal is, is maybe a more well known modern name is a, is a Next iteration of that workflow engine. Anyway, [00:14:00] so this thing started to blow up, and the reason it started to blow up was that it was backed by a, a single, very hard, a large database instance. And that database instance was struggling to, to keep up with. An unanticipated load. And this was not necessarily a new issue. In fact, cadence had rather this, this, nothing to say about the cadence Service is perfectly fine workflow engine, but the design was just not well des it was not well designed to be very scalable. And so as a result over the last several years, people had kind of wanted to avoid This system ’cause it was known to be problematic and it had burned people out trying to support it. So, but it had finally tipped over and, and by tipped over, I meant it actually stopped keeping up with the abil, all of the workflows coming in.

    So it started building a history list. I think something on the order of maybe a million. Runs behind and it was continuing to fall behind. Yeah. So, you know, when you see that it’s, [00:15:00] it’s a downward spiral, right? It’s, it, it, and so we brought in AWS people and we performed a quick crew. I. To, to set up basically like a war room situation, to try to triage and stop the internal bleeding.

    And so what’s the first thing you do? You say, okay, well let’s, let’s, if we can’t horizontally scale because we hadn’t sharded this system, let’s scale up. Right? And whenever I hear scale up, I think all of us, and especially in the infrastructure space, kind of cringe ’cause you know, there is a finite limit to scaling up and scaling up. Doesn’t actually solve the underlying problem. Ultimately it just delays the problem. yoU know so we did, there’s, again, our first focus was stop the bleeding. We scale up. It, it helped. Still some things were, were not quite as stable as we wanted. anD this is where I think the more interesting part of the story it comes in because all these kinds of technical problems in my whole 20 year experience. I’ve very rarely been [00:16:00] on what I would consider you know, a Mars landing kind of problem where you’re maybe doing something fairly novel and even that maybe isn’t as novel anymore because we’ve done it before. Uh, most problems are not, in other words, insurmountable technical problems, where there just is no answer. generally, I’ve found that 99% of problems that I’ve had to deal with are more about organizational problems. And, you know, you might even go to say leadership problems in the sense of how do you, how do you think about approaching this kind of crisis? What are the right things to do when a crisis like this happens? And so the steps we took first, the very first thing is recognize that. Upper leadership partners, customers who are relying on this thing all want somebody to say, I’m gonna raise my hand and say, I’ll take ownership of this problem. That’s the very first thing everybody needs. They need to hear you

    Alexis: Mm-Hmm.

    Michael: And so [00:17:00] we did. I I basically said, okay, we recognize this as a problem. I’m not gonna make up stories about this. It’s a problem and it needs to be resolved, so we’re gonna take ownership of it. And what we did was formed a permanent team around this. And that sent a very clear signal, we’re gonna own this problem.

    We’re going to move it to a, a place where you can trust it. anD that was actually a really important thing, not just for the ownership aspect, but there was real lack of trust in building these, these workflows by teams because of the instability history. And so, as a result, teams started to look for alternative approaches, and that would’ve led to a much more complicated universe to manage. So it was very important that they, they knew somebody was going to own solving it. Once we did that we defined some specific outcomes towards stability and scalability that we needed to be able to achieve. It needs to be horizontally scalable, not vertically. I think that was one of the most important things that we emphasized, that the thing we did today [00:18:00] to bandaid, this is not a solution. It’s, it’s a bandaid. What we need is not to try to put all our cargo on one ship. We need multiple ships. And, and so once some of the fundamental, and these are not complicated concepts, but they are complicated to execute on because having multiple ships means a whole lot of additional complexity and logistics up front for figuring out what goes on those ships and so on.

    I don’t know, I just suddenly jumped into a nautical analogy. But these, this is You know, establishing this is what we are, are, this is our success criteria, this is our strategy was critical to get out early. What are the outcomes, not the physical deliverables. The next thing we had to do deliver short-term wins. And by that I mean short term, what anybody ever cared about was stability in, in the short term, as well as enabling products to launch. So the products that we’re afraid to Right on this. We [00:19:00] immediately engaged them, prioritize, making sure that they were stable. They had the resources within the system to be reliable.

    And so we enabled those product launches. And then we pumped out every week what the reliability status was, what were there any issues and any updates or communication on progress towards those outcomes that we had. This was critical. Those two things were vital for us to establish credibility and for people to actually feel like the wind had changed and that this ship was actually going to turn that built.

    Confidence and trust gave us momentum. And, and as we continued to execute, this team has completely revamped the architecture, the system. They’ve migrated a bunch of the critical systems to starting to be able to Have better resource isolation, which are fundamental things in an infrastructure universe to be able to isolate workloads and manage resource consumption by each of those workloads. We didn’t have some of these fundamental abilities before. Now we’re in a state where we’re executing on the we’ve moved away from RDS and we’re bringing in. A scalable [00:20:00] backend, which is, you know, a, a Cassandra backend, which will allow us to horizontally scale. So we’re in a much different space, to the point where a leader about a week ago said to me ” not only do I no longer worry about cadence, I, I’ve basically entirely forgotten that it was ever a problem”. wHich is great except that I said just make sure that we don’t think we can remove people from this team right now. I’m glad you are confident.

    Alexis: Yeah, exactly. But yeah, I, I believe that’s, that’s very interesting. The what, what you offer as a solution. If I put aside the technical solution I, we could apply that to basically a lot of different problems that we have. Having a team that is able to say, okay, we are owners of that thing. And now we own that problem and we will solve it.

    Being really clear about what are the outcomes, where we are today, how we measure those ourselves compared to those outcomes. That’s very, very critical. And and [00:21:00] knowing that you will not win the trust of people by announcing 24 months plan. You will win the trust of people because you are delivering something now.

    yes.

    Michael: yes. 

    Alexis: Getting into that mindset is critical also. So I, I love what you’re saying about all that. Have I missed anything in what you, what you propose?

    Michael: No, I think you sum some, summarized it exceptionally well. I will say generally this you are, I fully agree with you. This is not a unique situation. This is a pattern and a strategy for approaching a, what is, what comes up fairly often in every job I’ve taken, there is always a crisis and I’m going to misquote the person.

    But it’s what I think the famous saying is, never let a good crisis go to waste.

    Alexis: Yeah.

    Michael: these are hugely valuable opportunities to actually have a tangible impact on the business.[00:22:00] anD you know where others may be afraid to tread. These are the opportunities that really enable you to shine as a leader.

    Alexis: I, I really like that. Are there other pivotal moments in your career when, when you, you really learn something significant about change and leadershIp? 

    Michael: Oh my gosh, yes. Well first, if anything I’m saying here sounds at all polish, please understand it comes from the many battle scars that I have over my history of, of making mistakes and reading and learning from, from the wisdom of others, and then having the opportunity again to apply them. But yes, let me answer your question more directly.

    So at Netflix .We and delivery engineering embarked on this initiative called Managed Delivery. It was a very ambitious project that is still very near and dear to my heart. It’s it’s, it’s fundamentally what it is, is delivery in [00:23:00] Spinnaker is done using pipeline, basically articulating pipelines. And what we found from From the way that we were operating where every team was defining their own pipelines. In Spinaker, I think we had about 16,000 pipelines at that time. We across about 4,000 applications, about 400 teams was about the size we were at. Platform Engineering has some challenges. One of the specific challenges was as we, we were still very VM based as we would release new base OS AMI s. That might include security improvements, patches, other things that needed to be there. We had an adoption rate of it took on the order of months to years for certain patches or updates to be rolled out. That was really problematic for us because you can imagine that there is, sure. I mean, if you did a security sev one incident, they could broadcast across the company and people might take action, but that’s a pretty disruptive thing to do. [00:24:00] What you want is, is a design that helps enable the, the bottom tier to be as evergreen as possible.

    Right. But we had a, we had a problem. All the teams owning their own pipelines Spinnaker had no intelligence about those pipelines. It, it just knew, run this, it, it was a workflow engine in many ways. Right. Run this step if that step Gives me a green light. Go to this next step, go to this next step, and, and maybe some conditional logic, but what do those steps represent? And, and what is the confidence after you know, step two as to whether this, this new update is safe to roll out? All of that was opaque to the engineering system. So what we needed was a way that we could evolve our infrastructure and we could evolve our amis, we could evolve our strategies under the covers. anD do so without having to get all the teams involved. So that was one of the motivations. Another motivation was we thought it would make it easier for [00:25:00] teams to also not need to articulate or come up with strategies in their pipelines for safe delivery, right? We teams would deliver applications to multiple regions. What’s the right sequence of steps that would enable you to catch a problem and roll back the change? If, if a failure happened in, say, the second region you rolled out to, which is a very complicated problem, right? First region successful, second region fails, most of the time pipelines would just die. And now you have this very confusing universe where you have different versions of your shafter running and, and problems

    can surface. So we thought, Hey, let’s take that problem away from teams two. Let’s create a declarative form of delivery that basically enables people to define the Criteria for success that would enable promotion from one lower environment to higher environments.

    That was essentially the goal of managed delivery, was move them towards the description of what needed to happen as opposed to defining how it should happen. [00:26:00] Very ambitious on the size that I was mentioning, especially because Netflix culture very much operated with a freedom and responsibility concept, and so that meant that teams were never Really obligated to use a service or a new system. So imagine operating in an environment where you have lots of very smart and talented people from all around the world that are working on their problems, their projects, and you ask them, you, you need to engage them on something that they honestly would prefer to not really have to think about.

    Right? I don’t con like, it, it, the water company doesn’t reach out to me to talk about Repiping .You know, pipes to my house. Like I have no interest in that conversation. If you need to do it, sure.

    Go ahead. Right. It, it’s the same way in delivery, engineering and reaching out to these teams. I don’t know it, my software always continues to deliver.

    It’s fine. Why do I need to care about this? thIs is a very common problem in [00:27:00] platform engineering, but also come from for library producers, API producers, anybody that’s producing something that others are consuming

     you almost always have more interest in in making that happen. Than they do especially when you, the value proposition may be more on one side and the other.

    And that was the key mistake I made. At that time you know, we very much wanted to take the approach of, if we built something really valuable and very interesting for folks they would adopt it. And I think there was merit to that. And so we spent a lot of time thinking about, you know, the early adopters.

    We got some early successes. We got some people to enjoy it. But then we hit that classic crossing the chasm problem where we couldn’t get past the early innovators to the early adopters. And we struggled on that. What was it, was it some combination of features? Was it some combination of capabilities, something that this could do that other things couldn’t? What, what I miscalculated personally was the actual value to the business was the platform engineering side of the, the, the [00:28:00] equation platform engineering needed to see this adopted. Across the fleet for there to be real value. And so given that the strategy may not necessarily be one of slow adoption, but rather it may be more important to take a little bit stronger of, of a, of a, of an approach. And John Kotter talks about this in, in leading he has an article in HBR called Leading Change, but he has a book called, why Transformations Fail. And I will say I read that book during that time and I failed in probably at least the top three even after I read it. So it’s, I will tell you, there is a very, I, I learned how big the gap is between knowledge and wisdom. And, and, and that that gap being how wide experience needs that gap, that that which is experience is that gap, right? And how much of that you actually need. Long story short [00:29:00] you know, managed deliveries, value proposition. Very much is alive, it is moving forward. But that was an experience where I realized because our adoption was very slow, you could imagine that we did not take as an aggressive of an approach, specifically by aggressive, I mean, we didn’t establish a sense of urgency. So teams were necessarily complacent in the adoption. And it’s not no fault to them, that’s the way the culture was designed to operate. But as a result it’s getting adoption, getting that change to actually happen. It was much harder. Now I know that they are doing amazing stuff now over there in terms of, of growing it.

    They, we’ve learned a lot of those lessons and the impact of that approach is really being felt. In fact, years later, I landed at HashiCorp. My peer came from Samsung. Smart Things. He recognized me and said, oh you know, managed delivery. And they apparently larger footprint than Netflix much higher traffic than Netflix.

    All the iot devices right, call into their[00:30:00] and they. Overnight, basically. Maybe it’s not quite overnight, but they, they they fully adopted it and saw some of the benefits of that adoption as a result. And, and and so it was, it was a cathartic to hear or comforting rather to hear. But yes, it was a, it was a good experience in the challenges of change.

    Alexis: Yeah, it’s, it’s very interesting that we are coming, going, going back to that idea of a team owns a problem and now tries to solve it. Unfortunately it’s really a problem for the business, but it’s not necessarily a problem for the other teams. thAt are consuming something from that team. And now how do you create a sense of urgency for the other team when they are not even aware that it’s really a problem for the business and you cannot count on that for them to investigate that part.

    So maybe that it’s other nudge.

    Michael: Well, and I have a, a story about creating the urgency because I, [00:31:00] that’s what one of the things I learned, there’s actually two pieces to that that I learned. And I applied at the next job, actually after I left Hashi after, sorry, after I left Netflix. It was a mid-tier company. We were on a, a, all the entire fleet was on a, a Heroku actually.

    We were hitting problems with that platform. Going back to the ability to introspect and understand how things work, Heroku was too abstract, too high level for us to be able to operate it effectively for the things that we wanted to be able to do. You know, it got us the zero to one, but that, that hard abstraction. mAde a a, it made it impossible for us to get past that one. loNg story short, though, we needed to migrate, we decided the business decided we needed to migrate off. But even with that, we wanna migrate off like all things that happen in a business, they are good goals. They’re, they’re set, like you said, the 24 month goal.

    Oh yes, we should be But how important is that? How urgent is that? I. [00:32:00] This is from my experience with managed delivery, this is what I, I learned. Okay, so two things. One you need a sense of urgency. So how do we create that urgency? You need to get a date set and that date needs to have consequences. So we talked specifically about setting a nine month target from the point that I had started that job and, and the reason for nine months is nine months. Feels close enough that it will happen, but far enough away that virtually no engineering team says no. Right? And, and and I mean this very much affectionately, we all believe that the world is possible in nine months, not three months, but nine months.

    Yes. Nine months. I for sure we’ll have time. So we we got alignment that in nine months we would, we would hit this target. We made sure that the other aspect of this was we were going to shut off Heroku. We were going to actually disable and tear up the contract. And so that was the, the cliff date. [00:33:00] That’s great to have that date. And there’s a lot to unpack on the importance of setting dates, but the other bit that was vital was we needed to get executive, Alignment with that, that needed to be something that the executives would back. And by that I mean you know, the term leadership or executives is, is nebulous just someone in a position of authority at, at the right level that can basically say once you get to that three months away from landing this. That this is a date that will not move. And we, we were able to get that. And those two things ensured that this, that project very ambitious. We moved the entire fleet out and over to Azure, and we had zero service disruption. It was a, it was a remarkable feat. The, the team did an amazing job, but I truly believe having both of those factors Enabled us to do that Herculean task because the last three, three months you can imagine were brutal, stressful[00:34:00] you know we we bought lots of DoorDash for people to, to and, and, you know, and supported them as they were executing on all of this stuff. But once we landed that the entire crew, Could look back and they did and said this was an amazing thing we were able to accomplish, and there was real pride with being able to do it. So very good lessons learned.

    Alexis: I love it. I love it. And once again, that’s, that’s really interesting to, to unpack the learnings about that. Yeah. You need a date and when, when people hear that. They can hear that, yeah, that’s a date, but maybe we can be late and no, that’s really a cliff that’s, there’s nothing behind. And and you need that support, that alignment.

    So nobody will dare to change the date. There’s no option around that. And that’s absolutely clear for everybody. So now they can make plans. They have the time. Nine months is, is is a good one. We were thinking, yeah, it’s feasible. And, and, and I, and then, you know, thing about it, I, I realized that when you [00:35:00] were saying it, that if you would’ve said three months, I would’ve say, oh, no.

    That I would’ve started to think why it was not possible. But nine months I was comfortable to say, yeah, okay. And I know nothing about the challenge, the reality of the challenge. funny. So yeah, you can start making plans. That’s a, that’s a, that’s a.

    Michael: That’s right.

    Alexis: What, what would be your advice to emerging leaders or who want to make a meaningful impact?

    Michael: The first thing I would say is you need to understand your stakeholders. I have learned the enormous value in getting, developing those relationships and deeply understanding who your customers are who your peers are. Who and what leadership is expecting of your organization? A lot of people, I think, focus, especially emerging leaders, they focus on their team and down. I have a lot of experience in [00:36:00] doing that and failing beautifully because I misunderstood what was expected, what was not spoken, but expected by my peers and by upper leadership. And so you really need to understand not just the the surface statements of here’s our goals, here’s our outcomes. What you want to ask is what keeps you up at night You want to ask where things have failed in the past. You want to hear the, the, the reactions. More than you want to hear the thoughtful process of, of desires, right? It’s those emotional reactions, those small perceptions of your team and of what is expected of, of your organization that actually will influence whether or will, will influence whether or not you are. Well, it’ll affect whether or not you are successful because those are the micro perceptions that actually determine whether they are are, they’re going to think of your team as a team to rely upon for those next strategic steps that they want [00:37:00] to take. Right. So understand them very well, and that takes a lot of time, and there’s great books on this. But this is where it truly is around a psych the, the psychological approach far more than it is that technical execution or delivery. The next one is you need to deliver wins within the first 90 days of starting a new job. And there is a great book, first 90 Days. I think it’s a fantastic book on this topic. I Have, I’ve applied it and successfully a few times now. It very much is correct. Get that, get that win. You have to have credibility when you go into a room. You have to be able to be believed when you say we should do X or Y. Otherwise, you’re gonna stay in the tactical level always because you haven’t established that you can actually solve bigger problems. The key thing with getting that credibility in the first 90 days is you don’t need a big win. You just need something meaningful, something that addresses a concern. Peers of mine had actually mentioned this to me years before too. Don’t [00:38:00] try to run after. The biggest thing you can run after, especially when you first start, start with something. yoU, you, you can own and influence, so it’s something within your control. Don’t do something that’s gonna require a bunch of other folks to be aligned, especially when you first start. It’s challenging to do that, so it should be something for the most part, you can control. I. Second part, it’s gotta be something that matters to other people.

    It doesn’t really matter what it is. It doesn’t have to be a technical solution. It could be an organizational solution. It could be an information solution. It could be a communication solution. It could be any of these things, but it needs to be something that actually addresses a, a, a fear or concern. A great example of this is just starting a monthly newsletter for your organization and ensuring the rest of the business understands even what your team does or your group does. That’s surprisingly a big problem in many places is just the awareness factor, and doing that suddenly puts you on the radar of a lot of people, and it can really, it can really move things forward.

    That’s not a technical problem at all,

    Alexis: Yeah.

    Michael: but it is a problem and it can establish you. [00:39:00] The third thing that emerging leaders need to be taking a look at to have real meaningful impact, define The purpose for your team. And by that I mean you need to bring your team into that. But defining a purpose is one of the most fundamentally powerful actions that I have ever learned to take with my team.

    And purpose is different from mission and vision. a Purpose is. It is the, it lives the lifetime of that team or that group that you are managing. And a purpose is not it, it sometimes it’s referred to as a North star. I don’t think it’s quite that. It’s not quite that right way of seeing it. A purpose.

    This establishes a philosophy that everything stems from. So one of my favorite examples of this was I think he was a, gosh, and the name is gonna slip outta my mind, but he was a, a French designer actually, I think that helped establish the purpose for Disneyland and that purpose was to create happiness in the visitors. Now, if you think about that, that sounds very simple, [00:40:00] but it’s a very powerful fulcrum. Because at that point, when you have that, everything from how you name the parking lots, you name them after Mickey and Goofy, not A and B and C, the design of the trash cans, the uniforms, the decision to have very pleasing flower beds that are millions and millions of dollars of investment for each of these things. Why do you do that? Because each of these pieces maybe make somebody smile a little bit more. Establishing a purpose for your organization enables you to prioritize. It gives your teams freedom to execute and to think more broadly and it enables you to align with what your next strategic steps need to be. It it really is the guiding, you can think of it as a guiding principle. So there’s, I, I’ve written articles on this and, but there’s much better, smarter minds than mine that have, have spoken on this

    Alexis: Ah, I will link to that and we will let people [00:41:00] people decide. About that . So what, what’s next for you? Any exciting projects or initiatives you, you, you want to share?

    Michael: Yeah, so well with Hashi Corp I think one of the exciting things that we have coming up next from the platform engineering organization is really trying to crack this self-service nut. You know, Hashi Corp is an organization that has, we we build tools for infrastructure management, right?

    I mean, we build tools for platform engineering. How do we, how do we leverage all of the, the tools that we have and the patterns and behaviors that we wanna encourage to enable self-service within our organization? So a team being able to go from zero to one. I know this is a nut that a lot of people have cracked in the sense of they’ve created, you know, IDPs, right?

    In, in internal developer platforms. But I think that that’s more of a, a, a how, and I think I wanna get back to again, the principles. What should that, what, what are we caring about enabling the actual day One [00:42:00] problem of give me a service is not a hard problem to solve. It’s been solved a lot. The day two problem of now I wanna add a database to my service. That’s a harder problem. And that’s one of the ones I’m excited to see get moved forward. Yeah, so that’s, that’s, I’m looking forward to that next

    Alexis: That’s very cool. So let’s talk again. Thank you very much Michael for joining. have fun solving that.

    Michael: Thank you, Alexis. 

  • The Conductor’s Magic Wand: Transforming Leadership

    The Conductor’s Magic Wand: Transforming Leadership

    In the latest episode of Le Podcast on Emerging Leadership, I had the pleasure of hosting Noah Max, a visionary in the realm of classical music. Noah, a composer and conductor, shares his profound insights on leadership within the creative arts.

    🔹 Creative Leadership: Noah describes his role as a composer akin to being a thought leader, constantly striving to innovate and push the boundaries of classical music.

    🔹 Challenges in Classical Music: He highlights the difficulties in bridging the gap between classical music and wider audiences, emphasizing the need to communicate its relevance and vitality in people’s lives.

    🔹 The Power of Art: Noah passionately speaks about the personal and almost therapeutic impact of engaging with the arts, beyond intellectual understanding.

    🔹 Leadership in Practice: Sharing his experience with the opera “The Child in the Striped Pyjamas,” Noah reflects on the importance of team synergy and the challenges of leading a creative project.

    🔹 The Conductor’s Role: He delves into the unique dynamics of conducting, where a blend of vision, listening, and collaboration is key to creating a harmonious performance.

    🔹 Immersive Leadership Workshops: Noah discusses his innovative workshops that allow individuals to experience the role of a conductor, emphasizing self-discovery and personal growth.

    🔹 Personal Development: He stresses the importance of continually challenging oneself to grow as a leader, drawing parallels to physical training.

    🔹 Mentorship and Inspiration: Noah shares his experiences with mentorship, both as a mentee and a mentor, highlighting the reciprocal nature of these relationships.

    🔹 Future Projects: Looking ahead, Noah is excited about his upcoming compositions, including his first symphony.

    🔹 Advice for Leaders: He advises emerging leaders to tune out the noise and listen to themselves, making decisions based on what truly matters to them.

    Tune in this enlightening conversation with Noah Max, where music and leadership intertwine to create a symphony of insights. Tune in to this episode to be inspired, regardless of your field!

    Listen now and let the music of leadership elevate your day! 🎧

    References:

    Transcript:

    Alexis: Today, we have a truly enchanting episode lined up for you. Noah Max masterfully blends the art of music with the essence of leadership. He’s a creative artist, not only a composer and a conductor he’s an innovator in the world of classical music.

    Alexis: Welcome to Le Podcast on Emerging Leadership, Noah. How do you typically introduce yourself to someone you just met? 

    Noah: Well, it’s lovely to see you, Alexis. Thanks for having me on the podcast. I suppose I would go in with creative artist. Because that’s something everyone can relate to immediately and understand. I work specifically in the field of music. I do a number of different things within the field of music, including conducting, which I know we’re going to speak about later on.

    But primarily, at heart, I’m a composer, which means I write music. And that sometimes leaves people a little bit nonplussed, because they’re not quite sure what [00:01:00] it means to create music from scratch, or You know for what context are you creating music? What does your life look like if you’re getting out of bed every morning and what writing music?

    I mean, how does it work? So the way I would describe it is that I’m attempting to imagine sounds that nobody’s heard before and then notate those sounds either for existing instruments, combinations of instruments, or perhaps even inventing an instrument physically or electronically which doesn’t yet exist, in such a way, so notating it in such a way that Performers could then realize that vision for an audience.

    And often for me, that’s within the context of classical music in the concert hall. Sometimes it will be for television, film, something of that description.

    Alexis: Okay, that’s fantastic. So now I guess people are wondering, are, are we on a [00:02:00] podcast about leadership? And I’d say, yes, we are. And I will ask a question about how do you define leadership in that context of composing and conducting? And what are some of those unique challenges you face as a leader?

    in the musical world. 

    Noah: I suppose there’s two ways that you can look at a question like that. And one of them is intensely creative and one of them is intensely practical. So from the perspective of composing, I suppose it’s sort of like being a thought leader or a philosopher in that you’re trying to move things forward.

    You don’t simply want to repeat things that have already been done although there’s nothing inherently wrong with that but you want to bring something original and valuable to the table, which is going to in some way move the dialogue forward during the course of your creative lifetime. And then there’s the more practical side, which I suppose Through my composing [00:03:00] through my conducting, excuse me, and my other activities one gets a little bit closer to this, which is the fact that there’s a lot of worry in the classical music world that we are in a sort of declining landscape.

    It’s certainly a very confusing landscape at the moment. I think there has been a great failure in the world of classical music to communicate itself to the wider world and to build bridges with the wider world. To show people who may feel no great connection in their life with classical music, contemporary classical music, romantic classical music, baroque or renaissance music it’s felt to communicate the ways in which that can be an important, an incredibly vital and, and life giving and sustaining force in, in people’s lives. 

    And so, you know, having failed to communicate that, no wonder people don’t necessarily feel as connected to it as maybe they could or should. And so, part of my mission in all the different things that I do is to connect people [00:04:00] with the arts in any which way, no matter what they spend their life.

    doing. I would like them to have an inroad so that they can, you know, feel the beauty and the sometimes overwhelming power of these mediums in their own life.

    Alexis: Wow, that’s beautiful. Ah, that’s beautiful. And I hope that will trigger the interest of people to have a taste at it without the intellectual knowledge that is coming to that. I’ve, I’ve observed times and times that people don’t Listen, or don’t watch paintings or look at it because they don’t have the knowledge that is going with it.

    And I’m saying that’s, that’s like tasting food. You, you don’t necessarily have all the knowledge behind it, but you can taste it and maybe you like it. Maybe you don’t, or that could be a drink, that could be food, and that could be music, or that could be painting. Maybe just have a look at it and listen to what is happening inside [00:05:00] yourself.

    That would be. Maybe your first time, don’t you think? 

    Noah: Oh, absolutely. And the wonderful thing with these things is that there’s no incorrect response. Including, you know, perhaps a work of art which everyone says is a great piece of genius leaves you feeling cold. And, you know, that’s fine. It’s an intensely personal thing. I think to just sit and observe a work of art or to sit in a concert hall, which feels incredibly formal and sometimes quite rigid.

    And to experience a work of music over a period of time. It’s an incredibly intense experience and it’s a beautiful experience, but beauty can be terrifying. particularly if you’re not used to it, if you’re not accustomed to it immersing yourself in that beauty can be a terrifying experience, and that’s one of the reasons I’d encourage everyone to do it.

    I think that’s part of the vital nature of it. But you also mentioned the intellect there, Alexis, so just to pick up on that for a minute. Often I [00:06:00] find we over intellectualize, actually, the problems in our lives, whereas accessing the creative arts is to do with intuition and the realm which is beyond the intellectual and beyond the statistical and the scientific and the measurable, although all those do come to play in their own.

    special, interesting ways. But so much of what’s important is not that. And actually, I think this is the sense in which this is a life giving force. So you compared the analogy with food and in some sense that’s correct, except that we all have to eat three times a day or thereabouts in order to sustain ourselves.

    So food is a life giving force in a physical sense. We need the calories in order to sustain our lives. Just like we need a roof over our heads. Et cetera, et cetera. But You might say, well, why do I need painting in my life? Why do I need theatre in my life? Why do I need cinema, for that matter, in my life?

    it gives you something which is completely personal to you and which is [00:07:00] not quantifiable, no matter whether you think you’re a creative person or not. And I used to be incredibly naive and evangelical about this. I felt that everybody was creative. And I no longer think that’s True.

    And I think a lot of people actually feel tremendous pressure that maybe they should be creative and actually it’s not part of their nature to produce things from scratch. And that’s completely fine. a work of art can feel as though it’s judging you, but there should be nothing judgmental about the process of appreciating art.

    And I would like everybody to have their own way in, perhaps to step out of the intellect. And this is something I continually remind myself that I need to do. as well, because it’s not always the best way to solve a problem.

    Alexis: I love it! Thank you for sharing that. Can you share an experience where your leadership skills were put to the test. 

    Noah: Well, the obvious one which comes to mind, and there might be some listeners who are aware of this, as I know you are I’ve spent the last five [00:08:00] years bringing an operatic adaptation of John Boyne’s novel, The Boy in the Striped Pyjamas. And you know this because you were at one of the instrumental rehearsals actually in London back in early January.

    Can’t believe it’s so long ago already. But every single part of that process was a struggle. Writing the music was a struggle. Doing the research in order to take the entire project with the requisite seriousness was a struggle. Digging into my own family history and my connection with the topic matter was an immense.

    Uphill climb spiritually and the logistics of putting on the performance, which we did pretty much single handedly myself and the Echo Ensemble, which is my orchestra, which sort of morphed into an opera production company for that project. And everything went wrong, which could possibly have gone wrong on ways to, I mean, I would.

    We could just [00:09:00] sit here for an hour talking about the litany of things which went wrong and I was working all hours in a very unhealthy way. So it’s not something I would hold up as a model of good practice per se. And it’s certainly not an experience I would like to repeat. But it was in its own way, the best of times.

    And the reason for that was because of the wonderful synergy in the team. And the only thing which functioned properly on that whole project. Was my team and I told them that and I even with all the other things vying for my attention. I made my priority to Nurture the synergy of that team and fortunately that turned out to be a good investment of resources.

    Alexis: Yeah, it’s, it’s, it’s very interesting what you’re saying about the unhealthy way and all the things going wrong. I was, I was listening to the serial entrepreneur, who created several companies not all of them were [00:10:00] successful. In reality a few of them were successful and a lot were small disaster and bigger disasters.

     and he was reflecting on that and he was saying, oh, you, read on LinkedIn and you believe all those people are very highly successful and highly driven and they are really good at all what they are doing and, and everything is going well for them. in reality everything is going wrong every day. And you just need to handle it. And sometimes you do it well, and sometimes you learn something in the process of, in your experience, and sometimes you don’t. And it’s even getting worse. So, there’s just a few things that matter, and that That’s how you are doing that, not all by yourself, but building a support team, you just mentored on that.

    That was your team. So what happened with that team? What, what is that team and how it works [00:11:00] for you to work with the team? 

    Noah: Well, there are certain differences, I suppose in that making music is a process which is incredibly emotionally vulnerable. and very intimate and you have to be sharing of yourself whenever you’re doing it. I was conducting this project as well. So it was my own music that I was conducting with a team that I had hand picked.

    So these were all musicians I deeply admired and. respected and enjoyed working with, but when you’re working on topic matter, that’s as dark as that for a sustained period of time, it’s just a great challenge. And the endurance is a challenge. I mean, on a personal level, what I kept reminding myself whenever I was fatiguing, which was often was It’s never going to get better than this.

    So just enjoy every minute, which seems counterintuitive again, given the topic matter, but, [00:12:00] but it was necessary to get through it. And actually on the team level, I think that was reflected too, because I wanted to make sure that there was enough room for. levity and a bit of risque gallows humor, you know, because you can’t just be heavy and serious all the time.

    And opera making is fun. It should be fun. It’s very interesting to me what you’re saying about the, you know, the, the, the front facing is, is always incredibly. Successful. And then, you know, generally the failures are kept private. I mean, there was just such a huge litany of failures and false starts on the road to this project.

    And without the support of, I mean, the whole team, but particularly certain individuals who were attached to it for, you know, right from the start years earlier. I don’t know whether I would have pushed through all of those, but it’s just interesting as well, when you zoom out. You know, if you read the daily news feed, it’s always bad news because bad news happens in the short term.

    I do, I don’t do any social media. I deleted all my social media. I do a newsletter once a month and when you zoom out And you only [00:13:00] do your news once a month, generally the news is more positive over the mid and the long term. Just an interesting thing to, keep in mind. I mean, it’s wonderful that with pyjamas, I think, you know, given that I’d never put so much energy and effort into anything in my life.

    And to see it rewarded and to see my team rewarded through the reviews that we got and the recognition that the project got was, was absolutely wonderful. But that’s not an accurate reflection of what was going on under the surface. You know, the duck’s legs were, were very much tangled in the weeds there.

    Alexis: you mentioned the rehearsal I was amazed of a lot of different things, but things that I still have in mind, there were the composer and the conductor. And so that was your own music. But you were already comfortable with the musician to challenge a little bit the composer or to to make fun of the composer [00:14:00] in some ways about the music itself.

    And I thought it was really funny to say they are, and you are making fun of yourself or Separating yourself from the composer, from the music, because now we are trying to to play the music. it’s two different times. And I was looking at that, it was really interesting.

    And there was sometimes the, the explanation of the music also. What is happening? That to give the context of, okay, we are, we are starting at that particular measure and you give the context about what is going on and you you explain what is going on what you would like to hear and and there’s a dialogue with the the musician and i i saw them taking notes on the on the score about what was going on and and you give them feedback And they ask something and I was that dialogue was fantastic in a way in my mind the music is on the score.

    You just play [00:15:00] it and you’re done and that’s absolutely not what is happening Which was amazing to me Do you have some some reflection about what is going on when you are doing the rehearsal with the team? 

    Noah: Well, that situation was very specific. And I think being a composer who conducts creates a very specific. Scenario whereby you can offer certain insights. into the process of how something’s been created and what the thought process was behind it. Whereas if it’s somebody else’s music, you’re not necessarily in a position to do that.

    Although even that only goes so far, interestingly. I often feel as British composer William Walton must have felt, there’s a possibly apocryphal story of a occasion when he was conducting his own great oratorio, huge orchestra and choir called Belshazzar’s Feast. Tremendous piece. I recommend everybody who is listening to this should go and find it on YouTube, but he was conducting a performance of it and somebody asked him a very [00:16:00] specific question of, oh, you know, you wrote this marking in this bar.

    What did you mean? And he said, well, I’ve got no idea. I wrote it 20 years ago.

    Not the response you’d expect or maybe hope for, but by the time we were performing that I had written the piece a year and a half ago in a frenzy of creative activity. And so much of the creative process is a mystery, even to the creator. So there were situations where people were saying, you know, what did you mean by this?

    It’s like, well, you know, what did I mean then? What do I? think I might want now, and you know, are they the same thing? Possibly not, and neither of them might be right. So it’s tricky, but you know, under more normal circumstances, I, I mean, see with conducting, there are no normal circumstances. It’s an extraordinarily strange situation you find yourself in.

    [00:17:00] Just to give people an idea, just the slightest idea if you’re an international conductor, say, and you are guest conducting with a series of symphony orchestras around the world, you’ll be traveling one week, one place, one week, another place, one week, another place, maybe you’ve never gone to these places before, maybe you don’t speak.

    the languages in any of them, and you’re confronted with 80 people who you’ve never met before, and you’re all performing music in three days time that none of you have ever performed before, and somehow you’ve got to create a performance that is going to be spiritually valuable to the 5, 000 people who are paying to see it.

    Or however many people it is. So it comes with extraordinary pressure, and it’s an extraordinarily aspirational job. There’s so much of it which is mysterious. It’s actually the mysterious elements of it which I really love. And when I’m introducing people who have no idea about conducting to it, as you know, I know you want to talk about these workshops a little bit [00:18:00] later on I think those mysterious and magical elements are the ones which are worth paying the greatest attention to, in a way.

    But there is that magical synergy between the group, almost like a murmuration of birds. You know, how they know when the next one’s going to turn in that direction. It’s, it’s all just, you know, it shouldn’t be possible. It really shouldn’t be possible. According to science, it shouldn’t be possible for a string player to play their instrument in tune.

    And yet everyone does. I mean, to get your finger within a nanomillimeter of whatever it is, it shouldn’t be physically possible. So, you know, what we’re doing here is the impossible. That’s what we’re talking about. And I mean that literally, not figuratively.

    Alexis: and that and that’s a that’s a very interesting thing and I would like to go back to What is the level of freedom for the musicians to express themselves, express themselves when they are playing that music? [00:19:00] I thought there was a dialogue between the conductor and the musician. And so that means they have a degree of freedom in that process, individually and together.

    So there’s something going on there, I believe. 

    Noah: Yes, I think It’s very interesting because I think a group is looking to, the leader for the vision of the whole because everybody has their part to play in the whole. So you need to present a vision of the whole but not in a way that feels dictatorial. It’s got to start with listening and assessing what’s the player’s needs are as specialists.

    You are essentially a generalist as a conductor and you are there to help a group of specialists achieve something together, which perhaps they hadn’t even dreamed of possible was possible when they were just individuals in their practice room or, or, you know, whatever it was [00:20:00] sometimes an individual will have an idea which is incredibly valuable.

    Sometimes the hive mind will just come out with something which, you know, you never would have thought of. Much better than anything you could have thought of. And so rather than feeling as though you’ve got to impose your vision, I think there’s always got to be a dialogue between the two. And if you are trying to convince people to do something your way then first of all, you really need to be sure about it.

    But also, you know, just telling people to do it isn’t enough. You sort of need to coax them to, to sort of, to try it and explore it and, and to maybe feel as though they thought of it themselves. And there’s a little bit of You know, magic about that as well. Maybe misdirection, but

    Alexis: I love that because now I can see the parallel with the world of business and all the teams that needs or so the to assemble the creativity of specialists to accomplish something bigger. [00:21:00] and speaking of that, you offer. Immersive sessions with musicians for people to understand what happens behind the scenes.

    And so what inspired you to start those sessions? 

    Noah: that’s right. It’s an incredibly exciting journey, sort of honing these sessions into what they are now. I think I was inspired by the figure of the conductor itself, which looms large over the popular culture in a very strange way, because nobody really knows how it works. Conducting. Sort of this person who stands up on a podium and waves a magic wand, and there is that image there, that archetype of the magician, the wise old sage, and you’re sort of harnessing that power.

    And that’s been an incredibly powerful icon, I mean all these films coming out now, there’s a film just coming out very soon about Leonard Bernstein who was a big force in the culture. There was a film with Cate Blanchett, the name of which I forget. [00:22:00] And you know, there was a film about 10 years ago now called Whiplash, which is an extraordinary movie with a great performance from J.

    K. Simmons in that. So people sort of have these preformed ideas of what a conductor might be. What I’m very interested in is the fact that when one steps onto the conducting podium, your personality transforms. this is as true of me as it is of anyone else, and it’s as true of as it is of non musicians.

    that self transformation can be, I mean, it’s incredibly volatile. But I think it can be a great vehicle for self discovery and for self actualization. And in that space where you can no longer verbalize, going back to this thing of intellectualizing, you know, when you’re confronted with a bunch of specialists who do something that you know, nothing about.

    And all you can do is wave your arms at them and communicate yourself physically. Suddenly you strip away all the nonsense and you’ve got a space in which there’s this [00:23:00] embodied learning experience. And you can, oh, you can discover things through this, which I promise you, you could not discover any other way, given years and endless streams of cash.

    It’s a unique experience and I recommend it to everyone. So this is part of my mission to sort of coax everyone into trying it, I suppose, and to see what it can offer them.

    Alexis: you describe a little bit how it works? 

    What people are supposed to be doing? 

    Noah: So we have an ensemble and we have some music and the participants and I will do a little crash course on how you hold the stick, what the basic moves are, just get a little bit comfortable with that. And then we throw people in the deep end and we invite you up to stand in front of the group and We see what happens and whatever your starting point is, we work from there and it’s quite extraordinary because I’ve never [00:24:00] had a situation where we’re unable to make progress.

    I mean, even somebody who’s never listened to a piece of classical music in their life. Sometimes people who have that actually have no foreknowledge. Often end up being the best at it, strangely. But you can make a lot of progress. And once you sort of got used to the very strange sensory overload, all these different things coming at you at once things start happening.

    It’s very hard to verbalize. You know, I struggle to verbalize it. All I do in my situation as sort of mentor is I just try and again, just sort of lead people along and see if I can get them to notice the sensations within themselves and how they can modify what they’re doing to get a better more vibrant response from the musicians.

    And we get the musicians feedback as well, which is It’s incredibly exciting because obviously they’ve played for many, many conductors. And I’ve heard behind closed doors from some of my players that actually some of the conducting they witness in these sessions is better than [00:25:00] some of the conducting they witness in their professional lives as performers.

    So you’d be surprised at what you’re capable of, man. I mean, I don’t know. You should.

    Alexis: really love that idea that people who know nothing about it able to feel it in a way. So, basically Listen to what is going on in themselves. Listen to what is the feedback they have from the team and adjust their behavior so that the result will be different. And basically that’s what we are trying to tell leaders in other fields to really understand.

    How they should.

    adjust what they are doing to have a different response. And that’s not, that’s not changing the others, that’s changing yourself. and look at what is going on, what is really going on. And it’s it’s very interesting that the parallel is so obvious. I am, and I’m now really excited and I would like to try that. 

    Noah: [00:26:00] You should.

    Alexis: When the people are going through that immersive experience what do you believe they take away from that? 

    Noah: they won’t necessarily take away What they want, but I believe they will take away what they need. And it may not be something that they’re capable of verbalizing at the time. It will start off as a felt difference in the way they operate. And then maybe when you step away from that slightly remarkable experience and go back to your life, which is also remarkable.

    I mean, everyone’s life is remarkable in its own way, but you know, it’s, it’s also repetitive and it’s the world that you know. You take the treasure back from the cave into the world that you know, and you see if there’s things you can do, optimize, streamline in order that you can find that sensation again you find out what [00:27:00] that embodied knowledge means to you.

    I’m hesitant to say too much because. I don’t want people to come along thinking that they should. I mean, you might come to the session thing. Oh, I really just want to increase my confidence in front of a crowd. And, and, you know, my, my presentation skills, it could be something as simple as that, but that’s not, I mean, you’ll get that.

    Don’t get me wrong. You will get that. And then some, but. it goes much deeper. There’s almost something therapeutic about it. And I’m very interested in the depth psychologists and their writings. And I’ve also, because of my, my Viennese heritage, my ancestors escaped from Vienna at the same time as the Freuds. 

    And they were very much in that scene, which was filled with you know, these great thinkers and artists and stuff. So I, I’m very interested in all that literature and all that thought. You know, I’m hesitant to say too much because I think it’s something deep I don’t want people to have too many preconceptions.

    Alexis: But I love it. I believe that we discussed [00:28:00] enough so that people can understand that that’s an experience that you need to live and something will happen. And I, I love what you are saying about, that’s not necessarily what you want, but that’s what you need. And that’s a kind of Nanny McPhee experience.

    So, sorry, 

    Noah: it’s funny you say that, because I, I often think of the Nanny McPhee thing, that when you, you want me, but you, sorry, you need me, but you don’t want me, I have to stay. Is this right? And when you want me, but you no longer need me, I have to go. It’s one of the tragic truths of, of life, I think.

    Alexis: that’s, that’s a, that’s a very interesting, interesting one. So, how do you continue to, to grow and develop yourself as a leader? 

    Noah: Well, you have to do things which are going to stress you and stretch you regularly. Anybody who goes to the gym knows this. It’s, you know, relaxation is no good, and pure tension is no good. It’s a [00:29:00] cycle of tension and relaxation which creates hypertrophy. And I think the same is true in terms of the challenges one needs to take on.

    So I’ve recently completed this huge challenge and I spent some time after that feeling slightly listless with a big striped pajamas shaped hole in my life. But now I’ve got myriad new challenges which are really stretching me in completely unexpected and completely different directions. So I’m flexing muscles that I hadn’t used before and I hadn’t maybe even known were there.

    And I think that’s, that’s crucial. 

    Alexis: Excellent. I, I, I love the stress and stretch and the part with the, the gym that will really help to, to understand that. Do you have any mentors or role models who have influenced you? 

    Noah: Well, I, I did. In some sense I still do. But I had a mentor called [00:30:00] John Whitfield, who was a bassoonist and a conductor. He founded his own ensemble, just as I have my echo ensemble. He founded Endymion Ensemble, which was a jewel in the crown of British chamber music making in the 80s if anyone’s interested in Endymion, again, you can find their recordings on Spotify, YouTube tremendous stuff to be found there.

    I met John in the last years of his life. He was very unwell. He died quite young. He was in his mid sixties when he died. He’d had health problems throughout his life, but he was a tremendous mentor and support to me. We met completely by chance at a concert. So, go to concerts, you never know who you’ll meet. it’s strange to me now, because it’s been several years since he passed away. And Stripe Pyjamas originally was his idea, actually, we, we, it came up in a conversation that we had. he would have loved to have seen it realised. And, and that made [00:31:00] me think, you know, that he was investing all this time and energy in me, knowing that he wouldn’t live to see me fulfil my potential.

    But it was what he wanted to do, and actually I’m convinced that, I mean, I, I supported him with his endeavours as well, and those were life giving for him in his state. But the ability to engage with. musicians and players to arrange and orchestrate music, which he’d always loved doing. And he did some of his best work in those last few years of his life.

    So he was an incredibly inspiring man, a difficult man as well. And I think he wanted me to avoid some of the pitfalls that he felt he’d fallen into. when he was my age, particularly regarding the vicissitudes of a creative lifestyle, which maybe are more volatile than if one were working in a different, slightly more stable field.

    Alexis: Do you have other people now? that are that are inspiring [00:32:00] you? And the second question that is coming just after is are you are you mentoring other people yourself? 

    Noah: Hmm. Well, there are plenty of people I find inspiring. I find you inspiring, Alexis. But in terms of mentorship, you know, John was my mentor and I was very, very fortunate. Nowadays, I keep my own counsel and I do my own thing. So life has changed in that regard over the last few years. And yes, I do try my best to be a support to my own colleagues and to my students of whom I have a few and they’re tremendously bright and, you know, many of them conductors, some of them composers.

    And so I try to just nudge them in the direction of interesting things. in order that they might shape themselves, which I think is what John did for me. And I mean, also [00:33:00] in funny sort of ways, I was a mentor to John as well, in that I encouraged him to remain musically active despite his ill health. I have a lot of friends of mine who are of older generations as well, and I occasionally try to provoke them and poke them into some kind of creative activity, which I think might be good for them and usually I’m right, so.

    Alexis: Yeah, I love it. I love it. So, What are some upcoming projects you’re excited about? 

    Noah: Oh, well, it’s mostly writing at the moment. I’m very deeply involved in writing projects. I’m currently writing my first symphony, which is a huge undertaking, very, very different from the first opera. And that is a commission for the London Mozart players, which is a chamber orchestra here in London, tremendous group, really lovely, lovely people as well, which is a wonderful thing.

    I feel very fortunate to be doing that. And that will be premiered [00:34:00] in the summer as the opening concert of the Thaxted Festival, which was the birthplace of a composer called Gustav Holst. So if you’re new to classical music, you’re getting loads of names here today. Gustav Holst is one to stick into your browser, particularly because next year will be 150 years since he was born.

    So it’s sort of commemorating that happy occasion, that milestone. So, so it’s all, it’s a great honor to be doing that. And I’ve got a number of Very exciting composing projects, which are lined up for the new year as well. So it’s going to be busy for the next bit. But at some stage, I look forward to getting back to some, some carving, some conducting as well.

    Alexis: Love it! there will be a lot of references to add to the companion blog post And, and finally do you have any advice for emerging leaders, regardless of their 

    Noah: See, I’m always just hyper aware of how specific my field is and in giving general advice. I never want to, you know, I’m just so [00:35:00] conscious of the fact that. Music can feel like an alien world, so could I really give advice more, more generally? Well, you know, maybe, maybe I can. At the risk of sounding blithe and clichéd, I think you’ve really got to learn to tune out the noise and listen to yourself. It’s very easy to expend a lot of energy on stuff that you do not care about and which you’re not really interested in pursuing for whatever reason. And there is so much static and noise out there now.

    So learning how to tune your radio set so that you can figure out a good principle on which to make decisions so that you know what it is you want to do and where it is you want to go. I think, you know, whatever kind of entrepreneur you might be. That’s useful because you could [00:36:00] invest a huge amount of your time, energy, money, other people’s money into creating something that you don’t really believe in.

    And I know people who’ve done that and, you know, they always learn from it, but never ends well. if you can avoid it, then perhaps that’s a good thing too.

    Alexis: that’s beautiful. love it. I will add a few links about where the people can find your work, follow your work and get in touch with you. And I’m very thankful for having you join the podcast today. So thank you very much, Noah. 

    Noah: Oh, well, Alexis, it’s been a pleasure. Thank you for having me, and if anybody wants to know more about what I do, they can go to www. noahmax. net. That’s n o a h m a x dot net. That has my music, my paintings as well and various other things. It has a place where you can get in touch. You can also find my music on YouTube, on Vimeo, on [00:37:00] SoundCloud, and you can also, through the website, you can sign up to my monthly newsletter that I mentioned earlier.

    And that’s just a monthly burst of creative energy from my part of the world. And you can find out what I’m doing. And if you want to come be a groupie then you can find out where I’m performing, what’s going on. And nine times out of 10, I will be there. So if you want to say hello, that is also really the best way to do it.

    Alexis: Thank you very much, Noah. 

    Noah: Thanks. Bye.

  • Ioanna Mantzouridou on Revolutionizing Leadership with AI

    Ioanna Mantzouridou on Revolutionizing Leadership with AI

    In our latest episode of Le Podcast on Emerging Leadership, I am honored to feature Ioanna Mantzouridou, Co-founder & CEO of Dextego. Join us as we delve into Ioanna’s inspiring journey from her roots in HR to leading an innovative AI coaching platform.

    Key Highlights of the Episode:

    1. Journey to Dextego: Ioanna shares her transition from considering a PhD in organizational psychology to spearheading an AI-driven talent development platform.
    2. Dextego’s Mission: Learn about her vision for reducing talent attrition through personalized soft skills training and the role of AI in democratizing leadership development.
    3. Overcoming Remote Work Challenges: Insights into the challenges of developing talent in remote settings, especially during the COVID era.
    4. Empathy in Leadership: Discover Ioanna’s emphasis on empathy, discipline, and a continuous learning mindset when building her team.
    5. Addressing CEO Challenges: Ioanna discusses balancing fundraising, sales, and maintaining vision in the early stages of a startup.
    6. Innovation Culture: How employee-driven innovation and aligning with company strategy can revolutionize workplaces.
    7. Success Metrics at Dextego: The focus on top talent retention and the transformative impact of personalized development tools.
    8. AI Tailoring for Career Stages: Exploring how Dextego’s AI coach adapts to individual skill levels and career phases.
    9. Ioanna’s Leadership Evolution: Her personal growth since starting Dextego and embracing ambiguity and vulnerability.
    10. Advice to Her Younger Self: Ioanna reflects on the virtues of patience and enjoying the journey.
    11. Upcoming Events: Get a sneak peek into Dextego’s future events, including LinkedIn Audio and LinkedIn Live sessions, and the exclusive ‘Dextagon’ event for HR leaders.

    Don’t miss this episode if you’re interested in how AI is transforming leadership and talent development. Tune in to gain invaluable insights from a visionary leader in the tech world.

    References

    Transcript

    Alexis: [00:00:00] Welcome to Le Podcast on Emerging Leadership. I’m your host, Alexis Monville. Today, we are thrilled to bring you insights from a distinguished guest whose dedication to enhancing leadership through technology sets her apart. Ioana Mantzouridou, a community builder, talent development strategist, and fervent advocate for applied AI, join us to share her groundbreaking journey. As the co-founder and CEO of Dextego Ioana is pioneering and AI coaching platform dedicated to revolutionizing talent development. Johanna, how do you introduce yourself to someone you just met?

    Ioanna: Awesome. That’s a great question. So I would say that my name is Ioana, I’m the co founder and CEO of Dextego, an AI coaching platform for reducing top talent attrition by half. I’m from Greece, so I’ve been living in the U. S. for seven years now, [00:01:00] and really focused on leveraging technology to push human capital further.

    That’s my quick intro.

    Alexis: Excellent, I love it. What inspired you to start Dextego?

    Ioanna: So, my background is in HR I actually thought I was going to pursue my PhD for a second on organizational psychology, but then I ended up working in startups. I was the VP of people and chief of staff at the, at the end of another B2B SaaS startup here in New York. And I quickly realized, you know, the importance of developing talent and also the challenges.

    that come with this development when it is in a remote setting, because especially during COVID, you know, everyone started working from home and I saw how hard it was for us to develop entry and mid level managers. And that’s primarily because [00:02:00] soft skills like communication, collaboration and leadership take time to be developed, right?

    You need life experience. You need to go through situations where you talk to multiple people, you negotiate, you handle conflict between colleagues. And so it was very hard for us to do this and talking to other, you know, HR leaders and learning and development experts. I quickly realized it was not just a struggle we faced, but the whole industry, and that the current organizational tools we had, e learning tools, learning management tools, were not sufficient enough, because they lacked the personalization needed to develop such skills and also the interaction with the learner and the experiential learning, if you wish.

    Alexis: hmm,

    Ioanna: That is the moment when I realized that I had to do something and I created the team around [00:03:00] Dextego to develop an AI coach that can democratize access to such skills across the organization, especially for anyone outside of the C suite that couldn’t afford an executive coach or didn’t have access to an executive coach.

    And make it in a way that it can leverage also the company’s internal know how. So we can integrate with the existing systems that a company has again, whether this is a learning management system or PDFs or, you know, information they have, we can fine tune our model to that so that it can speak their language and really maximize, the value it can give to its employee to support them during their day.

    So high level, that is, you know everything behind the reasoning. And for me personally, there’s another layer of equity, which [00:04:00] in my opinion, you know, people with soft skills sometimes tend to have. Access to more opportunities, whether we like it or not. Because they’re not afraid of asking for help.

    They’re not afraid of meeting people. And on the contrary, you have some people, like introverts, that without the perfect pitch, they won’t go out of their way to, like, go to conferences or meet mentors. And as a result they might stay behind. And I think this is very unfair. And it shouldn’t be the case.

    But the right training can equalize, you know, the playing field for, for everyone.

    Alexis: Very, very, very interesting. So I love, the mission of Dextego and how it, it aligns with , your leadership philosophy. you spoke about hiring new people and growing talents. So tell me what, what qualities do you look for in team members?

    Especially in those [00:05:00] early stage of of a startup.

    Ioanna: Yeah, I love this question because I was just talking to a friend of mine who were talking about the fact that outside of the U. S. recruiters tend to see employee, both as a person and as a professional. But in the U S we tend to have this distinction between okay, professional versus personal, like the same thing for coaching.

    Sometimes you go to a corporate coach and they just talk about how to boost your revenue. And then you go to someone that has more of the personal life coach approach and you see that the way they coach people is different. And to me, Also coming from Greece, I think the lines get blurry a little bit.

    And I like to work with people, but also hire people that I can see myself spending time with outside of work. So to find this like culture [00:06:00] personal fit I think it’s very hard, but it’s the number one thing I look for. I look for people that have empathy, because when times get rough this empathy will allow us to work well together and overcome any difficulties.

    I like people who are very hardworking and disciplined. So that I can count on them and I know that if they say, you know, they will be on a task, they will actually do it successfully and on time. That doesn’t mean perfectly, that just means that, you know, they, they do what they say. And I think that is something I really value, trustworthiness. 

    And lastly I love to work and hire people that are always eager to learn, like they want to be developed, because if you don’t have that willingness, no matter, you know, what your employer throws at you, it won’t [00:07:00] land, right? So this, I would say, is the most important part. 

    Alexis: So let’s let’s speak about a specific challenge that you faced as a CEO and how you managed it.

    Ioanna: Very interesting. There is a lot I can think right now, but if I was to pick one, as a CEO, you know, for an early stage company, there are two main things you should focus on, and this is fundraising, if you are not bootstrapped, and getting sales in. I don’t think that what I’ll say is just specific to me, honestly, it’s probably something other founders of our states face, but I think there is always a difference between where you’re in now and where you want to get as a startup, right?

    Like you have limited resources, so you do what you can today, but you have this grand vision. And so [00:08:00] that gap is sometimes. It’s very difficult to put in words and to be explained to someone that just is getting introduced, for instance, to your venture. So when I’m talking to investors or I’m talking to potential partners and companies that are super established and it’s, it could obviously be a risk of association for them to work with a company that’s new, that doesn’t have the brand awareness and recognition in the field.

    I found myself many times, you know. Struggling to find the confidence. To persuade them that they should work with us now, because I know how far we can get, and that this might take some time, but if I, as the CEO, don’t speak into existence this vision today, right, to get to that level, then what am I doing?

    So, it’s Someone gave me very good advice. [00:09:00] It’s the fear, you know, of overselling and under delivering sometimes that holds us back. Or, you know, imposter syndrome, all these things, different terminologies, but I cannot wear all the hats at the same time because I won’t move the company further.

    Like I have to think, okay, right now, I’m selling, then I’m doing customer success. Then I’m doing investor relations. So I think the biggest thing I’ve learned. This last month since starting Dextego is how to split these roles. So don’t get overwhelmed and don’t act for the best, you know, of the company.

    Alexis: that’s in a way balancing the, the needs of different stakeholders. By playing different personas and you know, yeah, that’s, that’s really hard when you need to do a lot of different things by yourself. Yeah.

    Ioanna: You know, as a chief of staff, it’s the same thing, but now it’s, I would say, with more responsibility.

    Alexis: Yeah, that’s absolutely true. Yeah.[00:10:00] how do you feel, how do you believe we can really foster an innovative mindset?

    Ioanna: Even a time where Suddenly, the innovation doesn’t come from the top. It comes from the bottom. I think employees have so much power today to drive innovation and to speak up about what they want to see in a company. So I think, you know, the responsibility is. Spread across organization like anyone today can bring innovation, I think, to a company because we see, and I’ll speak on the L& D side, like 70 percent of employees today say that they’re willing to leave. 

    To go to a company that develops them. So, similarly, I feel like there is a lot of fear from leadership to not satisfy employees when it comes to [00:11:00] innovation, to leveraging AI in particular because the employees could easily go somewhere else. So to me, to drive innovation successfully, you just have, if I speak to an employee now, right, you have to understand how the outcome, the ROI of whatever solution you’re bringing in will help leadership achieve their goals.

    So if you speak their language. They will say yes. I think most of the times employees find such cool tools they want to use, but they can’t make a case to actually implement them because they’re missing that piece of, okay, but how will it really help us achieve our, like, five year plan or, you know, our quarterly goals.

    And at the end of the day, whether we like it or not, the leadership cares about these things because they have to report to someone else. So I would say. It’s more [00:12:00] about understanding the strategy of the company and identifying the right type of innovation rather than a question of is the company open to innovation, yes or no?

    Alexis: it’s very interesting because you are looking at some success metrics that, that could be met using something. for your company, what, what success metrics do you focus on and why?

    Ioanna: Yes. So we focus on top talent retention. Because no matter who, what CEO you take from what field today they really care about their top talent, right? They care about the people that can call and they know they will get it done. these are people that they’ll do anything to keep in their company.

    And so when you’re able to bring them a tool that is very personalized, that it matches their needs where they are today and you help them develop for the next day. You’re able to retain [00:13:00] them, but the other part and I made a post about this is totally on the company is how the company does the right change management to explain to the company that implementing a tool like Dextego is for them.

    It’s not just the checkbox. It’s something that they understand they need for their personal and professional growth, whether they’re. Working at this company or not, but as a result, the employees will become loyal because they will. be part of this company where the culture is always about personal development and moving forward and improving each other. 

    But today, unfortunately for, you know, the lack of technology, technological advancements in L and D for the last years, HR leaders have had the misconception that they have no power because they can’t drive revenue. They can’t drive a significant[00:14:00] you know, metric in the company. So for us being able to deliver reduction of top talent attrition by half in just a quarter makes them the heroes they wish they were all these years. 

    And now we can have a seat at the table and really have others understand that they can make or break a company. At the end of the day, we know without talent. You got nothing. No matter what strategy you have on paper, you have no one to execute. So, to me, it’s a very important metric, and we see it across industries from, like, consulting firms that are really suffering from attrition, to startups, to big enterprises, and it’s a way to impact, you know the workforce overall, and knowing that, It’s for their own development.

    It’s, it’s a, to me, it’s a just cause.

    Alexis: So you, you mentioned that the tool is [00:15:00] adjusted to the needs of the people. 

    Ioanna: Yes.

    Alexis: what kind of adjustment are, I mean If I, if I’m early in my career or if I am a little bit later in my career, like me, for example, with over 50, how does the tool with, will adjust to our needs?

    Ioanna: Excellent question. So, let’s take an example of something that will not adjust first. Like you go to a learning management system and you take the same course. On leadership that everyone else in your organization takes, for instance, right? What we do with DexEgo is the AI coach is able to understand through your answers, the way you answer to scenario based challenges, your level of skills, and adjust the level of Difficulty or the types of questions it asks you, and I’ll give you an example, to really make sure you develop the right skills.

    So, [00:16:00] for instance, let’s take an example of a salesperson, and the scenario could be, hey, you have this client, that they’re throwing you this objection. How would you handle it? So you record yourself through video. The coach is your facial expressions, your tone, your pits and content of what you’re saying.

    And it gives you personalized feedback back on what you did great, what you can improve. And over time, by you completing some more challenges, it understands. For instance, you might lack negotiation skills so you can close the deal. So we’ll give you more feedback and more related challenges to these till it sees that you improve.

    And what we have behind the scenes to track that is our proprietary coachability index framework, which shows you. Basically, how coachable you are, how fast you’re implementing that feedback and how you’re improving your [00:17:00] skills over time. Because at the end of the day, it doesn’t matter if you start at, let’s say, 4 out of 10 in negotiation.

    What matters is that you’re able to improve to 8 to 9 over time. And that’s, I think, what any employer cares about today because we’re moving into this skills culture. It’s not just what you have on paper. Can you actually learn on the spot and develop? And can we see you becoming an important part of Our company, you know, in years to come, I

    Alexis: Excellent. So now I turn back the questions to you, to you. Have you evolved as a leader since starting Dextego?

    Ioanna: think so. No, for sure. I think you know, in startups, we have talked about this before one year equals 10. If you will, you learn so much, you see so much, you meet so many people like every day [00:18:00] putting myself out of my comfort zone being in like a situation for the first time. I love it.

    It’s super, Intriguing and challenging, but it allows for a lot of self reflection. I think the people that are following my journey can see that, you know, since the last time we meet, for instance, a lot has happened, or I’m improving, or the way I handle things is developing. So, I, I feel like I get feedback from others, and also from my self reflection, I can definitely see that growth.

    I think the most challenging thing is to be okay with ambiguity, right? And vulnerability as a leader, whether you’re like a leader for the first time or the 10th time in your career, there will always be some ambiguity. And I’m definitely learning to, to handle that better than I did some months ago.

    Alexis: [00:19:00] So if you, if you could give an advice to your younger self. Before starting Dextego what would it be?

    Ioanna: that’s a great one. You know, my number one weakness, I’ve always said, is my patience. I’ve always said that. Since I was young, I feel like I’m very impatient. So, life has a way to Teach you to become patient or else, you know I wouldn’t be able to do what I’m doing now, but I would tell myself that it’s okay when, when things take time, there’s actually a beauty in it.

    Cause you can. Be more excited when you get to the end result, and you can Develop more as a result as well. So I would tell myself to, to be patient and to Enjoy each moment, whether it’s tough or not. I think looking back, obviously every difficult moment in your life has made you right for who you are [00:20:00] today.

    And if you took that away, you wouldn’t be who you are. Thanks. My little speech to my younger self.

    Alexis: I love it. Thank you for that. Oh, can you tell us about an upcoming event? You’re particularly excited about?

    Ioanna: Yes, a lot. We have three events in November on LinkedIn Audio and LinkedIn Live. We’re talking about leadership. We’re talking about why mentorship programs fail and how to overcome that. About flexibility. And then in 2024, I can say we’re preparing what’s called Dextagon. It’s basically an invite only event for HR leaders and C suite here in New York. But yeah, I, I won’t say much more. It will be very exciting and we’ll talk about human potential and how to drive us further as a human race.[00:21:00] 

    Alexis: Excellent. I love it. So where can people learn more about Dextego and get in touch with you?

    Ioanna: They can go to our website at dextego. com. That’s D E X T and ego, dextego. com as well as our LinkedIn. And mine as well, you know, Ioana Mantzouridou and check out all our events and upcoming shows.

    Alexis: Excellent. Thank you very much Ioana for joining the podcast today.

    Ioanna: Thank you, Alex. Thank you very much for your time.