WEBVTT - A Conversation with Beena Ammanath

0:00:04.400 --> 0:00:07.800
<v Speaker 1>Welcome to tex Stuff, a production from I Heart Radio.

0:00:12.200 --> 0:00:16.000
<v Speaker 1>Hey therein Welcome to tex Stuff. I'm your host, Jonathan Strickland.

0:00:16.000 --> 0:00:18.919
<v Speaker 1>I'm an executive producer with I Heart Radio. And how

0:00:19.040 --> 0:00:22.560
<v Speaker 1>the tech are you? I gotta treat view folks. Today

0:00:22.600 --> 0:00:26.599
<v Speaker 1>I had the opportunity to speak with Bena Amnath, the

0:00:26.640 --> 0:00:31.520
<v Speaker 1>executive director of Deloitte AI Institute. Vina is an accomplished

0:00:31.560 --> 0:00:37.960
<v Speaker 1>technologist and expert in artificial intelligence. She's a coder, she's,

0:00:38.560 --> 0:00:42.159
<v Speaker 1>you know, an engineer, and she's a great communicator too.

0:00:42.240 --> 0:00:47.600
<v Speaker 1>She has appeared on numerous shows and panels talking about AI.

0:00:47.680 --> 0:00:51.960
<v Speaker 1>She's also the author of a book called Trustworthy AI.

0:00:52.600 --> 0:00:56.360
<v Speaker 1>And this was a fantastic opportunity to speak with someone

0:00:56.400 --> 0:00:59.600
<v Speaker 1>who actually has a deep amount of experience in the

0:00:59.640 --> 0:01:04.600
<v Speaker 1>field and really talk about some of the big concepts

0:01:04.600 --> 0:01:07.200
<v Speaker 1>in AI and get a little more perspective on them.

0:01:07.400 --> 0:01:13.520
<v Speaker 1>And I have to admit Beena's responses really open up

0:01:13.560 --> 0:01:16.640
<v Speaker 1>the blinders that I have on And of course I'm

0:01:16.680 --> 0:01:18.560
<v Speaker 1>like a lot of people, right I I go through

0:01:18.600 --> 0:01:21.560
<v Speaker 1>life thinking I have a pretty good handle on this.

0:01:21.720 --> 0:01:23.959
<v Speaker 1>I think I know what's going on, and then I

0:01:23.959 --> 0:01:27.319
<v Speaker 1>meet someone else who has had a you know, a

0:01:27.319 --> 0:01:30.880
<v Speaker 1>different experience, and especially a different depth of experience in

0:01:30.880 --> 0:01:34.360
<v Speaker 1>a particular field and realize, oh gosh, I hadn't even

0:01:34.400 --> 0:01:41.120
<v Speaker 1>considered some of these specific scenarios, for example. So I

0:01:41.240 --> 0:01:45.240
<v Speaker 1>really very much enjoyed my conversation with Bena. She's also

0:01:45.720 --> 0:01:50.240
<v Speaker 1>incredibly good at putting things in a way that are

0:01:50.360 --> 0:01:54.040
<v Speaker 1>easily understandable. A lot of technologists, when you start to

0:01:54.040 --> 0:01:58.880
<v Speaker 1>talk with them, they get really heavy with jargon or

0:01:59.040 --> 0:02:03.040
<v Speaker 1>or concepts. That makes sense if you've had experience working

0:02:03.080 --> 0:02:06.400
<v Speaker 1>in that area, but if you haven't, your eyes kind

0:02:06.400 --> 0:02:09.799
<v Speaker 1>of glaze over and you just trust that what they

0:02:09.800 --> 0:02:12.160
<v Speaker 1>say makes sense. That was not the issue with Bina.

0:02:12.320 --> 0:02:16.600
<v Speaker 1>She is really good at talking about this stuff on

0:02:16.680 --> 0:02:20.239
<v Speaker 1>a level that that the average person can easily understand,

0:02:21.040 --> 0:02:25.840
<v Speaker 1>and yet also really stressing how AI is a very

0:02:25.880 --> 0:02:28.839
<v Speaker 1>important component today. I mean, we're seeing it rolled out

0:02:28.919 --> 0:02:33.520
<v Speaker 1>in all sorts of different ways across all different sectors.

0:02:34.120 --> 0:02:38.079
<v Speaker 1>We mostly talked about business in this conversation, but clearly

0:02:38.680 --> 0:02:43.880
<v Speaker 1>AI is everywhere. Whether we're talking about facial recognition technology

0:02:43.880 --> 0:02:46.880
<v Speaker 1>that might be built directly into the camera on your phone,

0:02:47.560 --> 0:02:51.440
<v Speaker 1>or maybe we're talking about a personal digital assistant, you know,

0:02:51.520 --> 0:02:55.040
<v Speaker 1>something like the Amazon one. I won't say her name

0:02:55.240 --> 0:02:58.320
<v Speaker 1>because some of you have her and she gets real

0:02:58.720 --> 0:03:02.680
<v Speaker 1>like she she perks up when you say her name. Um,

0:03:02.720 --> 0:03:05.680
<v Speaker 1>those sort of things obviously have components of AI built

0:03:05.680 --> 0:03:08.680
<v Speaker 1>into them, but we were really looking at things like

0:03:09.680 --> 0:03:14.840
<v Speaker 1>processes in business where you might need to use automation

0:03:14.919 --> 0:03:23.320
<v Speaker 1>and artificial intelligence to make complicated processes more efficient and

0:03:23.840 --> 0:03:27.520
<v Speaker 1>less human intensive. And so, yeah, this was a great

0:03:27.560 --> 0:03:30.320
<v Speaker 1>conversation and I really feel like I learned a lot.

0:03:30.360 --> 0:03:34.200
<v Speaker 1>I hope that you all enjoy it. And again, she

0:03:34.320 --> 0:03:37.440
<v Speaker 1>does have a new book out. It's called Trustworthy AI,

0:03:37.520 --> 0:03:39.360
<v Speaker 1>and there's a copy on the way to me, so

0:03:39.400 --> 0:03:43.680
<v Speaker 1>I'm very eager to read it myself because just talking

0:03:43.680 --> 0:03:46.840
<v Speaker 1>with Bina I felt like I was just scratching the surface.

0:03:47.000 --> 0:03:49.400
<v Speaker 1>But you're gonna hear all that, So let's get to

0:03:49.640 --> 0:03:53.760
<v Speaker 1>that interview. Bina. I want to welcome you to the show.

0:03:54.040 --> 0:03:57.119
<v Speaker 1>I am so pleased to have an expert on AI.

0:03:57.160 --> 0:04:02.320
<v Speaker 1>Trustworthy AI, no less, Welcome to tech stuff, Jonathan, thank

0:04:02.360 --> 0:04:04.720
<v Speaker 1>you so much for having me on your show. I

0:04:04.800 --> 0:04:08.200
<v Speaker 1>really enjoy your episodes, so I'm looking forward to having

0:04:08.240 --> 0:04:11.360
<v Speaker 1>this conversation with you. I am as well. And one

0:04:11.400 --> 0:04:13.400
<v Speaker 1>of the things that I like to do is kind

0:04:13.440 --> 0:04:18.800
<v Speaker 1>of set some foundation for any kind of conversation around AI,

0:04:18.839 --> 0:04:22.480
<v Speaker 1>because in my experience, and I'm sure you've experienced something

0:04:22.520 --> 0:04:26.000
<v Speaker 1>similar chatting with people about AI, it seems like everyone

0:04:26.080 --> 0:04:30.680
<v Speaker 1>has a different, sometimes very specific idea of what AI is.

0:04:31.279 --> 0:04:35.960
<v Speaker 1>And I'm curious, how do you describe AI to people? Yeah,

0:04:36.040 --> 0:04:39.680
<v Speaker 1>that's a great question to start with. So AI is

0:04:39.720 --> 0:04:43.520
<v Speaker 1>a form of intelligence that uses machines to do things

0:04:43.600 --> 0:04:51.039
<v Speaker 1>that traditionally required human intelligence. So it is artificial intelligence

0:04:51.040 --> 0:04:55.680
<v Speaker 1>which is created artificially by machines. So now I like

0:04:55.800 --> 0:04:59.919
<v Speaker 1>that description because it covers such a wide spectrum every

0:05:00.080 --> 0:05:04.039
<v Speaker 1>thing from sort of the science fiction approach we've all

0:05:04.480 --> 0:05:08.000
<v Speaker 1>seen about machines that seem to think like humans to

0:05:08.080 --> 0:05:10.200
<v Speaker 1>a point where they usually become the threat. I mean,

0:05:10.240 --> 0:05:12.680
<v Speaker 1>that's typically the way we look at it, which is

0:05:12.760 --> 0:05:14.360
<v Speaker 1>I'm sure going to come into play when we talk

0:05:14.360 --> 0:05:17.120
<v Speaker 1>about trustworthiness, because I'm sure a lot of people aren't

0:05:17.120 --> 0:05:22.320
<v Speaker 1>aware how AI can sometimes be a danger, but not

0:05:22.400 --> 0:05:27.680
<v Speaker 1>necessarily like sky Net from Terminator type danger. Let me

0:05:27.720 --> 0:05:31.920
<v Speaker 1>elaborate on that description than a little bit more on

0:05:32.200 --> 0:05:35.640
<v Speaker 1>you know that next level down on AI definition, Right,

0:05:36.080 --> 0:05:38.200
<v Speaker 1>you know, the way I think about it. There are

0:05:38.200 --> 0:05:43.080
<v Speaker 1>three types of AI. One is artificial narrow intelligence, which

0:05:43.160 --> 0:05:47.480
<v Speaker 1>can do a very specific, narrow task that a human

0:05:47.680 --> 0:05:52.760
<v Speaker 1>can do, like sort a bunch of photographs, Right, That's

0:05:52.760 --> 0:05:56.360
<v Speaker 1>a very narrow specific task. So that's artificial narrow intelligence.

0:05:56.720 --> 0:06:00.000
<v Speaker 1>And then there is a form of artificial general intelligence,

