Ian Golding talks CX Measures, Metrics and ROI - YouTube

Channel: unknown

[7]
Hi everyone, this is Janelle
[8]
here from Amplified Customer
[10]
Experience. And today I have Ian
[11]
Golding here with me and we are
[13]
going to explore a CX win that
[16]
he has to share with us. So we
[17]
want to look at the elements
[20]
that make a cx project
[21]
successful and most particularly
[23]
thinking about measures, metrics
[25]
and ROI. So Ian, do you want to
[27]
introduce us to this project
[29]
that you maybe have in mind to
[30]
share with
[32]
I'm going to share something
[33]
that's quite old. I say quite
[35]
old. I'm one of these people
[37]
who's gray on the inside, not
[39]
the outside, so I'm much older
[40]
than I look anyway. And many
[44]
customer experience wins in
[47]
inverted commas. It doesn't
[49]
matter when you won. When it
[52]
happens, if it is something that
[55]
drove what I call demonstrable
[57]
change, and it's something that
[59]
should always be leveraged to
[61]
inspire and influence others to
[63]
do the same. And one of the most
[68]
significant wins, if I can
[71]
describe it that way, in my
[73]
career as a customer experience
[75]
professional came in 2007. So
[80]
it's 13 years ago now, but 13
[84]
years later, what happened in
[86]
2007 has become a hugely
[90]
significant element of not just
[94]
what I share knowledge with
[96]
people about but how I approach
[99]
helping organizations to improve
[102]
customer experiences all around
[103]
the world. And the when was
[106]
this. When I was great head of
[110]
customer experience for an
[111]
online retailer. At the time, we
[114]
were the second largest online
[116]
retailer in the UK. of the good
[119]
old Amazon is After one second
[122]
what I wanted to be able to do
[126]
was to help my leadership
[129]
understand the relationship
[132]
between what we were doing every
[134]
day as an organization, and how
[137]
the customer felt about what we
[139]
did every day. Because we've
[142]
been measuring at the time
[144]
customer satisfaction to six
[146]
years by this stage. And
[149]
everyone knew how the customer
[152]
felt about everything. But no
[155]
one had any real understanding
[160]
as to why. Because my
[163]
background, and I don't want
[164]
anyone to think badly of me when
[166]
I say this. And my background,
[168]
ultimate background is in
[169]
process improvement. And I'm a
[171]
Lean Six Sigma master black
[172]
belts, amongst other things, but
[174]
I only share that with the few,
[175]
not the many. And I was brought
[178]
up understanding But what we
[180]
needed to be able to do was
[182]
recognize the connection between
[185]
cause and effect we did, and how
[188]
that made someone feel as a
[190]
result. And so what I understood
[194]
is that I was in an organization
[196]
that thought it understood the
[198]
effects and everything. I
[200]
thought it understood what
[202]
customers weren't happy about.
[205]
But there was no connection to
[207]
the cause what was causing them
[208]
to feel that way? So I wanted to
[211]
do something about it. And
[213]
measurement, in my opinion is
[215]
the most important competency
[217]
when it comes to this subject of
[219]
customer experience, because
[221]
unfortunately, too often,
[223]
customer experience
[224]
professionals working in an
[226]
environment where they're trying
[227]
to change mindset can be accused
[230]
of being over passionate, you
[234]
know, evangelical, preachy, you
[238]
know, all of these words that
[239]
are true Trying to demean us,
[241]
largely because people are
[243]
fearful of those who are trying
[245]
to make change happen. And so,
[248]
for us to move the conversation
[251]
away from, you know, the over
[254]
enthusiasm, the best way of
[256]
doing that is to stop being
[258]
subjective and start talking
[261]
facts. If we've got facts, then
[264]
people can throw whatever words
[265]
they want to me. But I've got
[268]
facts that you know, you can't
[269]
argue with the facts. So, what I
[271]
wanted to do was to create a
[274]
mechanism that enables our
[277]
organization to measure
[279]
everything that we did, that
[282]
enabled the touch points in our
[284]
customer journey to become a
[286]
reality. In other words, I
[289]
wanted to measure processes,
[291]
what our people did every day.
[294]
Now, if you work in an
[296]
organization, and you will know
[298]
this, that is not customer
[300]
centric. If you approach a
[304]
processor and say to them, I
[306]
want to start measuring what
[307]
your team do, it doesn't
[310]
particularly land very well. In
[313]
fact, you suddenly become public
[315]
enemy number one. Because all
[317]
that's going through the mind
[318]
that that processing is here
[321]
comes that smart smarty pants,
[323]
who thinks that he's going to
[325]
start demonstrating how bad you
[327]
might see me doing things. So
[329]
I'm going to make this guy look
[330]
even smaller than I was making
[332]
before. So to cut a very long
[334]
story short, what I wanted to do
[337]
was to create a mechanism to
[339]
measure operational processes in
[342]
alignment with the customer
[344]
journey in an environment where
[347]
those who owns the operational
[350]
processes, didn't want me to do
[352]
it. And so I did it anyone and
[356]
this is a message that I deliver
[357]
to any customer experience
[359]
professionals. is starting to
[361]
grapple with how to make change
[363]
happen. And it's the message of
[365]
seek forgiveness. Never ask
[367]
permission to do these things.
[370]
If you're doing the right thing
[371]
for the right reason, then just
[373]
do it, you know and seek
[375]
forgiveness later. What I needed
[378]
to demonstrate to the senior
[380]
leaders is that I was not doing
[382]
this to humiliate their
[384]
immediate reaction is you're
[387]
going to show us show everyone
[388]
how bad we are. But actually,
[390]
that wasn't the case. I wanted
[394]
them to understand this. Where
[396]
is it that we are unable to do
[398]
what we need to do? So as a
[401]
result, it's having the biggest
[402]
negative effects on the way the
[404]
customer feels. So what I want
[406]
to do is not humiliate you, but
[409]
I want to help build the
[411]
business case that demonstrates
[413]
why you need people a system
[417]
something else because it's the
[420]
The only way you're going to
[421]
improve the ability of that
[423]
process to do what the customer
[424]
needs you to do, or in Meg's is
[427]
that I had to become the
[429]
ultimate diplomat, that the
[431]
ultimate diplomat using fact to
[434]
help them feel much better about
[437]
what they were trying to do to
[438]
help them actually show off and
[442]
not be worried that I was making
[443]
them feel stupid. And you know
[446]
what, this was not easy. What
[448]
I'm describing, I actually call
[450]
voice of the process. This is
[454]
the third of three voices of
[456]
measurement, sharing knowledge
[460]
about but whilst it's not easy,
[463]
and in the early stages of
[464]
trying to do something like
[465]
this, you won't be popular.
[467]
Doing that in my organization
[469]
was groundbreaking. And we
[471]
demonstrated the correlation
[474]
between improving operational
[476]
performance and improving
[479]
customer perception. We embedded
[484]
measurements of operational
[486]
process across the end to
[489]
engine. Even if something wasn't
[492]
a priority, there was an
[493]
accountable processing,
[495]
maintaining performance or
[496]
driving incremental improvement.
[498]
We completely change the nature
[500]
of the way the business thought
[502]
about what he did. And it is
[505]
something that I've since
[506]
replicated in 15 different
[509]
organizations in different
[510]
industries around the world. It
[512]
is so powerful, but it's hard to
[515]
do and it's hard to do because
[520]
in addition to not making
[521]
yourself popular, process
[523]
management principles have
[524]
disappeared for businesses. So
[526]
trying to determine who is
[527]
accountable for a process is
[529]
nigh on impossible for many
[531]
organizations. If no one is
[534]
accountable for a process, it's
[536]
also extremely likely that
[537]
process isn't being measured. So
[540]
you've actually got to even
[541]
start measuring it. These are
[544]
fundamental, but remarkably
[547]
simple disciplines that just are
[550]
not there in businesses anymore.
[552]
But the final point I will make
[554]
is that in this connection to
[556]
return on investment, return
[560]
when it comes to customer
[561]
experience is about three
[562]
things. It is about revenue
[565]
generation. The revenue
[567]
generation is the focusing on
[572]
customer experience. So many
[574]
people that run businesses think
[576]
that that is the only return
[578]
and when they do not see revenue
[581]
increase from their customer
[583]
experience program in six
[585]
months, they want to give up
[586]
because it doesn't work. The
[589]
other two returns that are the
[592]
short term returns are cost
[594]
reduction and cost avoidance by
[597]
eliminating the random In the
[601]
experiences that the
[602]
organization delivers, by
[604]
stopping things from going
[606]
wrong, that's where the
[608]
immediate return comes from. And
[610]
that's where organizations
[612]
should be saving a fortune, that
[615]
then gives them the time and
[616]
space to deliver that longer
[619]
term revenue generation in the
[620]
future. So, very, I hope I
[623]
haven't gone on for too long.
[624]
But it is a hugely important
[627]
thing. voice that the process is
[630]
not happening in organizations
[632]
around the world. It can change
[634]
the game.
[637]
There's so many different
[638]
strings I want to pull on here
[639]
in but for the sake of time, and
[641]
because I know that just so many
[643]
people are struggling with the
[645]
concept of measurement, metrics
[647]
and ROI. What are you know,
[651]
maybe the one two or three kind
[653]
of tips that you would give to a
[656]
cx team that's really struggling
[657]
with securing their place and
[659]
then value in an organization.
[663]
So I think you need to be able
[666]
to demonstrate, firstly, to
[669]
senior leaders who are
[671]
responsible for processes
[673]
without necessarily even
[675]
realizing it, that you are there
[678]
to help them. You're not there
[680]
to humiliate them. You're there
[683]
to help them. You're there to
[685]
give them the facts, the facts
[687]
that are produced that matches
[690]
their facts. You want to help
[692]
them build a case. So their
[695]
people can do what they do
[697]
better, quicker, more
[699]
accurately, whatever it might
[701]
be. And if you can facilitate
[705]
that conversation that you are
[707]
there to help them, you are
[709]
there to make them look good.
[711]
That's what this is about. It's
[713]
not about us, it's about them.
[716]
Then you will start to see both
[718]
their eyes opening up doors
[720]
opening at the same time. You
[722]
know, this is not about us. I've
[725]
always said to people that being
[727]
a customer experience
[728]
professional isn't about getting
[729]
a job title and a big salary.
[732]
You know, if that's what it's
[733]
about, this is the wrong
[734]
profession. You know, the
[735]
benefit comes later. You know,
[737]
this is about us, doing whatever
[740]
we need to do to help an
[742]
organization, do what is
[744]
necessary to deliver better
[745]
experiences for its customers.
[748]
And if that means that sometimes
[750]
you got to be unpopular, then so
[752]
be it. But if it's for the right
[753]
reason, that's fine. You know,
[755]
if it means that we never get
[758]
promoted, you know, we're never
[759]
given you know, that seats at
[761]
the top, who cares? That's not
[763]
what it's about. You know, it's
[765]
got to be about the good of the
[766]
organization. And if that's what
[768]
you focus on, not only will it
[771]
happen, you know, you will
[773]
become a wonderful example of
[776]
the customer experience
[777]
professional. He will have a
[778]
very long very fruitful and
[781]
remarkably rewarding career. But
[784]
that's what this is all about.
[786]
Thanks so much and I really
[788]
appreciate you taking some time
[789]
to connect with my viewers. And
[792]
for those of you who are
[793]
interested in connecting with
[794]
Ian further, all of his contact
[796]
information will be in the
[796]
description below. Thanks,
[798]
everyone.
[799]
Thank you