WEBVTT - Smart Talks with IBM: Brewing Smarter: How HEINEKEN Is Using AI To Revolutionize Its Global Operations

0:00:00.160 --> 0:00:02.960
<v Speaker 1>Hey everyone, it's Robert and Joe here. Today we've got

0:00:02.960 --> 0:00:05.240
<v Speaker 1>something a little bit different to share with you. It's

0:00:05.280 --> 0:00:09.400
<v Speaker 1>a new season of the Smart Talks with IBM podcast series.

0:00:09.720 --> 0:00:13.520
<v Speaker 2>This season on Smart Talks with IBM, Malcolm Gladwell is back,

0:00:13.520 --> 0:00:15.760
<v Speaker 2>and this time he's taking the show on the road.

0:00:15.880 --> 0:00:19.160
<v Speaker 2>Malcolm is stepping outside the studio to explore how IBM

0:00:19.239 --> 0:00:22.880
<v Speaker 2>clients are using artificial intelligence to solve real world challenges

0:00:23.079 --> 0:00:25.080
<v Speaker 2>and transform the way they do business.

0:00:25.480 --> 0:00:29.560
<v Speaker 1>From accelerating scientific breakthroughs to reimagining education. It's a fresh

0:00:29.600 --> 0:00:33.040
<v Speaker 1>look at innovation in action, where big ideas meet cutting

0:00:33.120 --> 0:00:33.960
<v Speaker 1>edge solutions.

0:00:34.320 --> 0:00:37.160
<v Speaker 2>You'll hear from industry leaders, creative thinkers, and of course

0:00:37.280 --> 0:00:40.920
<v Speaker 2>Malcolm Gladwell himself as he guides you through each story.

0:00:41.440 --> 0:00:44.680
<v Speaker 1>New episodes of Smart Talks with IBM drop every month

0:00:44.680 --> 0:00:48.279
<v Speaker 1>on the iHeartRadio app, Apple Podcasts, or wherever you get

0:00:48.320 --> 0:00:52.240
<v Speaker 1>your podcasts. Learn more at IBM dot com slash smart Talks.

0:00:52.880 --> 0:00:55.360
<v Speaker 1>This is a paid advertisement from IBM.

0:00:57.640 --> 0:01:01.000
<v Speaker 3>H'm Malcolm Gladwell. Welcome to Season seven of Smart Talks

0:01:01.000 --> 0:01:04.680
<v Speaker 3>with IBM. This year, we're exploring new stories about how

0:01:04.720 --> 0:01:08.480
<v Speaker 3>companies are using the latest advancements in AI and quantum

0:01:08.520 --> 0:01:12.520
<v Speaker 3>computing to create smarter business. For the first episode of

0:01:12.560 --> 0:01:16.160
<v Speaker 3>the season, I flew to Austin, Texas to join Sergei

0:01:16.280 --> 0:01:20.800
<v Speaker 3>Ghosh on stage at south By Southwest. Sergei is Chief

0:01:20.840 --> 0:01:25.600
<v Speaker 3>AI Officer at Heineken, the world's pioneering beer company. Founded

0:01:25.640 --> 0:01:28.880
<v Speaker 3>in eighteen sixty four. Heineken is deep roots, but it

0:01:28.920 --> 0:01:33.319
<v Speaker 3>continues to push the boundaries of innovation today. In twenty twenty,

0:01:33.319 --> 0:01:35.760
<v Speaker 3>the company came up with a goal to become the

0:01:35.800 --> 0:01:39.640
<v Speaker 3>world's best connected brewer. Surge plays a key role in

0:01:39.720 --> 0:01:42.720
<v Speaker 3>leading that transformation, and I sat down with him in

0:01:42.760 --> 0:01:45.640
<v Speaker 3>front of a live audience to understand what that journey

0:01:45.640 --> 0:01:48.760
<v Speaker 3>looks like and what it takes to reinvent a global

0:01:48.760 --> 0:01:55.160
<v Speaker 3>company from the inside out. And before we get to

0:01:55.280 --> 0:01:57.960
<v Speaker 3>the question of what you do in your job. So

0:01:58.120 --> 0:02:00.440
<v Speaker 3>I'm really interested in people who have jobs it didn't

0:02:00.440 --> 0:02:03.160
<v Speaker 3>exist for most of their life, and I'm curious how

0:02:03.200 --> 0:02:03.760
<v Speaker 3>you got there.

0:02:03.960 --> 0:02:06.360
<v Speaker 4>Yeah, first of all, thanks for having me here. Yeah,

0:02:06.640 --> 0:02:09.959
<v Speaker 4>actually it did exist, and people sometimes don't realize AI

0:02:10.080 --> 0:02:13.640
<v Speaker 4>is not new. It's been there for seventy five years,

0:02:13.680 --> 0:02:14.680
<v Speaker 4>since nineteen fifty.

0:02:15.680 --> 0:02:16.919
<v Speaker 5>It just changed over time.

0:02:16.960 --> 0:02:19.720
<v Speaker 4>How the application is happening, right, So one thing to

0:02:19.800 --> 0:02:22.240
<v Speaker 4>keep up with is as AI became more popular and

0:02:22.280 --> 0:02:25.560
<v Speaker 4>more embedded in business, how do we upscal ourselves to

0:02:25.600 --> 0:02:28.960
<v Speaker 4>stay at par with the technology trends. So the preparation

0:02:29.080 --> 0:02:31.280
<v Speaker 4>for me personally started actually a long time ago, so

0:02:31.280 --> 0:02:33.359
<v Speaker 4>when I was in grad school in US, and I

0:02:33.400 --> 0:02:34.800
<v Speaker 4>also to live in US by the way, for a

0:02:34.800 --> 0:02:35.280
<v Speaker 4>long time.

0:02:35.560 --> 0:02:36.400
<v Speaker 3>You're Indian.

0:02:37.040 --> 0:02:39.200
<v Speaker 4>I'm an Indian originally, but it's news. I did my

0:02:39.200 --> 0:02:42.800
<v Speaker 4>grad school here and there. Actually I started taking courses

0:02:42.800 --> 0:02:46.160
<v Speaker 4>in newer networks and at fission diagents back in two

0:02:46.200 --> 0:02:48.880
<v Speaker 4>thousand and two, and it wasn't popular back then.

0:02:49.200 --> 0:02:51.040
<v Speaker 5>I was just curious, what is it? Maybe it's the

0:02:51.080 --> 0:02:51.720
<v Speaker 5>next big thing.

0:02:52.200 --> 0:02:54.560
<v Speaker 4>And I'm so glad I did that because that sort

0:02:54.600 --> 0:02:55.960
<v Speaker 4>of helped me build that foundation.

0:02:56.400 --> 0:02:59.519
<v Speaker 3>What was it you said you were? You were curious

0:02:59.520 --> 0:03:02.160
<v Speaker 3>about it? You're curious about it? Why what caught your

0:03:02.200 --> 0:03:03.200
<v Speaker 3>eye about it?

0:03:03.240 --> 0:03:06.760
<v Speaker 4>Was very different because the main difference was before that

0:03:06.840 --> 0:03:08.280
<v Speaker 4>I was an engineer by professions.

0:03:08.480 --> 0:03:09.760
<v Speaker 5>I went to engineering college.

0:03:10.200 --> 0:03:12.919
<v Speaker 4>Everything is rule based, Everything is based on a formula,

0:03:13.000 --> 0:03:16.880
<v Speaker 4>a physical equation. AI is something different because based on

0:03:17.000 --> 0:03:19.920
<v Speaker 4>data and statistics, it never gives you a clear answer.

0:03:20.000 --> 0:03:22.440
<v Speaker 4>It gives you a probability, and I just thought this

0:03:22.480 --> 0:03:25.639
<v Speaker 4>is very interesting because if you're trying to solve a problem,

0:03:25.919 --> 0:03:27.920
<v Speaker 4>you don't know exactly how to solve it. There is

0:03:27.960 --> 0:03:30.720
<v Speaker 4>no equation. How do you get around that? I think

0:03:30.720 --> 0:03:33.760
<v Speaker 4>that's where AI comes in. It finds those patterns within

0:03:33.880 --> 0:03:37.360
<v Speaker 4>data and comes up with some prediction that intrigued me.

0:03:37.800 --> 0:03:41.800
<v Speaker 4>So this is what year that you start I started dabbling,

0:03:42.040 --> 0:03:44.080
<v Speaker 4>let's call it dabbling in AI was two thousand and two.

0:03:44.400 --> 0:03:45.960
<v Speaker 5>It was almost twenty four years ago.

0:03:45.800 --> 0:03:49.120
<v Speaker 3>Four years so put what you were playing with in

0:03:49.160 --> 0:03:52.960
<v Speaker 3>two thousand and two was an extremely primitive version of what.

0:03:52.920 --> 0:03:53.560
<v Speaker 5>We have now.

0:03:53.920 --> 0:03:56.360
<v Speaker 4>I think it was very relevant because the way I

0:03:56.440 --> 0:04:00.080
<v Speaker 4>see it, should I have skipped all the foundations that

0:04:00.120 --> 0:04:02.040
<v Speaker 4>I learned over the years and just gone to the

0:04:02.040 --> 0:04:05.880
<v Speaker 4>current state. Maybe, But when I look back, I think

0:04:05.880 --> 0:04:09.440
<v Speaker 4>that foundation really helped me because back then, and surprisingly,

0:04:09.480 --> 0:04:11.560
<v Speaker 4>by the way, new on networks. When I talk about that,

0:04:12.040 --> 0:04:15.360
<v Speaker 4>it's still very ralliant and relevant within AI. The entire

0:04:15.400 --> 0:04:18.719
<v Speaker 4>foundation is new on networks. So I think that foundation

0:04:18.839 --> 0:04:21.080
<v Speaker 4>really helped. Yeah, and I still find it very relevant

0:04:21.120 --> 0:04:22.120
<v Speaker 4>and I apply it day to day.

0:04:22.400 --> 0:04:26.120
<v Speaker 3>Yeah, imagine in having a conversation with you twenty years

0:04:26.120 --> 0:04:29.280
<v Speaker 3>ago and I say what are you up to? And

0:04:29.320 --> 0:04:33.599
<v Speaker 3>you say, I'm playing with this thing neural networks. Early version,

0:04:33.640 --> 0:04:35.680
<v Speaker 3>would you have used the term artificial intelligence?

0:04:37.080 --> 0:04:37.599
<v Speaker 5>Probably not.

0:04:37.800 --> 0:04:40.520
<v Speaker 4>I probably would have used something is called statistics, which

0:04:40.560 --> 0:04:43.600
<v Speaker 4>is everyone is aware of. Back then, it was more statistical,

0:04:43.680 --> 0:04:46.520
<v Speaker 4>so you don't have these big algorithms at that point.

0:04:47.400 --> 0:04:49.200
<v Speaker 4>But then something happened. I don't know if you heard

0:04:49.200 --> 0:04:52.000
<v Speaker 4>of this company called Cago. They used to host these

0:04:52.000 --> 0:04:55.320
<v Speaker 4>sort of data science competitions and anyone can participate and

0:04:55.360 --> 0:04:58.039
<v Speaker 4>if you do really well, you get a price. That

0:04:58.200 --> 0:05:00.599
<v Speaker 4>was a good motivation, just to see, okay, learned something,

0:05:01.080 --> 0:05:02.680
<v Speaker 4>let me apply it and see how good I am

0:05:02.880 --> 0:05:04.880
<v Speaker 4>I'm getting at it. So I think that was my

0:05:04.960 --> 0:05:07.440
<v Speaker 4>first entry point where I really got hands on into AI,

0:05:08.120 --> 0:05:10.240
<v Speaker 4>and that probably stayed with me for a while. I

0:05:10.240 --> 0:05:12.800
<v Speaker 4>think that was back in two thousand and six. That's

0:05:12.800 --> 0:05:15.120
<v Speaker 4>what I started getting hands on. And the funny thing

0:05:15.200 --> 0:05:17.600
<v Speaker 4>is when you look at these Caggle competitions, the use

0:05:17.640 --> 0:05:21.240
<v Speaker 4>cases they used to give actual industry applications, so you

0:05:21.240 --> 0:05:24.400
<v Speaker 4>were really dealing with business problems applying AI to solve it,

0:05:25.000 --> 0:05:27.280
<v Speaker 4>and then you know, wait a minute, a medical company

0:05:27.320 --> 0:05:29.719
<v Speaker 4>is using it. A manufacturing company is using it, a