0:06:00.440 --> 0:06:03.239
<v Speaker 1>which is a form of AI that can do any

0:06:03.360 --> 0:06:06.680
<v Speaker 1>task that human beings can do, right, So it is

0:06:06.720 --> 0:06:09.840
<v Speaker 1>pretty much everything that a human being can do. And

0:06:09.880 --> 0:06:12.719
<v Speaker 1>then I think of a third category, which is artificial

0:06:12.920 --> 0:06:17.000
<v Speaker 1>super intelligence, which is a form of intelligence which is

0:06:17.120 --> 0:06:22.239
<v Speaker 1>smarter than all human beings combined and can do more

0:06:22.360 --> 0:06:26.920
<v Speaker 1>things that human intelligence couldn't do. So when we talk

0:06:27.000 --> 0:06:32.839
<v Speaker 1>about AI in the business world or in reality, it

0:06:33.000 --> 0:06:35.479
<v Speaker 1>is where we are with AI. It's very much in

0:06:35.520 --> 0:06:39.440
<v Speaker 1>that artificial narrow intelligence space. But when we hear a

0:06:39.480 --> 0:06:43.200
<v Speaker 1>lot about the in the media or the hype and

0:06:43.320 --> 0:06:46.880
<v Speaker 1>the fear, you know, it's talking really about that super

0:06:46.960 --> 0:06:50.160
<v Speaker 1>intelligence phase, which is a form of AI that is

0:06:50.200 --> 0:06:55.040
<v Speaker 1>smarter than all human beings combined and has more capabilities

0:06:55.080 --> 0:06:57.679
<v Speaker 1>that human intelligence. And I think there's a big gap

0:06:57.760 --> 0:07:02.200
<v Speaker 1>between reality and between where we you know, we are

0:07:02.240 --> 0:07:06.159
<v Speaker 1>anticipating things to be right and and you know. Part

0:07:06.160 --> 0:07:09.320
<v Speaker 1>of the reason is, you know, actual super intelligence is

0:07:09.360 --> 0:07:12.800
<v Speaker 1>a lot of our human imagination, which is where AI

0:07:13.120 --> 0:07:17.240
<v Speaker 1>was when I was studying years ago, right, So I

0:07:17.320 --> 0:07:19.720
<v Speaker 1>do think there is value in imagination. I do think

0:07:19.720 --> 0:07:22.200
<v Speaker 1>there is value in thinking of worst case scenarios so

0:07:22.240 --> 0:07:25.040
<v Speaker 1>that you can address it. But the reality is we

0:07:25.160 --> 0:07:28.440
<v Speaker 1>still today don't have the tools or the capabilities to

0:07:28.520 --> 0:07:32.640
<v Speaker 1>build out artificial general intelligence or super intelligence, and we

0:07:32.720 --> 0:07:36.320
<v Speaker 1>do not have that capability today. I see parallels in

0:07:36.320 --> 0:07:40.160
<v Speaker 1>this as well, like I have a very similar description

0:07:40.440 --> 0:07:44.400
<v Speaker 1>of autonomous cars, for example, like people talk about autonomous

0:07:44.480 --> 0:07:48.240
<v Speaker 1>cars like we've reached level five autonomy, when really I

0:07:48.280 --> 0:07:51.760
<v Speaker 1>would argue we're still around level two creeping into level three,

0:07:51.880 --> 0:07:54.280
<v Speaker 1>but we we are not close to level four or five.

0:07:55.080 --> 0:07:57.960
<v Speaker 1>And this is why I like having this kind of

0:07:57.960 --> 0:08:00.720
<v Speaker 1>conversation right up front, so that people kind of set

0:08:00.760 --> 0:08:06.640
<v Speaker 1>their expectations, because artificial intelligence can already do incredible things

0:08:06.640 --> 0:08:12.600
<v Speaker 1>in these very narrow, narrow uses, and I'm blown away

0:08:12.600 --> 0:08:15.480
<v Speaker 1>by it whenever I learned about that. But I do

0:08:15.640 --> 0:08:19.840
<v Speaker 1>also see the the allure and sometimes the trap of

0:08:20.360 --> 0:08:25.000
<v Speaker 1>extrapolating that beyond the narrow cases and thinking what happens

0:08:25.080 --> 0:08:29.239
<v Speaker 1>when this goes beyond that, which it could very well happen,

0:08:29.480 --> 0:08:33.600
<v Speaker 1>but we're not we're not at that stage yet. Um.

0:08:33.720 --> 0:08:37.319
<v Speaker 1>But but I think of things like, yes, I think

0:08:37.320 --> 0:08:40.600
<v Speaker 1>of things like like the image recognition like that to

0:08:40.679 --> 0:08:45.520
<v Speaker 1>me is still an amazing thing to see developed, Like

0:08:45.960 --> 0:08:48.840
<v Speaker 1>you know it is. Ever since I started covering tech,

0:08:49.360 --> 0:08:54.480
<v Speaker 1>the ability has grown so fast. Like I remember when,

0:08:54.679 --> 0:08:58.160
<v Speaker 1>at least on the consumer side, you might see something

0:08:58.200 --> 0:09:01.640
<v Speaker 1>that was like detecting a ace, not recognizing a face,

0:09:01.679 --> 0:09:05.720
<v Speaker 1>but detecting the structure that makes a face and for

0:09:05.760 --> 0:09:09.320
<v Speaker 1>a camera, And now you know that that looks like

0:09:09.360 --> 0:09:14.360
<v Speaker 1>stone age technology by comparison of what we're seeing today. Yes, Jarthan,

0:09:14.520 --> 0:09:16.880
<v Speaker 1>And you I know you've been cowering tech for a

0:09:16.920 --> 0:09:23.160
<v Speaker 1>long time. You know you've certainly seen seen the early evolution, right,

0:09:23.240 --> 0:09:26.880
<v Speaker 1>but you know, and look, when I studied computer science,

0:09:27.320 --> 0:09:31.240
<v Speaker 1>I did program assembly language programming basically using zeros and

0:09:31.400 --> 0:09:34.760
<v Speaker 1>ones right that level. And you know the languages that

0:09:34.840 --> 0:09:38.640
<v Speaker 1>I use, like Pascal and Fortran lots, you know those

0:09:38.640 --> 0:09:42.280
<v Speaker 1>don't even exist today, right, So there's a whole evolution happening.

0:09:42.600 --> 0:09:45.600
<v Speaker 1>And I do think that is a big component to

0:09:45.840 --> 0:09:49.600
<v Speaker 1>imagine the future so that we can at least go

0:09:49.760 --> 0:09:53.240
<v Speaker 1>towards take care of the risk, and focus on all

0:09:53.240 --> 0:09:56.880
<v Speaker 1>the good things that you know AI and technology can do. Right,

0:09:56.960 --> 0:10:00.000
<v Speaker 1>So imagination is a good thing, but not the fear

0:10:00.000 --> 0:10:03.080
<v Speaker 1>a part. And also I think I think what you

0:10:03.440 --> 0:10:06.800
<v Speaker 1>said kind of is a great message to anyone who's

0:10:06.840 --> 0:10:10.720
<v Speaker 1>interested in really focusing on AI. The fact that you

0:10:10.800 --> 0:10:15.040
<v Speaker 1>were working in assembly so close such a low level language,

0:10:15.520 --> 0:10:19.320
<v Speaker 1>you get you get a real familiarity with what these

0:10:19.520 --> 0:10:24.920
<v Speaker 1>machines can do and their their potential that I think, uh,

0:10:25.240 --> 0:10:27.719
<v Speaker 1>you you almost lose when you start working on high

0:10:27.840 --> 0:10:33.000
<v Speaker 1>level uh programming languages Like you you get so focused

0:10:33.080 --> 0:10:35.880
<v Speaker 1>on what the programming language lets you do. But if

0:10:35.880 --> 0:10:38.080
<v Speaker 1>you've worked out at that low level, you're like, hey, no,

0:10:38.280 --> 0:10:41.920
<v Speaker 1>I know circuits and wires, Okay, I am, I am,

0:10:41.960 --> 0:10:44.920
<v Speaker 1>I am one step away from this machine. Yeah, we

0:10:45.080 --> 0:10:47.120
<v Speaker 1>we have to realize, you know, just like you know,

0:10:47.200 --> 0:10:49.520
<v Speaker 1>when you talk about it today, will talk mostly about

0:10:49.520 --> 0:10:52.480
<v Speaker 1>the software, but the hardware is also evolving. Right. We

0:10:52.559 --> 0:10:56.160
<v Speaker 1>certainly don't have wax of those massive back from pure

0:10:56.320 --> 0:11:00.520
<v Speaker 1>systems that we had to program, right. I think there

0:11:00.640 --> 0:11:05.520
<v Speaker 1>is evolution happening in every dimension, and you know, it's

0:11:05.559 --> 0:11:08.960
<v Speaker 1>it's part of the growth of AI or any technology

0:11:09.000 --> 0:11:11.880
<v Speaker 1>if you think about it. M hmm, Well, I also

0:11:11.960 --> 0:11:14.480
<v Speaker 1>want to know what you mean when you when you

0:11:14.600 --> 0:11:18.560
<v Speaker 1>use the phrase trustworthy AI. So what is it that

0:11:18.679 --> 0:11:23.439
<v Speaker 1>makes AI trustworthy? And what what's the what's the alternative?

0:11:23.480 --> 0:11:28.880
<v Speaker 1>What is the untrustworthy side? Yeah, that's that's a great question,

0:11:28.960 --> 0:11:31.960
<v Speaker 1>and that's something that you know. As a technologist, I'm

0:11:32.160 --> 0:11:35.760
<v Speaker 1>enamored by all the cool things that AI can do

0:11:36.120 --> 0:11:39.400
<v Speaker 1>because I just focus on all the value creation. But

0:11:39.559 --> 0:11:43.120
<v Speaker 1>over the past a few years, as AI started becoming real,

0:11:43.200 --> 0:11:45.760
<v Speaker 1>I also realized that there are you know, with all

