WEBVTT
00:00:00.000 --> 00:00:10.619
we're asking people to essentially rewrite their job description using a tool that they don't fully understand, but they're still accountable for what happens.
00:00:11.650 --> 00:00:18.820
And the opaque nature of AI makes that a pretty steep hill to climb.
00:00:19.859 --> 00:00:31.329
I mentioned before that at the end of all of this, we're asking someone to rewrite their job description, which is a bit of a leap of faith and what we need to do is we need to turn that leap of faith into more of a hop of faith.
00:00:32.750 --> 00:00:40.090
Confidence and correctness are two different things, but we aren't always great at noted-- knowing the difference.
00:00:41.549 --> 00:00:44.289
Traditional software fails loudly, right?
00:00:44.310 --> 00:00:46.810
You have a bug, it causes a problem.
00:00:47.189 --> 00:00:49.060
It's usually pretty noticeable.
00:00:49.659 --> 00:00:53.340
AI, I'm gonna say, fails with a straight face.
00:00:54.020 --> 00:00:56.670
It always sounds confident, even if it's making things up.
00:00:57.369 --> 00:00:58.829
Trust yields adoption.
00:00:59.000 --> 00:01:01.250
Adoption yields confident users.
00:01:01.509 --> 00:01:03.439
Confident users create ROI.
00:01:03.439 --> 00:01:04.359
I think that's the path.
00:01:15.248 --> 00:01:16.299
Hello, everybody.
00:01:16.399 --> 00:01:21.528
I'm your host, Ben Parker, and welcome back to Data Analytics Chat.
00:01:22.248 --> 00:01:28.588
Today, we're going to be talking about something almost every organization wants from AI, the magic value.
00:01:29.308 --> 00:01:37.778
Companies are investing heavily in AI, obviously launching new tools, running pilots, but investment alone doesn't guarantee ROI.
00:01:38.528 --> 00:01:46.179
One of the biggest questions is whether people actually trust the technology enough to use it, rely on it, and obviously, change the way we work.
00:01:46.638 --> 00:01:51.748
So today, we're gonna explore the relationship between trust, adoption, and ROI.
00:01:52.569 --> 00:01:54.539
Joining me is Paul Drennen.
00:01:54.858 --> 00:01:55.728
Welcome, Paul.
00:01:56.438 --> 00:01:57.569
Hi, glad to be here.
00:01:58.638 --> 00:01:58.998
Cool.
00:01:59.049 --> 00:02:04.118
I guess before we dive in, do you wanna give the listeners a quick introduction to who you are?
00:02:05.478 --> 00:02:05.989
Yeah, sure.
00:02:05.989 --> 00:02:07.009
I'll keep that brief.
00:02:07.058 --> 00:02:29.109
I have recently retired from my corporate career after about 30 years of building analytics and AI practices in a number of industries, most recently in insurance, and now interested in helping people navigate the change and understand what it takes to really be successful.
00:02:29.158 --> 00:02:33.739
And I'll say that after all that time, the, the main lesson for me is...
00:02:35.038 --> 00:02:49.908
and you already hinted at it, Ben, the data is always gonna be a challenge, but the real work is in building trust with users, and then once you've got that trust, how do you keep that trust once they've integrated the solution into their work process?
00:02:49.908 --> 00:02:51.908
So that's really what I'm about.
00:02:52.508 --> 00:02:53.739
Oh, I I'll see you touched on that.
00:02:53.899 --> 00:02:56.038
So why do you think it is trust is the issue?
00:02:56.038 --> 00:03:03.079
Is it just lack of like data literacy or is it just change?
00:03:03.118 --> 00:03:04.718
What do you think is the sort of key component
00:03:06.378 --> 00:03:06.438
here?
00:03:06.438 --> 00:03:08.989
There's a number of different factors going on.
00:03:08.989 --> 00:03:09.968
You mentioned literacy.
00:03:09.989 --> 00:03:34.699
I put that pretty high on the list that people's awareness of what's going on inside these algorithms and these platforms that have been created isn't very strong, and we're asking people to essentially rewrite their job description using a tool that they don't fully understand, but they're still accountable for what happens.
00:03:35.729 --> 00:03:42.899
And the opaque nature of AI makes that a pretty steep hill to climb.
00:03:43.938 --> 00:04:20.709
And if we don't climb it and we don't get that trust from the user, there is gonna be hesitation and at a certain point, every time it makes a mistake, there's a bit of a scorecard that's being kept by individuals and again, that the fact that people are still responsible for the outcome means that they really want to believe in the tools that they're using, and creating that transparency and trust is difficult when the algorithms are opaque and analytical literacy isn't always the highest
00:04:21.309 --> 00:04:23.129
I guess so look, let's focus on trust.
00:04:23.209 --> 00:04:31.899
So c- companies now are investing more and more in AI, but I guess still struggling to create meaningful value from it.
00:04:32.658 --> 00:04:35.519
How much of that problem comes down to trust itself?
00:04:37.483 --> 00:04:50.862
I think most of it, honestly, the investments that are being made right now are primarily in building and establishing the platforms and hiring the engineering talent.
00:04:51.903 --> 00:05:04.642
Those things are important, but the cost of AI, and I'm gonna be inclusive here, Ben, of traditional AI as well as these frontier model-based tools.
00:05:05.923 --> 00:05:07.442
The cost was never in the build.
00:05:07.612 --> 00:05:22.023
It was always in the maintenance of it and the monitoring and the drift detection and the repair that hap- has to occur, and that was always where most of the effort was.
00:05:22.973 --> 00:05:37.892
And now with these frontier models and the fact that they're not deterministic in their outputs, trust maintenance is actually harder than it used to be, and the skills required to do validation are...
00:05:39.413 --> 00:05:40.463
They're not widespread.
00:05:41.122 --> 00:05:46.872
There's a high opportunity cost to using your subject matter experts to test the AI's output.
00:05:47.632 --> 00:06:05.913
So I feel like the disconnect is everyone is chasing the technology and wanting to make sure that they are on pace with the world and that they've got the right tools and platforms and talent, but building an AI is not that hard.
00:06:06.682 --> 00:06:26.372
Owning one that you're proud of in the future takes a lot more effort, and that disconnect, I think, shows up in the high cost of development today, but the relatively low rates of adoption and and consequently impact on business processes.
00:06:27.752 --> 00:06:28.033
Yeah.
00:06:28.033 --> 00:06:35.302
So what you're saying is it's a lot of emphasis on more the, the technology instead of like people that actually build it.
00:06:35.302 --> 00:06:36.923
'Cause I guess now you...
00:06:37.452 --> 00:06:40.593
I guess the value you're gonna get is people that actually know the domain.
00:06:40.843 --> 00:06:43.442
'Cause obviously you've got the technologies there now, isn't it?
00:06:43.442 --> 00:06:44.583
It can do a lot of the heavy lifting.
00:06:44.853 --> 00:06:50.882
It's actually g- I guess having the, being the middle person to actually under- I guess blend it all together.
00:06:50.882 --> 00:06:54.083
Is that do you think where businesses should get more value from?
00:06:54.093 --> 00:06:54.103
I
00:06:55.072 --> 00:06:55.452
do.
00:06:55.483 --> 00:07:15.523
I think we're treating this AI emergence primarily as a technology deployment, and I think it's really more of an operating model change and the focus on the creation of AI you certainly have to do that, but value isn't created when I build it.
00:07:15.543 --> 00:07:25.872
Value is created when I deploy it, and in my definition, deployment means I have a set of confident users who have now integrated it into how they do their job.
00:07:26.607 --> 00:07:28.127
And that's where the value gets created.
00:07:29.127 --> 00:07:40.536
And so much of the distance between a f- a, a frontier model which is becoming highly commoditized now, and we're all renting the same models from the same vendors.
00:07:41.276 --> 00:07:45.047
So there's nothing very distinctive about what's happening in the LLM.
00:07:46.047 --> 00:07:57.747
All the distinction is happening in the rules and the wisdom and the experience and the judgment, those things that our best operators, our best decision-makers have.
00:07:58.607 --> 00:08:07.526
And how do I encode that so that the frontier model and that context layer are partnering well?
00:08:09.057 --> 00:08:11.966
And if I do that, I'll earn trust.
00:08:11.997 --> 00:08:14.396
And if I don't do that, I won't.
00:08:14.396 --> 00:08:19.476
And if I don't earn trust, I'm not gonna sustain a population of confident users for very long
00:08:20.076 --> 00:08:22.076
So obviously you're highly regarded in the market.
00:08:22.137 --> 00:08:25.286
I spoke to many people that, yeah, really rate you, I'll be honest.
00:08:25.377 --> 00:08:32.897
What, what happens where before employees or leaders become comfortable reliant on AI as part of their day-to-day work then?
00:08:34.677 --> 00:08:51.756
So this is a big question, and I think there's a number of things, and I often use a gardening analogy where I think about I have to prep the soil, I have to plant the seeds, I have to nurture them, I have to keep the weeds out.
00:08:51.797 --> 00:08:56.767
I have to do all these things and so this preparation is important.
00:08:57.996 --> 00:09:09.466
I mentioned before that at the end of all of this, we're asking someone to rewrite their job description, which is a bit of a leap of faith and what we need to do is we need to turn that leap of faith into more of a hop of faith.
00:09:10.836 --> 00:09:17.027
And so some specific ways that I have used that have been successful is a couple things.
00:09:17.057 --> 00:09:26.096
So one seems obvious, but you wanna have the users and the builders co-invent the solution.
00:09:26.716 --> 00:09:45.442
When the user feels like they've had equal authorship over what's being built, then their path to adoption is much easier the models are opaque, but you can make many of the moving parts as transparent as possible.
00:09:45.442 --> 00:09:52.893
And so you want to make the system visible and transparent so that people understand how it works.
00:09:52.893 --> 00:10:02.442
There's a moment where the algorithm is gonna do something that's difficult to describe, but before and after that, we can make things very transparent.
00:10:03.842 --> 00:10:19.232
I got a lot of usage and value out of what we called the, the blind acceptance test, where we would score something and then show it to our experts without telling them what the model had said, have them reach their conclusion, and then reveal how the model compared to that.
00:10:19.232 --> 00:10:30.273
And, if you're lucky, it performs very well, and if not, then you iterate until you get to a point where the user believes in the quality of the outcome.
00:10:31.363 --> 00:10:46.842
And then the last piece, which I think is really important, and I'll probably say this more than once while we're chatting, once I've built it I really have a lot of duties that come with ownership, and AI is going to drift.
00:10:46.852 --> 00:10:48.403
It's trained on the past.
00:10:48.883 --> 00:10:50.253
The future will look different.
00:10:50.753 --> 00:11:00.592
As that difference widens, the confidence we have is going to erode, and you have to watch it, and you have to repair it.
00:11:01.283 --> 00:11:08.673
And I believe that at a certain point, as a user, I wanna know who's accountable for that activity.
00:11:08.722 --> 00:11:12.972
So I wanna know who is watching and who is going to take action when it drifts.
00:11:13.623 --> 00:11:21.202
Because without that warranty, the drift is accumulating, and it's happening invisibly.
00:11:21.393 --> 00:11:25.072
And at a certain point, I'm gonna start getting answers that don't make sense.
00:11:25.572 --> 00:11:28.822
And once trust is lost, it is very difficult to retain.
00:11:29.312 --> 00:11:33.863
So those are the things I think you have to bring people in.
00:11:33.863 --> 00:11:35.722
You have to create transparency.
00:11:36.273 --> 00:11:47.972
You have to put everything on display that you can, and there needs to be that warranty that says,"We're not just gonna build it and chuck it over the wall and hope for the best.
00:11:47.972 --> 00:12:11.613
We're gonna stand behind this." So I summarize all that in, in my practice as the safe to own promise, which is more comprehensive than a safe to buy promise because, as I said before, the real effort is in the long-term trust maintenance and ownership of these assets, and so a safe to own promise comes with those things.
00:12:13.222 --> 00:12:13.452
Yeah.
00:12:13.452 --> 00:12:23.893
So I'm guessing s- we need leaders to be good coaches, really, to do this constant education for inhe- or I guess helping people understand AI really then?
00:12:24.493 --> 00:12:26.873
Yes and we're all on a learning curve together.
00:12:26.873 --> 00:12:32.682
Even the professional data scientists are having to climb a learning curve with these new tools.
00:12:33.092 --> 00:12:37.352
So acknowledging that we're all learning together I think is an important fact.
00:12:38.533 --> 00:12:55.592
And a willingness to try, a tolerance for the iterations and cycles as we calibrate, and then studying how the machines are built, what they're good for, what they're not good for.
00:12:56.263 --> 00:13:08.923
I think inoculating ourselves a bit from the hype so that we can navigate more practically all of those things and leadership has to not only sponsor that, but actively participate in that
00:13:09.523 --> 00:13:21.633
So then obviously looking at technology c- can a AI system be, like, technically excellent but still fail to create value because people simply do not trust or adopt it?
00:13:23.133 --> 00:13:23.633
Totally.
00:13:23.732 --> 00:13:25.013
I've seen that before.
00:13:25.013 --> 00:13:41.623
And before, before the current frontier model-based AI in my own practice, one of the things I've talked about monitoring, so we paid a lot of attention to the shape and value of the data that was feeding the algorithm that we had trained.
00:13:42.182 --> 00:13:47.582
We spent a lot of time monitoring its outputs against references.
00:13:48.202 --> 00:14:01.682
But we also added a we called it an engagement rate, which said how often is the user agreeing with what the model is recommending, and we trended that over time.
00:14:02.113 --> 00:14:15.332
And what I have seen is models aren't perfect, and so every now and then they're going to recommend something that the user disagrees with and if the user is anxious about it, they're probably keeping score.
00:14:16.102 --> 00:14:24.702
And at some point it's gonna give them an untrustworthy response one time too many, and at that point you're gonna lose their confidence.
00:14:25.432 --> 00:14:39.942
And so I have seen algorithms that were performing well, the monitoring results were strong, but where I was losing the confidence of the user, and that will end value creation just as much as a model that has gone off target
00:14:40.543 --> 00:14:45.052
So would these, is changing behavior sometimes harder than actually building the technology, Tim?
00:14:46.373 --> 00:14:49.133
I think that is the hardest part of the job, honestly.
00:14:49.133 --> 00:14:50.692
You have to earn trust.
00:14:50.692 --> 00:14:54.682
You have to convince someone,"Here's what's really happening.
00:14:54.692 --> 00:14:56.312
I'm building a tool for you.
00:14:56.722 --> 00:14:59.003
I'm asking you to rewrite your job description.
00:14:59.423 --> 00:15:06.763
I can't fully expose exactly how the tool works." That is a difficult request And Yeah.
00:15:06.812 --> 00:15:31.562
That's just a really difficult request, and if I don't manage that part, the psychology part of it well, and I don't convince my users that I'm standing behind it, I'm gonna guard their commitment and keep, ke- keep earning the trust that they've given, then I risk losing that trust.
00:15:31.562 --> 00:15:34.072
And as I said before, once it's gone, it's very hard to get back.
00:15:34.673 --> 00:15:37.812
So what are the biggest things that cause people to lose trust in AI?
00:15:38.413 --> 00:15:43.503
Accumulation of wrong answers that they are still accountable for would be at the top of the list.
00:15:44.783 --> 00:15:51.062
And look, I was doing AI before the frontier models, and we had algorithms that were deterministic.
00:15:51.092 --> 00:15:59.613
So I would put the same inputs in, I would get exactly the same output out, and trust building and trust maintenance was the hardest part back then.
00:15:59.613 --> 00:16:04.753
And now you've got algorithms where the same input can generate a different answer.
00:16:05.442 --> 00:16:13.793
And so that, that breadth of what is it gonna say this time, I think creates a, a, a bigger trust barrier.
00:16:14.692 --> 00:16:31.982
And as the answers come through and as that variance accumulates, it's not only that I disagree, it's the unpredictability of it that can be a real threat to my confidence
00:16:32.582 --> 00:16:32.952
Okay.
00:16:33.673 --> 00:16:36.352
Then I guess, AI can sound convincing even when it's wrong.
00:16:37.543 --> 00:16:37.753
Yeah.
00:16:38.173 --> 00:16:43.582
And, yeah, And AI, it can produce answers that sound extremely convincing even when they're wrong.
00:16:43.653 --> 00:16:49.893
And so I guess how should organizations manage that risk without making people afraid to use the technology?
00:16:51.793 --> 00:16:59.133
Confidence and correctness are two different things, but we aren't always great at noted-- knowing the difference.
00:17:00.592 --> 00:17:03.332
Traditional software fails loudly, right?
00:17:03.352 --> 00:17:05.853
You have a bug, it causes a problem.
00:17:06.232 --> 00:17:08.103
It's usually pretty noticeable.
00:17:08.702 --> 00:17:12.383
AI, I'm gonna say, fails with a straight face.
00:17:13.063 --> 00:17:15.712
It always sounds confident, even if it's making things up.
00:17:16.413 --> 00:17:24.583
And in most business contexts, we're gonna, we're gonna manage the context layer so that the ability to just make things up wholesale is very controlled.
00:17:24.593 --> 00:17:30.913
But even when it starts to drift off target, it's always gonna sound sure of itself.
00:17:31.833 --> 00:17:39.282
So I would say the, the fix is not we have to condition everyone to be nervous or afraid.
00:17:39.742 --> 00:17:42.452
You have to design safety into your system.
00:17:43.163 --> 00:17:51.903
And so again, this, this idea of ownership and warranty is, I think, central to the answer here.
00:17:53.143 --> 00:18:12.133
I really need somebody dedicated to context curation, not a part-time job, somebody who is familiar with the domain but also understands what it takes to teach the context layer what the truth is.
00:18:13.542 --> 00:18:27.692
Validation cycles with your subject matter experts, not as an ad hoc or crisis response, but as a planned workforce capacity, a protected duty that you build into the way you think about staffing.
00:18:29.403 --> 00:18:32.212
I, I created a job family years ago.
00:18:32.212 --> 00:18:36.022
It was one of the smartest things I ever did that we ultimately called an asset owner.
00:18:36.022 --> 00:18:51.282
But think of this person as a, a combination of the best sales engineer you've ever met, the best scrum master release train engineer you've ever met, but they own the solution.
00:18:51.702 --> 00:19:02.653
And note, I'm not saying the model, I'm saying the solution because the solution often has multiple components, but they own it and they're accountable for its performance.
00:19:02.653 --> 00:19:06.042
They're accountable for how the trend is going.
00:19:06.042 --> 00:19:09.952
They're accountable for scheduling repair sessions in.
00:19:11.613 --> 00:19:16.772
And then the last piece I'll point is, you don't wanna, you don't wanna scare people.
00:19:17.123 --> 00:19:25.202
You build those controls and you build that visibility into the full life cycle And then you invite scrutiny.
00:19:25.202 --> 00:19:37.673
You ask your users to give you honest feedback and then you have to respond to that hon- honest feedback with gratitude rather than defensiveness, because you want to encourage that honest feedback.
00:19:38.593 --> 00:19:48.563
And if we all understand that every tool we're building is on an evolutionary path, it's not perfect, it's gonna get better.
00:19:49.002 --> 00:19:53.863
If I don't watch it, it could get worse, but ideally we're gonna pay attention and we'll make it better.
00:19:54.673 --> 00:20:21.252
So there are gonna be issues, and you wanna have that combination of ownership in- invitation of expert validation, invi- invite scrutiny and feedback, and you wanna respond to the challenges with gratitude and a commitment to learning from those challenges and investing those learnings back into the solution so that it evolves in a positive direction
00:20:23.222 --> 00:20:23.286
Okay.
00:20:23.286 --> 00:20:23.348
Good.
00:20:23.348 --> 00:20:26.840
I like the, obviously, yeah, the outcome focus,'cause, yeah, that's...
00:20:27.171 --> 00:20:30.411
Enda, you wanna be progressing, don't you?
00:20:30.590 --> 00:20:32.340
You want it to be running efficiently.
00:20:33.080 --> 00:20:33.800
So I guess, how would you...
00:20:34.631 --> 00:20:43.080
how should organizations encourage people to use AI while also making sure they continue to question its outputs when necessary?
00:20:45.050 --> 00:21:03.080
One of the trends that I see happening, and I'm not a fan of, is this kind of enterprise forcing function on AI that says,"30% of your code has to be generated by AI," or,"X percent of your work has to use it." I'm not a big fan of that.
00:21:03.830 --> 00:21:13.681
The future says, Paul's opinion, but I've said this out loud more than once, every job family is going to be AI-enabled in the future.
00:21:14.270 --> 00:21:25.990
So we want people to have hands-on experience, and we want them to start getting comfortable with what it's good for, what it's not good for, how do I get the best performance out of it?
00:21:26.000 --> 00:21:27.221
We want those things.
00:21:28.250 --> 00:21:35.510
But applying pressure to people to hit contrived milestones, I don't think is the answer.
00:21:36.111 --> 00:21:38.631
And you wanna have...
00:21:40.621 --> 00:21:45.421
we can't eliminate the human judgment, which is where the value's created.
00:21:45.421 --> 00:21:52.530
So I said that before, and I'll repeat it, like what's encoded in the front- frontier model is a commodity now.
00:21:53.191 --> 00:21:54.441
That's not where the value comes from.
00:21:54.441 --> 00:22:31.651
It comes from the wisdom of the people who have been doing this and have learned what works well, and you wanna get that embedded into a system where AI is a piece of the system, but AI is empowering the human to make better choices we had a lot of conversation about this, and one of the things that I actively championed was an enterprise-wide literacy campaign to get people hands on keyboard, but not just go try it, but to orient our entire workforce to how it works.
00:22:32.181 --> 00:22:37.270
Not down at the level of weights and biases and deep learning training.
00:22:37.300 --> 00:22:39.260
We don't need to go that deep.
00:22:39.320 --> 00:22:54.931
But what is it doing, and how do you influence the path it's following so that you can stay on target and not not get the hallucinations and those types of things?
00:22:55.621 --> 00:23:18.770
So I'm gonna say practical user literacy, not necessarily deep engineering or science literacy, and I felt like that was an important factor in starting to take the mystery and reduce that, black boxiness of it to where people felt like I understand how I can apply this now.
00:23:19.250 --> 00:23:27.361
And any program that does not take on the literacy challenge, I think, is just making the slope of the hill they have to climb steeper.
00:23:29.070 --> 00:23:29.441
Yep.
00:23:30.121 --> 00:23:32.641
You touched on an interesting point about human judgment then.
00:23:33.240 --> 00:23:41.780
So obviously, as organizations are automating more decisions with AI, where do we balance the...
00:23:41.961 --> 00:23:43.661
Where should human judgment remain?
00:23:44.480 --> 00:23:45.931
Do you think that's the challenge now?
00:23:46.530 --> 00:23:48.631
I think we're all still trying to figure out.
00:23:48.661 --> 00:23:52.780
We all understand and believe that human judgment is critical.
00:23:53.760 --> 00:23:54.980
Where does it show up?
00:23:55.050 --> 00:24:11.060
How do I integrate the tools and the judgment in a, a graceful way so that work gets done efficiently and we're proud of the output no one's asking the human to outperform the model at what the model was designed to do.
00:24:11.941 --> 00:24:22.371
One of the things that we implemented, and I think this was the right decision, was and honestly, this predated even the generative AI emergence.
00:24:24.060 --> 00:24:28.851
We only let systems have the authority to approve things.
00:24:29.790 --> 00:24:33.060
We never allow the system to automatically deny things.
00:24:34.951 --> 00:24:38.540
And I do think that as a hard rule was a smart one.
00:24:39.851 --> 00:24:48.800
I'm also a big fan of this idea that most of these solutions now, as I mentioned, are a combination of a frontier model and a context layer.
00:24:49.651 --> 00:25:08.820
And so investing deeply in how do we build, how do we sustain, how do we nurture, how do we clear the rot out of the context layer as a dedicated assignment, as a protected part of our workforce?
00:25:09.730 --> 00:25:21.711
If you do that well, then you really get the human in the loop at the foundation of your context layer, and that's where that judgment, it just flows all the way through the life cycle if we do that well.
00:25:22.300 --> 00:25:34.461
If we naively just grab a bunch of documents from a library and embed them or ingest them in a wiki or something like that, we run the risk of there being contradictions in that.
00:25:35.601 --> 00:25:36.911
It's drifting over time.
00:25:37.480 --> 00:25:49.260
The hum-- for me, the human in the loop adds a ton of value if I embed that very deeply at the front of this whole life cycle in the way we build and manage context.
00:25:51.090 --> 00:26:00.330
Then we allow the agents to be strong and have authority over easy yes outcomes.
00:26:00.691 --> 00:26:16.260
We don't let them have the complicated no outcome, and we engage the human judgment when things are ambiguous or if I'm making a decision that I'm gonna have to defend later.
00:26:16.861 --> 00:26:26.641
And so for me, human in the loop, human judgment, really powerful at the foundations of knowledge and in the ambiguous cases.
00:26:26.681 --> 00:26:29.461
That's where I think that's going to land.
00:26:30.711 --> 00:26:51.721
And I'll say it in just summarizing all of this, everything we've talked about so far, just one of the things that, that I said to my executive team and my board of directors is, at the end of the day, we wanna be proud of what we did, not just the day after we did it, but three years from now, I still wanna be proud of this thing that we created.
00:26:51.851 --> 00:26:54.760
And that's the kind of final exam score on all of this
00:26:55.361 --> 00:26:55.691
Yep.
00:26:56.260 --> 00:27:05.080
No, I agree, like I said, that you wanna, you want fa-- like you, it gets, you, if you get more value out of it, there's-- things are gonna, it's constantly gonna evolve, isn't it?
00:27:05.131 --> 00:27:10.340
So you need to keep building and it's obviously, it's one of them tools, isn't it?
00:27:10.351 --> 00:27:12.740
Technology where you need constant development on it.
00:27:13.181 --> 00:27:18.121
But yeah, you need, like you said, you need to be actually getting value from it so you...
00:27:18.520 --> 00:27:25.421
It's not every time you gotta start projects again or,'cause it's just, that's, obviously that's where a lot of the investment's gonna go, isn't it?
00:27:26.530 --> 00:27:33.371
It is, and I think one of the, one of the things that we're all wrestling with is our familiarity with traditional software.
00:27:33.911 --> 00:27:45.131
And this feels so similar in a lot of ways that there's this sense of this is just a, an extension of what I'm familiar with.
00:27:45.191 --> 00:27:48.090
And I think superficially there's a lot of truth in that.
00:27:48.300 --> 00:27:58.911
But where it gets different is that in traditional software, I wrote a bunch of logic and the same activities produce the same outcome every time.
00:27:59.621 --> 00:28:05.580
And so I could have a team of people who built software, and then I could have a totally different team of people who maintain software.
00:28:06.290 --> 00:28:12.191
And and with AI, building is not where the hard part is, it's in the maintenance.
00:28:12.840 --> 00:28:16.320
And that is under constant daily threat of drift.
00:28:16.340 --> 00:28:20.310
And you have to know it, you have to recognize it, you have to repair it.
00:28:20.891 --> 00:28:25.211
You have to re-credential the solution with your users over and over again.
00:28:25.211 --> 00:28:33.151
And that part is very different And it forces you to think about your workforce and your capacity and the conversation you're having with users.
00:28:33.151 --> 00:28:41.171
It forces you to think about that very differently, which is why I said earlier the illusion that this is technology is, I think, strong.
00:28:41.171 --> 00:29:00.201
But honestly, in my opinion, this is an operating model change, and it-- in a lot of ways, it's forcing us to pay more attention and to be more deeply engaged with our users than we've ever had to be before, which I think is a challenge, but also a really positive thing
00:29:00.800 --> 00:29:00.810
Yeah.
00:29:00.810 --> 00:29:02.443
No I agree with you on the operating operating change'cause, it's...
00:29:02.443 --> 00:29:05.304
You're embedding it across the whole business now, isn't it?
00:29:05.304 --> 00:29:09.544
It's just AI's, yeah it's critical for every business now.
00:29:09.544 --> 00:29:13.114
Every bus- every department wants as a business use case now, doesn't it?
00:29:13.134 --> 00:29:16.618
So I think it's, you're fl- flipping your business upside down, aren't you?
00:29:16.618 --> 00:29:17.598
And building again.
00:29:18.729 --> 00:29:19.138
Yes.
00:29:20.479 --> 00:29:24.048
So listen, I want to talk about trust, adoption, and ROI.
00:29:24.249 --> 00:29:29.898
So what's the relationship between trust, adoption, AI for an organization so it's, from AI?
00:29:31.578 --> 00:29:38.679
So I think it's a chain that runs in one direction, and if I don't have trust, I'm gonna struggle with adoption.
00:29:39.608 --> 00:29:47.138
If I don't get adoption, I'm not gonna get an ROI, and it doesn't really matter how great the algorithm or the tool we've built is.
00:29:48.048 --> 00:29:51.108
So you really have to start with trust.
00:29:51.989 --> 00:29:52.759
You have to earn it.
00:29:53.669 --> 00:30:03.028
You have to gain confident users, and then you have to protect the decision they've made to adopt over time.
00:30:03.959 --> 00:30:14.118
And as you do that, and as confidence grows, they'll integrate the tool into the way they do their job more and more deeply, and that's when the ROI will start to show up.
00:30:15.519 --> 00:30:27.979
And I mentioned this idea of a final exam grade and so I'm gonna say, my opinion, the final exam grade is not that I got a 30% productivity number, it's did they adopt it and were they still using it the same way or more a year from now?
00:30:27.979 --> 00:30:28.169
And if that is true, I'm gonna get the productivity numbers, but I'm also gonna keep the productivity numbers.
00:30:28.169 --> 00:30:34.489
And so I think there's a little shortsightedness at times where we set a target, and we work really hard, and we get to that target, and we declare victory, and we move on.
00:30:34.489 --> 00:30:39.669
And what I'm saying is, I want confident users more than anything else.
00:30:41.348 --> 00:30:54.709
I think having a set of confident users is far more valuable than a bunch of solutions and models that I, hit some target number on a report card.
00:30:55.429 --> 00:30:56.469
And the recap.
00:30:57.308 --> 00:30:58.769
Trust yields adoption.
00:30:58.939 --> 00:31:01.189
Adoption yields confident users.
00:31:01.449 --> 00:31:03.378
Confident users create ROI.
00:31:03.378 --> 00:31:04.298
I think that's the path.
00:31:05.409 --> 00:31:07.759
And if I lose trust, the whole thing collapses
00:31:08.358 --> 00:31:13.469
So do you think, everyone has a goal if they wanna get A to B.
00:31:13.499 --> 00:31:19.618
So do you think op- adoption is the missing link between AI investment and business value?
00:31:19.669 --> 00:31:21.739
'Cause,'cause it's...
00:31:21.759 --> 00:31:23.209
Adoption is the hard bit, isn't it?
00:31:23.269 --> 00:31:24.648
It's just you cha- if you're...
00:31:24.729 --> 00:31:35.959
Whenever you're going through a change journey, you are, like I said, you've gotta build trust with people, you've gotta do the change management piece, which is obviously changing people.
00:31:36.449 --> 00:31:37.749
Do you think that's the...
00:31:38.398 --> 00:31:40.118
Adoption is the hard bit for businesses?
00:31:41.528 --> 00:31:46.219
I do, but I would modify it, Ben, only to say I think it's sustained adoption.
00:31:46.338 --> 00:31:52.519
Because we can apply management pressure to a workforce to get them to hit a number on a report card.
00:31:52.519 --> 00:31:55.538
I want them to hit that number because they believe in it.
00:31:56.778 --> 00:31:58.009
I don't wanna give up.
00:31:59.568 --> 00:32:03.568
When management attention shifts s- somewhere else, I don't wanna go backwards, right?
00:32:03.568 --> 00:32:22.499
So it's really sustained adoption that matters And look it's hard to quantify some of these things, and we all want, a, a, a, a bunch of KPIs on a report card that I can generate and I can show to my leadership team on a quarterly basis and demonstrate the trend and so on.
00:32:23.219 --> 00:32:31.979
I understand why we all want this, but we're talking about people's belief systems and how that manifests in how they behave.
00:32:33.229 --> 00:32:36.429
The metrics are often a lagging indicator on belief.
00:32:38.028 --> 00:32:39.108
Belief is what I need.
00:32:39.108 --> 00:32:46.298
So I think we all have to be a little more comfortable with this isn't that easy to measure directly.
00:32:47.219 --> 00:33:00.949
But when I check in with my users and when I watch how they are engaging with the tools, how often they are agreeing with it, are they starting to abandon the use of it?
00:33:01.439 --> 00:33:09.298
Those things I think are how we measure whether people believe or not, and that's ultimately what's gonna be the most important.
00:33:11.189 --> 00:33:22.338
So how should leaders measure whether an AI initiative is creating business value rather than simply just cre- generating lots of usage or experiments?
00:33:22.939 --> 00:33:40.939
You certainly want some, some direct mechanical observations if you can get them what I don't think works is saying something like,"30% of your code has to be generated in AI." It's pretty easy for me to hit that target and have not really integrated the tool into how I do my job.
00:33:41.969 --> 00:33:43.148
So you have to be careful.
00:33:43.148 --> 00:33:49.939
I don't think usage measurement is going to translate into value very well.
00:33:51.019 --> 00:33:56.598
And we have lots of usage measurements out there because they're mechanically easy to produce.
00:33:56.598 --> 00:34:10.608
But I think that there's a gap between usage and value, and we're gonna have to pay more attention to engagement and how well has my workforce integrated the tool.
00:34:11.528 --> 00:34:13.199
I would put those higher on the list.
00:34:14.068 --> 00:34:21.898
And then I think we also have to accept that for a while it's going to be more qualitative than quantitative.
00:34:22.869 --> 00:34:27.898
And so on a qualitative basis, do my users trust it?
00:34:28.539 --> 00:34:34.579
And are they trusting it over time, back to my sustained confidence point those are the key things I think.
00:34:36.059 --> 00:34:36.918
Oh, interesting.
00:34:37.648 --> 00:34:49.179
What should organizations put in place across technology, data, governance, and people to build AI that employees and leaders are prepared to rely on?
00:34:50.668 --> 00:35:03.418
So I did a couple things that I think were pretty impactful and so you mentioned governance, and I will tell you that I had tried to rebrand governance internally to, to safe enablement.
00:35:03.918 --> 00:35:15.699
Governance often feels like friction and second-guessery, whereas safe enablement feels like an accelerator for me to get where I want to.
00:35:15.768 --> 00:35:31.458
So I I brought together a group of individuals who historically represented that risk of friction or that risk of the 11th hour challenge We all know and love them.
00:35:31.679 --> 00:35:34.289
I call this gr- group collectively the guardians.
00:35:35.739 --> 00:35:41.509
It's compliance, it's legal, it's procurement, it's risk management, it's architecture, it's security.
00:35:42.679 --> 00:35:45.458
To deploy a system, we have to gain their approval.
00:35:46.148 --> 00:35:52.389
And I brought the group together and I said I want you to join me on Team Yes.
00:35:52.699 --> 00:35:59.909
And Team Yes's job is to approve use cases and solutions, but not as a rubber stamp.
00:36:00.688 --> 00:36:03.028
I'm not asking you to abandon your duties.
00:36:03.028 --> 00:36:28.539
I'm asking you to help me encode what does it take so that you can say yes, because saying yes is what you wanna do." And so I think this shift from governance as a post-hoc inspection or evaluation, and instead invite that group to co-author the safe perimeter.
00:36:29.239 --> 00:36:52.438
And then as we got better and patterns started to emerge, we were able to document what that safe boundary set looked like, and use cases that were inside that safe boundary got approved without a lot of oversight, because we had already we had already published what the boundaries were.
00:36:52.509 --> 00:37:09.389
And that actually opened up the use case pipeline a great deal, and then the guardians could use their time and skill and wisdom to look at novel things, new use cases, new patterns, things we hadn't seen before, which is where they add the most value.
00:37:09.389 --> 00:37:25.358
So I'm gonna say on the governance side, excuse me, bringing the guardians in at the front of the process and having them co-author what I call that, that safe boundary set, that was really valuable.
00:37:26.518 --> 00:37:43.969
I've mentioned this idea of an asset owner before, and I do think that having a named person who owns the solution and is standing behind that safe to own promise over time is a great idea from an accountability and a visibility standpoint.
00:37:43.969 --> 00:37:52.829
It's also a confidence builder for users, and we've talked a lot about building confidence in users as really the, the key milestone here.
00:37:52.829 --> 00:37:57.438
And I think having that named asset owner was really valuable in that regard.
00:37:58.039 --> 00:38:10.048
Anything that we do in a repetitive way that can be engineered into the platform and the methodologies that we deploy is well worth doing.
00:38:10.068 --> 00:38:17.259
And, one of my taglines that we use was safety through design, not supervision.
00:38:17.798 --> 00:38:38.282
And so whether it's governance or technology, just taking recurring things and shifting left and being very deliberate about what they are, how they're supposed to work, what the safe approach is and engineering that into our systems and our methodologies I think that those are all really good things to do.
00:38:40.032 --> 00:38:48.722
And then on the data side, I'm gonna beat this drum really hard, Ben, but the context layer is where all of the value gets created.
00:38:48.722 --> 00:39:00.262
And so having dedicated, qualified, and protected capacity to manage the context is key.
00:39:01.521 --> 00:39:16.391
And so safety through design, not supervision, bringing the guardians in at the start of the life cycle, and really committing to that safe to own curation of context, those are the key moves, I think.
00:39:18.192 --> 00:39:26.681
So do you think that with projects before you ha- always had project coordinators to keep projects on t- task.
00:39:26.681 --> 00:39:35.244
Do you think that in data they need more, I guess p- like more people that do similar type of role that's got, obviously, to take the ownership, so they are like the glue.
00:39:35.304 --> 00:39:37.923
They make sure everything's gets the outcomes.
00:39:37.923 --> 00:39:40.233
Do you think that's what's missing or What do you think?
00:39:40.713 --> 00:39:45.344
Certainly when I made that a full-time job, it accelerated everything.
00:39:45.673 --> 00:39:51.623
And I'm gonna call back to this idea of the skills of AI have gotten much easier.
00:39:51.623 --> 00:40:06.344
The duties of AI have not, and in some cases, I think the duties of AI are actually more difficult now because of the non-deterministic nature of how the models work, and they're more opaque than they used to be.
00:40:07.184 --> 00:40:25.574
And so that, that accountability to not only get the, the solution over the finish line and deployed, but to stay with it throughout its life cycle and to safeguard its accuracy and be hungry for two things.
00:40:27.333 --> 00:40:34.614
As I gain operational experience, can I use that knowledge to improve my solution so that feedback loop gets created?
00:40:35.983 --> 00:40:45.353
And can I take this solution and reapply it to adjacent use cases so that I can multiply the value that was created?
00:40:45.353 --> 00:40:59.684
And, in the old, older traditional AI days, we did that but the trans- the transferability of the solutions was a little more brittle because, you had the trained algorithm.
00:41:00.653 --> 00:41:07.733
W- with a generative or agentic solution, we're orchestrating components, so there's a lot more fluidity.
00:41:07.764 --> 00:41:25.184
So this idea of I've deployed it, I'm standing behind it, I'm watching closely, I'm inviting feedback, I'm taking those learnings, I'm improving my algorithm, but I'm also looking for the nearest neighbors that I can reapply it to.
00:41:25.773 --> 00:41:28.164
If nothing else, the pattern can be reapplied.
00:41:28.164 --> 00:41:41.273
But in many cases, if I've invested in a deep context library on some domain, the ability to reapply that to a number of different solution opportunities is quite wide.
00:41:41.764 --> 00:41:49.764
But if that's not somebody's job, it's not gonna happen with the same speed or durability.
00:41:49.773 --> 00:41:50.074
It's...
00:41:50.094 --> 00:41:52.764
so I don't know, Ben you asked me a bunch of questions.
00:41:52.764 --> 00:42:00.934
I keep coming back to this idea of accountability for the context layer and its commitment to safe to own over time.
00:42:00.943 --> 00:42:05.224
These, these things end up being at the center of most of the questions you're asking
00:42:05.824 --> 00:42:06.123
Yeah.
00:42:06.123 --> 00:42:09.543
No, I think it's also once something's...
00:42:09.623 --> 00:42:12.293
once you build something, people wanna move on to the next project, don't they?
00:42:12.344 --> 00:42:15.023
It's just, just natural.
00:42:16.244 --> 00:42:16.543
People don't
00:42:16.724 --> 00:42:17.083
wanna do something new.
00:42:17.594 --> 00:42:22.063
I think that's one of the legacies of traditional software, and I'm not, I'm not-
00:42:22.063 --> 00:42:22.423
Yeah
00:42:22.543 --> 00:42:33.753
I'm not trying to beat up traditional software but we had matured the pipeline of traditional software to a point where you had dedicated builders and a different group of dedicated maintainers.
00:42:35.164 --> 00:42:42.023
And because drift was not the challenge in traditional software, it is in AI, that's the pattern.
00:42:42.023 --> 00:42:43.414
We all understand that pattern.
00:42:43.414 --> 00:42:45.043
We've all lived through that many times.
00:42:45.914 --> 00:42:47.704
But AI inverts that.
00:42:48.184 --> 00:42:49.974
Building is not challenging.
00:42:50.653 --> 00:42:56.324
Sustaining is very challenging, and we have to adjust to that.
00:42:56.373 --> 00:43:08.233
We ha- we have to factor that into how we think about who's involved in the build cycle, how do I create dedicated skill for maintenance?
00:43:08.333 --> 00:43:10.963
And I don't mean maintenance like just mechanical maintenance.
00:43:10.963 --> 00:43:15.764
There's certainly a piece of that, but it's this idea of trust and confidence maintenance.
00:43:16.974 --> 00:43:18.583
That's the really key job here
00:43:19.184 --> 00:43:31.094
So then I guess once AI is deployed, how should organizations continue testing and monitoring it so trust is maintained rather than just assumed?
00:43:32.853 --> 00:43:39.923
So this is gonna echo back to what I just said, but you have to treat an AI solution as a living system.
00:43:39.923 --> 00:43:43.304
It's going to drift every day.
00:43:43.594 --> 00:43:59.713
It's going to experience some level of microscopic damage to its logic, and if you aren't monitoring it and you don't have a regular repair mechanism, eventually it will drift too far and it will start to give you bad answers.
00:44:00.824 --> 00:44:04.713
And I've used the word drift a number of times, but let me just spend a minute defining it.
00:44:06.373 --> 00:44:11.594
There's a couple different sources of drift, and so one of those things is very much external.
00:44:11.603 --> 00:44:24.454
So if I'm building a, a pricing model for an insurance product, climate change, geopolitics, supply chain disruptions, these are external things.
00:44:24.454 --> 00:44:40.503
But what they mean is tomorrow looks different than the last 10 years because one of these things have gone in a different direction, and I have to know about it, and I have to make adjustments for it, and I have to layer that knowledge into my system.
00:44:41.264 --> 00:44:42.784
That's external drift.
00:44:43.574 --> 00:44:45.474
And then there's internal drift.
00:44:45.483 --> 00:44:59.264
So maybe we're going to market differently, or we've changed our appetite for risk, or we're applying different incentives to our workforce, which is gonna cause a shift in their decision-making process.
00:45:00.313 --> 00:45:13.764
Again, these all represent a difference in the future from the past, and my algorithms, whether it's a traditional AI or the foundation model, they're built on examples, past examples.
00:45:13.793 --> 00:45:22.534
And so that separation between the training data and current and future reality, that's drift.
00:45:23.244 --> 00:45:28.634
And so you have to watch for that, and there's several ways to do that.
00:45:28.643 --> 00:45:37.884
You can certainly, and you should, watch your data sources and pay attention to how the shape of your data is changing over time.
00:45:37.934 --> 00:45:41.514
My mix of product or my mix of geography is changing.
00:45:42.043 --> 00:45:45.103
The cost of repair of an automobile is changing.
00:45:45.114 --> 00:45:45.653
All these things.
00:45:45.653 --> 00:45:46.664
You have to watch that.
00:45:46.684 --> 00:45:49.393
That's really a, a data monitoring.
00:45:49.414 --> 00:45:55.213
But those data that are inputs to my solutions have to be watched.
00:45:55.813 --> 00:46:00.994
And then the other piece of this is- How frequently am I running my repair?
00:46:01.764 --> 00:46:08.443
Because if I can do microscopic repair missions, that's better.
00:46:08.483 --> 00:46:22.884
More frequent repair is better because the performance of my system is the average of its best day, the day after the model was deployed, and its worst day, the, the day that it has had the longest to drift.
00:46:22.893 --> 00:46:26.583
And quality of what I'm getting is somewhere in between.
00:46:26.643 --> 00:46:40.773
And so if I can shorten that window between when I notice it's drifting and when I adjust my algorithm, my performance of my overall solution is gonna be much improved.
00:46:40.773 --> 00:46:47.893
And so I think watching it and then engineering that detection and repair.
00:46:48.554 --> 00:46:59.773
And by the way to do that requires a commitment of capacity that's often at the expense of building the next new cool thing.
00:47:00.623 --> 00:47:19.193
And so that's where I come back to, like there is this idea of protected capacity, which is specifically protected to monitor and fix and improve my existing solutions with the same fervor as I put capacity against building the next new thing
00:47:19.793 --> 00:47:26.844
You know, and I'm guessing this all tie back to what you mentioned earlier about having, yeah, ownership on each part.
00:47:27.123 --> 00:47:32.884
'Cause if it's just too much, then obviously you are gonna, yeah, face challenges as a business
00:47:33.483 --> 00:47:35.614
I'm completely convinced of that, Ben
00:47:36.213 --> 00:47:44.103
Okay, so wh- so when you look at, say, organizations successfully creating value from AI, what are they doing differently to build trust and adoption?
00:47:44.704 --> 00:47:52.943
I, th-three big things, and I-I'm, I'm afraid I'm gonna end up repeating some things I've said, so I'll try and be more succinct about it.
00:47:52.943 --> 00:47:58.574
But I think treating this as an operating model change and not a technology deployment at the start.
00:47:59.094 --> 00:48:04.603
Work and the accountability that comes with the choices we're making is getting redesigned.
00:48:05.233 --> 00:48:08.034
We're not doing component replacement.
00:48:08.063 --> 00:48:15.153
We're not picking the biggest friction generator or the biggest error generator in the process and replacing that.
00:48:15.153 --> 00:48:24.224
We're actually thinking about how work gets done with AI enablement end to end.
00:48:24.643 --> 00:48:29.684
So that's an operating model change, and that comes with rewrite of job descriptions.
00:48:29.684 --> 00:48:32.414
It comes with the creation of new job descriptions.
00:48:32.414 --> 00:48:35.864
I mentioned this idea of a dedicated content curator.
00:48:35.873 --> 00:48:39.403
Not a lot of places have that as a dedicated role yet.
00:48:40.123 --> 00:48:56.873
So the operating model change is gonna make us think about how work actually gets done and which skills or which sets of duties as a defined role need to be reinforced or introduced.
00:48:57.523 --> 00:48:58.103
That's one.
00:48:59.963 --> 00:49:15.713
Directly related to that, as I create those roles, my, my asset owner, one of my favorites, but this content curator, and then this idea of the subject matter expert as the validator, how are we staffing that?
00:49:15.713 --> 00:49:20.244
Because if we're staffing that as a part-time job probably not gonna work.
00:49:21.043 --> 00:49:25.893
I think about SMEs as validators as a really strong example of this.
00:49:26.324 --> 00:49:35.603
The non-deterministic nature means that validation often requires an expert to look at some sample and give an agreement rate.
00:49:36.414 --> 00:49:40.664
That's how we validate that the algorithm or the solution is performing well.
00:49:41.914 --> 00:49:54.643
That's an expensive thing to do in a couple ways but not the least of which is that there's a high opportunity cost for taking some expert out of their day job and having them play validator of an AI.
00:49:56.043 --> 00:50:00.054
And w- I think we have to rethink how we do that validation.
00:50:01.753 --> 00:50:23.534
That's-- So when I talk about staffing these, these duties, ownership and curation and validation as real jobs and not something that I do as a part-time by the way, that part-time assignment always shows up at the worst possible moment for that individual because they're probably really busy on something else.
00:50:23.574 --> 00:50:25.653
So how dedicated are they?
00:50:25.903 --> 00:50:27.173
How focused are they?
00:50:27.204 --> 00:50:28.923
Those things are gonna matter a lot.
00:50:30.844 --> 00:50:43.213
In my practice, the asset owner was, so valuable because the business thought of the asset owner as their agent inside the AI building shop.
00:50:44.603 --> 00:50:49.673
But the IT folks thought of that person as their inside agent on the customer side.
00:50:49.673 --> 00:51:10.134
And so that two-way, that two-way role is a trust and adoption mechanism by itself because it's building confidence in both the builders and the users because they each feel like they've got their advocate, the person who gets w- what their day is like in the middle of the loop.
00:51:10.204 --> 00:51:12.423
And so I feel like that one's really key.
00:51:13.233 --> 00:51:20.916
And then I mentioned this before, but I think the third answer is really Th- this idea of a blameless feedback loop.
00:51:20.985 --> 00:51:36.246
And so what I mean by that is we're hungry for feedback, and we're gonna treat the inevitable mistakes that are made not as, how do I hunt down who was responsible?
00:51:36.275 --> 00:51:44.306
But instead, th- these are how we're gaining our operational learning to reinvest back into the system.
00:51:44.356 --> 00:51:52.096
And I'm using the word system very deliberately because the foundation model is part of the system, but I don't have the ability to change that.
00:51:52.755 --> 00:51:55.715
The context layer is part of the system, I can change that.
00:51:56.695 --> 00:52:00.315
But also, how is the information being presented operationally?
00:52:01.135 --> 00:52:03.775
What policies have I put around user behavior?
00:52:03.775 --> 00:52:07.626
All of those things are available as part of the system.
00:52:08.045 --> 00:52:13.965
And when we make a mistake, how do we use that to upgrade those things?
00:52:14.675 --> 00:52:19.726
And we want to establish an appetite for that feedback.
00:52:19.726 --> 00:52:22.016
We're hungry for those observations.
00:52:22.806 --> 00:52:28.326
And if we react to those observations with,"Thank you very much.
00:52:28.815 --> 00:52:39.376
I'm now gonna use that to return that insight to the system," that is a flywheel for confidence building as well.
00:52:39.485 --> 00:52:48.755
And as long as we're behaving that way, then we're gonna encourage people to be very forthcoming with what they see, which is what we want.
00:52:48.755 --> 00:52:59.356
So I think operating model, staffing those duties as real jobs, and this idea of a blameless feedback loop, those are the three power moves in my opinion.
00:53:00.365 --> 00:53:02.755
Yeah, no, there's some good feedback there.
00:53:02.856 --> 00:53:19.476
So I guess for a practical takeaway I know you should provide some value, but if, say if a, a leadership team wanted to improve both trust and ROI from AI, I guess in the next sort of 90 days, three months what is the first meaningful action you'd encourage them to take?
00:53:20.076 --> 00:53:24.505
I think there's two things, and the first one is gonna come right back to where we started, which is trust.
00:53:24.505 --> 00:53:42.746
And so I would go to a business unit that has a deployed solution, an AI solution, and ask,"Do you believe in it?" And be very prepared for an honest answer, which is not really.
00:53:43.246 --> 00:54:22.945
I think that there's an illusion that says,"We built this thing, it took six weeks, we deployed it to a team of 200 people, and we've got a 20% increase in token usage among that population and believe I've achieved something." But if you go and interview the users and say,"Do you believe in this answer?" I think we should be prepared for many of them to say,"Not really." And so I would want a very honest assessment of my deployed solutions from that perspective.
00:54:22.956 --> 00:54:32.356
That's the first thing I would do And then the second thing I would do is maybe pick one where the answer was yes a lot, where people generally do believe in it.
00:54:33.726 --> 00:54:46.076
And then it would start to create that middle measurement layer between the token usage and am I seeing a metric that's really moving in the right direction?
00:54:46.076 --> 00:54:52.235
So if, I was an insurance guy, so am I seeing claim duration come down?
00:54:52.726 --> 00:55:00.126
Because I'm getting through my research tasks, I'm making a decision faster I'm resolving this thing sooner.
00:55:00.925 --> 00:55:09.065
So a- am I starting to see that manifest in a metric that really implies a change in the business outcome?
00:55:09.076 --> 00:55:11.306
So is it happening faster?
00:55:11.686 --> 00:55:15.146
Am I having a lower re- representment rate?
00:55:15.186 --> 00:55:20.826
I'm not reworking as many things as I used to, which would be more of a qualitative assessment.
00:55:21.255 --> 00:55:23.195
But the, but those are things you can measure.
00:55:23.686 --> 00:55:28.326
There's gonna be a lag between deployment, adoption, and those metrics changing.
00:55:28.726 --> 00:55:45.516
So that's why I say step one, go figure out which things you've deployed that people are confident in, and then pick one of those and see if you can't build that bridge between adoption and a business process outcome that I care about.
00:55:46.005 --> 00:56:08.996
And stay with that until, until I feel like I've got a story that we can express well and that we can defend and then build trust in my other solutions and repeat that process and start to generate a report card that says, back to the question you asked me earlier, like what's the chain?
00:56:09.735 --> 00:56:12.826
Trust, adopt, ROI.
00:56:13.735 --> 00:56:16.425
So step one, figure out what people trust.
00:56:16.525 --> 00:56:28.005
Step two, pick one they trust and start to build that adopt to ROI pathway, and then you'll have a great diagnostic tool that says,"I've got a trusted one I can't measure.
00:56:28.025 --> 00:56:29.365
Let me go work on measurement.
00:56:29.436 --> 00:56:34.295
I've got an untrusted one, not worth my time to measure it yet.
00:56:34.295 --> 00:56:44.585
I gotta go solve my trust problem." But if you inventoried your solutions from that trust perspective first, I think it'd give a pretty straight line roadmap for what you need to do next
00:56:45.186 --> 00:56:47.405
But I see, sure, I find it fascinating.
00:56:47.786 --> 00:56:53.615
I've seen, I've interviewed a lot of people on the podcast and I just, a lot of it is just down to people problems.
00:56:53.615 --> 00:56:58.735
It's like it's just seems like that's the hardest challenge for businesses.
00:56:59.846 --> 00:57:11.585
Look, I think human psychology is always- Yeah important for us to acknowledge and try our best to get an honest assessment of w- what, where we're starting from.
00:57:12.246 --> 00:57:20.686
And then trust comes from transparency, so bringing the right people in and having them truly participate.
00:57:20.706 --> 00:57:32.865
And in order to get them to truly to participate, I have to be willing to accept answers I don't like If I'm not willing to accept answers I don't like, people are probably not gonna tell me what I need to hear.
00:57:32.865 --> 00:57:45.675
So it really we get so fascinated, Ben, by the technology breakthroughs and so on, and I go, those things are great, but what's hard about this is still back to what I said.
00:57:45.675 --> 00:58:05.846
At the end of the day, I'm asking someone to rewrite their job description, to use a tool they don't understand, to be accountable for the outcome anyway, and in the worst case, I may not even be giving them enough grace to learn the new tool and integrate it into their process without adjusting their report card.
00:58:05.846 --> 00:58:08.985
And those are really hard things to ask another person to do.
00:58:09.715 --> 00:58:16.425
And I have almost never failed to build a solution because the data was too hard.
00:58:17.246 --> 00:58:18.766
Technology has never been a gap.
00:58:20.596 --> 00:58:26.565
Convincing a human to do their job differently has always been the hardest part, and I think that will stay true for a very long time.
00:58:28.416 --> 00:58:28.666
Yeah.
00:58:29.525 --> 00:58:30.246
Okay, brilliant.
00:58:30.315 --> 00:58:31.936
No I've enjoyed the conversation.
00:58:32.005 --> 00:58:38.635
And I guess, so if anyone wants to continue the conversation with you, is it best to connect with you on LinkedIn?
00:58:39.085 --> 00:58:40.235
Yes, definitely.
00:58:40.235 --> 00:58:40.565
Okay, perfect.
00:58:40.565 --> 00:58:46.226
And I would I would be delighted to follow up with anybody who's listening and wants to go deeper on any of this.
00:58:46.726 --> 00:58:46.896
Amazing.
00:58:46.896 --> 00:58:47.536
Yeah, like I said, I'll...
00:58:47.706 --> 00:58:49.166
I can I'll put, I'll add your LinkedIn to the podcast.
00:58:49.766 --> 00:58:53.195
And also if anyone wants to connect with Paul, just, yeah, please do reach out to me.
00:58:53.856 --> 00:59:00.226
And yeah, finally, Paul, it's been a pleasure having you on the podcast, and you've provided some great advice and knowledge.
00:59:00.896 --> 00:59:02.996
I'm so glad you invited me to do this, Ben.
00:59:03.025 --> 00:59:05.456
I'm really grateful for the time and the conversation.
00:00:00.000 --> 00:00:10.619
we're asking people to essentially rewrite their job description using a tool that they don't fully understand, but they're still accountable for what happens.
00:00:11.650 --> 00:00:18.820
And the opaque nature of AI makes that a pretty steep hill to climb.
00:00:19.859 --> 00:00:31.329
I mentioned before that at the end of all of this, we're asking someone to rewrite their job description, which is a bit of a leap of faith and what we need to do is we need to turn that leap of faith into more of a hop of faith.
00:00:32.750 --> 00:00:40.090
Confidence and correctness are two different things, but we aren't always great at noted-- knowing the difference.
00:00:41.549 --> 00:00:44.289
Traditional software fails loudly, right?
00:00:44.310 --> 00:00:46.810
You have a bug, it causes a problem.
00:00:47.189 --> 00:00:49.060
It's usually pretty noticeable.
00:00:49.659 --> 00:00:53.340
AI, I'm gonna say, fails with a straight face.
00:00:54.020 --> 00:00:56.670
It always sounds confident, even if it's making things up.
00:00:57.369 --> 00:00:58.829
Trust yields adoption.
00:00:59.000 --> 00:01:01.250
Adoption yields confident users.
00:01:01.509 --> 00:01:03.439
Confident users create ROI.
00:01:03.439 --> 00:01:04.359
I think that's the path.
00:01:15.248 --> 00:01:16.299
Hello, everybody.
00:01:16.399 --> 00:01:21.528
I'm your host, Ben Parker, and welcome back to Data Analytics Chat.
00:01:22.248 --> 00:01:28.588
Today, we're going to be talking about something almost every organization wants from AI, the magic value.
00:01:29.308 --> 00:01:37.778
Companies are investing heavily in AI, obviously launching new tools, running pilots, but investment alone doesn't guarantee ROI.
00:01:38.528 --> 00:01:46.179
One of the biggest questions is whether people actually trust the technology enough to use it, rely on it, and obviously, change the way we work.
00:01:46.638 --> 00:01:51.748
So today, we're gonna explore the relationship between trust, adoption, and ROI.
00:01:52.569 --> 00:01:54.539
Joining me is Paul Drennen.
00:01:54.858 --> 00:01:55.728
Welcome, Paul.
00:01:56.438 --> 00:01:57.569
Hi, glad to be here.
00:01:58.638 --> 00:01:58.998
Cool.
00:01:59.049 --> 00:02:04.118
I guess before we dive in, do you wanna give the listeners a quick introduction to who you are?
00:02:05.478 --> 00:02:05.989
Yeah, sure.
00:02:05.989 --> 00:02:07.009
I'll keep that brief.
00:02:07.058 --> 00:02:29.109
I have recently retired from my corporate career after about 30 years of building analytics and AI practices in a number of industries, most recently in insurance, and now interested in helping people navigate the change and understand what it takes to really be successful.
00:02:29.158 --> 00:02:33.739
And I'll say that after all that time, the, the main lesson for me is...
00:02:35.038 --> 00:02:49.908
and you already hinted at it, Ben, the data is always gonna be a challenge, but the real work is in building trust with users, and then once you've got that trust, how do you keep that trust once they've integrated the solution into their work process?
00:02:49.908 --> 00:02:51.908
So that's really what I'm about.
00:02:52.508 --> 00:02:53.739
Oh, I I'll see you touched on that.
00:02:53.899 --> 00:02:56.038
So why do you think it is trust is the issue?
00:02:56.038 --> 00:03:03.079
Is it just lack of like data literacy or is it just change?
00:03:03.118 --> 00:03:04.718
What do you think is the sort of key component
00:03:06.378 --> 00:03:06.438
here?
00:03:06.438 --> 00:03:08.989
There's a number of different factors going on.
00:03:08.989 --> 00:03:09.968
You mentioned literacy.
00:03:09.989 --> 00:03:34.699
I put that pretty high on the list that people's awareness of what's going on inside these algorithms and these platforms that have been created isn't very strong, and we're asking people to essentially rewrite their job description using a tool that they don't fully understand, but they're still accountable for what happens.
00:03:35.729 --> 00:03:42.899
And the opaque nature of AI makes that a pretty steep hill to climb.
00:03:43.938 --> 00:04:20.709
And if we don't climb it and we don't get that trust from the user, there is gonna be hesitation and at a certain point, every time it makes a mistake, there's a bit of a scorecard that's being kept by individuals and again, that the fact that people are still responsible for the outcome means that they really want to believe in the tools that they're using, and creating that transparency and trust is difficult when the algorithms are opaque and analytical literacy isn't always the highest
00:04:21.309 --> 00:04:23.129
I guess so look, let's focus on trust.
00:04:23.209 --> 00:04:31.899
So c- companies now are investing more and more in AI, but I guess still struggling to create meaningful value from it.
00:04:32.658 --> 00:04:35.519
How much of that problem comes down to trust itself?
00:04:37.483 --> 00:04:50.862
I think most of it, honestly, the investments that are being made right now are primarily in building and establishing the platforms and hiring the engineering talent.
00:04:51.903 --> 00:05:04.642
Those things are important, but the cost of AI, and I'm gonna be inclusive here, Ben, of traditional AI as well as these frontier model-based tools.
00:05:05.923 --> 00:05:07.442
The cost was never in the build.
00:05:07.612 --> 00:05:22.023
It was always in the maintenance of it and the monitoring and the drift detection and the repair that hap- has to occur, and that was always where most of the effort was.
00:05:22.973 --> 00:05:37.892
And now with these frontier models and the fact that they're not deterministic in their outputs, trust maintenance is actually harder than it used to be, and the skills required to do validation are...
00:05:39.413 --> 00:05:40.463
They're not widespread.
00:05:41.122 --> 00:05:46.872
There's a high opportunity cost to using your subject matter experts to test the AI's output.
00:05:47.632 --> 00:06:05.913
So I feel like the disconnect is everyone is chasing the technology and wanting to make sure that they are on pace with the world and that they've got the right tools and platforms and talent, but building an AI is not that hard.
00:06:06.682 --> 00:06:26.372
Owning one that you're proud of in the future takes a lot more effort, and that disconnect, I think, shows up in the high cost of development today, but the relatively low rates of adoption and and consequently impact on business processes.
00:06:27.752 --> 00:06:28.033
Yeah.
00:06:28.033 --> 00:06:35.302
So what you're saying is it's a lot of emphasis on more the, the technology instead of like people that actually build it.
00:06:35.302 --> 00:06:36.923
'Cause I guess now you...
00:06:37.452 --> 00:06:40.593
I guess the value you're gonna get is people that actually know the domain.
00:06:40.843 --> 00:06:43.442
'Cause obviously you've got the technologies there now, isn't it?
00:06:43.442 --> 00:06:44.583
It can do a lot of the heavy lifting.
00:06:44.853 --> 00:06:50.882
It's actually g- I guess having the, being the middle person to actually under- I guess blend it all together.
00:06:50.882 --> 00:06:54.083
Is that do you think where businesses should get more value from?
00:06:54.093 --> 00:06:54.103
I
00:06:55.072 --> 00:06:55.452
do.
00:06:55.483 --> 00:07:15.523
I think we're treating this AI emergence primarily as a technology deployment, and I think it's really more of an operating model change and the focus on the creation of AI you certainly have to do that, but value isn't created when I build it.
00:07:15.543 --> 00:07:25.872
Value is created when I deploy it, and in my definition, deployment means I have a set of confident users who have now integrated it into how they do their job.
00:07:26.607 --> 00:07:28.127
And that's where the value gets created.
00:07:29.127 --> 00:07:40.536
And so much of the distance between a f- a, a frontier model which is becoming highly commoditized now, and we're all renting the same models from the same vendors.
00:07:41.276 --> 00:07:45.047
So there's nothing very distinctive about what's happening in the LLM.
00:07:46.047 --> 00:07:57.747
All the distinction is happening in the rules and the wisdom and the experience and the judgment, those things that our best operators, our best decision-makers have.
00:07:58.607 --> 00:08:07.526
And how do I encode that so that the frontier model and that context layer are partnering well?
00:08:09.057 --> 00:08:11.966
And if I do that, I'll earn trust.
00:08:11.997 --> 00:08:14.396
And if I don't do that, I won't.
00:08:14.396 --> 00:08:19.476
And if I don't earn trust, I'm not gonna sustain a population of confident users for very long
00:08:20.076 --> 00:08:22.076
So obviously you're highly regarded in the market.
00:08:22.137 --> 00:08:25.286
I spoke to many people that, yeah, really rate you, I'll be honest.
00:08:25.377 --> 00:08:32.897
What, what happens where before employees or leaders become comfortable reliant on AI as part of their day-to-day work then?
00:08:34.677 --> 00:08:51.756
So this is a big question, and I think there's a number of things, and I often use a gardening analogy where I think about I have to prep the soil, I have to plant the seeds, I have to nurture them, I have to keep the weeds out.
00:08:51.797 --> 00:08:56.767
I have to do all these things and so this preparation is important.
00:08:57.996 --> 00:09:09.466
I mentioned before that at the end of all of this, we're asking someone to rewrite their job description, which is a bit of a leap of faith and what we need to do is we need to turn that leap of faith into more of a hop of faith.
00:09:10.836 --> 00:09:17.027
And so some specific ways that I have used that have been successful is a couple things.
00:09:17.057 --> 00:09:26.096
So one seems obvious, but you wanna have the users and the builders co-invent the solution.
00:09:26.716 --> 00:09:45.442
When the user feels like they've had equal authorship over what's being built, then their path to adoption is much easier the models are opaque, but you can make many of the moving parts as transparent as possible.
00:09:45.442 --> 00:09:52.893
And so you want to make the system visible and transparent so that people understand how it works.
00:09:52.893 --> 00:10:02.442
There's a moment where the algorithm is gonna do something that's difficult to describe, but before and after that, we can make things very transparent.
00:10:03.842 --> 00:10:19.232
I got a lot of usage and value out of what we called the, the blind acceptance test, where we would score something and then show it to our experts without telling them what the model had said, have them reach their conclusion, and then reveal how the model compared to that.
00:10:19.232 --> 00:10:30.273
And, if you're lucky, it performs very well, and if not, then you iterate until you get to a point where the user believes in the quality of the outcome.
00:10:31.363 --> 00:10:46.842
And then the last piece, which I think is really important, and I'll probably say this more than once while we're chatting, once I've built it I really have a lot of duties that come with ownership, and AI is going to drift.
00:10:46.852 --> 00:10:48.403
It's trained on the past.
00:10:48.883 --> 00:10:50.253
The future will look different.
00:10:50.753 --> 00:11:00.592
As that difference widens, the confidence we have is going to erode, and you have to watch it, and you have to repair it.
00:11:01.283 --> 00:11:08.673
And I believe that at a certain point, as a user, I wanna know who's accountable for that activity.
00:11:08.722 --> 00:11:12.972
So I wanna know who is watching and who is going to take action when it drifts.
00:11:13.623 --> 00:11:21.202
Because without that warranty, the drift is accumulating, and it's happening invisibly.
00:11:21.393 --> 00:11:25.072
And at a certain point, I'm gonna start getting answers that don't make sense.
00:11:25.572 --> 00:11:28.822
And once trust is lost, it is very difficult to retain.
00:11:29.312 --> 00:11:33.863
So those are the things I think you have to bring people in.
00:11:33.863 --> 00:11:35.722
You have to create transparency.
00:11:36.273 --> 00:11:47.972
You have to put everything on display that you can, and there needs to be that warranty that says,"We're not just gonna build it and chuck it over the wall and hope for the best.
00:11:47.972 --> 00:12:11.613
We're gonna stand behind this." So I summarize all that in, in my practice as the safe to own promise, which is more comprehensive than a safe to buy promise because, as I said before, the real effort is in the long-term trust maintenance and ownership of these assets, and so a safe to own promise comes with those things.
00:12:13.222 --> 00:12:13.452
Yeah.
00:12:13.452 --> 00:12:23.893
So I'm guessing s- we need leaders to be good coaches, really, to do this constant education for inhe- or I guess helping people understand AI really then?
00:12:24.493 --> 00:12:26.873
Yes and we're all on a learning curve together.
00:12:26.873 --> 00:12:32.682
Even the professional data scientists are having to climb a learning curve with these new tools.
00:12:33.092 --> 00:12:37.352
So acknowledging that we're all learning together I think is an important fact.
00:12:38.533 --> 00:12:55.592
And a willingness to try, a tolerance for the iterations and cycles as we calibrate, and then studying how the machines are built, what they're good for, what they're not good for.
00:12:56.263 --> 00:13:08.923
I think inoculating ourselves a bit from the hype so that we can navigate more practically all of those things and leadership has to not only sponsor that, but actively participate in that
00:13:09.523 --> 00:13:21.633
So then obviously looking at technology c- can a AI system be, like, technically excellent but still fail to create value because people simply do not trust or adopt it?
00:13:23.133 --> 00:13:23.633
Totally.
00:13:23.732 --> 00:13:25.013
I've seen that before.
00:13:25.013 --> 00:13:41.623
And before, before the current frontier model-based AI in my own practice, one of the things I've talked about monitoring, so we paid a lot of attention to the shape and value of the data that was feeding the algorithm that we had trained.
00:13:42.182 --> 00:13:47.582
We spent a lot of time monitoring its outputs against references.
00:13:48.202 --> 00:14:01.682
But we also added a we called it an engagement rate, which said how often is the user agreeing with what the model is recommending, and we trended that over time.
00:14:02.113 --> 00:14:15.332
And what I have seen is models aren't perfect, and so every now and then they're going to recommend something that the user disagrees with and if the user is anxious about it, they're probably keeping score.
00:14:16.102 --> 00:14:24.702
And at some point it's gonna give them an untrustworthy response one time too many, and at that point you're gonna lose their confidence.
00:14:25.432 --> 00:14:39.942
And so I have seen algorithms that were performing well, the monitoring results were strong, but where I was losing the confidence of the user, and that will end value creation just as much as a model that has gone off target
00:14:40.543 --> 00:14:45.052
So would these, is changing behavior sometimes harder than actually building the technology, Tim?
00:14:46.373 --> 00:14:49.133
I think that is the hardest part of the job, honestly.
00:14:49.133 --> 00:14:50.692
You have to earn trust.
00:14:50.692 --> 00:14:54.682
You have to convince someone,"Here's what's really happening.
00:14:54.692 --> 00:14:56.312
I'm building a tool for you.
00:14:56.722 --> 00:14:59.003
I'm asking you to rewrite your job description.
00:14:59.423 --> 00:15:06.763
I can't fully expose exactly how the tool works." That is a difficult request And Yeah.
00:15:06.812 --> 00:15:31.562
That's just a really difficult request, and if I don't manage that part, the psychology part of it well, and I don't convince my users that I'm standing behind it, I'm gonna guard their commitment and keep, ke- keep earning the trust that they've given, then I risk losing that trust.
00:15:31.562 --> 00:15:34.072
And as I said before, once it's gone, it's very hard to get back.
00:15:34.673 --> 00:15:37.812
So what are the biggest things that cause people to lose trust in AI?
00:15:38.413 --> 00:15:43.503
Accumulation of wrong answers that they are still accountable for would be at the top of the list.
00:15:44.783 --> 00:15:51.062
And look, I was doing AI before the frontier models, and we had algorithms that were deterministic.
00:15:51.092 --> 00:15:59.613
So I would put the same inputs in, I would get exactly the same output out, and trust building and trust maintenance was the hardest part back then.
00:15:59.613 --> 00:16:04.753
And now you've got algorithms where the same input can generate a different answer.
00:16:05.442 --> 00:16:13.793
And so that, that breadth of what is it gonna say this time, I think creates a, a, a bigger trust barrier.
00:16:14.692 --> 00:16:31.982
And as the answers come through and as that variance accumulates, it's not only that I disagree, it's the unpredictability of it that can be a real threat to my confidence
00:16:32.582 --> 00:16:32.952
Okay.
00:16:33.673 --> 00:16:36.352
Then I guess, AI can sound convincing even when it's wrong.
00:16:37.543 --> 00:16:37.753
Yeah.
00:16:38.173 --> 00:16:43.582
And, yeah, And AI, it can produce answers that sound extremely convincing even when they're wrong.
00:16:43.653 --> 00:16:49.893
And so I guess how should organizations manage that risk without making people afraid to use the technology?
00:16:51.793 --> 00:16:59.133
Confidence and correctness are two different things, but we aren't always great at noted-- knowing the difference.
00:17:00.592 --> 00:17:03.332
Traditional software fails loudly, right?
00:17:03.352 --> 00:17:05.853
You have a bug, it causes a problem.
00:17:06.232 --> 00:17:08.103
It's usually pretty noticeable.
00:17:08.702 --> 00:17:12.383
AI, I'm gonna say, fails with a straight face.
00:17:13.063 --> 00:17:15.712
It always sounds confident, even if it's making things up.
00:17:16.413 --> 00:17:24.583
And in most business contexts, we're gonna, we're gonna manage the context layer so that the ability to just make things up wholesale is very controlled.
00:17:24.593 --> 00:17:30.913
But even when it starts to drift off target, it's always gonna sound sure of itself.
00:17:31.833 --> 00:17:39.282
So I would say the, the fix is not we have to condition everyone to be nervous or afraid.
00:17:39.742 --> 00:17:42.452
You have to design safety into your system.
00:17:43.163 --> 00:17:51.903
And so again, this, this idea of ownership and warranty is, I think, central to the answer here.
00:17:53.143 --> 00:18:12.133
I really need somebody dedicated to context curation, not a part-time job, somebody who is familiar with the domain but also understands what it takes to teach the context layer what the truth is.
00:18:13.542 --> 00:18:27.692
Validation cycles with your subject matter experts, not as an ad hoc or crisis response, but as a planned workforce capacity, a protected duty that you build into the way you think about staffing.
00:18:29.403 --> 00:18:32.212
I, I created a job family years ago.
00:18:32.212 --> 00:18:36.022
It was one of the smartest things I ever did that we ultimately called an asset owner.
00:18:36.022 --> 00:18:51.282
But think of this person as a, a combination of the best sales engineer you've ever met, the best scrum master release train engineer you've ever met, but they own the solution.
00:18:51.702 --> 00:19:02.653
And note, I'm not saying the model, I'm saying the solution because the solution often has multiple components, but they own it and they're accountable for its performance.
00:19:02.653 --> 00:19:06.042
They're accountable for how the trend is going.
00:19:06.042 --> 00:19:09.952
They're accountable for scheduling repair sessions in.
00:19:11.613 --> 00:19:16.772
And then the last piece I'll point is, you don't wanna, you don't wanna scare people.
00:19:17.123 --> 00:19:25.202
You build those controls and you build that visibility into the full life cycle And then you invite scrutiny.
00:19:25.202 --> 00:19:37.673
You ask your users to give you honest feedback and then you have to respond to that hon- honest feedback with gratitude rather than defensiveness, because you want to encourage that honest feedback.
00:19:38.593 --> 00:19:48.563
And if we all understand that every tool we're building is on an evolutionary path, it's not perfect, it's gonna get better.
00:19:49.002 --> 00:19:53.863
If I don't watch it, it could get worse, but ideally we're gonna pay attention and we'll make it better.
00:19:54.673 --> 00:20:21.252
So there are gonna be issues, and you wanna have that combination of ownership in- invitation of expert validation, invi- invite scrutiny and feedback, and you wanna respond to the challenges with gratitude and a commitment to learning from those challenges and investing those learnings back into the solution so that it evolves in a positive direction
00:20:23.222 --> 00:20:23.286
Okay.
00:20:23.286 --> 00:20:23.348
Good.
00:20:23.348 --> 00:20:26.840
I like the, obviously, yeah, the outcome focus,'cause, yeah, that's...
00:20:27.171 --> 00:20:30.411
Enda, you wanna be progressing, don't you?
00:20:30.590 --> 00:20:32.340
You want it to be running efficiently.
00:20:33.080 --> 00:20:33.800
So I guess, how would you...
00:20:34.631 --> 00:20:43.080
how should organizations encourage people to use AI while also making sure they continue to question its outputs when necessary?
00:20:45.050 --> 00:21:03.080
One of the trends that I see happening, and I'm not a fan of, is this kind of enterprise forcing function on AI that says,"30% of your code has to be generated by AI," or,"X percent of your work has to use it." I'm not a big fan of that.
00:21:03.830 --> 00:21:13.681
The future says, Paul's opinion, but I've said this out loud more than once, every job family is going to be AI-enabled in the future.
00:21:14.270 --> 00:21:25.990
So we want people to have hands-on experience, and we want them to start getting comfortable with what it's good for, what it's not good for, how do I get the best performance out of it?
00:21:26.000 --> 00:21:27.221
We want those things.
00:21:28.250 --> 00:21:35.510
But applying pressure to people to hit contrived milestones, I don't think is the answer.
00:21:36.111 --> 00:21:38.631
And you wanna have...
00:21:40.621 --> 00:21:45.421
we can't eliminate the human judgment, which is where the value's created.
00:21:45.421 --> 00:21:52.530
So I said that before, and I'll repeat it, like what's encoded in the front- frontier model is a commodity now.
00:21:53.191 --> 00:21:54.441
That's not where the value comes from.
00:21:54.441 --> 00:22:31.651
It comes from the wisdom of the people who have been doing this and have learned what works well, and you wanna get that embedded into a system where AI is a piece of the system, but AI is empowering the human to make better choices we had a lot of conversation about this, and one of the things that I actively championed was an enterprise-wide literacy campaign to get people hands on keyboard, but not just go try it, but to orient our entire workforce to how it works.
00:22:32.181 --> 00:22:37.270
Not down at the level of weights and biases and deep learning training.
00:22:37.300 --> 00:22:39.260
We don't need to go that deep.
00:22:39.320 --> 00:22:54.931
But what is it doing, and how do you influence the path it's following so that you can stay on target and not not get the hallucinations and those types of things?
00:22:55.621 --> 00:23:18.770
So I'm gonna say practical user literacy, not necessarily deep engineering or science literacy, and I felt like that was an important factor in starting to take the mystery and reduce that, black boxiness of it to where people felt like I understand how I can apply this now.
00:23:19.250 --> 00:23:27.361
And any program that does not take on the literacy challenge, I think, is just making the slope of the hill they have to climb steeper.
00:23:29.070 --> 00:23:29.441
Yep.
00:23:30.121 --> 00:23:32.641
You touched on an interesting point about human judgment then.
00:23:33.240 --> 00:23:41.780
So obviously, as organizations are automating more decisions with AI, where do we balance the...
00:23:41.961 --> 00:23:43.661
Where should human judgment remain?
00:23:44.480 --> 00:23:45.931
Do you think that's the challenge now?
00:23:46.530 --> 00:23:48.631
I think we're all still trying to figure out.
00:23:48.661 --> 00:23:52.780
We all understand and believe that human judgment is critical.
00:23:53.760 --> 00:23:54.980
Where does it show up?
00:23:55.050 --> 00:24:11.060
How do I integrate the tools and the judgment in a, a graceful way so that work gets done efficiently and we're proud of the output no one's asking the human to outperform the model at what the model was designed to do.
00:24:11.941 --> 00:24:22.371
One of the things that we implemented, and I think this was the right decision, was and honestly, this predated even the generative AI emergence.
00:24:24.060 --> 00:24:28.851
We only let systems have the authority to approve things.
00:24:29.790 --> 00:24:33.060
We never allow the system to automatically deny things.
00:24:34.951 --> 00:24:38.540
And I do think that as a hard rule was a smart one.
00:24:39.851 --> 00:24:48.800
I'm also a big fan of this idea that most of these solutions now, as I mentioned, are a combination of a frontier model and a context layer.
00:24:49.651 --> 00:25:08.820
And so investing deeply in how do we build, how do we sustain, how do we nurture, how do we clear the rot out of the context layer as a dedicated assignment, as a protected part of our workforce?
00:25:09.730 --> 00:25:21.711
If you do that well, then you really get the human in the loop at the foundation of your context layer, and that's where that judgment, it just flows all the way through the life cycle if we do that well.
00:25:22.300 --> 00:25:34.461
If we naively just grab a bunch of documents from a library and embed them or ingest them in a wiki or something like that, we run the risk of there being contradictions in that.
00:25:35.601 --> 00:25:36.911
It's drifting over time.
00:25:37.480 --> 00:25:49.260
The hum-- for me, the human in the loop adds a ton of value if I embed that very deeply at the front of this whole life cycle in the way we build and manage context.
00:25:51.090 --> 00:26:00.330
Then we allow the agents to be strong and have authority over easy yes outcomes.
00:26:00.691 --> 00:26:16.260
We don't let them have the complicated no outcome, and we engage the human judgment when things are ambiguous or if I'm making a decision that I'm gonna have to defend later.
00:26:16.861 --> 00:26:26.641
And so for me, human in the loop, human judgment, really powerful at the foundations of knowledge and in the ambiguous cases.
00:26:26.681 --> 00:26:29.461
That's where I think that's going to land.
00:26:30.711 --> 00:26:51.721
And I'll say it in just summarizing all of this, everything we've talked about so far, just one of the things that, that I said to my executive team and my board of directors is, at the end of the day, we wanna be proud of what we did, not just the day after we did it, but three years from now, I still wanna be proud of this thing that we created.
00:26:51.851 --> 00:26:54.760
And that's the kind of final exam score on all of this
00:26:55.361 --> 00:26:55.691
Yep.
00:26:56.260 --> 00:27:05.080
No, I agree, like I said, that you wanna, you want fa-- like you, it gets, you, if you get more value out of it, there's-- things are gonna, it's constantly gonna evolve, isn't it?
00:27:05.131 --> 00:27:10.340
So you need to keep building and it's obviously, it's one of them tools, isn't it?
00:27:10.351 --> 00:27:12.740
Technology where you need constant development on it.
00:27:13.181 --> 00:27:18.121
But yeah, you need, like you said, you need to be actually getting value from it so you...
00:27:18.520 --> 00:27:25.421
It's not every time you gotta start projects again or,'cause it's just, that's, obviously that's where a lot of the investment's gonna go, isn't it?
00:27:26.530 --> 00:27:33.371
It is, and I think one of the, one of the things that we're all wrestling with is our familiarity with traditional software.
00:27:33.911 --> 00:27:45.131
And this feels so similar in a lot of ways that there's this sense of this is just a, an extension of what I'm familiar with.
00:27:45.191 --> 00:27:48.090
And I think superficially there's a lot of truth in that.
00:27:48.300 --> 00:27:58.911
But where it gets different is that in traditional software, I wrote a bunch of logic and the same activities produce the same outcome every time.
00:27:59.621 --> 00:28:05.580
And so I could have a team of people who built software, and then I could have a totally different team of people who maintain software.
00:28:06.290 --> 00:28:12.191
And and with AI, building is not where the hard part is, it's in the maintenance.
00:28:12.840 --> 00:28:16.320
And that is under constant daily threat of drift.
00:28:16.340 --> 00:28:20.310
And you have to know it, you have to recognize it, you have to repair it.
00:28:20.891 --> 00:28:25.211
You have to re-credential the solution with your users over and over again.
00:28:25.211 --> 00:28:33.151
And that part is very different And it forces you to think about your workforce and your capacity and the conversation you're having with users.
00:28:33.151 --> 00:28:41.171
It forces you to think about that very differently, which is why I said earlier the illusion that this is technology is, I think, strong.
00:28:41.171 --> 00:29:00.201
But honestly, in my opinion, this is an operating model change, and it-- in a lot of ways, it's forcing us to pay more attention and to be more deeply engaged with our users than we've ever had to be before, which I think is a challenge, but also a really positive thing
00:29:00.800 --> 00:29:00.810
Yeah.
00:29:00.810 --> 00:29:02.443
No I agree with you on the operating operating change'cause, it's...
00:29:02.443 --> 00:29:05.304
You're embedding it across the whole business now, isn't it?
00:29:05.304 --> 00:29:09.544
It's just AI's, yeah it's critical for every business now.
00:29:09.544 --> 00:29:13.114
Every bus- every department wants as a business use case now, doesn't it?
00:29:13.134 --> 00:29:16.618
So I think it's, you're fl- flipping your business upside down, aren't you?
00:29:16.618 --> 00:29:17.598
And building again.
00:29:18.729 --> 00:29:19.138
Yes.
00:29:20.479 --> 00:29:24.048
So listen, I want to talk about trust, adoption, and ROI.
00:29:24.249 --> 00:29:29.898
So what's the relationship between trust, adoption, AI for an organization so it's, from AI?
00:29:31.578 --> 00:29:38.679
So I think it's a chain that runs in one direction, and if I don't have trust, I'm gonna struggle with adoption.
00:29:39.608 --> 00:29:47.138
If I don't get adoption, I'm not gonna get an ROI, and it doesn't really matter how great the algorithm or the tool we've built is.
00:29:48.048 --> 00:29:51.108
So you really have to start with trust.
00:29:51.989 --> 00:29:52.759
You have to earn it.
00:29:53.669 --> 00:30:03.028
You have to gain confident users, and then you have to protect the decision they've made to adopt over time.
00:30:03.959 --> 00:30:14.118
And as you do that, and as confidence grows, they'll integrate the tool into the way they do their job more and more deeply, and that's when the ROI will start to show up.
00:30:15.519 --> 00:30:27.979
And I mentioned this idea of a final exam grade and so I'm gonna say, my opinion, the final exam grade is not that I got a 30% productivity number, it's did they adopt it and were they still using it the same way or more a year from now?
00:30:27.979 --> 00:30:28.169
And if that is true, I'm gonna get the productivity numbers, but I'm also gonna keep the productivity numbers.
00:30:28.169 --> 00:30:34.489
And so I think there's a little shortsightedness at times where we set a target, and we work really hard, and we get to that target, and we declare victory, and we move on.
00:30:34.489 --> 00:30:39.669
And what I'm saying is, I want confident users more than anything else.
00:30:41.348 --> 00:30:54.709
I think having a set of confident users is far more valuable than a bunch of solutions and models that I, hit some target number on a report card.
00:30:55.429 --> 00:30:56.469
And the recap.
00:30:57.308 --> 00:30:58.769
Trust yields adoption.
00:30:58.939 --> 00:31:01.189
Adoption yields confident users.
00:31:01.449 --> 00:31:03.378
Confident users create ROI.
00:31:03.378 --> 00:31:04.298
I think that's the path.
00:31:05.409 --> 00:31:07.759
And if I lose trust, the whole thing collapses
00:31:08.358 --> 00:31:13.469
So do you think, everyone has a goal if they wanna get A to B.
00:31:13.499 --> 00:31:19.618
So do you think op- adoption is the missing link between AI investment and business value?
00:31:19.669 --> 00:31:21.739
'Cause,'cause it's...
00:31:21.759 --> 00:31:23.209
Adoption is the hard bit, isn't it?
00:31:23.269 --> 00:31:24.648
It's just you cha- if you're...
00:31:24.729 --> 00:31:35.959
Whenever you're going through a change journey, you are, like I said, you've gotta build trust with people, you've gotta do the change management piece, which is obviously changing people.
00:31:36.449 --> 00:31:37.749
Do you think that's the...
00:31:38.398 --> 00:31:40.118
Adoption is the hard bit for businesses?
00:31:41.528 --> 00:31:46.219
I do, but I would modify it, Ben, only to say I think it's sustained adoption.
00:31:46.338 --> 00:31:52.519
Because we can apply management pressure to a workforce to get them to hit a number on a report card.
00:31:52.519 --> 00:31:55.538
I want them to hit that number because they believe in it.
00:31:56.778 --> 00:31:58.009
I don't wanna give up.
00:31:59.568 --> 00:32:03.568
When management attention shifts s- somewhere else, I don't wanna go backwards, right?
00:32:03.568 --> 00:32:22.499
So it's really sustained adoption that matters And look it's hard to quantify some of these things, and we all want, a, a, a, a bunch of KPIs on a report card that I can generate and I can show to my leadership team on a quarterly basis and demonstrate the trend and so on.
00:32:23.219 --> 00:32:31.979
I understand why we all want this, but we're talking about people's belief systems and how that manifests in how they behave.
00:32:33.229 --> 00:32:36.429
The metrics are often a lagging indicator on belief.
00:32:38.028 --> 00:32:39.108
Belief is what I need.
00:32:39.108 --> 00:32:46.298
So I think we all have to be a little more comfortable with this isn't that easy to measure directly.
00:32:47.219 --> 00:33:00.949
But when I check in with my users and when I watch how they are engaging with the tools, how often they are agreeing with it, are they starting to abandon the use of it?
00:33:01.439 --> 00:33:09.298
Those things I think are how we measure whether people believe or not, and that's ultimately what's gonna be the most important.
00:33:11.189 --> 00:33:22.338
So how should leaders measure whether an AI initiative is creating business value rather than simply just cre- generating lots of usage or experiments?
00:33:22.939 --> 00:33:40.939
You certainly want some, some direct mechanical observations if you can get them what I don't think works is saying something like,"30% of your code has to be generated in AI." It's pretty easy for me to hit that target and have not really integrated the tool into how I do my job.
00:33:41.969 --> 00:33:43.148
So you have to be careful.
00:33:43.148 --> 00:33:49.939
I don't think usage measurement is going to translate into value very well.
00:33:51.019 --> 00:33:56.598
And we have lots of usage measurements out there because they're mechanically easy to produce.
00:33:56.598 --> 00:34:10.608
But I think that there's a gap between usage and value, and we're gonna have to pay more attention to engagement and how well has my workforce integrated the tool.
00:34:11.528 --> 00:34:13.199
I would put those higher on the list.
00:34:14.068 --> 00:34:21.898
And then I think we also have to accept that for a while it's going to be more qualitative than quantitative.
00:34:22.869 --> 00:34:27.898
And so on a qualitative basis, do my users trust it?
00:34:28.539 --> 00:34:34.579
And are they trusting it over time, back to my sustained confidence point those are the key things I think.
00:34:36.059 --> 00:34:36.918
Oh, interesting.
00:34:37.648 --> 00:34:49.179
What should organizations put in place across technology, data, governance, and people to build AI that employees and leaders are prepared to rely on?
00:34:50.668 --> 00:35:03.418
So I did a couple things that I think were pretty impactful and so you mentioned governance, and I will tell you that I had tried to rebrand governance internally to, to safe enablement.
00:35:03.918 --> 00:35:15.699
Governance often feels like friction and second-guessery, whereas safe enablement feels like an accelerator for me to get where I want to.
00:35:15.768 --> 00:35:31.458
So I I brought together a group of individuals who historically represented that risk of friction or that risk of the 11th hour challenge We all know and love them.
00:35:31.679 --> 00:35:34.289
I call this gr- group collectively the guardians.
00:35:35.739 --> 00:35:41.509
It's compliance, it's legal, it's procurement, it's risk management, it's architecture, it's security.
00:35:42.679 --> 00:35:45.458
To deploy a system, we have to gain their approval.
00:35:46.148 --> 00:35:52.389
And I brought the group together and I said I want you to join me on Team Yes.
00:35:52.699 --> 00:35:59.909
And Team Yes's job is to approve use cases and solutions, but not as a rubber stamp.
00:36:00.688 --> 00:36:03.028
I'm not asking you to abandon your duties.
00:36:03.028 --> 00:36:28.539
I'm asking you to help me encode what does it take so that you can say yes, because saying yes is what you wanna do." And so I think this shift from governance as a post-hoc inspection or evaluation, and instead invite that group to co-author the safe perimeter.
00:36:29.239 --> 00:36:52.438
And then as we got better and patterns started to emerge, we were able to document what that safe boundary set looked like, and use cases that were inside that safe boundary got approved without a lot of oversight, because we had already we had already published what the boundaries were.
00:36:52.509 --> 00:37:09.389
And that actually opened up the use case pipeline a great deal, and then the guardians could use their time and skill and wisdom to look at novel things, new use cases, new patterns, things we hadn't seen before, which is where they add the most value.
00:37:09.389 --> 00:37:25.358
So I'm gonna say on the governance side, excuse me, bringing the guardians in at the front of the process and having them co-author what I call that, that safe boundary set, that was really valuable.
00:37:26.518 --> 00:37:43.969
I've mentioned this idea of an asset owner before, and I do think that having a named person who owns the solution and is standing behind that safe to own promise over time is a great idea from an accountability and a visibility standpoint.
00:37:43.969 --> 00:37:52.829
It's also a confidence builder for users, and we've talked a lot about building confidence in users as really the, the key milestone here.
00:37:52.829 --> 00:37:57.438
And I think having that named asset owner was really valuable in that regard.
00:37:58.039 --> 00:38:10.048
Anything that we do in a repetitive way that can be engineered into the platform and the methodologies that we deploy is well worth doing.
00:38:10.068 --> 00:38:17.259
And, one of my taglines that we use was safety through design, not supervision.
00:38:17.798 --> 00:38:38.282
And so whether it's governance or technology, just taking recurring things and shifting left and being very deliberate about what they are, how they're supposed to work, what the safe approach is and engineering that into our systems and our methodologies I think that those are all really good things to do.
00:38:40.032 --> 00:38:48.722
And then on the data side, I'm gonna beat this drum really hard, Ben, but the context layer is where all of the value gets created.
00:38:48.722 --> 00:39:00.262
And so having dedicated, qualified, and protected capacity to manage the context is key.
00:39:01.521 --> 00:39:16.391
And so safety through design, not supervision, bringing the guardians in at the start of the life cycle, and really committing to that safe to own curation of context, those are the key moves, I think.
00:39:18.192 --> 00:39:26.681
So do you think that with projects before you ha- always had project coordinators to keep projects on t- task.
00:39:26.681 --> 00:39:35.244
Do you think that in data they need more, I guess p- like more people that do similar type of role that's got, obviously, to take the ownership, so they are like the glue.
00:39:35.304 --> 00:39:37.923
They make sure everything's gets the outcomes.
00:39:37.923 --> 00:39:40.233
Do you think that's what's missing or What do you think?
00:39:40.713 --> 00:39:45.344
Certainly when I made that a full-time job, it accelerated everything.
00:39:45.673 --> 00:39:51.623
And I'm gonna call back to this idea of the skills of AI have gotten much easier.
00:39:51.623 --> 00:40:06.344
The duties of AI have not, and in some cases, I think the duties of AI are actually more difficult now because of the non-deterministic nature of how the models work, and they're more opaque than they used to be.
00:40:07.184 --> 00:40:25.574
And so that, that accountability to not only get the, the solution over the finish line and deployed, but to stay with it throughout its life cycle and to safeguard its accuracy and be hungry for two things.
00:40:27.333 --> 00:40:34.614
As I gain operational experience, can I use that knowledge to improve my solution so that feedback loop gets created?
00:40:35.983 --> 00:40:45.353
And can I take this solution and reapply it to adjacent use cases so that I can multiply the value that was created?
00:40:45.353 --> 00:40:59.684
And, in the old, older traditional AI days, we did that but the trans- the transferability of the solutions was a little more brittle because, you had the trained algorithm.
00:41:00.653 --> 00:41:07.733
W- with a generative or agentic solution, we're orchestrating components, so there's a lot more fluidity.
00:41:07.764 --> 00:41:25.184
So this idea of I've deployed it, I'm standing behind it, I'm watching closely, I'm inviting feedback, I'm taking those learnings, I'm improving my algorithm, but I'm also looking for the nearest neighbors that I can reapply it to.
00:41:25.773 --> 00:41:28.164
If nothing else, the pattern can be reapplied.
00:41:28.164 --> 00:41:41.273
But in many cases, if I've invested in a deep context library on some domain, the ability to reapply that to a number of different solution opportunities is quite wide.
00:41:41.764 --> 00:41:49.764
But if that's not somebody's job, it's not gonna happen with the same speed or durability.
00:41:49.773 --> 00:41:50.074
It's...
00:41:50.094 --> 00:41:52.764
so I don't know, Ben you asked me a bunch of questions.
00:41:52.764 --> 00:42:00.934
I keep coming back to this idea of accountability for the context layer and its commitment to safe to own over time.
00:42:00.943 --> 00:42:05.224
These, these things end up being at the center of most of the questions you're asking
00:42:05.824 --> 00:42:06.123
Yeah.
00:42:06.123 --> 00:42:09.543
No, I think it's also once something's...
00:42:09.623 --> 00:42:12.293
once you build something, people wanna move on to the next project, don't they?
00:42:12.344 --> 00:42:15.023
It's just, just natural.
00:42:16.244 --> 00:42:16.543
People don't
00:42:16.724 --> 00:42:17.083
wanna do something new.
00:42:17.594 --> 00:42:22.063
I think that's one of the legacies of traditional software, and I'm not, I'm not-
00:42:22.063 --> 00:42:22.423
Yeah
00:42:22.543 --> 00:42:33.753
I'm not trying to beat up traditional software but we had matured the pipeline of traditional software to a point where you had dedicated builders and a different group of dedicated maintainers.
00:42:35.164 --> 00:42:42.023
And because drift was not the challenge in traditional software, it is in AI, that's the pattern.
00:42:42.023 --> 00:42:43.414
We all understand that pattern.
00:42:43.414 --> 00:42:45.043
We've all lived through that many times.
00:42:45.914 --> 00:42:47.704
But AI inverts that.
00:42:48.184 --> 00:42:49.974
Building is not challenging.
00:42:50.653 --> 00:42:56.324
Sustaining is very challenging, and we have to adjust to that.
00:42:56.373 --> 00:43:08.233
We ha- we have to factor that into how we think about who's involved in the build cycle, how do I create dedicated skill for maintenance?
00:43:08.333 --> 00:43:10.963
And I don't mean maintenance like just mechanical maintenance.
00:43:10.963 --> 00:43:15.764
There's certainly a piece of that, but it's this idea of trust and confidence maintenance.
00:43:16.974 --> 00:43:18.583
That's the really key job here
00:43:19.184 --> 00:43:31.094
So then I guess once AI is deployed, how should organizations continue testing and monitoring it so trust is maintained rather than just assumed?
00:43:32.853 --> 00:43:39.923
So this is gonna echo back to what I just said, but you have to treat an AI solution as a living system.
00:43:39.923 --> 00:43:43.304
It's going to drift every day.
00:43:43.594 --> 00:43:59.713
It's going to experience some level of microscopic damage to its logic, and if you aren't monitoring it and you don't have a regular repair mechanism, eventually it will drift too far and it will start to give you bad answers.
00:44:00.824 --> 00:44:04.713
And I've used the word drift a number of times, but let me just spend a minute defining it.
00:44:06.373 --> 00:44:11.594
There's a couple different sources of drift, and so one of those things is very much external.
00:44:11.603 --> 00:44:24.454
So if I'm building a, a pricing model for an insurance product, climate change, geopolitics, supply chain disruptions, these are external things.
00:44:24.454 --> 00:44:40.503
But what they mean is tomorrow looks different than the last 10 years because one of these things have gone in a different direction, and I have to know about it, and I have to make adjustments for it, and I have to layer that knowledge into my system.
00:44:41.264 --> 00:44:42.784
That's external drift.
00:44:43.574 --> 00:44:45.474
And then there's internal drift.
00:44:45.483 --> 00:44:59.264
So maybe we're going to market differently, or we've changed our appetite for risk, or we're applying different incentives to our workforce, which is gonna cause a shift in their decision-making process.
00:45:00.313 --> 00:45:13.764
Again, these all represent a difference in the future from the past, and my algorithms, whether it's a traditional AI or the foundation model, they're built on examples, past examples.
00:45:13.793 --> 00:45:22.534
And so that separation between the training data and current and future reality, that's drift.
00:45:23.244 --> 00:45:28.634
And so you have to watch for that, and there's several ways to do that.
00:45:28.643 --> 00:45:37.884
You can certainly, and you should, watch your data sources and pay attention to how the shape of your data is changing over time.
00:45:37.934 --> 00:45:41.514
My mix of product or my mix of geography is changing.
00:45:42.043 --> 00:45:45.103
The cost of repair of an automobile is changing.
00:45:45.114 --> 00:45:45.653
All these things.
00:45:45.653 --> 00:45:46.664
You have to watch that.
00:45:46.684 --> 00:45:49.393
That's really a, a data monitoring.
00:45:49.414 --> 00:45:55.213
But those data that are inputs to my solutions have to be watched.
00:45:55.813 --> 00:46:00.994
And then the other piece of this is- How frequently am I running my repair?
00:46:01.764 --> 00:46:08.443
Because if I can do microscopic repair missions, that's better.
00:46:08.483 --> 00:46:22.884
More frequent repair is better because the performance of my system is the average of its best day, the day after the model was deployed, and its worst day, the, the day that it has had the longest to drift.
00:46:22.893 --> 00:46:26.583
And quality of what I'm getting is somewhere in between.
00:46:26.643 --> 00:46:40.773
And so if I can shorten that window between when I notice it's drifting and when I adjust my algorithm, my performance of my overall solution is gonna be much improved.
00:46:40.773 --> 00:46:47.893
And so I think watching it and then engineering that detection and repair.
00:46:48.554 --> 00:46:59.773
And by the way to do that requires a commitment of capacity that's often at the expense of building the next new cool thing.
00:47:00.623 --> 00:47:19.193
And so that's where I come back to, like there is this idea of protected capacity, which is specifically protected to monitor and fix and improve my existing solutions with the same fervor as I put capacity against building the next new thing
00:47:19.793 --> 00:47:26.844
You know, and I'm guessing this all tie back to what you mentioned earlier about having, yeah, ownership on each part.
00:47:27.123 --> 00:47:32.884
'Cause if it's just too much, then obviously you are gonna, yeah, face challenges as a business
00:47:33.483 --> 00:47:35.614
I'm completely convinced of that, Ben
00:47:36.213 --> 00:47:44.103
Okay, so wh- so when you look at, say, organizations successfully creating value from AI, what are they doing differently to build trust and adoption?
00:47:44.704 --> 00:47:52.943
I, th-three big things, and I-I'm, I'm afraid I'm gonna end up repeating some things I've said, so I'll try and be more succinct about it.
00:47:52.943 --> 00:47:58.574
But I think treating this as an operating model change and not a technology deployment at the start.
00:47:59.094 --> 00:48:04.603
Work and the accountability that comes with the choices we're making is getting redesigned.
00:48:05.233 --> 00:48:08.034
We're not doing component replacement.
00:48:08.063 --> 00:48:15.153
We're not picking the biggest friction generator or the biggest error generator in the process and replacing that.
00:48:15.153 --> 00:48:24.224
We're actually thinking about how work gets done with AI enablement end to end.
00:48:24.643 --> 00:48:29.684
So that's an operating model change, and that comes with rewrite of job descriptions.
00:48:29.684 --> 00:48:32.414
It comes with the creation of new job descriptions.
00:48:32.414 --> 00:48:35.864
I mentioned this idea of a dedicated content curator.
00:48:35.873 --> 00:48:39.403
Not a lot of places have that as a dedicated role yet.
00:48:40.123 --> 00:48:56.873
So the operating model change is gonna make us think about how work actually gets done and which skills or which sets of duties as a defined role need to be reinforced or introduced.
00:48:57.523 --> 00:48:58.103
That's one.
00:48:59.963 --> 00:49:15.713
Directly related to that, as I create those roles, my, my asset owner, one of my favorites, but this content curator, and then this idea of the subject matter expert as the validator, how are we staffing that?
00:49:15.713 --> 00:49:20.244
Because if we're staffing that as a part-time job probably not gonna work.
00:49:21.043 --> 00:49:25.893
I think about SMEs as validators as a really strong example of this.
00:49:26.324 --> 00:49:35.603
The non-deterministic nature means that validation often requires an expert to look at some sample and give an agreement rate.
00:49:36.414 --> 00:49:40.664
That's how we validate that the algorithm or the solution is performing well.
00:49:41.914 --> 00:49:54.643
That's an expensive thing to do in a couple ways but not the least of which is that there's a high opportunity cost for taking some expert out of their day job and having them play validator of an AI.
00:49:56.043 --> 00:50:00.054
And w- I think we have to rethink how we do that validation.
00:50:01.753 --> 00:50:23.534
That's-- So when I talk about staffing these, these duties, ownership and curation and validation as real jobs and not something that I do as a part-time by the way, that part-time assignment always shows up at the worst possible moment for that individual because they're probably really busy on something else.
00:50:23.574 --> 00:50:25.653
So how dedicated are they?
00:50:25.903 --> 00:50:27.173
How focused are they?
00:50:27.204 --> 00:50:28.923
Those things are gonna matter a lot.
00:50:30.844 --> 00:50:43.213
In my practice, the asset owner was, so valuable because the business thought of the asset owner as their agent inside the AI building shop.
00:50:44.603 --> 00:50:49.673
But the IT folks thought of that person as their inside agent on the customer side.
00:50:49.673 --> 00:51:10.134
And so that two-way, that two-way role is a trust and adoption mechanism by itself because it's building confidence in both the builders and the users because they each feel like they've got their advocate, the person who gets w- what their day is like in the middle of the loop.
00:51:10.204 --> 00:51:12.423
And so I feel like that one's really key.
00:51:13.233 --> 00:51:20.916
And then I mentioned this before, but I think the third answer is really Th- this idea of a blameless feedback loop.
00:51:20.985 --> 00:51:36.246
And so what I mean by that is we're hungry for feedback, and we're gonna treat the inevitable mistakes that are made not as, how do I hunt down who was responsible?
00:51:36.275 --> 00:51:44.306
But instead, th- these are how we're gaining our operational learning to reinvest back into the system.
00:51:44.356 --> 00:51:52.096
And I'm using the word system very deliberately because the foundation model is part of the system, but I don't have the ability to change that.
00:51:52.755 --> 00:51:55.715
The context layer is part of the system, I can change that.
00:51:56.695 --> 00:52:00.315
But also, how is the information being presented operationally?
00:52:01.135 --> 00:52:03.775
What policies have I put around user behavior?
00:52:03.775 --> 00:52:07.626
All of those things are available as part of the system.
00:52:08.045 --> 00:52:13.965
And when we make a mistake, how do we use that to upgrade those things?
00:52:14.675 --> 00:52:19.726
And we want to establish an appetite for that feedback.
00:52:19.726 --> 00:52:22.016
We're hungry for those observations.
00:52:22.806 --> 00:52:28.326
And if we react to those observations with,"Thank you very much.
00:52:28.815 --> 00:52:39.376
I'm now gonna use that to return that insight to the system," that is a flywheel for confidence building as well.
00:52:39.485 --> 00:52:48.755
And as long as we're behaving that way, then we're gonna encourage people to be very forthcoming with what they see, which is what we want.
00:52:48.755 --> 00:52:59.356
So I think operating model, staffing those duties as real jobs, and this idea of a blameless feedback loop, those are the three power moves in my opinion.
00:53:00.365 --> 00:53:02.755
Yeah, no, there's some good feedback there.
00:53:02.856 --> 00:53:19.476
So I guess for a practical takeaway I know you should provide some value, but if, say if a, a leadership team wanted to improve both trust and ROI from AI, I guess in the next sort of 90 days, three months what is the first meaningful action you'd encourage them to take?
00:53:20.076 --> 00:53:24.505
I think there's two things, and the first one is gonna come right back to where we started, which is trust.
00:53:24.505 --> 00:53:42.746
And so I would go to a business unit that has a deployed solution, an AI solution, and ask,"Do you believe in it?" And be very prepared for an honest answer, which is not really.
00:53:43.246 --> 00:54:22.945
I think that there's an illusion that says,"We built this thing, it took six weeks, we deployed it to a team of 200 people, and we've got a 20% increase in token usage among that population and believe I've achieved something." But if you go and interview the users and say,"Do you believe in this answer?" I think we should be prepared for many of them to say,"Not really." And so I would want a very honest assessment of my deployed solutions from that perspective.
00:54:22.956 --> 00:54:32.356
That's the first thing I would do And then the second thing I would do is maybe pick one where the answer was yes a lot, where people generally do believe in it.
00:54:33.726 --> 00:54:46.076
And then it would start to create that middle measurement layer between the token usage and am I seeing a metric that's really moving in the right direction?
00:54:46.076 --> 00:54:52.235
So if, I was an insurance guy, so am I seeing claim duration come down?
00:54:52.726 --> 00:55:00.126
Because I'm getting through my research tasks, I'm making a decision faster I'm resolving this thing sooner.
00:55:00.925 --> 00:55:09.065
So a- am I starting to see that manifest in a metric that really implies a change in the business outcome?
00:55:09.076 --> 00:55:11.306
So is it happening faster?
00:55:11.686 --> 00:55:15.146
Am I having a lower re- representment rate?
00:55:15.186 --> 00:55:20.826
I'm not reworking as many things as I used to, which would be more of a qualitative assessment.
00:55:21.255 --> 00:55:23.195
But the, but those are things you can measure.
00:55:23.686 --> 00:55:28.326
There's gonna be a lag between deployment, adoption, and those metrics changing.
00:55:28.726 --> 00:55:45.516
So that's why I say step one, go figure out which things you've deployed that people are confident in, and then pick one of those and see if you can't build that bridge between adoption and a business process outcome that I care about.
00:55:46.005 --> 00:56:08.996
And stay with that until, until I feel like I've got a story that we can express well and that we can defend and then build trust in my other solutions and repeat that process and start to generate a report card that says, back to the question you asked me earlier, like what's the chain?
00:56:09.735 --> 00:56:12.826
Trust, adopt, ROI.
00:56:13.735 --> 00:56:16.425
So step one, figure out what people trust.
00:56:16.525 --> 00:56:28.005
Step two, pick one they trust and start to build that adopt to ROI pathway, and then you'll have a great diagnostic tool that says,"I've got a trusted one I can't measure.
00:56:28.025 --> 00:56:29.365
Let me go work on measurement.
00:56:29.436 --> 00:56:34.295
I've got an untrusted one, not worth my time to measure it yet.
00:56:34.295 --> 00:56:44.585
I gotta go solve my trust problem." But if you inventoried your solutions from that trust perspective first, I think it'd give a pretty straight line roadmap for what you need to do next
00:56:45.186 --> 00:56:47.405
But I see, sure, I find it fascinating.
00:56:47.786 --> 00:56:53.615
I've seen, I've interviewed a lot of people on the podcast and I just, a lot of it is just down to people problems.
00:56:53.615 --> 00:56:58.735
It's like it's just seems like that's the hardest challenge for businesses.
00:56:59.846 --> 00:57:11.585
Look, I think human psychology is always- Yeah important for us to acknowledge and try our best to get an honest assessment of w- what, where we're starting from.
00:57:12.246 --> 00:57:20.686
And then trust comes from transparency, so bringing the right people in and having them truly participate.
00:57:20.706 --> 00:57:32.865
And in order to get them to truly to participate, I have to be willing to accept answers I don't like If I'm not willing to accept answers I don't like, people are probably not gonna tell me what I need to hear.
00:57:32.865 --> 00:57:45.675
So it really we get so fascinated, Ben, by the technology breakthroughs and so on, and I go, those things are great, but what's hard about this is still back to what I said.
00:57:45.675 --> 00:58:05.846
At the end of the day, I'm asking someone to rewrite their job description, to use a tool they don't understand, to be accountable for the outcome anyway, and in the worst case, I may not even be giving them enough grace to learn the new tool and integrate it into their process without adjusting their report card.
00:58:05.846 --> 00:58:08.985
And those are really hard things to ask another person to do.
00:58:09.715 --> 00:58:16.425
And I have almost never failed to build a solution because the data was too hard.
00:58:17.246 --> 00:58:18.766
Technology has never been a gap.
00:58:20.596 --> 00:58:26.565
Convincing a human to do their job differently has always been the hardest part, and I think that will stay true for a very long time.
00:58:28.416 --> 00:58:28.666
Yeah.
00:58:29.525 --> 00:58:30.246
Okay, brilliant.
00:58:30.315 --> 00:58:31.936
No I've enjoyed the conversation.
00:58:32.005 --> 00:58:38.635
And I guess, so if anyone wants to continue the conversation with you, is it best to connect with you on LinkedIn?
00:58:39.085 --> 00:58:40.235
Yes, definitely.
00:58:40.235 --> 00:58:40.565
Okay, perfect.
00:58:40.565 --> 00:58:46.226
And I would I would be delighted to follow up with anybody who's listening and wants to go deeper on any of this.
00:58:46.726 --> 00:58:46.896
Amazing.
00:58:46.896 --> 00:58:47.536
Yeah, like I said, I'll...
00:58:47.706 --> 00:58:49.166
I can I'll put, I'll add your LinkedIn to the podcast.
00:58:49.766 --> 00:58:53.195
And also if anyone wants to connect with Paul, just, yeah, please do reach out to me.
00:58:53.856 --> 00:59:00.226
And yeah, finally, Paul, it's been a pleasure having you on the podcast, and you've provided some great advice and knowledge.
00:59:00.896 --> 00:59:02.996
I'm so glad you invited me to do this, Ben.
00:59:03.025 --> 00:59:05.456
I'm really grateful for the time and the conversation.