0:05:29.800 --> 0:05:32.480
<v Speaker 4>banking is using it. And this is two thousand and six,

0:05:33.040 --> 0:05:36.080
<v Speaker 4>so it already started and then it just yeah today,

0:05:36.120 --> 0:05:38.040
<v Speaker 4>it's a different ballgame now.

0:05:38.080 --> 0:05:40.840
<v Speaker 3>So you you came to Heineken.

0:05:40.920 --> 0:05:45.560
<v Speaker 4>When twenty twenty, twenty twenty right middle of COVID, right.

0:05:46.120 --> 0:05:48.880
<v Speaker 3>And where you brought in to be the chief AI officer?

0:05:49.040 --> 0:05:51.600
<v Speaker 4>Was you explore it and the title changed? But yes

0:05:51.640 --> 0:05:52.520
<v Speaker 4>I was the global leader?

0:05:52.600 --> 0:05:55.520
<v Speaker 3>Yeah yeah, And what made you want to take the job?

0:05:56.360 --> 0:05:59.159
<v Speaker 4>I was actually working for Amazon at that point, but

0:05:59.200 --> 0:06:01.200
<v Speaker 4>when I looked at High and I thought, okay, this

0:06:01.360 --> 0:06:05.479
<v Speaker 4>is a legacy, traditional company, right, and AI was not

0:06:05.720 --> 0:06:07.520
<v Speaker 4>a capability embedded.

0:06:07.040 --> 0:06:07.880
<v Speaker 5>At that point of time.

0:06:08.360 --> 0:06:10.719
<v Speaker 4>So it's a great opportunity if I can start something

0:06:10.720 --> 0:06:15.240
<v Speaker 4>from scratch, really build it across the entire valuation of Heineken.

0:06:15.760 --> 0:06:17.960
<v Speaker 4>I mean, that's probably the best job anyone can even

0:06:18.000 --> 0:06:20.760
<v Speaker 4>ask for. Yes, it's of course a lot of responsibility

0:06:21.320 --> 0:06:23.040
<v Speaker 4>that you have to make sure that you really build

0:06:23.080 --> 0:06:26.000
<v Speaker 4>the right products and right capability, But that also happened,

0:06:26.480 --> 0:06:28.599
<v Speaker 4>so I look back, it's quite fulfilling.

0:06:29.200 --> 0:06:32.040
<v Speaker 3>But it's also if I might playable was advocate for

0:06:32.120 --> 0:06:34.960
<v Speaker 3>a moment, you're also taking a risk going into an

0:06:35.080 --> 0:06:38.800
<v Speaker 3>established how long has Heineken been around one hundred and

0:06:38.800 --> 0:06:41.480
<v Speaker 3>sixty two years to be specific, eighteen sixty four. It's

0:06:41.520 --> 0:06:43.960
<v Speaker 3>a very different proposition walking into one hundred and sixty

0:06:44.040 --> 0:06:46.240
<v Speaker 3>year old company and saying I want to bring the

0:06:46.279 --> 0:06:48.400
<v Speaker 3>future to the way you operate. Then it is with

0:06:48.480 --> 0:06:49.440
<v Speaker 3>the startup.

0:06:49.960 --> 0:06:51.800
<v Speaker 5>That is true, but it's also a challenge.

0:06:51.839 --> 0:06:54.599
<v Speaker 4>It's a good challenge, and also that Heineken is also

0:06:54.680 --> 0:06:57.080
<v Speaker 4>looking externally. There are companies that are picking up speed

0:06:57.120 --> 0:07:00.600
<v Speaker 4>and embedding and adopting AI, so should be all behind

0:07:00.760 --> 0:07:02.800
<v Speaker 4>not really, so we also need to pick it up.

0:07:03.120 --> 0:07:05.680
<v Speaker 4>So I thought it was a good challenge because the

0:07:05.800 --> 0:07:08.560
<v Speaker 4>use cases were there, the opportunity I put sense the

0:07:08.600 --> 0:07:11.040
<v Speaker 4>business really was having the appetite.

0:07:11.120 --> 0:07:12.160
<v Speaker 5>Let's do something different.

0:07:12.760 --> 0:07:15.040
<v Speaker 4>When we apply AI in a corporate setting like this,

0:07:15.480 --> 0:07:18.080
<v Speaker 4>it's super important to understand how the business actually works.

0:07:18.400 --> 0:07:20.680
<v Speaker 4>What's the value chain looking like, what are the nuances?

0:07:20.680 --> 0:07:22.760
<v Speaker 4>Where can I And once you get an understanding. It

0:07:22.800 --> 0:07:24.720
<v Speaker 4>took me some time, by the way, to understand the

0:07:24.760 --> 0:07:27.760
<v Speaker 4>full business and the complexities, but once you cross that

0:07:27.800 --> 0:07:31.040
<v Speaker 4>threshold you figure out what's feasible what's.

0:07:30.840 --> 0:07:32.960
<v Speaker 5>Not, then it opens up.

0:07:33.080 --> 0:07:35.440
<v Speaker 4>Wait a minute, within the valuetion, I see ten areas

0:07:35.600 --> 0:07:36.520
<v Speaker 4>I can optimize.

0:07:36.600 --> 0:07:38.400
<v Speaker 3>You say, once you want to see in the business,

0:07:38.400 --> 0:07:40.920
<v Speaker 3>describe the business. What the Heineken puzzle?

0:07:41.160 --> 0:07:43.920
<v Speaker 5>So well, puzzle, Let's see if it's puzzle.

0:07:43.960 --> 0:07:46.720
<v Speaker 4>After I explained it's actually you start with the procurement

0:07:46.760 --> 0:07:49.520
<v Speaker 4>where you get the glasses, cans and all the raw materials.

0:07:49.880 --> 0:07:52.000
<v Speaker 4>Then it comes to the brewery where the magic happens.

0:07:52.000 --> 0:07:54.920
<v Speaker 4>That's what behinneqn beer is produced. Then it goes to

0:07:55.000 --> 0:07:58.560
<v Speaker 4>the distributors. Basically a supply chain takes over. Then it

0:07:58.600 --> 0:08:01.280
<v Speaker 4>goes to the customers. What we refer to as customers

0:08:01.320 --> 0:08:06.000
<v Speaker 4>are the bars, restaurants, retail stores, moment pop stores, convenience stores,

0:08:06.560 --> 0:08:10.080
<v Speaker 4>and that's where actually consumers then come and actually consume

0:08:10.120 --> 0:08:10.560
<v Speaker 4>the product.

0:08:11.000 --> 0:08:12.320
<v Speaker 5>So that's actually the value chain.

0:08:12.400 --> 0:08:14.720
<v Speaker 4>It's actually pretty linear when you think of it, but

0:08:14.800 --> 0:08:17.760
<v Speaker 4>there are nuances depending on the country and the market.

0:08:18.160 --> 0:08:20.120
<v Speaker 4>There are some specific rules and guard rails that you

0:08:20.160 --> 0:08:20.760
<v Speaker 4>have to be aware of.

0:08:21.080 --> 0:08:24.400
<v Speaker 3>So you have that process going on all around the

0:08:24.400 --> 0:08:27.600
<v Speaker 3>world and across multiple brands.

0:08:27.480 --> 0:08:30.560
<v Speaker 4>Multiple brands, multiple countries, multiple operating companies.

0:08:30.680 --> 0:08:34.440
<v Speaker 3>Yeah, from your perspective as someone who is the chief

0:08:34.480 --> 0:08:37.440
<v Speaker 3>AI officer, what are the tasks in front of you?

0:08:37.880 --> 0:08:38.840
<v Speaker 3>What's your opportunity?

0:08:38.880 --> 0:08:42.760
<v Speaker 4>There any process that you think that is maybe not

0:08:43.040 --> 0:08:46.400
<v Speaker 4>digitized or maybe not data driven, you can optimize. I

0:08:46.440 --> 0:08:49.480
<v Speaker 4>look at it like a pendulum. So one side of

0:08:49.520 --> 0:08:52.880
<v Speaker 4>the pendulum you have complete gut based decision making. The

0:08:52.920 --> 0:08:55.920
<v Speaker 4>other extreme is completely data driven. So the idea is,

0:08:56.040 --> 0:08:58.280
<v Speaker 4>can we swing this pendulum it will be towards data

0:08:58.360 --> 0:08:59.319
<v Speaker 4>driven from where we are.

0:09:00.200 --> 0:09:03.360
<v Speaker 3>Give me a specific example of a problem you set

0:09:03.400 --> 0:09:05.520
<v Speaker 3>out solve or address.

0:09:06.559 --> 0:09:08.080
<v Speaker 4>There are quite a few, but if I want to

0:09:08.559 --> 0:09:11.560
<v Speaker 4>pick one of the most fun one fun one may be.

0:09:11.440 --> 0:09:14.240
<v Speaker 5>The most most complex one. Let's bring that one. I think.

0:09:14.240 --> 0:09:17.320
<v Speaker 4>So we spend quite a bit on advertising, and Heineken

0:09:17.559 --> 0:09:20.560
<v Speaker 4>is a largely a lot of it marketing company, and

0:09:20.640 --> 0:09:22.600
<v Speaker 4>we really care about our brands.

0:09:22.280 --> 0:09:25.400
<v Speaker 5>And products, you know, we're almost obsessed with it. Let's

0:09:25.440 --> 0:09:26.000
<v Speaker 5>take an example.

0:09:26.080 --> 0:09:28.600
<v Speaker 4>Let's say you have X million dollars as your budget

0:09:29.200 --> 0:09:32.280
<v Speaker 4>and you have two brands, let's say Heineken and Tosa Kiss.

0:09:32.520 --> 0:09:34.760
<v Speaker 4>I think the crowd audienceale will be familiar with that.

0:09:35.600 --> 0:09:38.959
<v Speaker 4>And then you have three touch points TV, YouTube, Instagram,

0:09:39.360 --> 0:09:43.840
<v Speaker 4>and I want to optimize my advertising budget between different

0:09:43.880 --> 0:09:46.960
<v Speaker 4>brand and touch points, so heiniken on Instagram.

0:09:46.960 --> 0:09:49.640
<v Speaker 5>How much should I spend? It's a very easy question to.

0:09:49.600 --> 0:09:52.320
<v Speaker 4>Ask, but to actually solve this you have to study

0:09:52.440 --> 0:09:55.600
<v Speaker 4>historically how these performed and then create a model and

0:09:55.640 --> 0:09:59.080
<v Speaker 4>then predict if I allocate my budget in this way

0:09:59.559 --> 0:10:02.440
<v Speaker 4>that's probab more optimal. Before it was more like somebody

0:10:02.440 --> 0:10:05.319
<v Speaker 4>to con gun based decisions saying okay, here goes xpillion,

0:10:05.360 --> 0:10:07.560
<v Speaker 4>here goes five million, and we say no, no, no, that's

0:10:07.559 --> 0:10:08.520
<v Speaker 4>not the right proportion.

0:10:08.800 --> 0:10:11.959
<v Speaker 3>What did the AI tell you about the accuracy of

0:10:12.000 --> 0:10:14.240
<v Speaker 3>those spending decisions?

0:10:14.679 --> 0:10:17.319
<v Speaker 4>In the past, we looked at the return on investment

0:10:17.360 --> 0:10:20.200
<v Speaker 4>from this advertising, so how much incremental volume or volume

0:10:20.240 --> 0:10:23.520
<v Speaker 4>of brre reselling or revenue are recreating and we find

0:10:23.520 --> 0:10:26.640
<v Speaker 4>out can we improve that. It's a moment to apply AI.

0:10:27.200 --> 0:10:29.440
<v Speaker 4>And when we look at that this significant improvement. In

0:10:29.440 --> 0:10:33.439
<v Speaker 4>some cases we have thirty percent uplift, thirty percent, thirty percent,

0:10:33.480 --> 0:10:37.000
<v Speaker 4>three zero not everywhere. In some places we got but

0:10:37.040 --> 0:10:39.439
<v Speaker 4>it ranges between ten to thirty percent uplift depending on

0:10:39.480 --> 0:10:41.520
<v Speaker 4>the type of AI product you're building.

0:10:41.559 --> 0:10:43.079
<v Speaker 5>And that impacts the top line.

0:10:43.440 --> 0:10:45.960
<v Speaker 4>So it's very easy to also realize that value.

0:10:46.000 --> 0:10:47.000
<v Speaker 5>People get to see.