0:11:45.800 --> 0:11:49.640
<v Speaker 1>the good things that can do, there are negative consequences

0:11:49.720 --> 0:11:54.079
<v Speaker 1>to it, right, and so I put that negative consequences

0:11:54.240 --> 0:11:59.199
<v Speaker 1>in the under the bucket of untrusted untrustworthiness. Ethics is

0:11:59.240 --> 0:12:01.640
<v Speaker 1>a big composed under of it, right, Whether the AI

0:12:01.800 --> 0:12:05.800
<v Speaker 1>is fair or biased or transparent explainable, but also things

0:12:05.840 --> 0:12:09.480
<v Speaker 1>like is it compliant with local regulations, does it have

0:12:09.679 --> 0:12:12.800
<v Speaker 1>controls in place? Does it have governance in place to

0:12:12.920 --> 0:12:17.160
<v Speaker 1>continuously monitor for it going wrongue because you know, Jonathan,

0:12:17.200 --> 0:12:20.480
<v Speaker 1>today AI is mostly machine learning, so that it's learning

0:12:20.480 --> 0:12:23.400
<v Speaker 1>and evolving. It's not that era when we developed code

0:12:23.440 --> 0:12:25.800
<v Speaker 1>put it out there and the code states static and

0:12:25.840 --> 0:12:30.280
<v Speaker 1>its behavior was very predictable. With AI, the outputs can

0:12:30.360 --> 0:12:33.360
<v Speaker 1>change depending on inputs your feed and it's impossible to

0:12:33.480 --> 0:12:37.760
<v Speaker 1>trade on all possible inputs. So trustworthy for me is

0:12:37.920 --> 0:12:42.079
<v Speaker 1>you know, really, or is when you have addressed, when

0:12:42.120 --> 0:12:45.640
<v Speaker 1>you have thought about and addressed all the possible negative

0:12:45.760 --> 0:12:49.280
<v Speaker 1>things that this AI solution can cause. Well, I would

0:12:49.320 --> 0:12:51.320
<v Speaker 1>love to kind of dive into a little bit more

0:12:51.360 --> 0:12:53.760
<v Speaker 1>of that because one of the things that you said

0:12:53.760 --> 0:12:57.280
<v Speaker 1>that really resonated with me was the idea of transparency,

0:12:57.679 --> 0:13:01.480
<v Speaker 1>because I have covered this past episodes of tech stuff,

0:13:01.520 --> 0:13:05.160
<v Speaker 1>but the sort of the black box problem of creating

0:13:05.200 --> 0:13:09.280
<v Speaker 1>a system, for example, a machine learning system, and you

0:13:09.360 --> 0:13:13.719
<v Speaker 1>have this this machine that's training itself over and over

0:13:13.760 --> 0:13:16.200
<v Speaker 1>and over. Maybe it's adversarial training, maybe you actually have

0:13:16.240 --> 0:13:20.120
<v Speaker 1>two systems that are set against each other and you're training,

0:13:20.920 --> 0:13:25.320
<v Speaker 1>and the issues that can arise if you have distanced

0:13:25.360 --> 0:13:28.959
<v Speaker 1>yourself so far from what the machine is doing that

0:13:29.120 --> 0:13:33.120
<v Speaker 1>you are unable to determine the process by which it

0:13:33.760 --> 0:13:37.199
<v Speaker 1>arrives at its conclusions. And that to me is one

0:13:37.200 --> 0:13:41.120
<v Speaker 1>of those those pitfalls. Yes, but I would also challenge

0:13:41.120 --> 0:13:44.920
<v Speaker 1>it a little bit, Jonathan, because that a whole synthesis

0:13:44.960 --> 0:13:48.280
<v Speaker 1>of my book is that it depends on the use case.

0:13:48.760 --> 0:13:51.880
<v Speaker 1>It is not a one size fit soul. So depending

0:13:52.000 --> 0:13:55.920
<v Speaker 1>on where and to solve what problem are you using

0:13:55.920 --> 0:13:59.840
<v Speaker 1>that DAIR solution, it is for that organization that teams

0:14:00.080 --> 0:14:04.160
<v Speaker 1>decide if transparency is crucial. Right. If if your AI

0:14:04.280 --> 0:14:09.800
<v Speaker 1>solution is being used to for patient care in a

0:14:09.920 --> 0:14:15.840
<v Speaker 1>hospital system, then transparency is absolutely crucial, right. But if

0:14:15.880 --> 0:14:19.680
<v Speaker 1>you are using the AI solution to predict when an

0:14:19.800 --> 0:14:23.040
<v Speaker 1>X ray machine might fail, and you're able to predict

0:14:23.040 --> 0:14:26.680
<v Speaker 1>at accuracy rate that this machine is going to fail

0:14:26.680 --> 0:14:28.960
<v Speaker 1>in the next forty eight hours of call a technician,

0:14:29.760 --> 0:14:33.160
<v Speaker 1>transparency may not be as crucial, right. So I think

0:14:33.920 --> 0:14:37.360
<v Speaker 1>transparency is crucial depending on the use case. And that's

0:14:37.360 --> 0:14:40.440
<v Speaker 1>true for all the other dimensions as well, even fairness

0:14:40.440 --> 0:14:42.840
<v Speaker 1>and bias, which we hear a lot about. So it

0:14:43.000 --> 0:14:46.080
<v Speaker 1>really depends on the use case that that you're using

0:14:46.120 --> 0:14:49.760
<v Speaker 1>the I fall Hey there, Jonathan back at the home studio,

0:14:49.920 --> 0:14:52.560
<v Speaker 1>just here to say we are going to take a

0:14:52.640 --> 0:14:55.520
<v Speaker 1>quick break, but we'll be back with more with Bena Amanath,

0:14:55.640 --> 0:15:08.480
<v Speaker 1>the executive director of Deloitte AI Institute. Bias doesn't necessarily

0:15:08.560 --> 0:15:11.800
<v Speaker 1>mean negative, depending upon the use case of the technology.

0:15:12.640 --> 0:15:15.000
<v Speaker 1>In some cases you need to have a biased system

0:15:15.040 --> 0:15:18.440
<v Speaker 1>because it's specifically meant to be weighted to do one

0:15:18.480 --> 0:15:21.440
<v Speaker 1>thing versus another, and without the bias it doesn't do that.

0:15:22.400 --> 0:15:25.360
<v Speaker 1>But the way we typically hear about bias is when

0:15:25.400 --> 0:15:28.840
<v Speaker 1>it is making a negative impact, when it's something for

0:15:28.960 --> 0:15:32.720
<v Speaker 1>it's like like the facial recognition technologies. We've heard plenty

0:15:32.800 --> 0:15:36.920
<v Speaker 1>about that. So it is interesting to me, And uh,

0:15:37.080 --> 0:15:40.160
<v Speaker 1>I'm curious, like, what are what are some of the

0:15:40.320 --> 0:15:44.560
<v Speaker 1>uses of AI you're seeing in technology now that you

0:15:44.600 --> 0:15:49.560
<v Speaker 1>find really exciting. Yeah, no, I think you know, we're

0:15:49.600 --> 0:15:54.120
<v Speaker 1>still very early on in this technology evolution and there

0:15:54.160 --> 0:15:56.480
<v Speaker 1>are still so many use cases to be solved, so

0:15:56.520 --> 0:16:00.360
<v Speaker 1>many industries to take a I too right to point

0:16:00.400 --> 0:16:04.520
<v Speaker 1>about bias and its relevance. I completely agree with you that,

0:16:04.600 --> 0:16:06.600
<v Speaker 1>you know, it depends on the use case, and it

0:16:06.680 --> 0:16:09.560
<v Speaker 1>goes back to that first question we talked about, right,

0:16:09.640 --> 0:16:14.280
<v Speaker 1>how AI is really emulating human intelligence, which means that

0:16:14.440 --> 0:16:16.680
<v Speaker 1>it is going to carry over the biases of the

0:16:16.800 --> 0:16:20.640
<v Speaker 1>humans that are building it. Right, But as as a

0:16:20.680 --> 0:16:24.320
<v Speaker 1>business or as an organization who's looking to use an

0:16:24.320 --> 0:16:27.520
<v Speaker 1>air solution, who's looking to develop an a solution, they

0:16:27.560 --> 0:16:30.920
<v Speaker 1>really have to, you know, bring together the stakeholders to

0:16:31.240 --> 0:16:36.640
<v Speaker 1>discuss and decide how crucial is fairness or unbiased ness

0:16:36.680 --> 0:16:41.200
<v Speaker 1>important in this particular AI use case. And easy one

0:16:41.240 --> 0:16:44.080
<v Speaker 1>out is if it doesn't involve human data, then you

0:16:44.200 --> 0:16:46.960
<v Speaker 1>probably don't have to worry as biased as a factor

0:16:47.040 --> 0:16:50.360
<v Speaker 1>and address it. And if it does involve human data,

0:16:50.760 --> 0:16:53.800
<v Speaker 1>then again there is weightage in what right if there

0:16:53.920 --> 0:16:59.200
<v Speaker 1>is biased at in an algorithm that is providing personalized marketing,

0:17:00.120 --> 0:17:02.160
<v Speaker 1>that you know that there is a weight to it.

0:17:02.320 --> 0:17:04.160
<v Speaker 1>And if it is if there is biased in an

0:17:04.200 --> 0:17:09.359
<v Speaker 1>algorithm that is supporting law enforcement decisions, that's a higher rate, right.

0:17:09.440 --> 0:17:12.560
<v Speaker 1>And it's really about rating it, you know, weighing it

0:17:12.680 --> 0:17:16.800
<v Speaker 1>and deciding which ones are the one where biases acceptable

0:17:16.880 --> 0:17:19.639
<v Speaker 1>and you can still proceed and get value from the

0:17:19.680 --> 0:17:22.280
<v Speaker 1>AI solution, and which are the ones where it is

0:17:22.359 --> 0:17:26.359
<v Speaker 1>absolutely not acceptable and you need to stop and figure

0:17:26.400 --> 0:17:29.879
<v Speaker 1>out and alternate way to solve for that problem. It's

