প্রতিলিপি 🔗
WEBVTT
00:10.113 --> 00:14.488
I am absolutely delighted to be joined this afternoon for the latest Courseonomics
00:14.536 --> 00:17.886
podcast by the brilliant Jo Gordon. I've had the
00:18.386 --> 00:21.877
privilege and pleasure of knowing Jo for a few years now in many different roles
00:21.973 --> 00:25.419
that he has had. He tells me he's over 20 years in the
00:25.919 --> 00:28.304
industry, but I don't think so. I really don't think so, Jo. You're far too
00:28.804 --> 00:32.022
young. I'm not that old. young looking for that. But it is interesting because you
00:32.070 --> 00:35.451
have worked in fintech, you have worked in regulated
00:35.951 --> 00:39.713
sectors, you've been the CEO of First Direct, you've been the COO of OVO
00:40.097 --> 00:43.927
Energy, and then most recently the COO of Starling Bank,
00:44.344 --> 00:47.789
you know, which is renowned for both driving the service
00:48.289 --> 00:51.763
level but as a fintech organization. So I'm really interested in
00:51.859 --> 00:55.576
how you marry use of technology, and particularly
00:55.704 --> 00:59.377
AI, with brilliant service. So that would be certainly something that
00:59.570 --> 01:03.196
I would like to get to the bottom of. As we were saying even before
01:03.645 --> 01:07.431
upstairs when we were chatting, you know, that delicate balance of getting
01:07.931 --> 01:11.522
that right is probably on most CEOs' minds at the moment in terms
01:12.022 --> 01:15.260
of how much is human, how much is AI, do we know the difference?
01:15.950 --> 01:19.463
Tell us a bit about yourself, Joe, and tell us a bit about what
01:19.963 --> 01:21.067
has led you to where you are now.
01:21.469 --> 01:23.234
Thank you for the introduction. Always great
01:23.734 --> 01:27.104
to be here with you at the Institute. For me, 20 years, yes,
01:27.249 --> 01:30.782
the gray in my beard is evidence to that. 20 years working in kind of
01:31.282 --> 01:34.331
B2C environments. And you touched on it there,
01:34.556 --> 01:38.458
B2C environments that wanted to do some level of transformation.
01:39.293 --> 01:43.083
And for me, really focusing in on that intersection of where
01:43.405 --> 01:47.002
service and where customer experience and the latest
01:47.502 --> 01:49.057
technology, which has changed over those 20 years.
01:49.186 --> 01:49.346
Yeah.
01:49.716 --> 01:50.934
meet, and how do
01:51.434 --> 01:54.797
you find that kind of win-win outcome throughout those, those roles? And like you
01:55.297 --> 01:58.756
said, I've worked in different industries, be it telecoms, be it utilities,
01:58.852 --> 02:02.363
be it financial services, or fintech now, but really
02:02.395 --> 02:06.210
seeing the consistency of how you approach that problem,
02:06.242 --> 02:09.688
that problem that I think lots of people face. How do we deliver incredible
02:10.188 --> 02:13.984
service whilst engaging the latest level of technology to support our customers?
02:14.176 --> 02:16.628
And
Load full transcript
that's always been a driving force for me. How do I solve that problem?
02:17.222 --> 02:19.951
And the great thing about that in this environment is it keeps changing every day,
02:20.192 --> 02:23.852
every year, every moment. So you never get to be bored. And that's really
02:23.948 --> 02:26.822
been the driving force between me over the last kind of 20-odd years.
02:27.400 --> 02:30.916
And if we look at the technology, because we'll go very
02:30.948 --> 02:34.721
quickly to that, there's much that's
02:35.221 --> 02:38.782
really positive at the moment, Joe, but you're right, the speed of change is phenomenal.
02:38.975 --> 02:42.828
And most CEOs, most boards are struggling probably
02:43.328 --> 02:45.619
to keep up with You know, what does good look like?
02:46.437 --> 02:50.142
So how do you do that? How do you make sure that that
02:50.286 --> 02:54.151
balance between how we're using technology— because if
02:54.199 --> 02:57.727
you're a CEO or a COO at the moment, the challenges are to do
02:58.227 --> 02:58.416
more with less.
02:58.930 --> 02:59.154
Always.
02:59.587 --> 03:02.009
The challenge is a very unstable
03:02.073 --> 03:04.590
global environment, volatility everywhere,
03:05.184 --> 03:08.888
and the perception— and again, we were talking about this— that service costs.
03:09.546 --> 03:13.649
So How do you manage to convince the board that
03:13.841 --> 03:17.591
actually services are greater value to your business rather
03:17.687 --> 03:21.597
than it being a cost to the business? And how are you deploying technology
03:21.629 --> 03:22.687
in a way that would help that?
03:22.767 --> 03:24.802
It's a $64,000 question,
03:24.914 --> 03:28.007
to your point, that lots of people are dealing with. Firstly, I think I've always
03:28.376 --> 03:32.061
sought out organizations that wanted help in answering
03:32.561 --> 03:35.667
that question. You talked about them, organizations that wanted to be at the forefront of
03:36.052 --> 03:39.344
of driving good customer outcomes and delivering that
03:39.844 --> 03:43.518
in a kind of modern way. For me, the ability to do that with AI
03:44.018 --> 03:47.645
presents us with a choice. And I say choice because I think there's an
03:47.677 --> 03:49.572
opportunity. You can be passive in this.
03:50.888 --> 03:51.948
I actually think that's the lazy way.
03:53.136 --> 03:54.003
And dangerous, potentially.
03:54.051 --> 03:54.549
It's dangerous
03:54.838 --> 03:58.692
because that passivity leads to you inheriting or
03:59.192 --> 04:02.832
trying to adopt things at pace on the back foot. because you think you need
04:02.864 --> 04:06.920
to. My approach is one of proactivity
04:07.257 --> 04:09.854
and saying, okay, we now have a new tool in our arsenal.
04:11.040 --> 04:14.951
How and where we choose to deploy this tool, we should be proactive about
04:15.144 --> 04:18.574
making that actual choice about where we want to use this technology.
04:19.296 --> 04:22.870
Yes, granted, the technology will move and improve, but equally trying
04:22.903 --> 04:26.237
to think about where our USPs are. And, you know, we in Starling,
04:26.253 --> 04:28.786
and I talked about this at the conference as well,
04:29.234 --> 04:32.520
and making a choice to say, we believe there's huge value in human
04:32.536 --> 04:35.903
interaction and empathy right now. And we think that's
04:36.207 --> 04:39.621
something that's not a cost to our business, but an investment in
04:39.669 --> 04:42.699
our business. The same way you invest in marketing, the same way you invest in
04:43.199 --> 04:45.199
products, the same way you invest in going to market. How do you—
04:45.199 --> 04:46.161
Legal or—
04:46.850 --> 04:50.505
How do you invest in service in pursuit of delivering better,
04:51.098 --> 04:54.384
both customer outcomes, but ultimately better business outcomes and finding that
04:54.884 --> 04:58.237
sweet spot? of where you want to use humans in this environment
04:58.612 --> 05:00.798
versus where you want to deploy technology.
05:02.310 --> 05:05.576
That sliding scale has moved. Yeah, of course it has. But I
05:06.076 --> 05:09.474
think being proactive in saying, this is where I value humans right
05:09.974 --> 05:13.594
now, being choiceful about it will lead to better outcomes than just inheriting
05:14.094 --> 05:14.246
what comes your way.
05:14.734 --> 05:16.509
So there's a whole host of things, just picking up on
05:17.009 --> 05:20.415
a couple of things that you've said. So empathy. You know,
05:20.431 --> 05:24.369
we were having the discussion before we've gone live around Will we find
05:24.869 --> 05:28.221
a time when AI is genuinely empathetic? My personal
05:28.721 --> 05:32.266
view is no, I don't think we will get to that. Do I care as
05:32.298 --> 05:35.989
a customer might be another interesting kind of question that we are
05:36.489 --> 05:39.857
at. Good point, yeah. Also, is there a moral kind of dilemma here, Jo,
05:40.146 --> 05:44.302
around are there some things we just really
05:44.318 --> 05:47.560
do need a human to be able to actually drive
05:48.060 --> 05:51.138
for us? And how do you get that right? How do you get that balance
05:51.638 --> 05:54.921
right? We're going— you've got a shareholder or an investor that is pushing for greater
05:55.421 --> 05:58.897
returns, you know, but we've got vulnerable customers,
05:59.073 --> 06:02.135
we've got complex environments that we're trying to deliver
06:02.635 --> 06:04.347
through, we've got a regulator in financial services.
06:04.700 --> 06:04.860
Yeah.
06:05.245 --> 06:06.351
But there's also the moral
06:06.383 --> 06:10.054
thing, isn't there? The intent. How do we make sure that that
06:10.070 --> 06:11.144
intent stays with us?
06:11.512 --> 06:13.741
I think so. Part of that choice is where we,
06:13.821 --> 06:17.590
where we can use technology to break down barriers to
06:18.090 --> 06:20.367
make it easier for our customers, to
give them more access,
06:21.282 --> 06:24.941
and to help people. You know, we're deploying technology
06:24.973 --> 06:28.569
in Starling to help us identify vulnerable customers.
06:28.746 --> 06:28.826
Yeah.
06:29.324 --> 06:32.486
You know, when they're live talking to us, helping identify
06:32.759 --> 06:36.418
complaints, making sure— so using those technologies to augment us,
06:36.547 --> 06:39.869
to help us deliver better customer outcomes, I think is really key for
06:39.918 --> 06:43.289
us as well. I think what we need to think about
06:43.789 --> 06:48.246
against that backdrop you've articulated there is where does the line get
06:48.262 --> 06:52.305
drawn? And for me, there's an ability to be able to say, I want to
06:53.299 --> 06:56.909
augment humans at the front of our business with empathy. Now, I think you say
06:57.409 --> 06:59.732
you don't think it can do empathy. I think there'll be a point where it
07:00.232 --> 07:03.518
can probably do enough fake empathy in written word, for example.
07:03.647 --> 07:04.754
Yes, I'd agree with that.
07:05.026 --> 07:06.839
That you might be bought into it.
07:07.352 --> 07:10.096
But I think this kind of moral code might be,
07:10.304 --> 07:13.628
might be around are we overt in our usage
07:14.128 --> 07:16.823
of it with our customers? And I think as long as we're overt with them
07:17.323 --> 07:20.147
and they're happy, you know, customers can choose the way to engage with us.
07:21.319 --> 07:24.642
In terms of some of those use cases, I think it's really fascinating because I
07:24.707 --> 07:28.544
think whilst the tools have changed, those complex use cases
07:29.044 --> 07:31.097
you articulated persist. Bereavement.
07:31.515 --> 07:31.675
Yeah.
07:31.900 --> 07:32.093
You know,
07:32.317 --> 07:36.524
vulnerability. We've known for years in customer service There
07:36.572 --> 07:40.388
are some things you want to protect and you want to put a level of
07:40.581 --> 07:43.836
enhanced service around that is important to your customers
07:44.012 --> 07:46.930
at all odds. We already know those things. A lot of people do them.
07:47.027 --> 07:50.282
Like, you see lots of organizations who maybe have embraced outsourcing and say,
07:50.346 --> 07:52.045
actually, we, we keep this one onshore.
07:52.126 --> 07:52.286
Yeah.
07:52.366 --> 07:53.312
Because it's really important.
07:54.114 --> 07:57.978
So we already know some of those journeys and those impactful moments
07:58.478 --> 08:01.634
that matter, that we think should be held in higher regard,
08:02.067 --> 08:05.435
that we believe empathy is a super powerful So I don't think we need to
08:05.935 --> 08:07.746
reinvent the wheel in some of these things. We need to just say, okay,
08:07.762 --> 08:10.522
well, if we've got this tool, where do we choose to deploy it against that
08:10.570 --> 08:14.069
backdrop of knowledge that we've had for a long period of time as
08:14.085 --> 08:14.245
well?
08:14.598 --> 08:17.615
So to that point, Joe, and we again were having a bit of a
08:18.115 --> 08:21.547
chat about this before, one thing I have a challenge over
08:21.579 --> 08:25.029
is that we're deploying an awful lot of technology and an awful lot of AI
08:25.720 --> 08:29.298
at the coalface. And there might be some really good reasons why we're doing
08:29.346 --> 08:32.923
that. And much of what we've deemed as customer service
08:33.019 --> 08:34.975
is not customer service, it's processing.
08:35.119 --> 08:35.648
Processing.
08:35.744 --> 08:36.802
Yeah. And actually
08:37.267 --> 08:40.714
using technology to improve that and to make the life of the agent
08:41.214 --> 08:43.952
much better, brilliant. That is absolutely fantastic.
08:45.282 --> 08:49.129
Where we're not really using AI yet, some organizations are,
08:49.145 --> 08:52.881
but not enough, is further upstream. Because surely
08:52.913 --> 08:56.680
that's where the real gains of using technology.
08:57.145 --> 08:59.645
And some of the challenges we've got around that is data is not in the
09:00.145 --> 09:03.621
right places, the information, the processes more complex
09:03.733 --> 09:07.997
with that. But surely that would be the next frontier
09:08.221 --> 09:11.956
in my mind around really useful, better customer experiences,
09:12.309 --> 09:15.483
really understanding that journey and eradicating some of those problems
09:15.515 --> 09:19.186
further up that you and I don't see. So my example would be, and maybe
09:19.426 --> 09:23.402
we are doing this, but, you know, water companies using AI
09:23.450 --> 09:27.281
to be able to find a fault before we already are. I've got that problem.
09:27.698 --> 09:31.353
Stock control, we were talking about that before, and identifying where there might
09:31.385 --> 09:34.751
be an issue further down the line. You can see lots of opportunities.
09:35.056 --> 09:38.460
for where that would really improve. Why don't you think
09:38.669 --> 09:40.258
organizations are doing that?
09:40.676 --> 09:41.976
I think they will. And I
09:42.476 --> 09:46.793
think this is a maturity curve. And I think it was a shiny tool that
09:46.938 --> 09:50.342
got indiscriminately applied or is being indiscriminately applied for a period
09:50.842 --> 09:54.612
of time. To your point, I think the real value, in the same way
09:55.544 --> 09:58.402
that when we think of the coalface,
09:59.237 --> 10:02.720
sometimes we think of that as failure demand, or because to your point, as a
10:02.752 --> 10:05.882
cost to the business, as a cost of things that have gone wrong at some
10:06.382 --> 10:10.183
point in time. And I think for the longest time I've worked within customer service,
10:10.793 --> 10:14.227
we've always tried to focus on what's the root cause analysis? What's been driving this?
10:14.709 --> 10:14.837
Yes.
10:15.206 --> 10:18.978
And then really hard questions to answer. To your point, the computing power,
10:19.460 --> 10:22.653
the
cerebral capability to be able to answer this question is better now than it's
10:23.153 --> 10:26.409
ever been, consuming huge amounts of data and helping us answer those questions.
10:26.778 --> 10:30.850
So applying it there, I think, is, to your point, is the intelligent
10:31.350 --> 10:34.312
way to apply it. And of course, it might reduce your demand right there,
10:34.376 --> 10:37.502
but you can still deliver a fantastic service right there with,
10:37.598 --> 10:40.981
at the cold face with people. I think it's a lazy thing
10:41.029 --> 10:44.475
just to put it over there with people at the cold face. Equally on a
10:44.975 --> 10:48.627
process point of view, and I talked about this, you know, I think where we've
10:48.787 --> 10:52.250
found ourselves in large organizations out with service, and to your point,
10:52.426 --> 10:55.042
sometimes we conflate service with process.
10:55.283 --> 10:55.492
Yes.
10:56.423 --> 11:00.164
Within the process realm, I think there's huge opportunity.
11:00.501 --> 11:04.259
You know, we've been using people as biological middleware in some regards,
11:04.596 --> 11:07.470
you know, like do this thing, move this process, say this thing,
11:07.968 --> 11:11.725
even to the point in our cold-facing, do you know, we historically in
11:11.757 --> 11:14.711
the, in the '90s and noughties, this is the exact script I want you to
11:14.727 --> 11:14.904
read.
11:15.354 --> 11:15.530
Yeah.
11:15.755 --> 11:18.693
You know, don't, don't have a level of autonomy yourself or
11:19.310 --> 11:22.110
decision-making, choices. Decision-making, yeah, yeah, yeah. Don't be a human.
11:22.380 --> 11:23.780
Yes, yes, yes. Don't be intelligent.
11:23.790 --> 11:25.290
Be a bit more like a robot for us,
11:25.790 --> 11:28.350
would you? Which is the antithesis of actually what we really want and what we
11:28.850 --> 11:31.890
really value in today's world. Now we have robots that can do that. So I
11:32.390 --> 11:35.850
think deploying them on the process stuff, really valuable because I think humans
11:36.350 --> 11:39.640
aren't made to do that work. I honestly believe humans aren't made to be autonomous.
11:39.770 --> 11:43.250
You know, they're not made to do drudgery or monotonous work. They're made to be
11:43.750 --> 11:46.700
creative thinkers. They're made to kind of explore problems. They're made to build rapport,
11:46.850 --> 11:48.330
empathy, understanding.
11:48.330 --> 11:48.790
And I think using them on that,
11:50.668 --> 11:51.630
is going to be really key.
11:52.737 --> 11:54.533
And then to do that upstream stuff,
11:55.286 --> 11:58.590
how do we make our organisation better end-to-end
11:59.090 --> 12:02.471
customer experience? Because again, you and me talked about this before, some people
12:02.519 --> 12:04.860
think customer service is just the bit when it goes wrong.
12:04.924 --> 12:06.255
Yeah, or the operation
12:06.368 --> 12:10.152
bit, the execution or the delivery aspect of that.
12:10.217 --> 12:13.568
Whereas actually the strategy, the preparation, what do
12:14.068 --> 12:14.322
we stand for?
12:14.851 --> 12:16.118
From plough to plate.
12:16.246 --> 12:16.343
Yes.
12:16.920 --> 12:17.113
You know,
12:17.257 --> 12:19.986
how, how are we thinking about the customer through this? You know,
12:20.307 --> 12:23.821
creating a product that has inherent customer challenges, only to
12:23.838 --> 12:27.417
be really good at solving those challenges is not great customer experience or service.
12:28.428 --> 12:32.489
Going and looking at the product and saying, actually, the reason why this isn't fulfilling
12:32.585 --> 12:36.453
customer outcomes is because we're not picking up the right level of specific
12:36.597 --> 12:39.631
elements of a product that would help someone who's got a brief. We're not thinking,
12:39.663 --> 12:42.119
we're only thinking about the happy parts. We're not thinking about the unhappy parts.
12:42.199 --> 12:45.826
Yeah. And if we think about the unhappy path, or we often think about what
12:46.326 --> 12:49.420
makes it useful or more effective for us as organizations,
12:49.453 --> 12:50.480
how do we optimize it?
12:50.560 --> 12:52.758
How do we make it more efficient? Yeah. And there's
12:53.258 --> 12:56.771
almost that point there is you go down this, make everything uber efficient.
12:56.851 --> 12:59.948
And don't get me wrong, processes should be efficient. I'm an operator.
13:00.044 --> 13:04.201
That's what I do, but not if they're driving poor outcomes. But it's
13:04.701 --> 13:08.036
to your ability, it's ability to stitch that together across the business, which is,
13:08.133 --> 13:11.804
I think, again, It's that true RCA, which is where data could help us,
13:11.917 --> 13:15.299
that upstream, that upstream challenge. I'm all up for that challenge as well.
13:15.684 --> 13:18.825
And I hope, Joe, that we will start to move to that because I am
13:18.873 --> 13:22.384
worried, and we've talked about this, around the focus
13:22.496 --> 13:25.942
is very much on the execution, which back to
13:26.442 --> 13:30.399
the processes bit, fine, but we've done that now, Joe. Most organizations
13:30.815 --> 13:34.230
have got that efficiency from it. So the big question for me is how are
13:34.262 --> 13:38.080
we deploying that, as you said, across the whole of the stream.
13:39.010 --> 13:43.430
You've worked, just changing this slightly, you've worked in energy, worked in retail,
13:43.470 --> 13:47.350
worked in telcos, worked in financial services. And then we were again
13:47.850 --> 13:50.970
talking about the fact that every organization thinks they're different. And the truth is every
13:51.470 --> 13:55.330
organization is different, has a different context, it has a different, what it's trying
13:55.830 --> 13:59.570
to actually serve. But the reality is the issues are probably still the
14:00.070 --> 14:01.540
same. We probably end up talking about culture.
14:01.950 --> 14:02.150
Yeah.
14:02.150 --> 14:04.210
We'll talk about AI or systems
14:04.710 --> 14:08.550
development. We'll talk about processing, we'll talk about whether the board really
14:08.582 --> 14:11.613
buys the service agenda or customer centricity. Yeah.
14:11.790 --> 14:15.414
How far that kind of goes. What have you learned from going from
14:15.574 --> 14:18.846
different industries? And if you were advising the
14:19.346 --> 14:22.599
people that listen to this today, what would that, what would that be? Because you
14:23.099 --> 14:26.047
must have seen the whole, it's not, it's different here, Joe. You know, I know
14:26.547 --> 14:29.030
you've worked here, I know you've worked there, but it's different here. But the reality
14:29.530 --> 14:30.088
is it's not, Joe, is it?
14:30.393 --> 14:32.173
I don't think it is. And I think some
14:32.673 --> 14:36.825
of the transients in my career journey has been because there
14:37.325 --> 14:41.461
is transferability across these industries, especially B2C
14:41.943 --> 14:45.520
in my regard, what the consumers value. And from an
14:46.114 --> 14:49.563
experience point of view, the one thing I've found is the organizations that are
14:50.063 --> 14:54.456
really good at this, they aren't good at it because they have specific
14:55.002 --> 14:58.884
individuals who circumvent processes or who are irreverent
14:58.948 --> 15:01.563
to authority. They're good at it because,
15:02.702 --> 15:06.406
to our earlier conversation, they build it into the ecosystem.
15:07.288 --> 15:07.481
Yes.
15:08.010 --> 15:10.464
And regardless of what industry,
15:10.640 --> 15:14.152
you know, who are trying to solve the same problems,
15:14.264 --> 15:17.985
like you said, how can I show the value of customer experience? What's the return
15:18.033 --> 15:21.642
on investment? What does a truly customer-centric operating model look
15:22.142 --> 15:25.218
like? How do I build a way of working that solves customer problems and reduces
15:25.250 --> 15:28.701
root cause failure? Same questions are being asked everywhere.
15:29.087 --> 15:33.004
Building that into the DNA and way of working has,
15:33.277 --> 15:37.371
I've seen, has delivered, always delivered much better results than relying on a
15:37.871 --> 15:41.562
pure, you know, conversation with the people at the coalface that
15:42.062 --> 15:45.335
says, we know this is all not working, but you've got to try and recover
15:45.835 --> 15:45.544
it.
15:45.720 --> 15:45.929
Yes.
15:45.977 --> 15:48.947
Yeah. Which is a constant challenge that I have with boards.
15:48.996 --> 15:52.640
I'm sure you have convincing people is, again, people think oh,
15:52.721 --> 15:56.479
that's just all customer services, that's all customer experiences. It's fixing— yeah,
15:56.945 --> 15:59.499
the organizations that do really well, it's just part of it.
15:59.579 --> 16:00.495
Yes, you don't need
16:00.995 --> 16:00.977
to fix it.
16:01.121 --> 16:01.957
You don't need to fix it.
16:02.326 --> 16:04.703
And also, it transcends the leadership,
16:05.089 --> 16:08.494
it transcends the culture. You know, we touched a little bit briefly
16:08.767 --> 16:12.060
on the fact that you were CEO at First Direct, and I— this is no
16:12.560 --> 16:15.898
secret, I've had the privilege of working 3 different CEOs at First Direct.
16:16.461 --> 16:20.774
But the interesting thing for me is that there is a lot of consistency,
16:21.286 --> 16:25.004
which is exactly to your point. They have been able during that
16:25.052 --> 16:28.641
time to be able to deliver that across the piece. And I'm sure
16:29.141 --> 16:32.630
that's something that you are thinking hard at, at Starlink, in terms
16:32.726 --> 16:36.443
of, you know, a different organization. But that principle of
16:36.943 --> 16:40.721
about being genuinely customer-centric at the core of the business,
16:41.154 --> 16:42.628
in the boardroom and all the way down.
16:42.820 --> 16:44.567
And fighting for that consistency.
16:44.679 --> 16:44.903
Yes.
16:44.999 --> 16:48.526
Because there will always be And they're not because they don't
16:48.607 --> 16:51.398
want it, it's because they don't know about it. There'll always be people who will
16:51.414 --> 16:54.718
think there's different ways to get those outcomes. But I think from your
16:55.218 --> 16:58.953
vantage point, if you're sitting in those positions, being able to continually advocate for
16:59.453 --> 17:02.482
that as a way of working, as a reinforcing mechanism, is very important.
17:02.883 --> 17:03.108
So if
17:03.124 --> 17:06.974
we switched a little bit to the customer and to, you know, and the consumer
17:07.474 --> 17:11.112
generally, what are the sorts of things that you've seen change,
17:11.706 --> 17:15.331
Jo? Because we've definitely, since COVID you know, we've obviously had cost
17:15.379 --> 17:18.523
of living, there's a real challenge on that. But as you
17:19.023 --> 17:22.359
know, there are behavior changes that we are seeing. So what are the sorts of
17:22.859 --> 17:26.934
things that you would point to that we should be alive to or alert to
17:27.434 --> 17:29.599
as organizations in changing consumer behavior?
17:30.080 --> 17:31.092
I was having this exact
17:31.124 --> 17:35.089
conversation with someone and we were talking about
17:35.121 --> 17:38.668
things like digital hygiene factors, but even that now is
17:39.168 --> 17:42.617
semi passé because I think the way people want to,
17:43.163 --> 17:46.759
you have to move with the way people want to interact. And to your point,
17:46.775 --> 17:50.018
we've seen that check. Some people argue it's generational.
17:50.692 --> 17:53.838
I think it might be led by a gen— led by generation, but it becomes
17:54.338 --> 17:54.239
a halo.
17:54.544 --> 17:54.608
Yeah.
17:54.785 --> 17:57.899
You know, the way we want to interact. And I think for
17:57.931 --> 18:02.312
us, we are becoming positively, I think,
less accepting
18:02.329 --> 18:04.239
of subpar interactions.
18:04.672 --> 18:06.293
Okay. So not gonna accept
18:06.793 --> 18:08.107
if you tell me to do this, why should I have to do that?
18:08.171 --> 18:09.053
It's more challenging.
18:09.246 --> 18:11.252
But also if I wanna do something simple,
18:12.280 --> 18:15.539
why is it hard to do something simple? You know, and before we might have
18:15.571 --> 18:18.558
said, okay, of course I have to ring up. But now I'm like, well,
18:18.574 --> 18:21.032
I just want to click a thing in the app. Thanks. I don't want to
18:21.532 --> 18:25.192
have that interaction. Now, the converse to that, to our earlier point, where I
18:25.208 --> 18:28.822
want to do something really complicated, I need to have a route
18:29.322 --> 18:30.026
in to have that conversation.
18:30.524 --> 18:30.620
Yeah.
18:31.006 --> 18:33.335
Now, our ability as organizations to
18:33.835 --> 18:36.965
be able to decipher some of that and be able to find out where do
18:37.465 --> 18:40.867
we want to remove friction and where do we want to put friction. To your
18:40.883 --> 18:44.140
point on helping customers answer some of those challenges.
18:44.509 --> 18:48.263
So I think, of course, it'll be generational-led. Of course, there's an element of technology
18:48.763 --> 18:52.161
and adopting to that pace of change. But I think the general appetite of,
18:52.610 --> 18:56.284
if I can do this over here with an organization, in my
18:56.784 --> 19:00.343
world, in fintech, for example, what was leading edge a couple of years ago was
19:00.375 --> 19:01.113
freezing your card.
19:01.466 --> 19:02.220
Yes. Yeah.
19:02.444 --> 19:03.648
But now everyone needs to freeze their
19:04.148 --> 19:05.589
card. And if I need to ring up to freeze my card, I'm probably not
19:06.089 --> 19:08.138
gonna bother and I might just go to another bank because it's too much effort.
19:08.442 --> 19:08.538
Yeah.
19:08.971 --> 19:12.048
So there's, there's the hygiene element of that kind of stuff versus,
19:12.224 --> 19:16.422
okay, well, now I want to be able to engage with an AI assistant.
19:16.470 --> 19:16.567
Yeah.
19:16.887 --> 19:19.932
So one of the things we've built in Starling is a Starling assistant to
19:20.432 --> 19:23.954
deal with that interaction. So you can do things like move some money into
19:24.082 --> 19:27.447
what's our savings called Spaces accounts. So you can do some
19:27.947 --> 19:31.068
of that stuff. It's how do we meet the customer where they want to be
19:31.373 --> 19:34.915
in some of those instances, or again, be intent,
19:35.236 --> 19:38.812
have intent and be proactive to say, if we think inserting friction is
19:38.908 --> 19:42.371
good, yeah, how do we do that? Fraud is a great example right now.
19:42.516 --> 19:42.900
Scamming.
19:43.029 --> 19:43.510
Scamming.
19:43.798 --> 19:43.894
Yeah.
19:44.119 --> 19:46.284
You know, like, how, how do we put a positive
19:46.784 --> 19:49.971
friction in to help the customers in, in that regard as well?
19:50.308 --> 19:50.613
And do
19:51.113 --> 19:53.820
you think, actually, Jack, because I think this is quite interesting, I would argue,
19:53.916 --> 19:57.524
and, you know, we've got banking and building societies at the top of the
19:58.024 --> 20:01.725
UK CSI, which, you know, yeah, you know, and we've been doing
20:01.773 --> 20:05.707
the UK CSI now since 2009. And if you think about the crisis
20:06.207 --> 20:08.725
in 2009 and you think about where the sector was,
20:09.319 --> 20:13.461
we certainly see that the banking sector has genuinely
20:13.493 --> 20:16.608
led the way. And I think that a lot of that is due to the
20:17.108 --> 20:21.007
technology that's being deployed. And it's interesting what you're saying about scams
20:21.424 --> 20:24.892
and using technology to detect. So now,
20:25.309 --> 20:28.744
you know, you know before I know that I'm being scammed,
20:29.061 --> 20:32.595
you know, that whole kind of— and then the actual human bit
20:33.095 --> 20:36.413
of that then becomes, you're phoning me up, actually a human being is phoning
20:36.509 --> 20:38.980
me up going, can I just check a few things with you?
20:39.060 --> 20:39.157
Yeah.
20:39.317 --> 20:39.638
Is this—
20:40.138 --> 20:43.360
yeah. And actually, I've got to say, and that's happened sadly a couple of times
20:43.408 --> 20:47.885
for me recently, that whole experience was so much better because you'd
20:47.901 --> 20:51.013
identified the problem, there was an issue with that, but the human
20:51.109 --> 20:54.783
was highly competent in taking me through that process,
20:55.201 --> 20:58.744
giving me huge amounts of confidence. Yeah. And that kind of
20:59.244 --> 21:02.190
approach, but also very, dare I say, empathetic.
21:02.686 --> 21:03.872
What a brilliant use of humans.
21:03.936 --> 21:04.786
Yes. Yes.
21:04.914 --> 21:05.795
You know, against that backdrop,
21:06.100 --> 21:07.205
augmented by technology.
21:07.622 --> 21:07.975
Totally.
21:08.279 --> 21:09.545
Especially, I think, what I think
21:09.561 --> 21:12.830
banks have done. One, I would say lots of the challenges raised the
21:12.846 --> 21:13.519
bar for banks.
21:13.968 --> 21:14.176
Yes.
21:14.353 --> 21:16.628
You know, Starling included. You know, a great
21:16.853 --> 21:19.288
advocate is it came in and said, this is how we should do things.
21:19.336 --> 21:21.740
And to your point, I think we've seen lots of people say, oh crikey,
21:21.804 --> 21:25.172
let's all Try and do things better. And then using technology,
21:25.188 --> 21:27.819
to your point, if we can see the data, we can see the interactions,
21:27.916 --> 21:31.301
we can see what's happening, we have a responsibility.
21:31.750 --> 21:32.006
Yes.
21:32.247 --> 21:35.119
And I know the regulators in where I am now in FS, but also
21:35.135 --> 21:38.552
in other areas, are holding industries
21:38.568 --> 21:42.097
and businesses to
account for the responsibility they have. You know, in energy, it might
21:42.597 --> 21:46.268
be to support those people who need a kind of warm home discount,
21:46.284 --> 21:49.380
for example. In FS, it's scam protection,
21:49.412 --> 21:52.509
fraud protection, you know, application push payment scams.
21:52.830 --> 21:55.570
If we can see that, we have a responsibility to engage. And the reason we
21:56.070 --> 21:58.290
can see that is because we've got good technology that can identify that.
21:58.290 --> 21:58.490
But to
21:58.990 --> 22:01.530
your point, that's not just because the regulators told you that. That is because you're
22:02.030 --> 22:05.530
a customer-centric organization that actually does care enough
22:06.030 --> 22:10.310
about actually the outcome for the customer. So if we were more outcome-led as
22:10.810 --> 22:14.610
organizations, you know, okay, the FCA regulates that, consumer duty
22:15.110 --> 22:18.870
has driven that. But actually, if we had more in the boardroom of a perception
22:19.370 --> 22:22.510
about actually what is the outcome for the customer and why is that a good
22:23.010 --> 22:26.804
outcome and how does that you know, improve our position,
22:26.916 --> 22:29.464
then that has got to be something to really focus on.
22:29.544 --> 22:30.746
Yeah, and finding ways
22:31.246 --> 22:34.833
to continually raise the bar. You talk about scam detection. We've got
22:34.849 --> 22:38.935
a new tool even within Starling Bank that can
22:39.000 --> 22:41.788
measure, if you turn it on, can measure the velocity of which your phone has
22:41.820 --> 22:45.907
moved. To think actually, we've got like a snatch detector. And immediately
22:46.407 --> 22:47.381
say, well, if we can identify that—
22:47.814 --> 22:48.839
We know that that's not good.
22:49.096 --> 22:49.320
How do
22:49.336 --> 22:49.977
we know that if I—
22:49.977 --> 22:51.916
I must stop chucking it up in the air and
22:52.416 --> 22:52.493
doing that.
22:52.974 --> 22:56.050
But how do you, how do we make sure that If we've noticed
22:56.550 --> 22:58.290
that, then you go into that banking app. How do we, how do we put
22:58.790 --> 23:01.030
some friction in the way to make sure that it is actually—
23:01.030 --> 23:01.430
Yeah.
23:01.630 --> 23:02.330
And continually
23:02.830 --> 23:05.970
raising that bar for other people is, I think, is really beneficial
23:06.470 --> 23:07.770
in terms of what, what matters for the customer.
23:08.070 --> 23:09.930
Because you're forensically focused on
23:10.430 --> 23:10.430
that.
23:10.430 --> 23:11.030
Yeah.
23:11.030 --> 23:13.320
Okay. What should we be worried about, Joe?
23:13.690 --> 23:15.170
Yeah. Is Armageddon gonna happen?
23:15.170 --> 23:17.250
It's a long list, Joe.
23:17.250 --> 23:17.530
Yeah.
23:18.030 --> 23:21.149
We haven't got, we haven't got enough time in the podcast for that, but What
23:21.358 --> 23:25.022
is keeping organizations, you awake, either in
23:25.522 --> 23:28.059
the deployment of AI, but not necessarily just AI?
23:28.911 --> 23:30.276
What should we be thinking about?
23:30.839 --> 23:34.711
I'm going to try and steer away from geopolitical
23:34.952 --> 23:38.006
challenges right now and bring it to—
23:38.488 --> 23:38.954
Practical
23:39.454 --> 23:41.460
things in the UK that we might be kind of trying to do.
23:41.605 --> 23:42.151
The practical
23:42.264 --> 23:45.911
things. By all accounts, I'm no expert on AI per
23:45.960 --> 23:49.505
se. My role, as lots of business leaders, is how do
23:50.005 --> 23:52.264
I use the latest tools and help make them help my, help my business?
23:52.681 --> 23:53.098
But I think—
23:53.098 --> 23:56.290
I think you're being modest though. I think your adoption of
23:56.370 --> 24:00.012
AI would definitely put you up, up there, uh, Joe, in terms of
24:00.512 --> 24:00.557
how you're using it.
24:00.621 --> 24:02.129
I think what I've tried to do throughout my career is
24:02.225 --> 24:05.658
just adopt the latest technologies that will enable better customer outcomes.
24:05.834 --> 24:05.930
Yeah.
24:06.331 --> 24:10.229
I think for us within that, you always get into kind of space races.
24:10.807 --> 24:14.159
You know, we saw it with chatbots when chatbots were a thing.
24:14.576 --> 24:18.341
We saw it with outsourcing when outsourcing was the thing. And I think to my
24:18.581 --> 24:21.802
first point, being intentful and not being lazy about
24:22.302 --> 24:25.647
the deployment of this is really important for us. I also think we've got
24:26.147 --> 24:30.005
to be alive to wholesale shifts
24:30.213 --> 24:34.058
in the labor market. And we've
24:34.558 --> 24:38.288
got to be thinking about, I believe in a real circular economy, right? Like you
24:38.788 --> 24:41.156
take all the people at all the jobs out of the economy, who's buying anything?
24:41.204 --> 24:44.395
Who's paying the tax? Yeah, no one's paying any tax. You know, so,
24:44.411 --> 24:48.153
so there are other kind of existential problems that hopefully smarter than us,
24:48.169 --> 24:51.462
Joe, in the halls of power will be, will be residing over. But I think
24:51.962 --> 24:55.333
for us in our play, in our worlds, where do
24:55.833 --> 24:58.529
we use the latest technology and why will always be key to us. What do
24:59.029 --> 25:01.565
consumers really, really want, really want,
25:01.967 --> 25:06.834
really need against that backdrop? And how do we continue to advocate for
25:07.347 --> 25:10.863
customer experience in a world where technology deals with
25:10.879 --> 25:13.751
more customer experience? Because that's interesting for us.
25:13.896 --> 25:17.730
Because I think the old synergy that people always think is customer experience
25:18.230 --> 25:22.287
is people answering phones and stuff like that. We know that's not true. So what
25:22.787 --> 25:26.538
does that advocating for it look like? And what is it,
25:26.763 --> 25:30.565
what does
it mean in a, in a modern world to be thinking about
25:31.065 --> 25:30.790
that?
25:31.191 --> 25:34.657
And what are the skills and the capabilities that we are going to need?
25:35.202 --> 25:38.296
And to your point, some of those skills will be the same. So empathy,
25:38.312 --> 25:42.063
we've talked about curiosity, problem solving,
25:42.496 --> 25:46.118
the ability to look end to end, or much more holistic
25:46.618 --> 25:49.966
approaches, the ability to challenge. Because I think we do need
25:50.466 --> 25:53.653
to be honest, there are organizations that are less,
25:54.198 --> 25:57.644
shall we say, service orientated, that will see service, as we said, as a
25:58.144 --> 26:02.341
cost, or we'll see, you know, great opportunity to use technology
26:02.453 --> 26:05.916
to remove that cost or to remove human capital or whichever.
26:06.445 --> 26:08.993
Exactly. That awful saying, yeah, human factors.
26:09.105 --> 26:09.811
That phrase that
26:10.311 --> 26:13.577
we kind of use. That bothers me, Joe, not because we're,
26:13.657 --> 26:17.039
you know, I'm against driving greater efficiency or productivity, but again, it's back to your
26:17.539 --> 26:20.966
point about intent. And you've used the word intent quite a lot through
26:21.466 --> 26:25.358
this podcast, and I agree with you. I think that organizations need to think
26:25.598 --> 26:29.028
harder about what they are using
26:29.140 --> 26:33.035
technology to do in order to get the right outcome for their businesses.
26:33.212 --> 26:36.676
And how does, how does that actually feed in to their overarching
26:36.740 --> 26:40.145
strategy. Like, all organizations should have a strategy. What are they trying to achieve
26:40.194 --> 26:43.631
commercially? What are your outcomes? And what do you need from
26:43.904 --> 26:47.630
consumers to be able to do that? It's multidimensional. It's not a single
26:47.662 --> 26:50.151
dimension or an add-on to our point as well.
26:50.232 --> 26:51.019
And I think that bit has
26:51.131 --> 26:55.034
become more complex because I think— I don't think that consumers
26:56.030 --> 26:59.611
per se are more complex, Joe, but they have more options.
27:00.189 --> 27:01.378
They do. They have more choice.
27:02.117 --> 27:03.465
The stress of choice, in fact.
27:03.514 --> 27:06.805
Yes. Yeah, yeah. I mean, how many different types of coffee can I buy
27:07.431 --> 27:08.716
in my favourite retailer?
27:08.860 --> 27:10.658
You know, I try and do most every day. Yes.
27:12.087 --> 27:15.812
But that is also— that brings something else. And I do wonder whether, you know,
27:15.844 --> 27:18.959
we almost get overloaded with choice and actually,
27:19.392 --> 27:22.475
you know, will we see a reversal to, you know,
27:22.588 --> 27:26.971
reversing back to actually more of advice,
27:27.099 --> 27:30.306
you know, because There are some interesting, I think,
27:30.531 --> 27:33.849
challenges around that, Joe, about what's our role
27:34.349 --> 27:37.905
as a business to help or to enable an organization. And if you
27:38.405 --> 27:41.832
end up giving so much, does that actually, you know,
27:41.993 --> 27:44.830
give the right outcome? Does that actually support that?
27:44.894 --> 27:44.958
Yeah.
27:45.119 --> 27:48.982
And I think that to your point, there's a balance there because I think
27:49.367 --> 27:52.797
the argument today is you almost need to bust the stress of
27:52.829 --> 27:53.134
choice.
27:53.471 --> 27:54.674
Yes. Yes.
27:54.754 --> 27:55.894
Choice is stressful now. Yeah,
27:56.360 --> 28:00.069
go and try and decide what to watch every night on Netflix is stressful enough,
28:00.760 --> 28:03.746
right? Let alone what product you need and what service you need or what you'd
28:04.246 --> 28:08.146
benefit from. I think the real balance there is trying to help people
28:08.563 --> 28:12.352
narrow down some of that choice. Yes. But we have to be really careful that
28:12.898 --> 28:16.399
we're not there telling, telling, or reducing,
28:17.057 --> 28:18.888
or pigeonholing.
28:19.064 --> 28:19.225
Yeah.
28:19.867 --> 28:21.679
Or determining
28:21.968 --> 28:25.545
people are vulnerable because technology says they're vulnerable,
28:25.818 --> 28:28.497
when they would tell you, actually, I'm not vulnerable. And suddenly we put them in
28:28.529 --> 28:31.914
a box and we're treating them differently because of that. So I think there's,
28:32.074 --> 28:35.667
again, which is where the human lens comes in, which is so careful
28:36.167 --> 28:38.507
with all this data. How do we be sure we're right all the time?
28:38.699 --> 28:38.747
Yeah.
28:38.795 --> 28:42.405
We have to almost have that check digit with humans along that basis and
28:42.485 --> 28:45.613
give them the ability to say, with all the data, we think this is
28:45.693 --> 28:49.142
you. And you see this curated choice that we think you'll like this. We think
28:49.642 --> 28:52.448
these are products for you. we think this service is the right service for you,
28:52.769 --> 28:56.526
but also making sure that there is an element of choice and free will that
28:57.026 --> 28:59.913
we don't— and free will is such an important thing— that we don't, you know,
29:00.057 --> 29:01.438
expunge completely on this journey.
29:01.984 --> 29:03.798
And I could not agree with you more. I think
29:04.793 --> 29:08.485
the great thing about humans is we are unpredictable.
29:08.903 --> 29:10.990
Yeah, semi-volatile maybe.
29:11.054 --> 29:12.113
Yeah, yeah, definitely.
29:12.675 --> 29:15.902
We do stuff that you wouldn't expect or what,
29:16.111 --> 29:18.920
you know, and I think that is a really important part of that. I mean,
29:18.936 --> 29:22.385
we used to have old segmentation techniques, there is a danger that
29:22.885 --> 29:27.081
we'll use technology to actually just do the same sins of our forefathers
29:27.113 --> 29:31.023
in terms of— yeah. And because the data tells us that,
29:31.103 --> 29:34.549
you know, we'll therefore slavishly believe data over a gut
29:34.806 --> 29:38.011
instinct or a behavior. So to your point,
29:38.957 --> 29:42.611
the service role is always to, in my mind, be asking, yeah, but is that
29:42.723 --> 29:42.867
right?
29:43.300 --> 29:45.848
And if we could do it well, it becomes a segment of one as
29:46.348 --> 29:49.086
opposed to I'm pigeonholing you in an area. And what does that segment of one
29:49.134 --> 29:52.933
actually look like? And that's where the real data unlock, the real technology unlock comes
29:53.478 --> 29:57.229
because we do know you well enough and can interact with you as an individual
29:57.630 --> 29:58.864
versus a group of—
29:58.864 --> 29:59.794
A very vanilla.
29:59.954 --> 30:00.146
Yeah.
30:00.211 --> 30:01.076
And I do think at the
30:01.576 --> 30:05.404
moment, Joe, how we're deploying some of the technologies in quite a vanilla
30:05.904 --> 30:07.536
way. And I think, you know, if we're not careful—
30:07.600 --> 30:08.402
It's nascent, isn't it?
30:08.450 --> 30:08.578
Yes.
30:08.963 --> 30:11.800
It's the maturity, coming up that maturity curve.
30:11.913 --> 30:12.153
I agree.
30:12.538 --> 30:15.551
We talked loads about AI. We talked about consumers. We've talked about
30:15.599 --> 30:18.789
the mad world that we are working in. We talked about the
30:19.289 --> 30:21.899
lessons from the ability to learn from different industries.
30:23.039 --> 30:26.393
If you had a magic wand, Joe, and you could go forward
30:26.505 --> 30:29.795
and you could kind of— where do you think
30:29.876 --> 30:33.262
we will land? Yeah, what is nirvana for you in terms of
30:33.762 --> 30:34.739
a brilliant customer experience?
30:35.236 --> 30:37.627
I think the ability— something
30:37.643 --> 30:41.158
that I know we've discussed many, many times— the ability
30:41.977 --> 30:45.411
to be able to put a real-world
30:46.165 --> 30:47.979
ROI on customer experience.
30:48.332 --> 30:49.697
Okay. Well, in, in, in the
30:50.197 --> 30:51.093
moment, in every, yeah.
30:51.142 --> 30:53.646
In the, in the moment. Yeah. And in every boardroom
30:54.288 --> 30:57.820
in terms of understanding, I might be different industry to industry depending
30:57.868 --> 31:01.625
on, on choice, but the ability to do that, because what always blows
31:01.721 --> 31:04.787
my mind is to your point, we continue to put the companies that do
31:05.287 --> 31:08.367
it on positive pedestals and we should. And to our earlier conversation,
31:09.041 --> 31:11.433
we look at it, but then we don't replicate it.
31:11.610 --> 31:11.770
Yeah.
31:12.493 --> 31:14.981
Well, that's really good. They're really good. Oh, we can't do that.
31:15.318 --> 31:15.655
So what
31:15.687 --> 31:16.860
stops us from doing that?
31:17.614 --> 31:18.899
Because it's seen as too
31:19.059 --> 31:22.527
hard, or the articulation is hard. And again, to our earlier
31:23.027 --> 31:25.337
point of view, I think every organization is probably asking a number of questions,
31:25.353 --> 31:29.880
or wants a number of questions answered. You know, what is the true value of
31:29.913 --> 31:33.782
customer experience? Why would it make a difference to my business? If I invested
31:34.282 --> 31:36.656
in it, what return would I get? What does that mean for customer loyalty,
31:36.720 --> 31:40.349
for product penetration, for growth? All very hard intangibles that
31:40.849 --> 31:43.608
we've been wrestling with, and I've been wrestling with throughout my career. I've been wrestling
31:43.704 --> 31:47.007
with them. That ability to articulate that,
31:47.344 --> 31:49.748
I think, would be a game changer.
31:50.133 --> 31:50.982
Well, it's interesting,
31:51.015 --> 31:54.413
Joe. You will be aware we've created the Return
31:54.461 --> 31:55.743
on Investment Toolkit.
31:55.872 --> 31:57.010
Yeah, I know. I'm well aware of it.
31:57.106 --> 31:57.443
Yeah. Yeah.
31:57.747 --> 32:00.761
But it's hard. It's hard for organizations to deploy that.
32:01.033 --> 32:01.178
Yeah.
32:01.434 --> 32:05.089
But it is, I think, where genuine service
32:05.842 --> 32:09.257
professionals need to go. Because if we need to convince the board,
32:09.369 --> 32:12.046
which is what we're always talking about, we need to be able to show that
32:12.078 --> 32:15.348
return and we need to be able to demonstrate that whatever industry sector that
32:15.444 --> 32:19.118
we are in. And, you know, that isn't always easy.
32:19.310 --> 32:23.080
But back to your point, using technology, using what we do now,
32:23.401 --> 32:26.610
using data, we should be able to get much faster at that and be able
32:27.110 --> 32:27.155
to prove that.
32:27.251 --> 32:29.561
And I think that's, that's the opportunity, right? That really, of course,
32:29.577 --> 32:32.786
but to your point, we work in a corporate commercial ecosystem.
32:33.267 --> 32:35.770
We're not going to necessarily change that overnight.
32:36.556 --> 32:41.144
We need to go to a place of communicating that
32:41.513 --> 32:44.820
helps them understand. the real value of the service and helps
32:45.320 --> 32:48.755
them understand it, uh, from a point of articulation. Because me
32:49.255 --> 32:52.882
and you will be stalwart advocates for the longest time. How do we meet them
32:52.914 --> 32:56.688
on their terms in terms of helping articulate and talk in the language and
32:56.720 --> 32:57.652
actually influence that?
32:57.989 --> 33:00.446
And whether that's the investor, the board member,
33:00.784 --> 33:05.007
you know, the— but the people that pay for the
33:05.023 --> 33:08.316
service experience ultimately need to be able to see that return.
33:08.573 --> 33:09.889
And I couldn't agree more.
33:10.018 --> 33:10.114
Yeah.
33:10.275 --> 33:11.720
And us being able to do that.
33:12.025 --> 33:15.847
Okay. Last kind of couple of questions, Joe, for you. We started by saying that
33:15.879 -->
33:19.910
you've been 20 years in the industry. I don't actually
33:20.410 --> 33:24.519
believe that, but if you had any advice to your
33:24.728 --> 33:26.751
younger self, what would that be, Joe?
33:27.378 --> 33:28.421
I might argue I've taken some
33:28.921 --> 33:32.757
of it as well. It would probably be on the transferability of skills. I think
33:32.998 --> 33:36.627
a lot of people, which I think actually is, is good for service and experience,
33:36.916 --> 33:40.529
A lot of people will stick in an industry. Your ability to get
33:41.029 --> 33:45.041
perspective as an individual, both on transferability, all industries, a lot
33:45.541 --> 33:48.782
of industries face the same problems, the same challenges. It's hard to
33:48.798 --> 33:52.170
get that perspective if you stay siloed. And I think the biggest benefit I've
33:52.670 --> 33:56.265
had in my career is that breadth of going in different industries and experiencing it.
33:56.505 --> 33:56.602
Yeah.
33:56.746 --> 33:58.336
You know, and I advocate to lots of people,
33:59.797 --> 34:03.151
uh, it's a great learning and it's a great grounding. Uh, to be able to
34:03.167 --> 34:07.237
understand what it means in those environments to be focused on customer,
34:08.055 --> 34:11.324
what it means to deliver good commercial outcomes through better customer experience,
34:12.798 --> 34:15.698
and what skills you needed as an individual and how portable they are.
34:16.227 --> 34:20.073
I completely agree. I mean, I'm very privileged to be the CEO of
34:20.573 --> 34:23.983
the Institute because I see lots of different industry sectors. But as we were saying,
34:23.999 --> 34:27.973
the issues and the challenges, whether you're in automotive, whether you're in banking,
34:28.326 --> 34:32.164
whether you're in telcos, whether you're in retail, they're often very similar
34:32.357 --> 34:35.970
in terms of those 5 questions that the board will ask of you to
34:36.115 --> 34:39.905
answer. And that ability to be able to manoeuvre between them, it's also really
34:40.405 --> 34:44.321
exciting and really interesting because you can take what you have learned, which is what
34:44.821 --> 34:48.658
you have done, Jo, and apply that in another environment. So you are,
34:49.220 --> 34:53.042
you are growing, the organisation is growing, and this whole service ethos
34:53.395 --> 34:53.861
needs to grow.
34:54.134 --> 34:54.487
It is growing.
34:54.600 --> 34:55.883
Or will grow. as a part of that.
34:56.124 --> 34:59.217
Yeah, and you learn things in different industries. They're ahead in different elements and,
34:59.330 --> 35:03.770
and behind in others. You get to kind of be a semi-magpie about
35:04.139 --> 35:07.601
picking up those skills and capabilities to give you
35:08.101 --> 35:08.900
some ability to—
35:09.509 --> 35:11.577
But maybe that is, you know, what we've talked about,
35:11.609 --> 35:16.161
service. Maybe that is the skills of the future service
35:16.661 --> 35:20.217
professional, the ability to move between different industry sectors
35:20.954 --> 35:23.776
and take that learning and really apply that. I mean, you know,
35:24.401 --> 35:27.991
at the Institute, we talk about the service movement, we talk about trying
35:28.087 --> 35:31.308
to change the UK PLC, get it far more focused
35:31.808 --> 35:35.058
around the fact that we're the second largest exporter of services, we— our GDP over
35:35.558 --> 35:38.807
80% is service, we better be good at this. So actually,
35:39.881 --> 35:43.711
rather than worrying about will AI take my job, we should
35:44.211 --> 35:47.428
be really focusing on how can I ensure that my
35:47.928 --> 35:51.819
skill set is going to be really deployable whatever industry sector
35:52.319 --> 35:55.717
I'm in, because how am I going to help that board to answer those 5
35:55.733 --> 35:59.153
questions, which are usually the same: culture, how do
35:59.185 --> 36:02.476
I drive the right service-led culture, productivity, how do I get more for
36:02.976 --> 36:06.266
less, how do I measure, you know, my service initiatives. If we
36:06.766 --> 36:10.762
could actually really focus on that and really help, you know, the service professional
36:11.262 --> 36:12.624
to answer that, then they will always be employed.
36:12.993 --> 36:13.796
I could not agree more,
36:13.812 --> 36:17.361
and it's kind of a— it's full circle to where we started. What is the
36:17.827 --> 36:18.999
value of humans and leaders?
36:19.352 --> 36:19.512
Yes.
36:19.737 --> 36:21.886
In this organization. And any
36:21.902 --> 36:24.838
one of us can spin up Claude, Gemini,
36:24.966 --> 36:28.432
ChatGPT, and become an instant expert on a specific theme
36:28.897 --> 36:32.506
or a specific topic for a moment. But that would augment
36:33.006 --> 36:36.821
us. What's our, what's our thesis? What's our experience? What's our DNA? What are we
36:37.321 --> 36:39.549
actually trying to do? That's the bit, you know, and the skill set that we
36:40.049 --> 36:43.318
have that isn't replicable unless you taught it, you experience
36:43.818 --> 36:46.704
it, you spread it versus I can learn it off a page. And I think
36:47.204 --> 36:50.304
that's where the value of humans, the value of these conversations, the value of people
36:50.320 --> 36:54.240
who are advocating for a service ethos will continue
36:54.740 --> 36:55.478
to be valuable in the future.
36:55.944 --> 36:58.161
I agree. And long may that be the case.
36:58.338 --> 37:01.873
Indeed. Joe, it's an absolute privilege and pleasure as always. I could talk to you
37:02.033 --> 37:05.440
all afternoon. So thank you. Thank you for taking the time.
37:05.729 --> 37:08.846
Thank you also for being such an ambassador in terms of service.
37:09.023 --> 37:12.583
We need far more of this and we need to better drive that. So thank
37:13.083 --> 37:13.905
you for all you are doing.
37:13.954 --> 37:14.378
Yeah, thanks,