0:10:46.760 --> 0:10:49.480
<v Speaker 3>It, so you say, oh, we we can do a

0:10:49.480 --> 0:10:51.640
<v Speaker 3>way better job if we spend x more or x

0:10:51.760 --> 0:10:54.440
<v Speaker 3>less in this particular area. Give me another example of

0:10:54.480 --> 0:10:54.920
<v Speaker 3>a if.

0:10:54.920 --> 0:10:57.880
<v Speaker 4>Another one would be we have a very big large

0:10:57.920 --> 0:11:01.679
<v Speaker 4>salesforce within Ainiken. So this sales reap. What they do

0:11:01.720 --> 0:11:04.480
<v Speaker 4>they go to the outlets, the bars and restaurants, and

0:11:04.559 --> 0:11:08.040
<v Speaker 4>they maintain that human to human relationships with these our

0:11:08.080 --> 0:11:11.240
<v Speaker 4>customers is super important to maintain that, and they go

0:11:11.360 --> 0:11:13.959
<v Speaker 4>solve the customer problems. Let's say someone is out of stock,

0:11:14.040 --> 0:11:17.320
<v Speaker 4>someone is about to churn, or their surprise mismatch, something

0:11:17.400 --> 0:11:19.720
<v Speaker 4>like this, and before they us to go like this,

0:11:19.880 --> 0:11:22.120
<v Speaker 4>let's say a sales rep on a day to day

0:11:22.200 --> 0:11:25.640
<v Speaker 4>job has to visit five places ab CD E, five

0:11:25.640 --> 0:11:29.760
<v Speaker 4>different outlets, and he used to go ABCDE. Turns out,

0:11:29.920 --> 0:11:32.679
<v Speaker 4>the model tells you on any given day, if you

0:11:32.760 --> 0:11:37.120
<v Speaker 4>optimize taking into account the traffic conditions, instead of going

0:11:37.160 --> 0:11:40.120
<v Speaker 4>from that linear route, you go to D first and

0:11:40.160 --> 0:11:42.000
<v Speaker 4>then to B, then to C, then to E and

0:11:42.040 --> 0:11:44.240
<v Speaker 4>then to A. And the reason for doing that is

0:11:44.600 --> 0:11:47.439
<v Speaker 4>the model tells you, if you visit customer D first,

0:11:47.440 --> 0:11:49.760
<v Speaker 4>he has the biggest problem that needs the most amount

0:11:49.800 --> 0:11:52.600
<v Speaker 4>of time to be solved, and that's how it optimize.

0:11:52.640 --> 0:11:54.280
<v Speaker 5>And also the sales reps now.

0:11:54.120 --> 0:11:57.600
<v Speaker 4>They are becoming so educated with some of these AI models,

0:11:57.840 --> 0:12:00.800
<v Speaker 4>they are now becoming a business advisors. So they are

0:12:01.080 --> 0:12:04.280
<v Speaker 4>no longer just solving little problems. They are having the

0:12:04.360 --> 0:12:06.400
<v Speaker 4>time to say what else can I do for you

0:12:06.960 --> 0:12:09.400
<v Speaker 4>as the customer? So that I think it was a

0:12:09.400 --> 0:12:12.000
<v Speaker 4>big change within Heineken because it impacted a lot of

0:12:12.000 --> 0:12:13.679
<v Speaker 4>people that were using that.

0:12:13.880 --> 0:12:16.560
<v Speaker 3>In an instance, it requires not just building a model

0:12:17.040 --> 0:12:19.600
<v Speaker 3>that can be smarter about how people should spend their

0:12:19.600 --> 0:12:21.720
<v Speaker 3>time and what they should say, but you have to

0:12:21.880 --> 0:12:27.280
<v Speaker 3>obviously educate your salesforce to believe in what the selling

0:12:27.840 --> 0:12:29.840
<v Speaker 3>tell me about that piece. Is that a piece that

0:12:29.520 --> 0:12:31.360
<v Speaker 3>you that you're a part of or is someone else?

0:12:31.480 --> 0:12:33.959
<v Speaker 4>Yeah, that's also part of because that is super important.

0:12:33.960 --> 0:12:36.680
<v Speaker 4>I think we can build the best models. Best algorithm's

0:12:36.760 --> 0:12:39.800
<v Speaker 4>highest accuracy doesn't mean anything if it's not used the

0:12:39.840 --> 0:12:42.199
<v Speaker 4>right way. So what we do we have within our

0:12:42.240 --> 0:12:46.440
<v Speaker 4>company a pretty big upskilling program. So bring everyone along

0:12:47.080 --> 0:12:50.640
<v Speaker 4>in common understanding, basic understanding of what AI does. Not

0:12:50.720 --> 0:12:54.640
<v Speaker 4>everyone needs to understand new networks or algorithms right, But

0:12:54.760 --> 0:12:58.320
<v Speaker 4>what we do is give them a handheld device and

0:12:58.360 --> 0:13:00.839
<v Speaker 4>an app which is driven by AI. Play with it,

0:13:01.200 --> 0:13:03.760
<v Speaker 4>have fun, see how it changes your life. And once

0:13:03.800 --> 0:13:07.160
<v Speaker 4>you start liking the product, liking the UIUX, then you

0:13:07.200 --> 0:13:09.680
<v Speaker 4>start getting more. And the insights also tell you the

0:13:09.679 --> 0:13:12.319
<v Speaker 4>story because once you start getting the value, I am

0:13:12.360 --> 0:13:16.840
<v Speaker 4>not having to pitch my models anymore. The sales reps

0:13:17.080 --> 0:13:19.439
<v Speaker 4>and the markets they are pitching on behalf of us.

0:13:19.960 --> 0:13:21.760
<v Speaker 5>And that's such a good place to.

0:13:21.720 --> 0:13:26.040
<v Speaker 3>Be, is it. It's interesting? So in that instance where

0:13:26.040 --> 0:13:29.760
<v Speaker 3>you're designing a more efficient form of interaction and fruitful

0:13:29.840 --> 0:13:33.000
<v Speaker 3>for of interaction between sales reps and customers, I could

0:13:33.040 --> 0:13:35.920
<v Speaker 3>see a version of that where it is really clear

0:13:36.559 --> 0:13:40.480
<v Speaker 3>looking up from a high level that things are working better,

0:13:40.720 --> 0:13:43.680
<v Speaker 3>but it might not be clear to the salesperson. Is

0:13:43.720 --> 0:13:46.680
<v Speaker 3>the salesperson who's now following the direction of the AI

0:13:47.200 --> 0:13:48.800
<v Speaker 3>aware that they are more efficient?

0:13:48.920 --> 0:13:50.359
<v Speaker 5>They are?

0:13:50.559 --> 0:13:51.600
<v Speaker 3>How are they aware the market?

0:13:51.600 --> 0:13:54.360
<v Speaker 4>They realize few things that they were visiting customers just

0:13:54.400 --> 0:13:57.040
<v Speaker 4>because they had to visit because it was in the schedule.

0:13:57.520 --> 0:13:59.959
<v Speaker 4>Now they go there and they find out, wait a minute,

0:14:00.200 --> 0:14:03.160
<v Speaker 4>I never tackled this big problem that was not being addressed,

0:14:03.600 --> 0:14:07.120
<v Speaker 4>and they solved it. And the customer feedback also comes

0:14:07.160 --> 0:14:09.920
<v Speaker 4>back saying we are really happy. So for all these products,

0:14:10.000 --> 0:14:12.000
<v Speaker 4>we get the feedback not just from the sales reps,

0:14:12.160 --> 0:14:14.760
<v Speaker 4>but also for the customers. Do you really like the

0:14:14.840 --> 0:14:17.920
<v Speaker 4>recommendations we are giving you? And that's the best validation

0:14:17.960 --> 0:14:20.440
<v Speaker 4>you can think of, because it's four stand or feedback.

0:14:20.880 --> 0:14:23.800
<v Speaker 3>When the AI is doing this ranking, it wants you

0:14:23.840 --> 0:14:27.920
<v Speaker 3>to focus on the customer with the biggest problem first

0:14:28.000 --> 0:14:29.240
<v Speaker 3>or is it much more complex than that.

0:14:29.320 --> 0:14:30.680
<v Speaker 5>It's a little bit more complex than that.

0:14:30.760 --> 0:14:33.400
<v Speaker 4>Yeah, but usually it's a rank pordert in terms of

0:14:33.400 --> 0:14:35.960
<v Speaker 4>which one is the biggest problem that needs the most

0:14:35.960 --> 0:14:36.640
<v Speaker 4>amount of time.

0:14:37.200 --> 0:14:38.160
<v Speaker 5>That's how it's ranked order.

0:14:38.240 --> 0:14:40.440
<v Speaker 4>But sometimes you can also override the model, right, We

0:14:40.520 --> 0:14:43.720
<v Speaker 4>also give options to people. You don't have to all

0:14:43.800 --> 0:14:46.080
<v Speaker 4>the time one hundred percent follow the recommendation. If you

0:14:46.080 --> 0:14:48.920
<v Speaker 4>have some urgent priority, you can overwrite that.

0:14:48.920 --> 0:14:51.800
<v Speaker 3>That's also possible with something like that. Is there a

0:14:51.920 --> 0:14:55.200
<v Speaker 3>next level you can go to? So you design this

0:14:55.280 --> 0:14:56.920
<v Speaker 3>system and you say, oh, I can make our sales

0:14:56.920 --> 0:14:59.480
<v Speaker 3>staff a lot more effective and the way they operate

0:14:59.560 --> 0:15:03.960
<v Speaker 3>with their customers, and then you see that it works,

0:15:04.320 --> 0:15:06.000
<v Speaker 3>and then it comes back and then you say, okay,

0:15:06.000 --> 0:15:09.240
<v Speaker 3>what's two point oh? Is there a two point oh.

0:15:09.040 --> 0:15:09.480
<v Speaker 5>It could be.

0:15:09.600 --> 0:15:13.120
<v Speaker 4>So it's always about innovation. Then you think, okay, today

0:15:13.160 --> 0:15:15.360
<v Speaker 4>we go and solve the problems that have already happened.

0:15:16.400 --> 0:15:19.080
<v Speaker 4>What if we solve the problems that are likely to happen,

0:15:19.680 --> 0:15:22.440
<v Speaker 4>that will be the next step. So this customer hasn't

0:15:22.480 --> 0:15:25.160
<v Speaker 4>been very active for a while, there's a high chance

0:15:25.200 --> 0:15:28.240
<v Speaker 4>that that customer might churn out of Heineken. So what

0:15:28.320 --> 0:15:31.640
<v Speaker 4>actions can I actually recommend to make sure And we

0:15:31.720 --> 0:15:33.640
<v Speaker 4>do this, by the way, we also gather a lot

0:15:33.680 --> 0:15:37.040
<v Speaker 4>of customer feedback and complaints and feedback, and we use

0:15:37.160 --> 0:15:39.600
<v Speaker 4>LLLMS to extract and glean information. Okay, what are the

0:15:39.600 --> 0:15:42.080
<v Speaker 4>real pain points? What's the theme and the topic that

0:15:42.200 --> 0:15:44.760
<v Speaker 4>needs to be addressed. And once you do that, then

0:15:44.800 --> 0:15:47.520
<v Speaker 4>also you can prepare ahead of time. We're already there,

0:15:47.560 --> 0:15:49.120
<v Speaker 4>by the way, when I say two point zero, we're

0:15:49.160 --> 0:15:52.600
<v Speaker 4>already testing it. You solve problems or you'll try to

0:15:52.600 --> 0:15:55.440
<v Speaker 4>solve problems before daven occur. So I think that's a

0:15:55.480 --> 0:15:57.280
<v Speaker 4>little bit of a two point zero. Then we have

0:15:57.320 --> 0:15:58.720
<v Speaker 4>to see what else we can do with it.

0:15:59.240 --> 0:16:03.600
<v Speaker 3>Tell me you've had this partnership at Heineken with IBM

0:16:04.240 --> 0:16:08.480
<v Speaker 3>for since twenty thirteen, twenty thirteen, So you came in

0:16:08.600 --> 0:16:12.200
<v Speaker 3>and there was already a strong working relationship. Tell me

0:16:12.240 --> 0:16:14.760
<v Speaker 3>about how that relationship started and what does it mean

0:16:14.800 --> 0:16:18.920
<v Speaker 3>on a practical basis. You're building all these tools, how

0:16:18.920 --> 0:16:20.400
<v Speaker 3>does the interaction with IBM work.