0:17:29.920 --> 0:17:32.600
<v Speaker 1>fascinating because it to me this is starting to sound

0:17:32.880 --> 0:17:35.879
<v Speaker 1>and I agree with you, like the machines we build

0:17:36.440 --> 0:17:39.760
<v Speaker 1>are in large part reflections upon ourselves, especially when we're

0:17:39.800 --> 0:17:44.000
<v Speaker 1>talking about coding and software. I mean obviously that's going

0:17:44.080 --> 0:17:47.040
<v Speaker 1>that's a creative process. I don't know that everybody views

0:17:47.080 --> 0:17:49.560
<v Speaker 1>it that way, but I think of it very similar

0:17:49.600 --> 0:17:53.200
<v Speaker 1>to creating any kind of creative work. It's a reflection

0:17:53.680 --> 0:17:56.600
<v Speaker 1>of your process and your you know, the things that

0:17:56.640 --> 0:18:00.399
<v Speaker 1>are important to you, the things you've prioritized. And it

0:18:00.440 --> 0:18:02.920
<v Speaker 1>makes me think of how we're in an era now

0:18:03.000 --> 0:18:06.240
<v Speaker 1>where I'm getting a little in the weeds here, but

0:18:06.240 --> 0:18:09.360
<v Speaker 1>we're in an era where we're more likely to address

0:18:09.440 --> 0:18:12.440
<v Speaker 1>things like, uh, mental health and the fact that we

0:18:12.520 --> 0:18:15.320
<v Speaker 1>need to be mindful and we need to improve ourselves.

0:18:15.359 --> 0:18:19.119
<v Speaker 1>And it's almost like taking that same approach, but applying

0:18:19.280 --> 0:18:22.280
<v Speaker 1>that sort of thinking to designing a system so that

0:18:22.680 --> 0:18:25.560
<v Speaker 1>we are being mindful to create the best system for

0:18:25.680 --> 0:18:31.400
<v Speaker 1>whatever purpose it is it's intended to address. Yeah, you've

0:18:31.400 --> 0:18:34.239
<v Speaker 1>got it exactly right. The way I think about it is,

0:18:34.280 --> 0:18:39.320
<v Speaker 1>how can we reduce the unintended consequences? Right? We know

0:18:39.480 --> 0:18:42.240
<v Speaker 1>there are going to be risk associated with it, How

0:18:42.280 --> 0:18:45.280
<v Speaker 1>are we going to have a discussion prior to putting

0:18:45.280 --> 0:18:48.199
<v Speaker 1>the solution out into the world and then you know,

0:18:48.280 --> 0:18:51.120
<v Speaker 1>see all the negative impacts. Can we have a proactive

0:18:51.119 --> 0:18:54.680
<v Speaker 1>discussion as part of your project planning meeting or your

0:18:54.760 --> 0:18:58.760
<v Speaker 1>design meeting right to proactively identify what are the ways

0:18:58.760 --> 0:19:01.080
<v Speaker 1>this could go wrong and fix it. Johnathan, you know,

0:19:01.160 --> 0:19:04.160
<v Speaker 1>the easiest example that I can give is we're living

0:19:04.160 --> 0:19:08.199
<v Speaker 1>in this very interesting era where you know, AI as

0:19:08.240 --> 0:19:11.960
<v Speaker 1>a core technology is developing and you know, there are

0:19:11.960 --> 0:19:14.439
<v Speaker 1>all these the value that you're getting from it, and

0:19:14.440 --> 0:19:17.600
<v Speaker 1>then there are all these negative things that can happen.

0:19:17.680 --> 0:19:20.080
<v Speaker 1>So think about you know, way back when when you

0:19:20.119 --> 0:19:23.440
<v Speaker 1>know the cars were first invented, right, we didn't even

0:19:23.520 --> 0:19:26.040
<v Speaker 1>have proper roads. We didn't have seed belts, we didn't

0:19:26.080 --> 0:19:29.080
<v Speaker 1>have speed limits, right, and be in that phase where

0:19:29.119 --> 0:19:31.679
<v Speaker 1>there are cars running on the road. They're taking us

0:19:31.680 --> 0:19:34.280
<v Speaker 1>from point to point be faster, so we want to

0:19:34.400 --> 0:19:37.280
<v Speaker 1>use it, but we don't have the seat belts put

0:19:37.320 --> 0:19:40.159
<v Speaker 1>in place, we don't have the speed limits set in place,

0:19:40.200 --> 0:19:43.240
<v Speaker 1>so you're going to see accidents. But we are humans.

0:19:43.359 --> 0:19:45.000
<v Speaker 1>We're going to learn from it and we're going to

0:19:45.080 --> 0:19:47.000
<v Speaker 1>come up with those speed limits. We're going to figure

0:19:47.000 --> 0:19:49.480
<v Speaker 1>out what are those card rails, and it is going

0:19:49.640 --> 0:19:52.600
<v Speaker 1>you know, we are going to you know, achieve a

0:19:52.680 --> 0:19:56.040
<v Speaker 1>point where you know, we have those guard rails in

0:19:56.040 --> 0:19:59.120
<v Speaker 1>place so that you can run with AI faster. It's

0:19:59.160 --> 0:20:02.720
<v Speaker 1>just that this interim phase is when you know, we

0:20:02.840 --> 0:20:06.240
<v Speaker 1>have to figure it out out in tandem while it's

0:20:06.520 --> 0:20:10.560
<v Speaker 1>running in the real world, causing accidents. And in some

0:20:10.640 --> 0:20:13.919
<v Speaker 1>cases that's that those accidents can be things where you

0:20:14.000 --> 0:20:16.560
<v Speaker 1>have it maybe in a test environment and you think, oh,

0:20:16.640 --> 0:20:19.240
<v Speaker 1>this isn't behaving the way I thought it was. But

0:20:19.480 --> 0:20:21.760
<v Speaker 1>you know, thank goodness, it hasn't been deployed out in

0:20:21.800 --> 0:20:26.240
<v Speaker 1>the real world for or within your company's UH processes,

0:20:26.240 --> 0:20:28.479
<v Speaker 1>so you think, oh, well, it didn't wipe out all

0:20:28.480 --> 0:20:31.879
<v Speaker 1>of our revenue because it's in a test environment. UH.

0:20:31.920 --> 0:20:34.440
<v Speaker 1>And in other cases, I see I see some companies.

0:20:34.480 --> 0:20:36.600
<v Speaker 1>I'm not gonna name names, Bina, I'm not gonna put

0:20:36.640 --> 0:20:39.760
<v Speaker 1>anyone on blast here, but I have seen some companies

0:20:40.200 --> 0:20:43.439
<v Speaker 1>that have taken that kind of idea and applied it

0:20:43.560 --> 0:20:48.080
<v Speaker 1>in UH specific deployments of technology where there can have

0:20:48.160 --> 0:20:52.440
<v Speaker 1>some some real world negative consequences to end users. UM.

0:20:52.760 --> 0:20:57.080
<v Speaker 1>And that to me has always a concern I find, yeah,

0:20:57.200 --> 0:21:00.280
<v Speaker 1>I find that I find it hits me wrong. Yes,

0:21:00.400 --> 0:21:04.040
<v Speaker 1>And that's the reality of how we've evolved as a

0:21:04.160 --> 0:21:07.359
<v Speaker 1>technology in their technology space. It's a bunch of you know,

0:21:07.440 --> 0:21:12.200
<v Speaker 1>technologists coming together and building these cool, new shiny technologists. Look.

0:21:12.680 --> 0:21:14.879
<v Speaker 1>You know, as I said, I am a technologist in

0:21:14.960 --> 0:21:18.159
<v Speaker 1>my DNA my training, and it's very easy to just

0:21:18.200 --> 0:21:20.760
<v Speaker 1>focus on all the good things that can do. But

0:21:20.920 --> 0:21:24.800
<v Speaker 1>with AI, now that realization has hit, you need other

0:21:25.760 --> 0:21:27.720
<v Speaker 1>you know, skill sets at the table, whether it is

0:21:27.720 --> 0:21:32.320
<v Speaker 1>a social site, is philosophers, legal and compliance to help

0:21:32.440 --> 0:21:35.199
<v Speaker 1>us figure out those seedbells and the you know, the

0:21:35.240 --> 0:21:39.439
<v Speaker 1>speed the lanes, you know, because technologies by themselves cannot

0:21:39.520 --> 0:21:42.120
<v Speaker 1>do it. So you'll see more of the discussions coming

0:21:42.160 --> 0:21:44.720
<v Speaker 1>around ethics and which is resulting in new roles and

0:21:44.800 --> 0:21:50.200
<v Speaker 1>new jobs, which becomes core and part of your engineering process. Right,

0:21:50.240 --> 0:21:53.600
<v Speaker 1>So that scope of who is involved in designing and

0:21:53.640 --> 0:21:57.920
<v Speaker 1>developing AI is definitely increasing. And the other big part,

0:21:58.080 --> 0:22:00.399
<v Speaker 1>you know, and this has been a challenge since I

0:22:00.440 --> 0:22:02.639
<v Speaker 1>started in tech. You know, there's a lack of diversity

0:22:02.680 --> 0:22:06.800
<v Speaker 1>in tech. It's a reality, right, But unfortunately, because AI

0:22:06.880 --> 0:22:09.760
<v Speaker 1>is so closely tied to human intelligence, if you don't

0:22:09.800 --> 0:22:13.679
<v Speaker 1>have enough diversity from you know, not only from a gender,

0:22:13.800 --> 0:22:17.440
<v Speaker 1>race at necessity perspective, but even a diversity of thought, right,

0:22:17.880 --> 0:22:21.119
<v Speaker 1>you're the AI solution you built is not going to

0:22:21.200 --> 0:22:24.480
<v Speaker 1>be as robust as it could be if you had

0:22:24.520 --> 0:22:27.560
<v Speaker 1>a diverse team at the table. Right, you've probably heard

0:22:27.600 --> 0:22:31.480
<v Speaker 1>of that classic example of you know, the robotic vacuums, right,