0:16:20.920 --> 0:16:22.640
<v Speaker 4>Yeah, so I think good to give a little bit

0:16:22.640 --> 0:16:26.760
<v Speaker 4>of context. Heineken started this digital transformation journey in twenty

0:16:26.840 --> 0:16:30.040
<v Speaker 4>twenty formally, but the tech was already there. We had

0:16:30.080 --> 0:16:34.120
<v Speaker 4>our systems, platforms, data, everything was there. So all the

0:16:34.200 --> 0:16:37.600
<v Speaker 4>IT four ID systems is where IBM was partnering with

0:16:37.680 --> 0:16:40.280
<v Speaker 4>us from the get go, from twenty thirteen, and it's

0:16:40.320 --> 0:16:43.080
<v Speaker 4>a very long standing partnership because as we found the

0:16:43.160 --> 0:16:46.560
<v Speaker 4>tech is evolving, our partnership also kept evolving because we

0:16:46.600 --> 0:16:49.600
<v Speaker 4>need to keep up up to the speed. So it

0:16:49.720 --> 0:16:53.520
<v Speaker 4>was more about IT for IT systems, cybersecurity platform, data,

0:16:54.280 --> 0:16:56.600
<v Speaker 4>incident management, service level, you name it.

0:16:57.000 --> 0:16:57.520
<v Speaker 5>All of that.

0:16:57.680 --> 0:17:00.600
<v Speaker 4>IBM was supporting us both in terms of hands and

0:17:00.680 --> 0:17:01.560
<v Speaker 4>also in terms.

0:17:01.360 --> 0:17:02.760
<v Speaker 5>Of strategy to create together.

0:17:03.360 --> 0:17:05.800
<v Speaker 4>But that also evolved, like I said, when we went

0:17:05.840 --> 0:17:09.600
<v Speaker 4>into this digital transformation journey in twenty twenty, then we

0:17:09.680 --> 0:17:13.960
<v Speaker 4>started building this digital core, which is the central nervous

0:17:13.960 --> 0:17:17.680
<v Speaker 4>system software system of finikin that's where IBM is really

0:17:17.720 --> 0:17:20.600
<v Speaker 4>partnering with us and helping us not just shape the

0:17:20.640 --> 0:17:22.560
<v Speaker 4>whole thing in terms of building it hands on, but

0:17:22.600 --> 0:17:25.080
<v Speaker 4>how do we strategize that so that it lands well.

0:17:25.160 --> 0:17:28.720
<v Speaker 4>So that's yeah, it's a long trusted partnership. I think

0:17:28.720 --> 0:17:30.200
<v Speaker 4>we are going to go a long way together.

0:17:30.560 --> 0:17:33.520
<v Speaker 3>Yeah, Heineken Space just sells out of Amsterdam.

0:17:34.160 --> 0:17:36.480
<v Speaker 5>The head office is absolutely so the IBN.

0:17:36.160 --> 0:17:38.359
<v Speaker 3>People who work with you are they on site?

0:17:38.640 --> 0:17:40.720
<v Speaker 4>There are some on site and there are some teams

0:17:40.720 --> 0:17:43.680
<v Speaker 4>in India some times spread across the globe. But for

0:17:43.680 --> 0:17:46.000
<v Speaker 4>for tech, I think the location doesn't matter. But you

0:17:46.040 --> 0:17:48.080
<v Speaker 4>still need people on site to actually talk with the

0:17:48.119 --> 0:17:50.960
<v Speaker 4>business and really understand what the problem for.

0:17:51.080 --> 0:17:52.720
<v Speaker 5>Those interactions are also very important.

0:17:53.040 --> 0:17:54.639
<v Speaker 3>When you said you wanted to when you got there,

0:17:54.640 --> 0:17:57.560
<v Speaker 3>you wanted to build a digital nervous system, what does

0:17:57.560 --> 0:17:58.000
<v Speaker 3>that mean?

0:17:58.440 --> 0:17:59.720
<v Speaker 5>Maybe good to give you an example.

0:18:00.200 --> 0:18:04.919
<v Speaker 4>Let's say iPhone, right, it's a central platform, but you

0:18:04.960 --> 0:18:08.440
<v Speaker 4>can download thousands of apps there and all of them

0:18:08.800 --> 0:18:11.600
<v Speaker 4>once you download seamlessly integrates with the system and you

0:18:11.600 --> 0:18:14.439
<v Speaker 4>don't see any difference. This is the same thing. So

0:18:14.480 --> 0:18:16.639
<v Speaker 4>what we want to build within Heineken is a central

0:18:16.680 --> 0:18:19.159
<v Speaker 4>software system which the old school way of saying it

0:18:19.200 --> 0:18:22.879
<v Speaker 4>is the ERP enterprise resource planning. It removes the fragmentation

0:18:22.920 --> 0:18:25.760
<v Speaker 4>of different platforms, it brings it all together. It makes

0:18:25.760 --> 0:18:29.240
<v Speaker 4>sure all the business applications within supply chain, commerce, finance

0:18:29.440 --> 0:18:33.600
<v Speaker 4>HR all in one place and coordinates them everything orchestrates them.

0:18:34.080 --> 0:18:37.040
<v Speaker 4>The benefit of doing that is two one across the

0:18:37.119 --> 0:18:39.919
<v Speaker 4>value channing of one way of doing business because everything

0:18:39.960 --> 0:18:44.560
<v Speaker 4>is standardized, but we also have multiple markets globally. Across

0:18:44.600 --> 0:18:47.440
<v Speaker 4>the multiple markets also it becomes one way of doing business,

0:18:47.640 --> 0:18:50.840
<v Speaker 4>so it's both ways. And once you standardize it, we

0:18:50.920 --> 0:18:55.360
<v Speaker 4>can embed new apps which will seamlessly integrate, and then

0:18:55.400 --> 0:18:58.200
<v Speaker 4>it just keeps scaling further. Can we scaled very quick

0:18:58.520 --> 0:19:01.359
<v Speaker 4>and having that digital core really help us scale because

0:19:01.400 --> 0:19:04.840
<v Speaker 4>the value from AI and insights is not just building

0:19:04.840 --> 0:19:07.359
<v Speaker 4>one product in one place. It's how quickly can you

0:19:07.400 --> 0:19:07.840
<v Speaker 4>scale it?

0:19:08.240 --> 0:19:10.000
<v Speaker 3>And are you still building it or is it an

0:19:10.040 --> 0:19:10.760
<v Speaker 3>ongoing thing or.

0:19:10.680 --> 0:19:13.160
<v Speaker 4>It's ongoing thing because there are nuances in markets, There

0:19:13.320 --> 0:19:17.359
<v Speaker 4>are nuances in tax systems and currency systems, so it

0:19:17.400 --> 0:19:19.440
<v Speaker 4>takes a little bit of as much as we want

0:19:19.440 --> 0:19:21.480
<v Speaker 4>to standardize, you also have to bake in some of

0:19:21.520 --> 0:19:25.440
<v Speaker 4>the nuances otherwise people cannot use it. So those sort

0:19:25.440 --> 0:19:27.560
<v Speaker 4>of outliers we have to also bake in.

0:19:28.240 --> 0:19:31.720
<v Speaker 3>You must learn something when you suddenly suddenly, but when

0:19:31.760 --> 0:19:33.800
<v Speaker 3>you standardize a bunch of things that have not been

0:19:33.840 --> 0:19:37.520
<v Speaker 3>standardized before, presumably you have a basis for comparisons you

0:19:37.560 --> 0:19:38.479
<v Speaker 3>couldn't make before.

0:19:39.840 --> 0:19:40.399
<v Speaker 5>That's correct.

0:19:40.440 --> 0:19:43.439
<v Speaker 4>So we also get a lot of external inspiration. So

0:19:43.520 --> 0:19:46.560
<v Speaker 4>sometimes these large projects we don't start by over whom,

0:19:47.000 --> 0:19:50.320
<v Speaker 4>so we get inspiration from partners like IBM or someone else.

0:19:51.040 --> 0:19:52.840
<v Speaker 4>How have they done it in somewhere else and where

0:19:52.880 --> 0:19:56.560
<v Speaker 4>it's really working. So then you get those ideas, the learnings,

0:19:56.840 --> 0:19:59.639
<v Speaker 4>and you start building that way, and while doing that,

0:19:59.680 --> 0:20:01.600
<v Speaker 4>you feel out that, wait a minute, we might have

0:20:01.640 --> 0:20:04.280
<v Speaker 4>done something different and maybe it's even better than what

0:20:04.359 --> 0:20:05.000
<v Speaker 4>others have done.

0:20:05.440 --> 0:20:07.280
<v Speaker 5>Yeah, so it also creates creativity.

0:20:07.520 --> 0:20:11.639
<v Speaker 3>Yeah, I'm just curious whether there was an insight that

0:20:11.720 --> 0:20:16.040
<v Speaker 3>you learned from that process that comes to mind A

0:20:16.080 --> 0:20:16.600
<v Speaker 3>big one.

0:20:16.680 --> 0:20:20.040
<v Speaker 4>I think we don't look at tech for the sake

0:20:20.080 --> 0:20:22.600
<v Speaker 4>of tech and embedding it, you know, just just as

0:20:22.920 --> 0:20:25.640
<v Speaker 4>one would say it's one single core, one single platform,

0:20:25.680 --> 0:20:29.080
<v Speaker 4>everything coordinated. What's the big deal. The big deal is

0:20:29.080 --> 0:20:31.560
<v Speaker 4>bringing people along to actually believe that there is a

0:20:31.720 --> 0:20:34.719
<v Speaker 4>benefit of doing one way of business, and that actually

0:20:34.760 --> 0:20:37.240
<v Speaker 4>means the entire company, not just the leadership team.

0:20:37.520 --> 0:20:38.320
<v Speaker 5>So to bring.

0:20:38.160 --> 0:20:41.679
<v Speaker 4>Everyone on board and say, tell us how this platform

0:20:41.720 --> 0:20:43.760
<v Speaker 4>should look like, what are the components we should build?

0:20:44.160 --> 0:20:46.440
<v Speaker 4>It's a pretty big task. Yeah, that's where the chain

0:20:46.520 --> 0:20:47.280
<v Speaker 4>management comes in.

0:20:47.359 --> 0:20:50.840
<v Speaker 3>Yeah, what was hard about that? Did you have bumps

0:20:51.080 --> 0:20:51.960
<v Speaker 3>or we did?

0:20:52.080 --> 0:20:55.359
<v Speaker 4>I think it's about convincing people the benefit of doing this.

0:20:55.920 --> 0:20:58.000
<v Speaker 4>Why do we say, if you standardize something, we can

0:20:58.040 --> 0:21:00.640
<v Speaker 4>go at high speed in scaling. It's not very easy

0:21:00.640 --> 0:21:03.199
<v Speaker 4>to visualize that at first. But what you do is

0:21:03.240 --> 0:21:05.960
<v Speaker 4>you show some proof of concepts. And that's I won't

0:21:05.960 --> 0:21:08.240
<v Speaker 4>call it a trick. It's almost bread and butter of

0:21:08.359 --> 0:21:11.320
<v Speaker 4>what we do. Show a small proof of concept, show

0:21:11.359 --> 0:21:13.919
<v Speaker 4>that it works, show that we can scale, and then

0:21:13.960 --> 0:21:16.120
<v Speaker 4>automatically if people start having the faith, and then well

0:21:16.160 --> 0:21:17.400
<v Speaker 4>say okay, I see it.

0:21:17.520 --> 0:21:18.679
<v Speaker 5>Yeah it makes sense.

0:21:19.000 --> 0:21:22.080
<v Speaker 3>Sergery, at least half of what you've talked about is

0:21:22.119 --> 0:21:24.080
<v Speaker 3>not about the check itself, but about being a kind

0:21:24.080 --> 0:21:27.320
<v Speaker 3>of evangelist for the check. It is half the right percentage.

0:21:27.440 --> 0:21:30.920
<v Speaker 3>How much of your time is spent convincing an organization

0:21:31.440 --> 0:21:33.480
<v Speaker 3>and people in the organization to see the value in

0:21:33.480 --> 0:21:35.480
<v Speaker 3>what you're doing as opposed to building the thing that

0:21:35.600 --> 0:21:36.280
<v Speaker 3>has value.

0:21:36.440 --> 0:21:38.879
<v Speaker 4>Yeah, I think that proportion changed over time. When I

0:21:38.920 --> 0:21:41.280
<v Speaker 4>first joined, I was very much into the products itself.

0:21:41.680 --> 0:21:44.000
<v Speaker 4>I was to review codes myself, let me check what's

0:21:44.040 --> 0:21:46.480
<v Speaker 4>going on. And over time, of course, then you focus

0:21:46.560 --> 0:21:49.480
<v Speaker 4>on somewhere else. You realize, like I said, best codes,

0:21:49.520 --> 0:21:52.280
<v Speaker 4>best models, I use this, if not use the right way,

0:21:52.359 --> 0:21:54.800
<v Speaker 4>then I said, okay, now my time is to actually

0:21:54.840 --> 0:21:57.840
<v Speaker 4>inspire and show people the value of it. What I

0:21:57.920 --> 0:22:02.760
<v Speaker 4>realized is explaining in very simple language really goes a

0:22:02.800 --> 0:22:06.639
<v Speaker 4>long way because you take away that that anxiety that

0:22:06.960 --> 0:22:09.359
<v Speaker 4>a new product is coming in and we humans a

0:22:09.400 --> 0:22:12.040
<v Speaker 4>little bit have this. I don't know if it's the

0:22:12.119 --> 0:22:14.560
<v Speaker 4>right thing to say, but it's inertia of rest. We

0:22:14.760 --> 0:22:17.919
<v Speaker 4>like status, poke, we don't sometimes like change that stops our.

0:22:18.640 --> 0:22:20.320
<v Speaker 4>So every time you build a new product that will

0:22:20.400 --> 0:22:22.879
<v Speaker 4>change our way of working. Yeah, there's inherent little bit

0:22:22.880 --> 0:22:26.000
<v Speaker 4>of anxiety. Yeah, take that away. Yeah, a job becomes

0:22:26.000 --> 0:22:26.640
<v Speaker 4>a lot easier.

0:22:26.800 --> 0:22:29.159
<v Speaker 3>Are you a good evangelist?

0:22:29.480 --> 0:22:30.479
<v Speaker 5>So far it's working?

0:22:30.640 --> 0:22:33.760
<v Speaker 4>I think I can do better, for sure, because it's

0:22:33.800 --> 0:22:37.760
<v Speaker 4>about understanding what's the reason people sometimes might be reluctant

0:22:38.160 --> 0:22:41.760
<v Speaker 4>to actually onboard or adopt a new technology. And once

0:22:41.760 --> 0:22:45.240
<v Speaker 4>you sort of understand that, then that anxiety goes away,

0:22:45.280 --> 0:22:46.240
<v Speaker 4>it becomes easier.

0:22:46.640 --> 0:22:48.520
<v Speaker 3>How many people work for a hidekinde.

0:22:48.600 --> 0:22:50.760
<v Speaker 5>About eighty five thousand, ninety thousand.

0:22:50.680 --> 0:22:55.160
<v Speaker 3>Globally, so you have essentially a city pretty much. And

0:22:55.480 --> 0:22:57.440
<v Speaker 3>if you look at that universe of eighty five thousand,

0:22:58.000 --> 0:23:00.719
<v Speaker 3>is there anyone in that universe who is not what

0:23:00.760 --> 0:23:01.200
<v Speaker 3>you're doing?

0:23:02.560 --> 0:23:05.200
<v Speaker 4>The way we do it is we prioritize based on

0:23:05.280 --> 0:23:09.080
<v Speaker 4>the size of the market and the potential opportunity. Yes,

0:23:09.200 --> 0:23:12.560
<v Speaker 4>if I had infinite resources, I would go everywhere within

0:23:12.560 --> 0:23:15.119
<v Speaker 4>the high Naken company and do everything, But we cannot.

0:23:15.400 --> 0:23:16.840
<v Speaker 5>We don't have infinite resources.

0:23:17.000 --> 0:23:18.960
<v Speaker 4>So we say, let's be a little bit picky and

0:23:19.000 --> 0:23:21.880
<v Speaker 4>choosy where the biggest opportunities are. But it's a matter

0:23:21.920 --> 0:23:24.560
<v Speaker 4>of time. Right today we touch upon the big market's

0:23:24.600 --> 0:23:28.080
<v Speaker 4>biggest scope. Over time, it's going to be pervasive through

0:23:28.080 --> 0:23:31.600
<v Speaker 4>the company. But the appetite is already there, so people

0:23:31.640 --> 0:23:34.280
<v Speaker 4>are really even if they have not really embedded some product,

0:23:34.720 --> 0:23:37.840
<v Speaker 4>they're asking for it, which is a fantastic place to be.

0:23:38.400 --> 0:23:41.359
<v Speaker 3>Yeah, yeah, what's been your biggest disappointment?

0:23:41.440 --> 0:23:41.840
<v Speaker 5>So far.

0:23:42.400 --> 0:23:44.640
<v Speaker 4>So far, it's been very fulfilling, I must say, but

0:23:44.720 --> 0:23:47.159
<v Speaker 4>I think what I would look back. Can we do

0:23:47.240 --> 0:23:49.240
<v Speaker 4>things a little bit quicker? Can we go a little

0:23:49.240 --> 0:23:52.400
<v Speaker 4>bit at high speed? And that's why this whole concept

0:23:52.400 --> 0:23:55.239
<v Speaker 4>of digital backbone. Can we standardized everything? If we can

0:23:55.320 --> 0:23:58.119
<v Speaker 4>speed that up, if we can really scale quickly, I

0:23:58.119 --> 0:24:00.159
<v Speaker 4>think that will be the best. Because today have a

0:24:00.240 --> 0:24:03.520
<v Speaker 4>very good problem. People are asking for products. Sometimes I say, yeah,

0:24:03.600 --> 0:24:07.040
<v Speaker 4>I need to put it on a timeline in a roadmap,

0:24:07.119 --> 0:24:08.960
<v Speaker 4>because I cannot just cater to it immediately.

0:24:09.400 --> 0:24:12.320
<v Speaker 3>Presumably that's one of the things that the people you're

0:24:12.320 --> 0:24:14.280
<v Speaker 3>working with at IBM can tell you. They can give

0:24:14.280 --> 0:24:18.639
<v Speaker 3>you a sense of how quickly others have adopted some

0:24:18.680 --> 0:24:19.440
<v Speaker 3>of these technology.

0:24:19.480 --> 0:24:21.400
<v Speaker 4>That's correct, and that's actually one of the bench funds

0:24:21.440 --> 0:24:24.200
<v Speaker 4>that you're referring to. We see I'll be losing pace,

0:24:24.240 --> 0:24:26.679
<v Speaker 4>and which other things can we go forward? And in

0:24:26.720 --> 0:24:28.720
<v Speaker 4>some case when you look at the digital core and

0:24:28.760 --> 0:24:32.040
<v Speaker 4>the backbone, maybe specific areas we can speed up because

0:24:32.080 --> 0:24:34.399
<v Speaker 4>those are the areas that are maximum potential value, and

0:24:34.440 --> 0:24:36.240
<v Speaker 4>some of them we can deprioritize a little bit.

0:24:36.359 --> 0:24:38.760
<v Speaker 5>Yeah, that we do all the time. Yeah, just a

0:24:38.760 --> 0:24:39.880
<v Speaker 5>pragmatic approach.

0:24:39.600 --> 0:24:43.879
<v Speaker 3>To I'm curious about a highly specific question, which is,

0:24:44.560 --> 0:24:49.800
<v Speaker 3>so here you have a legacy brewer bas in the Netherlands,

0:24:49.840 --> 0:24:53.840
<v Speaker 3>one hundred and sixty years old. If I were to say,

0:24:54.240 --> 0:24:56.480
<v Speaker 3>I want you to take an entirely new job, I

0:24:56.520 --> 0:24:58.800
<v Speaker 3>want you to do what you're doing, but I want

0:24:58.840 --> 0:25:02.159
<v Speaker 3>you to do it for an American company in a

0:25:02.240 --> 0:25:07.479
<v Speaker 3>completely different industry that's thirty years old, maybe a company

0:25:07.480 --> 0:25:11.919
<v Speaker 3>that makes the vacuum cleaners thirty years old in America.

0:25:11.960 --> 0:25:13.760
<v Speaker 3>How much of what you're doing. I guess what I'm

0:25:13.760 --> 0:25:16.159
<v Speaker 3>trying to say is, are there's things that are particular

0:25:16.200 --> 0:25:20.360
<v Speaker 3>to Heineken that have made your job sort of challenging

0:25:20.400 --> 0:25:23.520
<v Speaker 3>or interesting or that just wouldn't be an issue in

0:25:23.560 --> 0:25:24.680
<v Speaker 3>another environment.

0:25:25.240 --> 0:25:28.520
<v Speaker 4>So it's a good question, and thanks for the enticing offer,

0:25:28.600 --> 0:25:30.840
<v Speaker 4>but I will pollite.

0:25:31.040 --> 0:25:33.760
<v Speaker 3>I tried to make it as an average exactly.

0:25:33.400 --> 0:25:35.880
<v Speaker 4>But I won't polite to reject offer. But I'll tell

0:25:35.880 --> 0:25:36.560
<v Speaker 4>you why i'll reject.

0:25:36.600 --> 0:25:39.320
<v Speaker 3>You're going to be in Nebraska. They're making just one

0:25:39.400 --> 0:25:40.359
<v Speaker 3>kind of vacuum cleaner.

0:25:40.520 --> 0:25:43.159
<v Speaker 4>What I went to school in Iowas, Yes, exactly, So

0:25:43.240 --> 0:25:46.520
<v Speaker 4>I'm quite a bit. I think there's a cultural difference

0:25:46.720 --> 0:25:50.240
<v Speaker 4>we're all very passionate about our brands and products, and

0:25:50.280 --> 0:25:52.119
<v Speaker 4>there's a lot of it is connection based in the

0:25:52.160 --> 0:25:55.280
<v Speaker 4>sense we create these connections with our customers sometimes consumers,

0:25:55.800 --> 0:25:58.240
<v Speaker 4>and it's all about maintaining that. And once you get

0:25:58.240 --> 0:26:00.000
<v Speaker 4>a feel of it, you feel part of the family.

0:26:01.000 --> 0:26:03.000
<v Speaker 4>That's a very good feeling to have. And the fact

0:26:03.000 --> 0:26:04.639
<v Speaker 4>that today where I am, if I look back, I

0:26:04.720 --> 0:26:08.520
<v Speaker 4>probably will happy to say very fortunate to have probably

0:26:08.520 --> 0:26:09.800
<v Speaker 4>one of the best jobs in the world in the

0:26:09.840 --> 0:26:12.200
<v Speaker 4>current times. And there is no end to innovation, by

0:26:12.200 --> 0:26:14.760
<v Speaker 4>the way, and even within Heineken, yes it's a traditional

0:26:14.760 --> 0:26:17.600
<v Speaker 4>company who is stopping innovation. There's a lot more too,

0:26:18.240 --> 0:26:20.359
<v Speaker 4>so I'll be very busy for the next few years.

0:26:21.359 --> 0:26:23.439
<v Speaker 3>What are the Dutch like? This is one of the

0:26:23.440 --> 0:26:27.720
<v Speaker 3>oldest and most successful commercial cultures in the world, A

0:26:27.760 --> 0:26:31.000
<v Speaker 3>tiny country that's been solidly successful, that's for it. I'm

0:26:31.040 --> 0:26:34.560
<v Speaker 3>curious about innovating in that kind of environment. How is

0:26:34.600 --> 0:26:37.359
<v Speaker 3>that different from innovating in a huge country like the

0:26:37.440 --> 0:26:40.600
<v Speaker 3>United States or in a different kind of national culture.

0:26:41.200 --> 0:26:43.960
<v Speaker 4>I think it's a question of opportunity because within Netherlands,

0:26:43.960 --> 0:26:47.280
<v Speaker 4>by the way, Netherlands has one of the most highest

0:26:47.320 --> 0:26:51.280
<v Speaker 4>number of startups within Europe, if not the highest. So

0:26:51.359 --> 0:26:54.760
<v Speaker 4>there is this culture of innovation that's already embedded in there.

0:26:54.800 --> 0:26:57.840
<v Speaker 4>It's happening all the time. Companies like Phillips, ASML some

0:26:57.920 --> 0:27:01.640
<v Speaker 4>of the very big players already there. So it could

0:27:01.640 --> 0:27:04.399
<v Speaker 4>be a little bit different. I think in Netherlands we