0:22:31.560 --> 0:22:33.720
<v Speaker 1>how it was designed and now it was built out.

0:22:34.200 --> 0:22:37.200
<v Speaker 1>And then in the Eastern cultures it's normal to sleep

0:22:37.280 --> 0:22:41.480
<v Speaker 1>on the floor and it sucked up human somebody who's

0:22:41.480 --> 0:22:44.040
<v Speaker 1>sleeping their hair because it was never trade on it.

0:22:44.040 --> 0:22:46.879
<v Speaker 1>It didn't come you know, it didn't come to the discussion,

0:22:47.200 --> 0:22:49.880
<v Speaker 1>and it was being designed because nobody was there from

0:22:49.920 --> 0:22:53.879
<v Speaker 1>that culture. Right. So I think, you know, the realization

0:22:53.920 --> 0:22:56.080
<v Speaker 1>that you need more diversity at the table, you need

0:22:56.119 --> 0:22:59.080
<v Speaker 1>more controls in place. It's all coming to the forefront.

0:22:59.160 --> 0:23:03.000
<v Speaker 1>I definitely see companies addressing it. But the the DNA

0:23:03.119 --> 0:23:05.200
<v Speaker 1>will now has been oh, look at all the cool

0:23:05.240 --> 0:23:08.200
<v Speaker 1>things this technology can do, let's go put it out right.

0:23:08.480 --> 0:23:11.520
<v Speaker 1>But I do think, you know, companies are getting mindful

0:23:11.560 --> 0:23:17.400
<v Speaker 1>about it and hopefully we'll reduce the number of unintended consequences. Yeah.

0:23:17.480 --> 0:23:22.280
<v Speaker 1>I see the same thing reflected in the open source community,

0:23:22.440 --> 0:23:27.160
<v Speaker 1>where you have an open source approach to developing software,

0:23:27.800 --> 0:23:32.760
<v Speaker 1>and because it's open and and anyone interested and capable

0:23:33.320 --> 0:23:40.000
<v Speaker 1>can contribute ideas get tested, very quickly. New new perspectives

0:23:40.000 --> 0:23:43.600
<v Speaker 1>get incorporated very quickly. Things that are working stick around,

0:23:43.640 --> 0:23:47.520
<v Speaker 1>things that don't work get improved. And the way I've

0:23:47.520 --> 0:23:50.840
<v Speaker 1>described it to other people is, if you have a

0:23:50.880 --> 0:23:54.440
<v Speaker 1>closed off garden that you're working on, you're only as

0:23:54.480 --> 0:23:57.920
<v Speaker 1>good as the smart people who happen to work for you.

0:23:58.400 --> 0:24:00.439
<v Speaker 1>And if you go with this other approach where you

0:24:00.680 --> 0:24:04.439
<v Speaker 1>purposefully open it up, which is like the biggest version

0:24:04.480 --> 0:24:06.959
<v Speaker 1>of let's let's try and get as much diversity of

0:24:07.000 --> 0:24:10.600
<v Speaker 1>thought in here as possible. Uh, you don't have that

0:24:10.680 --> 0:24:13.520
<v Speaker 1>limitation because you've You've just said, well, now the world

0:24:13.760 --> 0:24:16.199
<v Speaker 1>is I mean it's not the whole world, but but

0:24:16.280 --> 0:24:19.800
<v Speaker 1>effectively the world. The world can contribute if if they,

0:24:19.880 --> 0:24:24.320
<v Speaker 1>if they wish, and uh agree, I think having that

0:24:24.400 --> 0:24:29.560
<v Speaker 1>diversity is absolutely key to creating solutions that work for

0:24:29.640 --> 0:24:34.320
<v Speaker 1>as many people and as many potential uses of that

0:24:34.359 --> 0:24:39.640
<v Speaker 1>technology as possible. I being a a a white man

0:24:39.840 --> 0:24:44.600
<v Speaker 1>in the United States, I am I am essentially the

0:24:44.760 --> 0:24:48.120
<v Speaker 1>catered to audience for a lot of tech, and so

0:24:48.800 --> 0:24:52.440
<v Speaker 1>I've seen how things that were made to work really

0:24:52.440 --> 0:24:55.480
<v Speaker 1>well for me do not work for some other people.

0:24:55.520 --> 0:24:58.639
<v Speaker 1>And that's such a tiny little microcosm when we're looking

0:24:58.680 --> 0:25:01.320
<v Speaker 1>at you know, the GREA and scope of tech which

0:25:01.359 --> 0:25:05.560
<v Speaker 1>goes so far beyond just consumer electronics. UM I absolutely

0:25:05.600 --> 0:25:10.560
<v Speaker 1>agree that that diversity is is required if we're going

0:25:10.640 --> 0:25:14.879
<v Speaker 1>to have a i that is truly trustworthy. Yeah, exactly,

0:25:15.040 --> 0:25:17.280
<v Speaker 1>And you know, and then but there it's not never.

0:25:17.680 --> 0:25:21.879
<v Speaker 1>It's never as straightforward as we tend to simplify it

0:25:21.920 --> 0:25:26.199
<v Speaker 1>down to, right, like when we talk about explainability. There

0:25:26.240 --> 0:25:30.040
<v Speaker 1>there are real challenges and those are real business challenges

0:25:30.480 --> 0:25:33.000
<v Speaker 1>on even when you go down the open source route right,

0:25:33.040 --> 0:25:34.879
<v Speaker 1>a lot of time, if you go too much on

0:25:34.960 --> 0:25:38.919
<v Speaker 1>the explainableitypath, you know, you you have to still share

0:25:39.040 --> 0:25:42.600
<v Speaker 1>data and algorithms and those are strategic assets and it

0:25:42.680 --> 0:25:46.439
<v Speaker 1>can result in compromising your company's i P. Right, it

0:25:46.560 --> 0:25:50.760
<v Speaker 1>can result in you know, security hacks because the more

0:25:50.880 --> 0:25:54.600
<v Speaker 1>explainable you make it, it is more susceptible to manipulation

0:25:54.720 --> 0:25:58.720
<v Speaker 1>if it's functionality is fully understood, the privacy aspect of it,

0:25:58.960 --> 0:26:03.200
<v Speaker 1>prioritizing playability and you know, how do you make sure

0:26:03.320 --> 0:26:07.200
<v Speaker 1>you hit a balance of why you are making sure

0:26:07.240 --> 0:26:10.560
<v Speaker 1>you're mitigating the risk but at the same time protect

0:26:11.080 --> 0:26:15.840
<v Speaker 1>your organizational i P. That's that's a that's a solution.

0:26:15.960 --> 0:26:18.760
<v Speaker 1>That's that there is no one single answer. It is

0:26:19.119 --> 0:26:23.080
<v Speaker 1>for the stakeholders to come together and discuss it and

0:26:23.200 --> 0:26:26.320
<v Speaker 1>identify were that balances, because it's going to be different

0:26:26.400 --> 0:26:29.360
<v Speaker 1>depending on your business. It seems to me like you're

0:26:29.359 --> 0:26:31.640
<v Speaker 1>saying the real world is a complicated place and there's

0:26:31.640 --> 0:26:35.000
<v Speaker 1>a lot of different shades of complexity to it, and

0:26:35.000 --> 0:26:39.040
<v Speaker 1>that I can't just simply uh summarize it in a

0:26:39.240 --> 0:26:43.520
<v Speaker 1>black and white approach, which I greatly appreciate, uh, and

0:26:43.560 --> 0:26:45.520
<v Speaker 1>that that's interesting to me too. I'm glad to have

0:26:45.600 --> 0:26:48.560
<v Speaker 1>that perspective because again, like as a as a communicator

0:26:48.600 --> 0:26:52.600
<v Speaker 1>for tech, uh, I know that I too fall into

0:26:52.680 --> 0:26:56.960
<v Speaker 1>the same sort of pitfalls of oversimplifying for the purposes

0:26:57.000 --> 0:27:01.439
<v Speaker 1>of trying to get a concept across, because to really

0:27:01.520 --> 0:27:05.000
<v Speaker 1>dive into it, you start to you start to feel

0:27:05.000 --> 0:27:07.000
<v Speaker 1>like they're there are so many threads that you can't

0:27:07.000 --> 0:27:09.800
<v Speaker 1>see the rope and that or you can't see the

0:27:09.800 --> 0:27:13.000
<v Speaker 1>forest for the trees if you prefer. But but that's

0:27:13.040 --> 0:27:17.080
<v Speaker 1>that's very important to remember, and I think it is

0:27:17.119 --> 0:27:21.720
<v Speaker 1>a great reminder that again, like we said at the top,

0:27:21.800 --> 0:27:26.040
<v Speaker 1>that the use for this technology kind of defines the

0:27:26.119 --> 0:27:28.960
<v Speaker 1>approach that you need to take in order to make

0:27:29.000 --> 0:27:32.520
<v Speaker 1>certain that you're you're getting the result that you want.

0:27:33.240 --> 0:27:37.280
<v Speaker 1>UM from a really high level, can you kind of

0:27:37.320 --> 0:27:41.280
<v Speaker 1>talk about your concept of what what it is? This

0:27:41.359 --> 0:27:44.280
<v Speaker 1>is almost a trick question because there's so many different variations,

0:27:44.320 --> 0:27:48.280
<v Speaker 1>but what what what an organization's process would be when

0:27:48.320 --> 0:27:55.160
<v Speaker 1>considering to implement AI solutions like high high level approach. Yes,

0:27:55.560 --> 0:27:59.800
<v Speaker 1>Historically it's always been you know, how can we use

0:27:59.840 --> 0:28:02.600
<v Speaker 1>ARE to solve this business problem? And what's the r

0:28:02.640 --> 0:28:04.840
<v Speaker 1>O I what you know? How much profits are we

0:28:04.880 --> 0:28:07.200
<v Speaker 1>going to increase by doing this? Or how much costs

0:28:07.200 --> 0:28:09.760
<v Speaker 1>are we going to save by doing this? Trust me,