0:27:04.440 --> 0:27:06.080
<v Speaker 4>want to make sure what we are doing really is

0:27:06.119 --> 0:27:08.320
<v Speaker 4>going to work, so there's a little bit of discussion alignment.

0:27:08.840 --> 0:27:11.960
<v Speaker 4>It's more structured, but also agile in a way we

0:27:12.040 --> 0:27:15.000
<v Speaker 4>do things, and us was more like let's do let's

0:27:15.000 --> 0:27:18.680
<v Speaker 4>go quick, experiment, learn fail. So I think there's pros

0:27:18.680 --> 0:27:22.120
<v Speaker 4>and cons on both sides, but so far it's quite good.

0:27:22.480 --> 0:27:25.240
<v Speaker 3>Give me a sense of what your what's a day

0:27:25.240 --> 0:27:28.960
<v Speaker 3>in a life like for you? What does it look

0:27:29.080 --> 0:27:31.040
<v Speaker 3>like to have the job that you have in a

0:27:31.160 --> 0:27:31.760
<v Speaker 3>place a cande.

0:27:32.080 --> 0:27:34.280
<v Speaker 4>First of all, it starts with the calendar and the

0:27:34.359 --> 0:27:37.600
<v Speaker 4>number of meetings I have, which is usually filled for

0:27:37.600 --> 0:27:41.240
<v Speaker 4>forty hours longer in the week. So that's the starting point,

0:27:41.520 --> 0:27:43.200
<v Speaker 4>and then I have to pick and choose which meetings

0:27:43.240 --> 0:27:45.679
<v Speaker 4>I need to prepare for what, and usually these meetings

0:27:45.680 --> 0:27:48.480
<v Speaker 4>are mostly about where are we with the product.

0:27:48.119 --> 0:27:48.960
<v Speaker 5>What are the challenges?

0:27:49.040 --> 0:27:51.840
<v Speaker 4>How can I help and solve it, and then sometimes

0:27:51.880 --> 0:27:55.560
<v Speaker 4>also pitching new products or convincing something, and also sometimes

0:27:55.600 --> 0:27:58.760
<v Speaker 4>chain management. I'd also do sessions where I present internally

0:27:58.880 --> 0:28:01.800
<v Speaker 4>quite quite often go to different places, because it always

0:28:01.840 --> 0:28:04.280
<v Speaker 4>helps to be in front of the audience when you're

0:28:04.280 --> 0:28:08.000
<v Speaker 4>presenting something. We also started something recently which we call

0:28:08.080 --> 0:28:11.239
<v Speaker 4>AI boot Camp, which is you use JANEAI as an

0:28:11.280 --> 0:28:14.600
<v Speaker 4>interface for all these big AI models and people can

0:28:14.640 --> 0:28:17.960
<v Speaker 4>interact in a very fun way. That's our new way

0:28:17.960 --> 0:28:21.639
<v Speaker 4>of really convincing the rest of the company that hey,

0:28:21.680 --> 0:28:23.840
<v Speaker 4>this is fun to play with and let's go.

0:28:24.520 --> 0:28:27.280
<v Speaker 3>So yeah, it's how many people would you cycle through

0:28:28.280 --> 0:28:29.800
<v Speaker 3>that kind of book camp anyone?

0:28:30.000 --> 0:28:32.040
<v Speaker 4>Usually we keep it a small group just to make

0:28:32.080 --> 0:28:36.320
<v Speaker 4>sure everyone is doing something hands on and nobody's just listening.

0:28:36.800 --> 0:28:39.320
<v Speaker 4>So usually a twenty to thirty people max. And then

0:28:39.480 --> 0:28:41.560
<v Speaker 4>go from one place to other and it's all hands on.

0:28:41.720 --> 0:28:44.000
<v Speaker 4>You cannot sit and watch. You have to participate.

0:28:44.240 --> 0:28:46.840
<v Speaker 3>Are you directly involved at all in the design or

0:28:46.880 --> 0:28:49.120
<v Speaker 3>creation of any of these tools?

0:28:49.400 --> 0:28:51.720
<v Speaker 4>So I review it and then I used to review

0:28:51.720 --> 0:28:54.920
<v Speaker 4>also the codes before, and now I'm mostly like trying

0:28:54.960 --> 0:28:57.280
<v Speaker 4>to get the feedback from the people that are using it,

0:28:57.520 --> 0:28:59.440
<v Speaker 4>because that's my best validation point.

0:28:59.600 --> 0:29:02.400
<v Speaker 5>I high net promoter score on these products.

0:29:02.560 --> 0:29:04.600
<v Speaker 4>I know the job is well done, but I do

0:29:04.680 --> 0:29:06.920
<v Speaker 4>check accuracy of model. Some of the basic things you'll

0:29:07.000 --> 0:29:09.720
<v Speaker 4>check in AI. Is the model drifting over time? What's

0:29:09.720 --> 0:29:10.400
<v Speaker 4>the accuracy?

0:29:10.480 --> 0:29:10.640
<v Speaker 5>You know?

0:29:10.760 --> 0:29:13.440
<v Speaker 4>How is it hosted on a platform? These things I check.

0:29:13.800 --> 0:29:15.920
<v Speaker 4>But we also have mechanisms on those, so it's not

0:29:16.000 --> 0:29:17.600
<v Speaker 4>like every time you have a DiPT deep and look

0:29:17.600 --> 0:29:18.160
<v Speaker 4>into everything.

0:29:18.480 --> 0:29:18.720
<v Speaker 5>Yeah.

0:29:18.720 --> 0:29:21.160
<v Speaker 4>So once you have these mechanisms in place, then these

0:29:21.240 --> 0:29:22.480
<v Speaker 4>sort of tasks become easier.

0:29:23.280 --> 0:29:25.280
<v Speaker 3>You've used the phrase that you want to make honey

0:29:25.360 --> 0:29:28.200
<v Speaker 3>in the Best Connected Brewer. What does that phrase mean?

0:29:28.880 --> 0:29:29.080
<v Speaker 5>Yeah?

0:29:29.120 --> 0:29:30.880
<v Speaker 4>So I think it started with the ambition in twenty

0:29:30.880 --> 0:29:33.720
<v Speaker 4>twenty when we said we're going to digital transform. Remember

0:29:33.720 --> 0:29:36.440
<v Speaker 4>the pendulum I was talking about from gut page to

0:29:36.520 --> 0:29:39.240
<v Speaker 4>all the way to data driven And in today's world,

0:29:39.240 --> 0:29:41.719
<v Speaker 4>when you think of digital transmission, there are a few components,

0:29:41.800 --> 0:29:44.920
<v Speaker 4>cybersecurity being one of them, the digital core, like I

0:29:44.960 --> 0:29:47.760
<v Speaker 4>was saying, is one of them. Simplification and automation of

0:29:47.800 --> 0:29:50.520
<v Speaker 4>systems is one of them. Our breweries, how can we simplify?

0:29:50.760 --> 0:29:52.960
<v Speaker 4>And then comes data and AI, which is the really

0:29:53.000 --> 0:29:55.520
<v Speaker 4>one of the biggest components. And when you think of

0:29:55.560 --> 0:29:58.520
<v Speaker 4>best connected Brewer, the idea is we have been serving

0:29:58.560 --> 0:30:01.720
<v Speaker 4>our consumers and customers for one hundred and sixty two years.

0:30:02.360 --> 0:30:06.160
<v Speaker 4>What's different If you leverage tech into Bay's world. I

0:30:06.200 --> 0:30:09.400
<v Speaker 4>think you can really enhance the experience the customers have.

0:30:09.920 --> 0:30:12.360
<v Speaker 4>The example I was giving you earlier about the salesforce

0:30:12.400 --> 0:30:15.960
<v Speaker 4>going in different places and optimizing the rout that's a

0:30:16.000 --> 0:30:18.720
<v Speaker 4>good example why the relation is maintained just simply by

0:30:18.760 --> 0:30:21.680
<v Speaker 4>data driven insights. So if you can connect all the

0:30:21.720 --> 0:30:26.240
<v Speaker 4>different applications, all the platforms, remove fragmentation, scale very quick,

0:30:26.720 --> 0:30:30.680
<v Speaker 4>make sure your company is CyberSecure, things are simple and automated.

0:30:31.360 --> 0:30:34.680
<v Speaker 4>That's what we call the best connected brower. That's the ambition.

0:30:34.800 --> 0:30:38.280
<v Speaker 3>Actually, how do you measure this success of what you're doing?

0:30:38.760 --> 0:30:44.200
<v Speaker 3>Is do you expect that your efforts will have a

0:30:44.280 --> 0:30:46.880
<v Speaker 3>measurable and tangible effect on the bottom line of the company?

0:30:46.960 --> 0:30:52.240
<v Speaker 3>And can you actually figure out what the impact of

0:30:52.280 --> 0:30:52.960
<v Speaker 3>your efforts is?

0:30:53.440 --> 0:30:53.960
<v Speaker 5>Yeah, we do.

0:30:54.080 --> 0:30:57.000
<v Speaker 4>I think that is super important to measure because the

0:30:57.080 --> 0:31:00.120
<v Speaker 4>first one I was referring to proof of value and

0:31:00.160 --> 0:31:03.000
<v Speaker 4>I'm embedding some model, does it really work? So we

0:31:03.080 --> 0:31:06.000
<v Speaker 4>do a B testing, which is basically you keep aside

0:31:06.000 --> 0:31:08.560
<v Speaker 4>some sample and you actually launch the product on a

0:31:08.600 --> 0:31:10.640
<v Speaker 4>different sample, and you see the difference between the two.

0:31:11.120 --> 0:31:14.000
<v Speaker 4>The assumption is those that had the product and those

0:31:14.000 --> 0:31:16.440
<v Speaker 4>that didn't have the product, both of them went through

0:31:16.440 --> 0:31:20.200
<v Speaker 4>the same experiences because of market seasonal, etc. That's one

0:31:20.240 --> 0:31:22.440
<v Speaker 4>good way of doing it. And if you cannot have

0:31:22.520 --> 0:31:25.120
<v Speaker 4>the luxury sometimes of doing a B testing because everyone

0:31:25.200 --> 0:31:27.520
<v Speaker 4>is having high appetite, give me the product I don't

0:31:27.520 --> 0:31:30.040
<v Speaker 4>want to sit aside. Then you do some sort of

0:31:30.880 --> 0:31:33.040
<v Speaker 4>causal models like we say, so you kind of look

0:31:33.040 --> 0:31:36.040
<v Speaker 4>at what would have happened if the model was not there,

0:31:36.920 --> 0:31:39.560
<v Speaker 4>and then you predict that and since the model was there,

0:31:39.640 --> 0:31:42.120
<v Speaker 4>something else happened. The difference between the two is the

0:31:42.120 --> 0:31:45.080
<v Speaker 4>incremental value the model is creating. A B testing is

0:31:45.080 --> 0:31:47.880
<v Speaker 4>more accurate the causal models. The other one, like you said,

0:31:47.920 --> 0:31:50.760
<v Speaker 4>which called time series model, a little bit less accurate,

0:31:50.760 --> 0:31:53.560
<v Speaker 4>but directionally both give you the sense that yes, it's working.

0:31:53.960 --> 0:31:55.800
<v Speaker 3>What happens if you do a B testing or a

0:31:55.840 --> 0:31:58.600
<v Speaker 3>new idea and you don't see a difference.

0:31:59.480 --> 0:32:01.280
<v Speaker 4>In that case, we will move on to something else

0:32:01.320 --> 0:32:04.800
<v Speaker 4>because it means it's already optimal. Then we said, good,

0:32:05.240 --> 0:32:07.680
<v Speaker 4>check that now let's move on to something else. But

0:32:07.760 --> 0:32:10.080
<v Speaker 4>we need to just make sure that the process is

0:32:10.120 --> 0:32:11.320
<v Speaker 4>still running optimally.

0:32:11.360 --> 0:32:12.600
<v Speaker 5>So time to time, you keep.

0:32:12.480 --> 0:32:15.440
<v Speaker 4>Doing every testing anyway, every six months or whatever the

0:32:15.440 --> 0:32:17.960
<v Speaker 4>timeframe is. Yeah, just to make sure that it's still

0:32:18.040 --> 0:32:18.760
<v Speaker 4>still relevant.

0:32:18.840 --> 0:32:21.040
<v Speaker 3>But what if this is we're getting out on a

0:32:21.080 --> 0:32:23.680
<v Speaker 3>little bit of a digression here, but it's something I've

0:32:23.720 --> 0:32:27.040
<v Speaker 3>often thought about. What if the value that is being

0:32:27.080 --> 0:32:30.440
<v Speaker 3>created is not measurable? So I'll give you a dumb example.

0:32:30.680 --> 0:32:34.960
<v Speaker 3>When you were talking earlier about the salesman and giving

0:32:34.960 --> 0:32:38.200
<v Speaker 3>them a new, you know, better instructions about how to

0:32:38.200 --> 0:32:42.440
<v Speaker 3>basically spend their day, what if you tested that, discovered

0:32:42.440 --> 0:32:45.400
<v Speaker 3>it it didn't have any effect on the bottom line.

0:32:45.640 --> 0:32:48.680
<v Speaker 3>But in fact, what was happening was that the salesmen

0:32:48.720 --> 0:32:51.520
<v Speaker 3>were a lot happier with their jobs. And we're satisfied

0:32:52.400 --> 0:32:55.160
<v Speaker 3>and we're excited to come to work. Do you measure

0:32:55.320 --> 0:32:57.040
<v Speaker 3>something like that? Something intolerable?

0:32:57.160 --> 0:32:57.640
<v Speaker 5>Measure?

0:32:58.120 --> 0:33:00.720
<v Speaker 4>One way is NPS four, which I said promoter score.

0:33:00.760 --> 0:33:02.640
<v Speaker 4>Are you really happy with the product? Has it changed

0:33:02.640 --> 0:33:05.920
<v Speaker 4>your life? That gives you a good indication then, And

0:33:06.320 --> 0:33:08.160
<v Speaker 4>by the way, it's a numeric output, so it gives

0:33:08.200 --> 0:33:12.480
<v Speaker 4>you a score between minus hundred to plus hundred, and

0:33:12.560 --> 0:33:15.400
<v Speaker 4>sometimes it's not even tangible. Let's say we do something

0:33:15.440 --> 0:33:18.040
<v Speaker 4>for corporate affairs because they want to get external signals

0:33:18.040 --> 0:33:21.640
<v Speaker 4>of consumer insights and then just lean some information. Maybe

0:33:21.640 --> 0:33:24.200
<v Speaker 4>we act on it, maybe we don't, but this is

0:33:24.200 --> 0:33:26.160
<v Speaker 4>for a good cause. Sometimes you just want to study

0:33:26.160 --> 0:33:28.680
<v Speaker 4>the market. There's no immediate value if you don't create

0:33:28.720 --> 0:33:31.000
<v Speaker 4>a product out of it, or something to do with

0:33:31.120 --> 0:33:34.400
<v Speaker 4>legal If there's a reputational risk for Heineken, can I

0:33:34.440 --> 0:33:36.800
<v Speaker 4>extract some insight that will prevent us or create the

0:33:36.800 --> 0:33:41.200
<v Speaker 4>best briefing or summary or external briefing that using AI

0:33:41.280 --> 0:33:45.880
<v Speaker 4>that will help us protect ourselves. That's also reputational damage.

0:33:46.240 --> 0:33:49.440
<v Speaker 3>Last question before we go to questions. I'm curious when

0:33:49.440 --> 0:33:53.680
<v Speaker 3>you look at the very beginning you talked about this

0:33:53.920 --> 0:33:58.080
<v Speaker 3>linear value chain we're in that along that chain are

0:33:58.120 --> 0:34:01.320
<v Speaker 3>you having the most and where are you having the

0:34:01.440 --> 0:34:03.760
<v Speaker 3>least impact. I'm more interested in the second half of that.

0:34:04.040 --> 0:34:07.880
<v Speaker 4>Yeah, I think we covered few things, but one area

0:34:07.920 --> 0:34:10.000
<v Speaker 4>I think we can do more is really.

0:34:09.800 --> 0:34:11.440
<v Speaker 5>Understanding consumer sentiments.

0:34:12.280 --> 0:34:15.279
<v Speaker 4>And the reason for that is Heineken is people go

0:34:15.360 --> 0:34:17.520
<v Speaker 4>to the bars and outlets and you're not really leading

0:34:17.600 --> 0:34:20.680
<v Speaker 4>your first hand data there right, you're enjoying a beer,

0:34:20.719 --> 0:34:23.239
<v Speaker 4>then you walk away. I don't know exactly what you did.

0:34:23.640 --> 0:34:25.799
<v Speaker 4>I can get some aggregated data to make some sense

0:34:25.840 --> 0:34:29.000
<v Speaker 4>out of it. But if we can really get consumer

0:34:29.040 --> 0:34:32.040
<v Speaker 4>insights as to what the consumers like and dislike, what

0:34:32.160 --> 0:34:34.640
<v Speaker 4>sort of ad you like? How should I design my

0:34:34.719 --> 0:34:39.319
<v Speaker 4>Hanneken campaign so it resonates with a cluster of individuals.

0:34:39.800 --> 0:34:41.400
<v Speaker 4>That would be a little bit of holy grail as

0:34:41.440 --> 0:34:43.560
<v Speaker 4>the next step, like you were talking about two point zero,

0:34:44.160 --> 0:34:47.040
<v Speaker 4>and to get consumer insights first party data.

0:34:46.880 --> 0:34:47.800
<v Speaker 5>It's not super easy.

0:34:48.200 --> 0:34:51.120
<v Speaker 4>So what we are trying to do is create digital

0:34:51.160 --> 0:34:54.680
<v Speaker 4>twins of consumers. So at an aggregate level, they give

0:34:54.719 --> 0:34:57.279
<v Speaker 4>you a sense of Also with agent Kei, which is

0:34:57.280 --> 0:35:00.000
<v Speaker 4>also you hear a lot about to get a sense

0:35:00.160 --> 0:35:03.200
<v Speaker 4>of how consumers might react to certain campaign or certain product,

0:35:03.719 --> 0:35:05.640
<v Speaker 4>and that should give us quite a bit of insights

0:35:05.640 --> 0:35:07.759
<v Speaker 4>that right now we don't have access to. I think

0:35:07.800 --> 0:35:09.359
<v Speaker 4>that's one of the areas we could really do.

0:35:09.280 --> 0:35:10.319
<v Speaker 5>A lot more. Yeah.

0:35:10.560 --> 0:35:12.960
<v Speaker 3>Yeah, So if I said last question, if I sat

0:35:13.080 --> 0:35:16.399
<v Speaker 3>down with you, it's twenty twenty six. Now, we did

0:35:16.400 --> 0:35:19.319
<v Speaker 3>this over five years from now twenty thirty one, we're

0:35:19.320 --> 0:35:22.680
<v Speaker 3>sitting in this chair, tell me what the kind of

0:35:23.600 --> 0:35:25.280
<v Speaker 3>what's going to be the next big score.

0:35:26.120 --> 0:35:28.480
<v Speaker 4>I think one area will be how we make our

0:35:28.520 --> 0:35:31.799
<v Speaker 4>lives as employees are finding a lot easier. So the repetitive,

0:35:32.360 --> 0:35:35.719
<v Speaker 4>boring task, manual task. Can we automate those things and

0:35:35.840 --> 0:35:38.160
<v Speaker 4>just use the time to do something more creative and

0:35:38.239 --> 0:35:41.520
<v Speaker 4>think big about the business itself. That will be one area,

0:35:41.560 --> 0:35:44.160
<v Speaker 4>most on the productivity side. But the other area would

0:35:44.200 --> 0:35:46.960
<v Speaker 4>be Indeed, when we look at gen Z and this

0:35:47.080 --> 0:35:50.319
<v Speaker 4>is fact, I'm not saying something my own opinion, there's

0:35:50.360 --> 0:35:54.319
<v Speaker 4>a trend of distinct trend of alcohol as a beverage.

0:35:54.560 --> 0:35:57.080
<v Speaker 4>The consumption is on a decline. So then what's the

0:35:57.120 --> 0:36:01.680
<v Speaker 4>next best thing for the new generation? What will resonate?

0:36:02.320 --> 0:36:04.279
<v Speaker 4>Those are the pockets we need to find, and I

0:36:04.280 --> 0:36:07.120
<v Speaker 4>think that's where we will transition very quickly over the

0:36:07.120 --> 0:36:07.719
<v Speaker 4>next five years.

0:36:07.760 --> 0:36:08.920
<v Speaker 5>And if you get there, I think that will be

0:36:08.920 --> 0:36:09.520
<v Speaker 5>big success.

0:36:10.120 --> 0:36:16.399
<v Speaker 3>So you think that your specific department responsibility can help

0:36:16.440 --> 0:36:18.880
<v Speaker 3>the company in discovering what the answer to that question

0:36:18.960 --> 0:36:19.360
<v Speaker 3>is about.

0:36:19.600 --> 0:36:21.880
<v Speaker 4>Definitely, that's the ambition, that's what we're trying to do.

0:36:22.120 --> 0:36:23.880
<v Speaker 4>That's what we are really trying to get this one

0:36:23.960 --> 0:36:26.080
<v Speaker 4>over insights. I think that's the last mile. That's the

0:36:26.120 --> 0:36:27.600
<v Speaker 4>one part that is left.

0:36:28.320 --> 0:36:31.000
<v Speaker 3>Sergey, this has been fascinating. Thank you so much. I

0:36:31.040 --> 0:36:33.320
<v Speaker 3>should say thank you for a question, sir. My uncle

0:36:33.680 --> 0:36:37.080
<v Speaker 3>was a Heineken salesman in Jamaica. He was the local

0:36:37.120 --> 0:36:40.960
<v Speaker 3>distributor and I have so many child memories of going

0:36:41.000 --> 0:36:43.359
<v Speaker 3>to Jamaica and he would show up in his Heineken truck.

0:36:44.160 --> 0:36:50.680
<v Speaker 3>So we're resonating deep in my mimory with this conversation.

0:36:50.760 --> 0:36:52.480
<v Speaker 3>He would come and he would have a Heineken right

0:36:52.520 --> 0:36:54.520
<v Speaker 3>there on the on the table and would drink it

0:36:54.560 --> 0:36:57.000
<v Speaker 3>at the end of the day. But we have we

0:36:57.080 --> 0:37:00.440
<v Speaker 3>have a few moments for questions. They're all the screen

0:37:00.480 --> 0:37:02.319
<v Speaker 3>and I don't have my glasses. Can you read them?

0:37:02.440 --> 0:37:04.640
<v Speaker 5>Yeah, I can, I can read them. Then they should

0:37:04.680 --> 0:37:05.879
<v Speaker 5>be going order to the first one.

0:37:06.040 --> 0:37:08.799
<v Speaker 3>Yeah no, no, no, no no, no, Rookie air, never

0:37:08.880 --> 0:37:12.400
<v Speaker 3>do that. Okay, read the first four and pick the

0:37:12.400 --> 0:37:13.360
<v Speaker 3>one you want to answer.

0:37:14.800 --> 0:37:15.959
<v Speaker 5>Okay, go tip.

0:37:16.440 --> 0:37:18.120
<v Speaker 4>But I gave it away already, so I'm going to

0:37:18.200 --> 0:37:21.120
<v Speaker 4>now do what I said. No, I think the first

0:37:21.120 --> 0:37:23.399
<v Speaker 4>one is quite relevant. So it's a question for both

0:37:23.400 --> 0:37:26.480
<v Speaker 4>of us. If you were advising a twenty year old,

0:37:26.880 --> 0:37:29.840
<v Speaker 4>what three skills. Would you tell them to start developing

0:37:30.000 --> 0:37:33.480
<v Speaker 4>right now to stay relevant in an AI driven world?

0:37:34.400 --> 0:37:37.799
<v Speaker 3>Oh well, well you don't you have a twenty year

0:37:37.800 --> 0:37:39.160
<v Speaker 3>old or a near twenty year old. You have a

0:37:39.200 --> 0:37:39.919
<v Speaker 3>fifteen year old?

0:37:39.960 --> 0:37:41.319
<v Speaker 5>You told me I have a fifteen year old?

0:37:41.400 --> 0:37:42.600
<v Speaker 3>All right, what do you tell your son?

0:37:42.760 --> 0:37:44.120
<v Speaker 5>I thought you were going to answer them this first,

0:37:44.120 --> 0:37:45.480
<v Speaker 5>but my.

0:37:45.520 --> 0:37:48.040
<v Speaker 3>Kids are two and four. I tell them to put

0:37:48.080 --> 0:37:52.239
<v Speaker 3>away their toys. You this is more, you start more?