0:28:09.840 --> 0:28:12.159
<v Speaker 1>I've done this project and you know that's how you

0:28:12.200 --> 0:28:14.800
<v Speaker 1>know every conversation starts because we want to make use

0:28:14.880 --> 0:28:18.480
<v Speaker 1>technology to drive more business value, right, whether it is

0:28:18.480 --> 0:28:21.800
<v Speaker 1>through customer engagement, optimizing our existing process and so on.

0:28:22.200 --> 0:28:26.280
<v Speaker 1>I think the discussion that that if you are serious

0:28:26.359 --> 0:28:30.040
<v Speaker 1>about getting making your AI trustworthy, the discussion that needs

0:28:30.080 --> 0:28:33.960
<v Speaker 1>to happen upfront is defining what does trustworthy I mean

0:28:34.520 --> 0:28:39.240
<v Speaker 1>for for my organization? Right? And uh and it could

0:28:39.240 --> 0:28:42.240
<v Speaker 1>be different depending on the organization, It could be different

0:28:42.240 --> 0:28:45.959
<v Speaker 1>depending on the use case. But having those high level principles,

0:28:46.000 --> 0:28:48.080
<v Speaker 1>and there are plenty of principles out there, there are

0:28:48.080 --> 0:28:51.560
<v Speaker 1>plenty of frameworks out there, but I think every organization

0:28:51.600 --> 0:28:54.680
<v Speaker 1>needs to think about what are the key pillars that

0:28:54.760 --> 0:28:56.720
<v Speaker 1>they agree upon and that they would never want to

0:28:56.800 --> 0:29:00.320
<v Speaker 1>void it right. And once you have those, then next

0:29:00.320 --> 0:29:03.480
<v Speaker 1>step is to decide to make sure every employee within

0:29:03.520 --> 0:29:07.280
<v Speaker 1>your organization understands it. Because it's not just your I

0:29:07.400 --> 0:29:09.760
<v Speaker 1>T team, It's not just the engineers of the data

0:29:09.800 --> 0:29:15.680
<v Speaker 1>scientists who need to understand ethics. It's that marketing marketing

0:29:15.720 --> 0:29:21.200
<v Speaker 1>account person who is looking at using an AI solution,

0:29:21.480 --> 0:29:24.480
<v Speaker 1>buying it from a vendor to use it within your company.

0:29:24.520 --> 0:29:26.960
<v Speaker 1>They need to make sure that they are asking the

0:29:27.080 --> 0:29:30.640
<v Speaker 1>questions which ensure trustworthiness and do they do is the

0:29:30.680 --> 0:29:33.800
<v Speaker 1>software they're buying, has it been tested for fairness? What

0:29:33.880 --> 0:29:37.640
<v Speaker 1>was it tested for? So every employee within the organization

0:29:37.760 --> 0:29:41.600
<v Speaker 1>needs to understand what distrustworthy I mean for my company

0:29:41.640 --> 0:29:45.080
<v Speaker 1>and how do I how do I make it, how

0:29:45.080 --> 0:29:47.840
<v Speaker 1>do I use it in my role? So role specific training.

0:29:48.520 --> 0:29:50.920
<v Speaker 1>And then the other crucial factor to decide, and we've

0:29:50.960 --> 0:29:53.600
<v Speaker 1>see variations of it in the industry, is you know

0:29:53.600 --> 0:29:56.440
<v Speaker 1>whether it is getting a cheap AI Ethics officer or

0:29:56.480 --> 0:30:00.200
<v Speaker 1>setting up an AI thinks advisory board right, making sure

0:30:00.280 --> 0:30:03.760
<v Speaker 1>that there is somebody who is responsible to keep you know,

0:30:03.840 --> 0:30:07.880
<v Speaker 1>to keep this moing within the organization is super important.

0:30:07.920 --> 0:30:10.640
<v Speaker 1>That's more from a people perspective. And then the last

0:30:10.680 --> 0:30:14.040
<v Speaker 1>thing is really looking at your existing processes. I don't

0:30:14.120 --> 0:30:17.120
<v Speaker 1>think you need to completely come up with new processes

0:30:17.160 --> 0:30:21.760
<v Speaker 1>or new controls, but just adding in an trustworthy check

0:30:21.920 --> 0:30:26.480
<v Speaker 1>in your existing engineering processes or in your existing development

0:30:26.520 --> 0:30:30.200
<v Speaker 1>process or your procurement process to make sure you're checking

0:30:30.360 --> 0:30:33.720
<v Speaker 1>for the trustworthiness of any AI that tool that you

0:30:33.840 --> 0:30:37.040
<v Speaker 1>buy or that you build, you know, having in addition

0:30:37.040 --> 0:30:40.480
<v Speaker 1>to the r O, I ask Sen spent ten percent

0:30:40.680 --> 0:30:43.640
<v Speaker 1>of your time to brainstorm on what are the ways

0:30:43.640 --> 0:30:46.720
<v Speaker 1>this could go wrong? Right? And capture it and when

0:30:46.720 --> 0:30:50.720
<v Speaker 1>you build that technology, put those guard rails in place.

0:30:50.800 --> 0:30:54.800
<v Speaker 1>Now it is guaranteed you It is impossible to identify

0:30:55.000 --> 0:30:57.640
<v Speaker 1>all the possible ways it could go wrong, but even

0:30:57.680 --> 0:31:00.920
<v Speaker 1>if you get you know the ways it could go wrong,

0:31:01.000 --> 0:31:03.640
<v Speaker 1>it is better than not thinking about it and not

0:31:03.720 --> 0:31:07.280
<v Speaker 1>addressing it. So that is a very comprehensive way you

0:31:07.360 --> 0:31:09.959
<v Speaker 1>can do it. But it is all easy. It fits

0:31:09.960 --> 0:31:14.720
<v Speaker 1>in with the existing trainings and processes that you already

0:31:14.800 --> 0:31:19.200
<v Speaker 1>have in your business. Right. I gotta say, like as

0:31:19.280 --> 0:31:22.280
<v Speaker 1>as someone who is a technologist and uh and coming

0:31:22.320 --> 0:31:25.960
<v Speaker 1>at this from that angle, that was such a human

0:31:26.040 --> 0:31:29.719
<v Speaker 1>centric kind of answer. I really appreciate that. I've had

0:31:29.760 --> 0:31:34.440
<v Speaker 1>a lot of discussions with various leadership around different companies

0:31:34.760 --> 0:31:38.640
<v Speaker 1>and this idea of of having that explanation and getting

0:31:38.680 --> 0:31:42.360
<v Speaker 1>buy in from different departments so that everyone's on the

0:31:42.400 --> 0:31:45.800
<v Speaker 1>same page and they have an understanding of the purpose

0:31:45.840 --> 0:31:48.280
<v Speaker 1>of a tool, how it's going to be implemented, what

0:31:48.440 --> 0:31:51.040
<v Speaker 1>we expect to get out of it. Uh. That's actually

0:31:51.160 --> 0:31:54.440
<v Speaker 1>crucial for anything, whether it's a I or not. But

0:31:55.160 --> 0:31:58.040
<v Speaker 1>because I've seen so many examples of companies where you

0:31:58.080 --> 0:32:01.400
<v Speaker 1>have one department who's like a business development team wanted

0:32:01.480 --> 0:32:03.479
<v Speaker 1>us to put this in and I don't understand why.

0:32:03.520 --> 0:32:07.080
<v Speaker 1>And if they don't understand why, then you don't get

0:32:07.120 --> 0:32:09.040
<v Speaker 1>as good output on the other end of it. I

0:32:09.040 --> 0:32:12.160
<v Speaker 1>think making that part of the conversation just as much

0:32:12.200 --> 0:32:15.920
<v Speaker 1>as you know, determining the approach to get a trustworthy AI,

0:32:16.000 --> 0:32:18.760
<v Speaker 1>I think that's absolutely crucial. Yes, And you know, a

0:32:18.760 --> 0:32:22.080
<v Speaker 1>lot of times we think it's a technology problem to fix,

0:32:22.320 --> 0:32:24.680
<v Speaker 1>right it's it's a technology. You know, to build trustworthy

0:32:24.720 --> 0:32:26.960
<v Speaker 1>air you need to you know, it's a technology problem.

0:32:27.000 --> 0:32:30.160
<v Speaker 1>It's your data scientists and engineers, which you think about it,

0:32:30.200 --> 0:32:33.280
<v Speaker 1>but that's that's not the case, right, It's a it's

0:32:33.320 --> 0:32:36.200
<v Speaker 1>the entire group that needs to come together. And the

0:32:36.360 --> 0:32:39.080
<v Speaker 1>risk is not just from a technology perspective. It's a

0:32:39.120 --> 0:32:45.720
<v Speaker 1>brand and reputation rusk. There's financial consequences, there's customer satisfaction consequences,

0:32:46.080 --> 0:32:50.600
<v Speaker 1>there is so many other risks associated with if your

0:32:50.680 --> 0:32:54.920
<v Speaker 1>AI is not trustworthy. Bina and I have a little

0:32:54.920 --> 0:32:57.240
<v Speaker 1>bit more to talk about with AI, but before we

0:32:57.280 --> 0:33:07.360
<v Speaker 1>get to that, let's take another quick break. I remember

0:33:07.440 --> 0:33:11.200
<v Speaker 1>covering that over in the European Union there were various

0:33:11.600 --> 0:33:15.400
<v Speaker 1>departments that were even talking about concepts that again are

0:33:15.520 --> 0:33:18.240
<v Speaker 1>let science fiction far off concept, but even the concept

0:33:18.280 --> 0:33:24.800
<v Speaker 1>of of granting personhood toward sufficiently advanced AI for the

0:33:24.840 --> 0:33:29.360
<v Speaker 1>purposes of figuring out accountability and responsibility for when something

0:33:29.400 --> 0:33:33.880
<v Speaker 1>goes wrong, who gets held accountable when the AI doesn't

0:33:33.920 --> 0:33:37.560
<v Speaker 1>work right? What's your take on that. I think, you know,

0:33:37.760 --> 0:33:40.560
<v Speaker 1>we might reach at that at some point, but in

0:33:40.600 --> 0:33:44.000
<v Speaker 1>the interim till we don't have that kind of you know,

0:33:44.400 --> 0:33:48.000
<v Speaker 1>rules or laws. I think it's absolutely you know, one

0:33:48.040 --> 0:33:53.000
<v Speaker 1>of the components dimensions of trustworthy A is defining accountability upfront,

0:33:53.400 --> 0:33:57.080
<v Speaker 1>meaning if the AI goes wrong, who is accountable for it?

0:33:57.080 --> 0:33:59.160
<v Speaker 1>Who's going to phase the Senate hearing? Who's going to

0:33:59.200 --> 0:34:02.040
<v Speaker 1>pay the fine? Is it the data scientists to milit it,

0:34:02.200 --> 0:34:05.640
<v Speaker 1>is it the c I O who approved the project?

0:34:05.800 --> 0:34:08.879
<v Speaker 1>Is it the CEO or is it a board member? Right? So,

0:34:09.360 --> 0:34:12.040
<v Speaker 1>and the good news with that one, you know, talking

0:34:12.080 --> 0:34:17.120
<v Speaker 1>about accountability upfront makes everybody proactively think about for the

0:34:17.120 --> 0:34:19.040
<v Speaker 1>ways it could go wrong, because you don't want to

0:34:19.080 --> 0:34:22.120
<v Speaker 1>put your name on something that might go wrong and

0:34:22.160 --> 0:34:25.040
<v Speaker 1>you have not thought about it. So until we get

0:34:25.120 --> 0:34:29.480
<v Speaker 1>to that, you know, machine citizens citizen rights level, I

0:34:29.520 --> 0:34:33.360
<v Speaker 1>think you know, even today there is a dimension of

0:34:33.400 --> 0:34:38.000
<v Speaker 1>trustworthiness which is really around defining putting in a name

0:34:38.120 --> 0:34:42.840
<v Speaker 1>for who is accountable when your AI goes wrong. I

0:34:42.920 --> 0:34:45.040
<v Speaker 1>agree that that's important. I have seen some of those

0:34:45.040 --> 0:34:48.919
<v Speaker 1>Senate hearings with various UH tech people sitting in the sea,

0:34:49.320 --> 0:34:51.000
<v Speaker 1>and I know that if I were in one of

0:34:51.040 --> 0:34:53.360
<v Speaker 1>these conversations, I would not want to be that person.

0:34:53.760 --> 0:34:57.080
<v Speaker 1>And making sure we specifically define who that person is

0:34:57.120 --> 0:34:59.200
<v Speaker 1>and that it's not me would be top of my

0:34:59.280 --> 0:35:06.239
<v Speaker 1>priority life. Well, I'm also curious then. Uh. So we've

0:35:06.239 --> 0:35:10.000
<v Speaker 1>seen in a similar sense some movement on things like

0:35:11.239 --> 0:35:15.160
<v Speaker 1>autonomous cars. Uh. In a similar note, I'll talking about accountability,

0:35:15.160 --> 0:35:20.840
<v Speaker 1>where we're starting to see more governments try and consider

0:35:20.920 --> 0:35:24.840
<v Speaker 1>who is accountable for any accidents that might have happened

0:35:24.920 --> 0:35:30.680
<v Speaker 1>under cars autonomous or semi autonomous operation. Obviously that's been

0:35:30.760 --> 0:35:33.760
<v Speaker 1>a big point of discussion here in the United States,

0:35:34.680 --> 0:35:39.239
<v Speaker 1>and uh, this is one of those things. How how

0:35:39.280 --> 0:35:43.799
<v Speaker 1>how closely tied do you think do technology experts need

0:35:43.840 --> 0:35:49.200
<v Speaker 1>to be with say politicians who may not have the

0:35:49.280 --> 0:35:54.160
<v Speaker 1>insight into tech, but yet are also responsible for creating

0:35:54.320 --> 0:35:58.400
<v Speaker 1>and enacting policy that's going to have an effect on tech.

0:35:58.520 --> 0:36:04.640
<v Speaker 1>Is do you see there being more cross talk? Yeah,

0:36:04.680 --> 0:36:08.400
<v Speaker 1>you know, unlike the car example and the seed belt

0:36:08.440 --> 0:36:12.239
<v Speaker 1>and speed limit example. You know, AI does need an

0:36:12.320 --> 0:36:17.000
<v Speaker 1>understanding of technology so to come up with those speed limits.

0:36:17.719 --> 0:36:20.880
<v Speaker 1>It is so, you know, and we've honestly entered that

0:36:21.000 --> 0:36:24.959
<v Speaker 1>era where collaboration is king, right. We have to make

0:36:25.000 --> 0:36:30.560
<v Speaker 1>sure that regulators and technologies, uh, policymakers, they have collaborating

0:36:30.719 --> 0:36:33.239
<v Speaker 1>and each one is learning from the other. To come

0:36:33.320 --> 0:36:38.480
<v Speaker 1>up with the best possible guard rails or regulations or laws,

0:36:38.560 --> 0:36:42.279
<v Speaker 1>because this is not something that can be done in isolation,

0:36:42.320 --> 0:36:46.279
<v Speaker 1>and like that auto speed limit example. So I think

0:36:46.320 --> 0:36:49.040
<v Speaker 1>we're going to see more whether it is an entities

0:36:49.120 --> 0:36:52.480
<v Speaker 1>being set up who will drive this collaboration, but there

0:36:52.600 --> 0:36:59.720
<v Speaker 1>is definitely, you know, across the globe technologists being pulled together,

0:36:59.719 --> 0:37:04.440
<v Speaker 1>whether as an advisory committee or a council. That is

0:37:04.719 --> 0:37:08.200
<v Speaker 1>happening now, and you know, I do think we will

0:37:08.239 --> 0:37:12.359
<v Speaker 1>start seeing results of that collaboration coming out sooner rather

0:37:12.400 --> 0:37:15.520
<v Speaker 1>than later. I think I also believe that just like

0:37:15.560 --> 0:37:19.000
<v Speaker 1>I was talking about every organization should train all their employees,

0:37:19.440 --> 0:37:24.239
<v Speaker 1>I think every everybody who is involved in the regulation

0:37:24.360 --> 0:37:29.040
<v Speaker 1>making process should have a basic understanding of AI, level

0:37:29.080 --> 0:37:32.239
<v Speaker 1>of AI fluency, or you know, an understanding of what

0:37:32.280 --> 0:37:34.680
<v Speaker 1>does machine learning really mean, what can it do, what

0:37:34.800 --> 0:37:37.000
<v Speaker 1>can it not do? So I call it the AI

0:37:37.120 --> 0:37:40.640
<v Speaker 1>literacy training, right, So I think it's that's like ground

0:37:40.680 --> 0:37:45.000
<v Speaker 1>stakes to drive a productive collaboration. But I think this

0:37:45.160 --> 0:37:47.360
<v Speaker 1>is the time for people like you and me, Jonathan,

0:37:47.400 --> 0:37:50.839
<v Speaker 1>to really step up and make sure that we're collaborating

0:37:51.080 --> 0:37:57.640
<v Speaker 1>closely so that that it's informed and informed and relevant

0:37:57.880 --> 0:38:02.400
<v Speaker 1>regulation or relevant policy that's put together. I think relevance

0:38:02.520 --> 0:38:06.600
<v Speaker 1>is is absolutely the right word to use. UH. Again,

0:38:06.640 --> 0:38:09.040
<v Speaker 1>I'm not putting anyone on blast, but there have been

0:38:09.120 --> 0:38:12.520
<v Speaker 1>plenty of stories of people, whether they are in the

0:38:12.600 --> 0:38:18.399
<v Speaker 1>regulatory field or general politics, where their level of tech

0:38:18.480 --> 0:38:24.000
<v Speaker 1>savvy is probably not even measurable based upon some of

0:38:24.000 --> 0:38:26.920
<v Speaker 1>the things we've seen, and that is that is terrifying

0:38:27.040 --> 0:38:33.440
<v Speaker 1>when you realize the reach and the effect of technology

0:38:33.480 --> 0:38:37.080
<v Speaker 1>and how if you have a misunderstanding of it, you

0:38:37.120 --> 0:38:40.440
<v Speaker 1>can tackle something that's not really a problem, but you've

0:38:40.560 --> 0:38:43.960
<v Speaker 1>built it up as if it were while completely missing

0:38:44.440 --> 0:38:47.520
<v Speaker 1>things that we absolutely need to pay closer attention to.

0:38:47.680 --> 0:38:51.560
<v Speaker 1>So I I do try to to make literacy one

0:38:51.600 --> 0:38:54.719
<v Speaker 1>of those things that I push for and hopefully I

0:38:54.800 --> 0:39:00.719
<v Speaker 1>succeed more often than I fail. Yeah, it's we live

0:39:00.840 --> 0:39:04.319
<v Speaker 1>in this era now that you know, at least in

0:39:04.440 --> 0:39:09.680
<v Speaker 1>the UH. In the corporate world, right, we're seeing more

0:39:09.719 --> 0:39:15.320
<v Speaker 1>and more boards getting more technology savvy. Leaders are leaders

0:39:15.360 --> 0:39:19.480
<v Speaker 1>who understand technology so that because every company uses technology,

0:39:19.560 --> 0:39:23.279
<v Speaker 1>uses AI no matter which industry they're in, right, So

0:39:23.320 --> 0:39:27.000
<v Speaker 1>we're seeing that composition of boards changing, right, And I

0:39:27.000 --> 0:39:29.960
<v Speaker 1>don't think we're very far from the time when you know,

0:39:30.400 --> 0:39:34.640
<v Speaker 1>having a basic AI or technology understanding will be almost

0:39:34.640 --> 0:39:38.640
<v Speaker 1>a prerequisite. Right Again, as I said, we're living in

0:39:38.680 --> 0:39:42.080
<v Speaker 1>this interim crazy phase where there's a lot of things