0:37:52.800 --> 0:37:55.000
<v Speaker 3>Do you have a is your fifteen year old son

0:37:55.080 --> 0:37:55.479
<v Speaker 3>or daughter?

0:37:55.600 --> 0:37:56.000
<v Speaker 5>His son?

0:37:56.239 --> 0:38:00.440
<v Speaker 4>And he's already thinker with AI. He's doing his own Python, etc.

0:38:00.719 --> 0:38:03.400
<v Speaker 4>Which I couldn't imagine when I was fifteen. So I

0:38:03.440 --> 0:38:06.640
<v Speaker 4>think I'll give a high level answer to be actually

0:38:06.680 --> 0:38:10.480
<v Speaker 4>successful depending on whether your hands on within AI, building

0:38:10.480 --> 0:38:13.160
<v Speaker 4>models yourself or not. There are three things I think

0:38:13.200 --> 0:38:17.160
<v Speaker 4>is super important. One is having that tech background, having

0:38:17.160 --> 0:38:19.319
<v Speaker 4>a common understanding of what AI really is.

0:38:19.400 --> 0:38:20.280
<v Speaker 5>It always helps.

0:38:20.520 --> 0:38:23.239
<v Speaker 4>Not everyone needs to have the details and algorithms and

0:38:23.280 --> 0:38:27.120
<v Speaker 4>how models work, not needed, but having that basic understanding

0:38:27.160 --> 0:38:29.520
<v Speaker 4>always is good. Then you know exactly how to gauge

0:38:29.640 --> 0:38:31.759
<v Speaker 4>what AI is really doing. And I think the other

0:38:31.800 --> 0:38:35.000
<v Speaker 4>thing is if you are in a corporate setting and

0:38:35.040 --> 0:38:37.839
<v Speaker 4>you are doing something for the business, work backwards from

0:38:37.840 --> 0:38:41.839
<v Speaker 4>the business and understand whatever you're building should actually touch

0:38:41.880 --> 0:38:44.279
<v Speaker 4>the business and make it beneficial for them. It's not

0:38:44.440 --> 0:38:46.680
<v Speaker 4>AI and modeling for the sake of it. That's for

0:38:46.680 --> 0:38:49.520
<v Speaker 4>a separate research and development. If you're in a corporate world,

0:38:49.719 --> 0:38:52.680
<v Speaker 4>try to build something beneficial for business. And I third

0:38:52.680 --> 0:38:54.719
<v Speaker 4>one I think which myself I learned quite a bit

0:38:54.760 --> 0:38:56.280
<v Speaker 4>in my in last six years.

0:38:56.920 --> 0:38:59.759
<v Speaker 5>It's communication. Talking about AI.

0:38:59.840 --> 0:39:02.840
<v Speaker 4>If you used a lot of tech jargon and mathematics,

0:39:03.320 --> 0:39:07.080
<v Speaker 4>sometimes people lose you. It's about how you really narrate

0:39:07.120 --> 0:39:09.440
<v Speaker 4>the story in a very simple way so people can

0:39:09.520 --> 0:39:11.839
<v Speaker 4>relate to it. I think if the combination of these

0:39:11.880 --> 0:39:14.480
<v Speaker 4>three has worked very well for me, so I can

0:39:14.800 --> 0:39:17.279
<v Speaker 4>say that anything you want to add.

0:39:17.480 --> 0:39:22.000
<v Speaker 3>It's funny because I I met this guy who's the

0:39:22.040 --> 0:39:25.480
<v Speaker 3>headmaster at a Jesuit school in Manhattan. We've been chatting

0:39:26.000 --> 0:39:28.120
<v Speaker 3>and I want to do a little program at his school,

0:39:28.760 --> 0:39:33.719
<v Speaker 3>and it's all about asking questions because we're now into

0:39:33.760 --> 0:39:36.000
<v Speaker 3>the era of asking questions right.

0:39:36.080 --> 0:39:36.560
<v Speaker 5>That's correct.

0:39:36.600 --> 0:39:38.560
<v Speaker 3>AI is this incredibly good tool, but you have to

0:39:39.280 --> 0:39:42.680
<v Speaker 3>ask the right questions. But this is not just true

0:39:42.680 --> 0:39:45.439
<v Speaker 3>of AI, but it's also true of the world we're

0:39:45.480 --> 0:39:49.480
<v Speaker 3>living in is a world that's so interconnected and everything

0:39:49.480 --> 0:39:53.640
<v Speaker 3>involves so many different people that your distinguishing feature in

0:39:53.680 --> 0:39:56.279
<v Speaker 3>many context is not where they're not the answers you have,

0:39:56.640 --> 0:39:58.239
<v Speaker 3>but the quality of the questions that you ask.

0:39:58.640 --> 0:40:00.759
<v Speaker 5>That's fantastic what you said. I fully avery.

0:40:00.800 --> 0:40:03.759
<v Speaker 4>I think it's about asking the right questions that really

0:40:03.800 --> 0:40:06.920
<v Speaker 4>tells you, you know, you're looking for that that unique

0:40:06.920 --> 0:40:07.960
<v Speaker 4>thing that that you're missing.

0:40:08.080 --> 0:40:09.839
<v Speaker 5>Yeah, I fully agree.

0:40:10.080 --> 0:40:14.120
<v Speaker 3>Maybe I'll advite you to this class and like you

0:40:14.200 --> 0:40:17.440
<v Speaker 3>have that kind of time on your hands, if you

0:40:17.480 --> 0:40:19.879
<v Speaker 3>brought if you brought up you know, Heineken for all

0:40:19.880 --> 0:40:23.080
<v Speaker 3>the kids in school, that would that would really.

0:40:22.920 --> 0:40:26.200
<v Speaker 5>Yeah, surely we have to build a special product for that.

0:40:26.360 --> 0:40:29.360
<v Speaker 5>Well let's see, all right, next question, let's.

0:40:29.160 --> 0:40:32.400
<v Speaker 4>Go to this one or Malcolm, is there a particular

0:40:32.480 --> 0:40:35.920
<v Speaker 4>AI capability you are each excited to explore?

0:40:37.239 --> 0:40:38.240
<v Speaker 3>That's for you, my friend.

0:40:39.719 --> 0:40:42.239
<v Speaker 4>I think in the in the short term, I'm really

0:40:42.239 --> 0:40:44.920
<v Speaker 4>looking forward to Agent K. I is hearing a lot

0:40:44.960 --> 0:40:48.400
<v Speaker 4>of noise and hype and there are a lot of

0:40:48.560 --> 0:40:51.000
<v Speaker 4>feedback that I'm getting from a lot of companies. Have

0:40:51.160 --> 0:40:54.320
<v Speaker 4>you really embedded Agent KI within your systems? There is

0:40:54.320 --> 0:40:56.640
<v Speaker 4>a very mixed feedback. Some say yes, some say no.

0:40:57.160 --> 0:40:59.000
<v Speaker 4>I think the potential of agent k I when we

0:40:59.000 --> 0:41:02.279
<v Speaker 4>look at this task we do day to day. Let

0:41:02.280 --> 0:41:05.640
<v Speaker 4>me gives an example, invoice management or transactional finance or

0:41:05.760 --> 0:41:08.879
<v Speaker 4>very repetitive task. If you can really automate augment those

0:41:08.880 --> 0:41:11.080
<v Speaker 4>things with agent KI, I think it's going to be

0:41:11.120 --> 0:41:13.400
<v Speaker 4>a game changer. If you free up thirty percent of

0:41:13.400 --> 0:41:16.960
<v Speaker 4>our time just by embedding these things, then I can

0:41:16.960 --> 0:41:20.680
<v Speaker 4>really think big. Everyone can think big. What's next? Then

0:41:20.719 --> 0:41:23.240
<v Speaker 4>the creativity comes in. Otherwise all day you are stuck

0:41:23.280 --> 0:41:26.000
<v Speaker 4>with the repetitive task. So I think that's what I'm

0:41:26.000 --> 0:41:28.320
<v Speaker 4>really looking forward to. And this is very short term.

0:41:28.400 --> 0:41:29.640
<v Speaker 4>Within the next few years.

0:41:30.000 --> 0:41:33.360
<v Speaker 3>Yeah, we have I think, what time for one more question,

0:41:34.760 --> 0:41:38.560
<v Speaker 3>Sergey go for let's see this is it's got to

0:41:38.640 --> 0:41:40.439
<v Speaker 3>be the last one always has to be the best one.

0:41:40.480 --> 0:41:45.600
<v Speaker 4>Certain let for people hearing the phrase for the first time,

0:41:45.719 --> 0:41:48.880
<v Speaker 4>what is the real example that shows Heineken being the

0:41:48.920 --> 0:41:52.600
<v Speaker 4>best connected broer? Basically you're asking for a proof point.

0:41:53.040 --> 0:41:55.640
<v Speaker 4>Are we really becoming the best connective brower when we

0:41:55.680 --> 0:41:58.640
<v Speaker 4>look at our markets. Heinek in Mexico is a very

0:41:58.640 --> 0:42:01.880
<v Speaker 4>good example across how value chain if you work backwards

0:42:01.880 --> 0:42:06.680
<v Speaker 4>from consumers, customers and so on. We have advertising optimization

0:42:06.760 --> 0:42:10.640
<v Speaker 4>for consumers. For customers, we have next best action. Actually

0:42:10.719 --> 0:42:14.319
<v Speaker 4>for customers we are pricing and promotion optimized. For the salesforce,

0:42:14.360 --> 0:42:16.880
<v Speaker 4>we have next best action. For the breweries, we have

0:42:16.960 --> 0:42:19.680
<v Speaker 4>connected brewery. We are getting signals from these machines and

0:42:19.680 --> 0:42:23.120
<v Speaker 4>optimizing them. I think it covers a significant portion of

0:42:23.120 --> 0:42:26.560
<v Speaker 4>a value chain that's fully automated end to end. So

0:42:26.600 --> 0:42:28.480
<v Speaker 4>that would be a good example where we really saw

0:42:28.520 --> 0:42:31.160
<v Speaker 4>the benefit of taking it to the next level when

0:42:31.160 --> 0:42:34.440
<v Speaker 4>it comes to automation. So Mexico Heineken Mexico is a

0:42:34.440 --> 0:42:35.040
<v Speaker 4>good example.

0:42:35.320 --> 0:42:38.000
<v Speaker 3>Thank you so much for joining us. Thank you to

0:42:38.080 --> 0:42:40.240
<v Speaker 3>all of you who came to listen.

0:42:40.640 --> 0:42:43.480
<v Speaker 5>Thanks for it. Asper, Thank you very much.

0:42:43.880 --> 0:42:48.000
<v Speaker 3>Yeah, that's it for the first episode of season seven

0:42:48.400 --> 0:42:51.759
<v Speaker 3>of Smart Talks with IBM, But stay tuned. There's so

0:42:51.880 --> 0:42:54.360
<v Speaker 3>much more to come this season as we die further

0:42:54.400 --> 0:42:59.360
<v Speaker 3>into how AI and Quantum Computing are creating smarter business.

0:43:00.600 --> 0:43:03.680
<v Speaker 3>Smart Talks with IBM is produced by Matt Ramano, Amy

0:43:03.680 --> 0:43:08.680
<v Speaker 3>Gains McQuaid, and Jake Harper. Engineering by Ninabird Lawrence, Mastering

0:43:08.719 --> 0:43:12.960
<v Speaker 3>by Sarah Buguer music by Gramoscope, Strategy by Cassidy Meyer

0:43:13.280 --> 0:43:17.920
<v Speaker 3>and Sophia Derlin. Special thanks to Sergei Ghosh and Michelle Ganji.

0:43:17.960 --> 0:43:21.440
<v Speaker 3>Post from the Heineken Company. Smart Talks with IBM is

0:43:21.440 --> 0:43:25.399
<v Speaker 3>a production of Pushkin Industries and Ruby Studio at iHeartMedia.

0:43:26.200 --> 0:43:30.120
<v Speaker 3>To find more Pushkin podcasts, listen on the iHeartRadio app,

0:43:30.360 --> 0:43:35.560
<v Speaker 3>Apple Podcasts, or wherever you listen to podcasts. I'm Malcolm Gladwell.

0:43:35.920 --> 0:43:39.440
<v Speaker 3>This is a paid advertisement from IBM. The conversations on

0:43:39.480 --> 0:43:50.840
<v Speaker 3>this podcast don't necessarily represent IBM's positions, strategies, or opinions.