0:39:42.120 --> 0:39:45.359
<v Speaker 1>happening and we don't necessarily have all the foundations set up.

0:39:45.719 --> 0:39:48.680
<v Speaker 1>The exciting news is for our generation, Jonathan, this is

0:39:48.680 --> 0:39:52.400
<v Speaker 1>our opportunity. Right the work we do today is going

0:39:52.480 --> 0:39:56.560
<v Speaker 1>to be setting the foundation for future generations. So I think, uh,

0:39:56.840 --> 0:39:59.640
<v Speaker 1>you know, having that basic AI literacy, No, it's not

0:39:59.760 --> 0:40:03.319
<v Speaker 1>set up, but you know, we we now understand that,

0:40:03.560 --> 0:40:07.400
<v Speaker 1>you know, everybody who is involved in policymaking our regulations

0:40:07.480 --> 0:40:10.640
<v Speaker 1>need to have that basic understanding. So let's make sure

0:40:10.800 --> 0:40:14.720
<v Speaker 1>that you know they have that. That's great, it's it's

0:40:14.760 --> 0:40:17.239
<v Speaker 1>it's looking at something that I have defined as a

0:40:17.239 --> 0:40:21.080
<v Speaker 1>problem and you have defined as an opportunity, which I

0:40:21.120 --> 0:40:24.399
<v Speaker 1>needed to hear honestly, because that's the kind of optimism

0:40:24.480 --> 0:40:29.520
<v Speaker 1>that I find really motivating. Been a thank you so

0:40:29.640 --> 0:40:33.680
<v Speaker 1>much for being on the show. Your book Trustworthy AI.

0:40:34.080 --> 0:40:36.319
<v Speaker 1>I have a copy coming to me. I have not

0:40:36.480 --> 0:40:39.160
<v Speaker 1>yet been able to read it. I am so eager

0:40:39.200 --> 0:40:42.120
<v Speaker 1>to go cover to cover on this because just this

0:40:42.120 --> 0:40:45.880
<v Speaker 1>this conversation has really energized me, and um, you know,

0:40:46.280 --> 0:40:48.719
<v Speaker 1>when you have a podcast about tech and you've done

0:40:48.719 --> 0:40:52.439
<v Speaker 1>more than sevent episodes, sometimes you feel like I've said

0:40:52.480 --> 0:40:54.400
<v Speaker 1>everything there is to say about that, and then I

0:40:54.400 --> 0:40:56.840
<v Speaker 1>have a conversation like this and I realized, this is

0:40:56.840 --> 0:40:59.520
<v Speaker 1>an Iceberg situation and I've just touched the very tip

0:40:59.560 --> 0:41:03.759
<v Speaker 1>of it. There an entire world beneath the surface of

0:41:03.760 --> 0:41:06.960
<v Speaker 1>the water that I haven't even scratched. So thank you

0:41:07.040 --> 0:41:09.719
<v Speaker 1>so much for coming onto the show, Jonathan. This is

0:41:09.760 --> 0:41:12.799
<v Speaker 1>a very energizing conversation for me as well. Thank you

0:41:12.880 --> 0:41:15.839
<v Speaker 1>so much for having me on your show. Once again,

0:41:15.880 --> 0:41:19.320
<v Speaker 1>I have to thank Bena Amanath for coming on the show. Uh.

0:41:19.360 --> 0:41:22.479
<v Speaker 1>I was thrilled at this opportunity when I first got

0:41:22.480 --> 0:41:25.279
<v Speaker 1>the email suggesting that I have her on my show,

0:41:25.320 --> 0:41:29.279
<v Speaker 1>because to be totally clear, her team reached out to

0:41:29.360 --> 0:41:33.879
<v Speaker 1>me and I just didn't even think about that possibility.

0:41:34.239 --> 0:41:36.719
<v Speaker 1>I am so glad that I followed up with that.

0:41:37.080 --> 0:41:40.120
<v Speaker 1>I do plan on having more interviews on this show

0:41:40.160 --> 0:41:42.560
<v Speaker 1>in the near future. I've got a couple more lined up.

0:41:43.040 --> 0:41:46.080
<v Speaker 1>I'm gonna try and do that more frequently. It is

0:41:46.239 --> 0:41:48.440
<v Speaker 1>I'm gonna be transparent with all of you. It is

0:41:48.560 --> 0:41:54.200
<v Speaker 1>very tricky for me because scheduling UH is tricky. People

0:41:54.200 --> 0:41:57.080
<v Speaker 1>are very busy, and it gives me a lot of

0:41:57.080 --> 0:42:01.319
<v Speaker 1>anxiety just being absolutely transparent with all of you out there.

0:42:02.160 --> 0:42:06.279
<v Speaker 1>The the the process of scheduling gives me a lot

0:42:06.320 --> 0:42:09.279
<v Speaker 1>of anxiety. So it's something I'm working through and I'm

0:42:09.320 --> 0:42:12.040
<v Speaker 1>trying to get more people on the show one because

0:42:12.080 --> 0:42:14.239
<v Speaker 1>there's so many interesting people out there. And just with

0:42:14.320 --> 0:42:17.160
<v Speaker 1>this conversation with Bena, I really got that that feeling

0:42:17.280 --> 0:42:21.239
<v Speaker 1>of I need this because it is giving me more

0:42:21.320 --> 0:42:23.919
<v Speaker 1>perspective than what I have and I'm I don't want

0:42:23.960 --> 0:42:27.239
<v Speaker 1>tech stuff to just be a narrow laser focus of

0:42:27.800 --> 0:42:32.719
<v Speaker 1>what Jonathan thinks about tech. Secondly, UM, you know, I

0:42:32.760 --> 0:42:36.160
<v Speaker 1>think that it benefits the show obviously to have that

0:42:36.160 --> 0:42:39.120
<v Speaker 1>that extra voice in there, and that means that it

0:42:39.360 --> 0:42:44.640
<v Speaker 1>becomes more enjoyable because despite my enormous ego, I realize

0:42:44.719 --> 0:42:48.080
<v Speaker 1>I cannot be the most entertaining person in all the world, UH,

0:42:48.320 --> 0:42:51.960
<v Speaker 1>no matter how hard I try. So I hope you

0:42:52.080 --> 0:42:56.000
<v Speaker 1>all enjoyed this. If you have suggestions for future topics,

0:42:56.000 --> 0:42:58.759
<v Speaker 1>maybe you have suggestions for future guests I should try

0:42:58.800 --> 0:43:02.520
<v Speaker 1>and get on the show. Reach out to me. Uh,

0:43:02.560 --> 0:43:06.040
<v Speaker 1>I promise I will do my best to get that

0:43:06.120 --> 0:43:08.680
<v Speaker 1>person on the show. I can't promise that it will happen,

0:43:08.680 --> 0:43:14.040
<v Speaker 1>but I'll try and I'll work through this weird stress

0:43:14.080 --> 0:43:16.600
<v Speaker 1>I get whenever it comes down to trying to schedule

0:43:16.640 --> 0:43:19.799
<v Speaker 1>things and uh, and just to be clear, Bena was

0:43:19.840 --> 0:43:23.319
<v Speaker 1>amazing because we actually tried to record that interview on

0:43:23.320 --> 0:43:26.799
<v Speaker 1>one day but had a technical issue ended up having

0:43:26.840 --> 0:43:31.400
<v Speaker 1>to reschedule. She was amazing. It was really good about

0:43:31.400 --> 0:43:36.120
<v Speaker 1>all that. So despite all of my anxiety, everything went great,

0:43:36.280 --> 0:43:38.920
<v Speaker 1>which I think is this isn't meant to be a

0:43:38.920 --> 0:43:41.480
<v Speaker 1>therapy session. But I think that's very typical for me,

0:43:41.600 --> 0:43:44.400
<v Speaker 1>where I get worked up about something turns out that

0:43:44.480 --> 0:43:46.680
<v Speaker 1>something wasn't really that big a deal. It was just

0:43:46.760 --> 0:43:50.080
<v Speaker 1>the anticipation of it that was the problem. So if

0:43:50.120 --> 0:43:52.120
<v Speaker 1>any of you out there suffer from something like that,

0:43:52.200 --> 0:43:54.480
<v Speaker 1>you know you have that same sort of experience. Listen,

0:43:54.480 --> 0:43:57.319
<v Speaker 1>I got your back. I know how it is. It

0:43:57.440 --> 0:44:00.160
<v Speaker 1>is frustrating, but you can do it all right. Eight

0:44:01.040 --> 0:44:03.920
<v Speaker 1>PEP talk Over, Episode over. I hope you enjoyed it.

0:44:03.960 --> 0:44:05.759
<v Speaker 1>I am on vacation for the rest of the week,

0:44:05.840 --> 0:44:09.279
<v Speaker 1>so you should expect some classic episodes for the rest

0:44:09.320 --> 0:44:11.600
<v Speaker 1>of this week. But that doesn't mean they're bad. It

0:44:11.719 --> 0:44:14.920
<v Speaker 1>just means they're old, just like me. I'm old, but

0:44:15.000 --> 0:44:17.440
<v Speaker 1>I'm not bad, and I will talk to you again.

0:44:17.440 --> 0:44:19.880
<v Speaker 1>Oh if you want to reach out to me, you

0:44:19.880 --> 0:44:22.239
<v Speaker 1>gotta do it on Twitter. The handle for the show

0:44:22.320 --> 0:44:26.080
<v Speaker 1>is tech Stuff h s W There. Now I get

0:44:26.120 --> 0:44:29.160
<v Speaker 1>to say the end catchphrase, I'll talk to you again

0:44:30.000 --> 0:44:38.520
<v Speaker 1>really soon. Tech Stuff is an I Heart Radio production.

0:44:38.760 --> 0:44:41.600
<v Speaker 1>For more podcasts from my Heart Radio, visit the i

0:44:41.719 --> 0:44:44.920
<v Speaker 1>Heart Radio app, Apple Podcasts, or wherever you listen to

0:44:45.000 --> 0:44:45.920
<v Speaker 1>your favorite shows.