The player is loading ...
Oct. 3, 2024
Procurement: The Unsung Hero of Business Success with Dr. Elouise Epstein
This episode of How I Met Your Data welcomes Dr. Elouise Epstein, a digital futurist, to discuss the often overlooked world of procurement. Listeners will learn what procurement is and why it's essential to business success. Dr. Epstein provides insights into the challenges that procurement teams face, including a lack of spend transparency, reliance on outdated technology, and the struggle to keep up with a rapidly evolving digital landscape. She also shares her vision for the future of procurement, where supply chains become a core competitive advantage, driven by data, AI, and a deep understanding of supplier relationships. This episode is a must-listen for anyone interested in data, technology, and the future of business.
Chapters
00:00 - Welcome Back to How I Met Your Data
02:37 - Understanding Procurement
08:33 - The Role of a Digital Futurist
13:16 - Myths About Procurement
19:32 - Gen AI in Procurement
24:46 - The Future of Supply Chains
32:12 - Data Strategies for Procurement
Transcript
WEBVTT
00:00:00.017 --> 00:00:03.117
Welcome, welcome. Welcome back to How I Met Your Data.
00:00:03.257 --> 00:00:09.017
Sandy Estrada here, myself and my co-host Anjali Banzal. Could not be more excited to be back.
00:00:09.257 --> 00:00:13.477
I know we took a little bit of hiatus for the summer, but we're back and ready
00:00:13.477 --> 00:00:18.397
to go with two more episodes for you to wrap up our first season of How I Met Your Data.
00:00:18.397 --> 00:00:23.097
We are so proud of what we've created here, and we cannot wait to share the
00:00:23.097 --> 00:00:24.637
last two episodes with you.
00:00:24.777 --> 00:00:31.857
And for this episode, myself and Anjali have asked Dr. Eloise Epstein to join us. So Dr.
00:00:32.037 --> 00:00:37.457
Epstein is a Carney partner, a published author, a prolific keynote speaker
00:00:37.457 --> 00:00:42.777
at supply chain and procurement events, and a dear advisor to me.
00:00:42.777 --> 00:00:47.517
I have gotten to know her over the last four and a half years as Carney has acquired Cervelo.
00:00:47.897 --> 00:00:51.757
And I just love chatting with her. She's just so chock full of insights and
00:00:51.757 --> 00:00:55.277
has a lot of fun pet peeves, some of which we will touch upon today.
00:00:55.797 --> 00:00:59.157
She's also a digital futurist. So you're going to hear a little bit about what
00:00:59.157 --> 00:01:03.197
that means during this episode. We wanted to wrap up the season with Dr.
00:01:03.477 --> 00:01:09.177
Eloise Epstein primarily because our goal has always been for this podcast to
00:01:09.177 --> 00:01:15.417
showcase all the different aspects and the kaleidoscope view that is the data world.
00:01:15.757 --> 00:01:21.157
And regardless of where you're coming from, for example, we are data consultancies.
00:01:21.177 --> 00:01:25.457
We help data leaders and business executives get the most out of data.
00:01:25.637 --> 00:01:28.937
You have your data leaders. You have business executives perspectives.
00:01:29.237 --> 00:01:31.597
You have software vendor perspectives.
00:01:32.077 --> 00:01:37.297
You have the, you know, data consumer perspectives. You have others as well
00:01:37.297 --> 00:01:40.057
that are impacting what people need to do with data.
00:01:40.117 --> 00:01:42.357
One of those others is a management consultant.
00:01:42.537 --> 00:01:47.177
And Eloise gives you a really good insight into how they think and how they help their clients.
00:01:47.377 --> 00:01:50.657
I mean, it's just another aspect of that kaleidoscope. And we wanted to shine
00:01:50.657 --> 00:01:55.977
a light on that and ensure that we have the full breadth of voices that make
00:01:55.977 --> 00:02:01.877
data work so challenging and intriguing and interesting for us who are in it
00:02:01.877 --> 00:02:04.797
because it is a tapestry of personalities,
00:02:05.157 --> 00:02:10.377
a tapestry of point of views, a tapestry of knowledge that comes together to
00:02:10.377 --> 00:02:12.737
create insight for an individual.
00:02:12.877 --> 00:02:18.337
So with data. So with that said, here's our conversation with Dr. Eloise Epstein.
00:02:18.480 --> 00:02:37.680
Music.
00:02:37.524 --> 00:02:40.964
So thank you for spending some time with us to have this conversation, Eloise.
00:02:41.184 --> 00:02:44.844
I think when we started thinking about this podcast, Anjali and I made a whole
00:02:44.844 --> 00:02:47.984
list and your name was probably the first one I had put on the list,
00:02:48.044 --> 00:02:50.724
but wasn't the first person we reached out to. I don't know why.
00:02:51.064 --> 00:02:52.284
I'm honored to be on the list.
00:02:52.704 --> 00:02:57.164
So thanks for doing this with us. The first thought that comes to mind,
00:02:57.244 --> 00:02:59.704
for me, procurement is part of my world.
00:02:59.764 --> 00:03:04.884
I started my career in basically helping FP&A and all roads from a cost perspective
00:03:04.884 --> 00:03:05.724
start with procurement.
00:03:05.984 --> 00:03:10.544
I'm sure a lot of our listeners don't have a background focused on that topic.
00:03:10.744 --> 00:03:15.724
And I was showing Anjali a video that you had put together answering a video
00:03:15.724 --> 00:03:18.704
that John Oliver had, which was really comical.
00:03:18.824 --> 00:03:22.464
But I figured, could you explain to our listeners what procurement is?
00:03:22.704 --> 00:03:28.604
Yes. So absolutely everybody, or at least in the Western world,
00:03:28.684 --> 00:03:29.984
is a procurement person.
00:03:30.164 --> 00:03:34.964
We are procurement people in our personal lives. When we go to buy a car,
00:03:35.064 --> 00:03:37.924
we negotiate a price or we do various negotiations.
00:03:38.544 --> 00:03:43.984
We manage to some degree, some less or more than others.
00:03:44.144 --> 00:03:47.624
Our money, how it comes in, where we're spending it.
00:03:47.784 --> 00:03:51.864
We look for deals on whatever it is we need to buy.
00:03:52.004 --> 00:03:57.024
Or when we go to make a big purchase, we look at reviews, get recommendations.
00:03:58.164 --> 00:04:02.064
We buy products and look at the quality over time.
00:04:02.444 --> 00:04:08.424
And so all of those concepts, everything I just said, is us in our individual
00:04:08.424 --> 00:04:10.204
lives doing procurement.
00:04:10.384 --> 00:04:15.944
And it stands to reason, of course, that big companies as well do the same thing.
00:04:16.064 --> 00:04:18.424
They spend a lot of money and...
00:04:19.187 --> 00:04:24.167
Other than salaries, money that goes out the building goes to suppliers.
00:04:24.387 --> 00:04:28.747
And so looking for deals, looking for quality, looking for availability.
00:04:29.347 --> 00:04:31.947
Et cetera, et cetera, managing to budgets.
00:04:32.267 --> 00:04:36.527
That's pretty much what procurement does in the corporate environment.
00:04:36.807 --> 00:04:42.647
And you would be surprised or maybe not shocked, but surprised at how the bigger
00:04:42.647 --> 00:04:46.507
the company, the more they struggle to just understand where they're spending
00:04:46.507 --> 00:04:49.847
their money, much less control it. What do you think is driving that?
00:04:50.007 --> 00:04:51.467
Well, it can be a lot of factors.
00:04:51.787 --> 00:04:57.067
One is oftentimes growth mindsets. When you grow at all costs,
00:04:57.247 --> 00:05:01.387
grow, innovate, disrupt, that's not always cost saving.
00:05:01.667 --> 00:05:06.507
So when you look at the growth drivers of the economy, certainly big tech is
00:05:06.507 --> 00:05:11.607
there, even big oil, all of them are high growth.
00:05:11.987 --> 00:05:16.947
And so when you're in high growth mode, you're not really managing to the bottom line.
00:05:16.947 --> 00:05:22.027
And especially where you have industries with lots of mergers and acquisitions
00:05:22.027 --> 00:05:26.787
or the rise of private equity, all of those together, you are constantly adding
00:05:26.787 --> 00:05:29.947
and subtracting businesses. And this I'm sure you can appreciate.
00:05:30.247 --> 00:05:34.627
You have different accounting methods, different classifications,
00:05:34.907 --> 00:05:40.547
you're taking different ERP systems, and you're trying to bring all these companies
00:05:40.547 --> 00:05:44.767
together. These companies are not just single building entities.
00:05:45.127 --> 00:05:50.607
They are massive global conglomerates that have many, many, many subsidiaries
00:05:50.607 --> 00:05:53.667
in different operating companies.
00:05:54.007 --> 00:05:55.647
And so it can be hard.
00:05:56.564 --> 00:06:01.104
To bring all of that stuff together. Now, that's the positive side.
00:06:01.184 --> 00:06:07.724
The negative side is, in general, we have not had at least the resourcing or
00:06:07.724 --> 00:06:10.744
the capabilities to do that management.
00:06:11.104 --> 00:06:15.984
And procurement as a function is only like 25, 30 years old.
00:06:16.144 --> 00:06:22.424
So we're still in our infancy. So we haven't had generations of schools putting
00:06:22.424 --> 00:06:26.924
out homogenized skill sets that have come into the market.
00:06:27.204 --> 00:06:30.524
Yeah. It was definitely not a topic when I was in college.
00:06:31.424 --> 00:06:35.964
No, no, nor I. It wasn't. Yeah. Yeah. So Eloise, I'm curious, right?
00:06:36.064 --> 00:06:42.464
So if procurement is kind of in its infancy, where were those activities handled
00:06:42.464 --> 00:06:45.104
before or how are those activities handled before?
00:06:45.464 --> 00:06:51.284
Well, either they weren't or they were in finance. So oftentimes you'll see
00:06:51.284 --> 00:06:53.344
procurement still reporting to finance.
00:06:53.604 --> 00:06:57.424
At its most basic, procurement is cost control. To your question,
00:06:57.544 --> 00:07:02.884
historically, it has been this, okay, you've set your budget and now you're going to go buy.
00:07:03.144 --> 00:07:09.164
Well, you should probably buy with some strategic intention behind it or understanding
00:07:09.164 --> 00:07:14.224
so you're not overpaying for license or software licenses or buying duplicate
00:07:14.224 --> 00:07:17.884
items or introducing reducing needless complexity.
00:07:18.104 --> 00:07:21.764
So if you think about a warehouse, supplies that go into that warehouse,
00:07:21.864 --> 00:07:27.844
not the goods that come in, but the gloves and the safety glasses and Gatorade and whatever else,
00:07:28.024 --> 00:07:32.804
you might have six different suppliers coming and going into that warehouse
00:07:32.804 --> 00:07:40.524
on a daily basis when actually one supplier could service all of your needs to run that warehouse.
00:07:40.804 --> 00:07:45.284
And you would cut down on the number of traffic, the number of suppliers that you have to manage.
00:07:45.284 --> 00:07:48.944
So part of it's that or, and this is the one that just kills me,
00:07:48.964 --> 00:07:52.304
is you have a business unit in North America, one in the UK,
00:07:52.704 --> 00:07:57.964
buying the same software off two different contracts and paying two different prices.
00:07:58.584 --> 00:08:02.504
So a lot of procurement as we mature is looking at that and saying,
00:08:02.624 --> 00:08:08.124
you know, if we bundled off the same, bought off the same contract, then we can do more.
00:08:08.264 --> 00:08:11.844
Yeah, I mean, I think one of the things that we run into on the data side is
00:08:11.844 --> 00:08:14.684
multiple acquisitions of the same third party data sets.
00:08:15.289 --> 00:08:21.149
Yeah, yeah. Same thing. Same thing. So if you had a strong procurement function
00:08:21.149 --> 00:08:25.649
where you saw where you were spending your money, you would catch that right away.
00:08:25.809 --> 00:08:30.169
Like that would be low hanging fruit to to because because that that's exactly
00:08:30.169 --> 00:08:33.689
then that happens, especially with third party data all the time. For sure.
00:08:33.829 --> 00:08:37.909
So now Eloise, you described yourself as the procurement futurist.
00:08:38.009 --> 00:08:43.809
So can you help us understand what that means and what you focus on in your role?
00:08:44.009 --> 00:08:48.689
Yeah. So I actually have sort of rebranded to be more of a digital futurist.
00:08:48.729 --> 00:08:56.089
What I mean by that is I look at where we are today and where we could be in the future.
00:08:56.209 --> 00:09:01.109
So I look at it unconstrained and I work backwards to where we are today.
00:09:01.409 --> 00:09:06.649
Too often when we do roadmaps, too often when we do transformations.
00:09:07.589 --> 00:09:11.389
We look at where we are today and what we can do incrementally.
00:09:11.429 --> 00:09:16.689
And I try to pick a point, a North Star, whatever term you want to use and say,
00:09:16.909 --> 00:09:20.789
no, this is where we should be and how do we work backwards to get there?
00:09:20.869 --> 00:09:25.909
I don't do the whole, oh, we'll have electric city and autonomous cars and blah,
00:09:25.969 --> 00:09:31.009
blah, blah. I try to anchor very much into where we are today and where we could
00:09:31.009 --> 00:09:33.489
get to if we had a huge leap.
00:09:33.669 --> 00:09:39.169
Now, I know that we're never going to get there, but I feel like my job is to
00:09:39.169 --> 00:09:42.669
push us to think bigger and raise our trajectories higher.
00:09:42.909 --> 00:09:49.409
Yeah, I love that because the reality of most situations that you get into when
00:09:49.409 --> 00:09:52.909
an organization is trying to go through any kind of, even if it's a small transformation
00:09:52.909 --> 00:09:56.329
of a specific area or process or a technology,
00:09:56.509 --> 00:10:00.109
they work within the constraints or only think through within the constraints.
00:10:00.449 --> 00:10:05.089
And I often think about, you know, the whole, and everyone uses this metaphor
00:10:05.089 --> 00:10:10.289
to some extent even in marketing today, but the idea of going to the moon, right?
00:10:10.389 --> 00:10:15.389
And how wild that was at the time when that vision was put out there,
00:10:15.449 --> 00:10:17.629
but it required everybody to think outside the box.
00:10:18.098 --> 00:10:21.478
So when you think incrementally, you're always thinking inside the box in which
00:10:21.478 --> 00:10:24.738
you're living in and working in and with the people that you have to work with
00:10:24.738 --> 00:10:25.938
and the budgets that you have.
00:10:25.958 --> 00:10:31.798
But when you think unconstrained, sometimes solutions come out of nowhere that
00:10:31.798 --> 00:10:34.658
you couldn't think of before. Right. And I'll give you a perfect example.
00:10:34.938 --> 00:10:38.858
Look at everybody's quote unquote digital transformations these days.
00:10:39.098 --> 00:10:44.878
It's really just upgrading to the next version of the ERP system.
00:10:44.878 --> 00:10:48.518
But very commonly it's, hey, our digital transformation is going to be around
00:10:48.518 --> 00:10:53.858
consolidating our 20 or 50 or 100 ERP systems down to one S4 instance.
00:10:54.138 --> 00:10:56.198
And that's fine, but that's incremental.
00:10:56.518 --> 00:11:00.338
That's not transformational. And one, if you took a step back,
00:11:00.378 --> 00:11:08.598
one, me, might argue that the ERP is a deprecated technology. We are well beyond that.
00:11:08.638 --> 00:11:14.658
The way the modern enterprise works is not relevant to the way the world is today.
00:11:14.878 --> 00:11:18.598
So in my world, we don't start with the premise that you're going to build your
00:11:18.598 --> 00:11:20.158
transformation off the ERP.
00:11:20.198 --> 00:11:23.498
I question, do we even need the ERP anymore?
00:11:23.818 --> 00:11:27.198
And what would that post-ERP world look like?
00:11:27.338 --> 00:11:32.218
And then I draw it back to where we are today. day. So truly outside the box
00:11:32.218 --> 00:11:36.858
is challenging just the basic assumptions, because guess what?
00:11:36.978 --> 00:11:40.918
There's going to be billions, if not hundreds of billions spent on,
00:11:40.978 --> 00:11:47.458
oh, I want to pick on SAP today, but on SAP upgrades that are not going to transform anything.
00:11:47.698 --> 00:11:52.198
And that's okay. Like SAP will make money, systems integrators will make money,
00:11:52.358 --> 00:11:58.198
partners will get new Mercedes or Teslas, But don't confuse that with actually
00:11:58.198 --> 00:12:01.818
transforming the organization to become more digital.
00:12:01.958 --> 00:12:05.738
And even I will oftentimes just ask the more fundamental question.
00:12:06.638 --> 00:12:12.118
Are you sure you want to operate as a digital company? Because what you often get.
00:12:12.733 --> 00:12:17.593
Is these old companies that are, I don't know, 50, 100, 200 years old.
00:12:17.853 --> 00:12:21.833
And they look at Silicon Valley here and they're like, oh, I want to be like
00:12:21.833 --> 00:12:24.293
Google. So we're going to go be a data company.
00:12:24.573 --> 00:12:29.793
And all of a sudden you have, I don't know, 50,000 employees that are,
00:12:29.853 --> 00:12:35.593
and many of them probably mid-career or higher or older, and they're not going
00:12:35.593 --> 00:12:36.593
to make that transition.
00:12:36.593 --> 00:12:39.433
Position and and and i mean i'm sure you both
00:12:39.433 --> 00:12:42.513
see it your way oh we want to be data driven
00:12:42.513 --> 00:12:46.113
we want to be ai this we want to be whatever advanced
00:12:46.113 --> 00:12:51.753
analytics money ball blah blah blah but but the reality is there is you can't
00:12:51.753 --> 00:12:57.633
just wish that there that takes a long time to get people in that realm and
00:12:57.633 --> 00:13:02.113
so so i will encourage people to get there but i will also poke them with a
00:13:02.113 --> 00:13:04.973
stick yeah there's a realism to the situation, right?
00:13:05.153 --> 00:13:09.833
You can't get people to change overnight despite what their ambition may be.
00:13:10.213 --> 00:13:13.973
But there's tangible steps we can take along the way to at least get them a
00:13:13.973 --> 00:13:16.073
little bit closer to what you're hoping for.
00:13:16.373 --> 00:13:20.793
100%. So as you mentioned, procurement is 25, 30 years old.
00:13:21.073 --> 00:13:25.733
And I find, at least in the work that we've done for our clients,
00:13:25.973 --> 00:13:29.073
procurement and the problems procurement have and the challenges procurement
00:13:29.073 --> 00:13:34.413
have are often overlooked looked until there's actually a serious issue with cost management.
00:13:34.553 --> 00:13:39.693
I guess, what is the biggest myth or misconception you've come across regarding
00:13:39.693 --> 00:13:41.613
the importance of procurement?
00:13:42.053 --> 00:13:46.353
I don't know about misconception, but first I'll start with a story because
00:13:46.353 --> 00:13:49.073
the way you set that question up is perfect for the story.
00:13:49.173 --> 00:13:55.173
I live in the Bay Area, Silicon Valley, and every so often the big tech companies will.
00:13:56.124 --> 00:14:01.964
Ask us and other procurement folks to come pitch or to come give them a briefing or whatever.
00:14:02.324 --> 00:14:07.264
And you walk in and there's just this arrogance and there's like,
00:14:07.384 --> 00:14:09.644
yeah, well, we're just printing money.
00:14:09.744 --> 00:14:13.524
So it's cute what you're doing. That's really fun.
00:14:13.744 --> 00:14:18.044
I'm happy for you that you're doing that. And then something in the market changes, whatever.
00:14:18.284 --> 00:14:21.304
And then like all of that revenue doesn't like decline.
00:14:21.404 --> 00:14:25.704
It like goes off a cliff. And then all of a sudden they They become big believers
00:14:25.704 --> 00:14:29.844
in procurement because they have to cut costs fast.
00:14:30.224 --> 00:14:35.444
And you've seen that over the last few years up and down the West Coast.
00:14:35.804 --> 00:14:40.904
And so for a company to be profitable, you can either cut costs one of two ways.
00:14:41.004 --> 00:14:46.764
You can cut people or you can manage your external spend with suppliers and
00:14:46.764 --> 00:14:48.404
your contracts and so forth.
00:14:48.404 --> 00:14:53.904
And I like to do the working with suppliers to renegotiate or to negotiate better
00:14:53.904 --> 00:14:57.864
terms and manage payments versus firing people because firing people doesn't
00:14:57.864 --> 00:15:01.744
necessarily, well, first of all, it's not sustainable and it's not helpful.
00:15:01.824 --> 00:15:06.344
And it's a huge black eye in the public from a public relations point of view.
00:15:06.404 --> 00:15:10.904
Oh, is earlier this year, I'd worked with a client that was really trying to
00:15:10.904 --> 00:15:15.844
get their arms around understanding the spend of their sites around the globe.
00:15:15.844 --> 00:15:20.804
Like we're really looking into spend transparency for several hundred sites.
00:15:21.124 --> 00:15:25.764
And one of the things that was really clear as we're going through that process
00:15:25.764 --> 00:15:32.164
was the team that was looking for that transparency simply didn't have the data
00:15:32.164 --> 00:15:36.364
that they were looking for or were unaware of the data that was available to
00:15:36.364 --> 00:15:38.884
help them get that level of transparency. heresy.
00:15:39.124 --> 00:15:45.504
So as data leaders, whoever really worked closely with these types of teams,
00:15:45.604 --> 00:15:46.644
with these procurement teams,
00:15:46.904 --> 00:15:51.764
are there any sort of strategies or things that they should be thinking about
00:15:51.764 --> 00:15:56.784
in order to build better collaboration so there is that visibility and ability
00:15:56.784 --> 00:15:59.564
to use the data that's available to them?
00:15:59.744 --> 00:16:04.624
Okay. So this is my, I'll say fundamental mental pet peeve, but I probably have a thousand of them.
00:16:04.824 --> 00:16:11.244
In procurement, job one or job zero is understanding where you're spending your money.
00:16:11.404 --> 00:16:16.604
So any procurement organization that doesn't have good spend transparency is
00:16:16.604 --> 00:16:18.984
not doing their job and they should be fired.
00:16:19.164 --> 00:16:21.224
We can't talk about negotiating.
00:16:21.544 --> 00:16:26.104
We can't talk about contract management, relationship management until we actually
00:16:26.104 --> 00:16:27.584
know what we're spending where.
00:16:28.343 --> 00:16:34.463
And there is no excuse for not knowing where you're spending your money.
00:16:34.623 --> 00:16:40.543
Not only that, but if you have dirty spend data and supplier data,
00:16:40.903 --> 00:16:43.083
that's a procurement leadership failure.
00:16:43.223 --> 00:16:48.883
And I will call anybody out and I will go right after procurement executives
00:16:48.883 --> 00:16:51.683
for not having that data readily available.
00:16:52.063 --> 00:16:57.583
And I've heard every excuse in the book for the last 20, almost 25 years.
00:16:57.583 --> 00:16:59.563
But I'm not having it anymore.
00:16:59.883 --> 00:17:04.903
There are plenty of solutions, both you can buy, you can build.
00:17:05.143 --> 00:17:09.803
So there's no excuse for not having good spend transparency.
00:17:10.183 --> 00:17:15.043
What you have in the situation you described is intransigence,
00:17:15.323 --> 00:17:18.443
maybe incompetence. I don't want to be pejorative.
00:17:18.623 --> 00:17:24.003
But you certainly have people that are not taking the job seriously because
00:17:24.003 --> 00:17:30.383
it's not acceptable. And getting data out of those places, that's not hard.
00:17:30.563 --> 00:17:35.303
To me, you go all the way up to the CEO if you need that, if you're the procurement
00:17:35.303 --> 00:17:37.263
leader, because that's your job.
00:17:37.363 --> 00:17:42.183
If you don't have that, then we're not having a realistic conversation.
00:17:42.423 --> 00:17:44.083
We are just playing pretend.
00:17:44.423 --> 00:17:50.343
And well, that's not for me. Interesting, though, because I've met CPOs who,
00:17:50.443 --> 00:17:55.263
when asked directly, do you have category management spend figured out?
00:17:55.263 --> 00:17:57.223
Like, do you have it readily accessible?
00:17:57.643 --> 00:17:59.683
The answer is often no. Right.
00:18:00.263 --> 00:18:04.703
So I asked that same question and then, then my followup and I don't even give
00:18:04.703 --> 00:18:09.283
them a chance is like, so why, why not? That's your job.
00:18:09.963 --> 00:18:15.463
Like, like, what are you doing? Like, like, like, I mean, I say it more diplomatically,
00:18:15.503 --> 00:18:20.023
but, but there are no, like literally there is no excuse for not having that.
00:18:20.063 --> 00:18:22.783
I mean, even if you've only been in the job 60 days, Jesus.
00:18:23.167 --> 00:18:26.407
There's no reason you can't. And you have nothing. Like you walk in the door,
00:18:26.447 --> 00:18:30.307
there's nothing. In 60 days, you can have good spend data.
00:18:30.487 --> 00:18:34.487
There's spend transparency, I should say. I'm not buying that excuse.
00:18:34.747 --> 00:18:43.067
That to me, when they say that, like alarm bells go off because they are either scared,
00:18:43.367 --> 00:18:49.807
incompetent, and I don't mean that as pejoratively as that comes out, Or they're just lazy.
00:18:50.007 --> 00:18:55.127
You can't do procurement effectively if you don't even know where you're spending your money.
00:18:55.367 --> 00:18:57.727
Yeah. Is there a conundrum there, though?
00:18:59.087 --> 00:19:02.687
So as a procurement leader, their job is to lower costs, right?
00:19:02.787 --> 00:19:06.007
In order to solve this problem, there's a cost associated to it.
00:19:06.087 --> 00:19:07.567
Either you're buying or building something.
00:19:07.807 --> 00:19:10.347
Is that it? No, that's bullshit.
00:19:11.467 --> 00:19:16.627
No, that's just like, come on. Don't give me an excuse that it costs too much
00:19:16.627 --> 00:19:17.907
money. it takes too much time.
00:19:18.407 --> 00:19:22.827
Well, I have companies that have gone from zero to full spend transparency in
00:19:22.827 --> 00:19:26.547
three weeks, and that's nine ERP systems, eight GL codes.
00:19:27.007 --> 00:19:32.287
Don't give me excuses. This is a will, like you have to have the will to do it.
00:19:32.627 --> 00:19:37.347
So Eloise, I don't think we can let you go or let this conversation go without
00:19:37.347 --> 00:19:42.747
asking, are there use case for procurement teams to be leveraging Gen AI capabilities.
00:19:43.667 --> 00:19:47.567
Okay. So I'm going to answer this in a different way.
00:19:47.747 --> 00:19:51.847
So the question we always have in procurement was context.
00:19:52.927 --> 00:19:59.487
Procurement kind of came about 25, 30 years ago, and there were some various
00:19:59.487 --> 00:20:01.767
point solution tools that came about.
00:20:02.007 --> 00:20:06.507
And then we started to get consolidation and development of procure to pay,
00:20:06.847 --> 00:20:13.347
which is your raising of of requisitions, fulfilling the requisitions,
00:20:13.347 --> 00:20:15.047
and then paying the suppliers.
00:20:15.367 --> 00:20:18.207
And then we also have what's also known as source to contract,
00:20:18.467 --> 00:20:23.387
which is running sourcing events, running RFPs, awarding business,
00:20:23.967 --> 00:20:27.287
contracting, and managing all the contracts.
00:20:27.507 --> 00:20:31.307
And then taken together, we call it source to pay, which is all of that stuff together.
00:20:31.927 --> 00:20:39.187
So we have a couple decades of source-to-pay providers that built tools that
00:20:39.187 --> 00:20:44.747
are massive and expensive and have failed, absolutely failed to deliver on the promise.
00:20:44.967 --> 00:20:50.947
So we have all this tech debt that is just sitting around that nobody's using, everybody hates.
00:20:51.187 --> 00:20:56.447
And so, of course, what happens when you have a technology that is ineffective?
00:20:57.646 --> 00:21:02.866
We take the data that we can get out, we put it into Excel, and we run our operations.
00:21:03.266 --> 00:21:08.386
I still see RFPs coming in my email with an Excel file attached.
00:21:09.186 --> 00:21:16.426
Or worse, a particular sourcing tool, an RFP tool, which is just simply being
00:21:16.426 --> 00:21:21.866
used to distribute said Excel file, which to me is a double failure, but whatever.
00:21:22.206 --> 00:21:26.606
So the question, so if you take a step back, the question, the provocative question
00:21:26.606 --> 00:21:32.146
there is, is, well, if we have all this tech debt, why don't we just run the whole thing in Excel?
00:21:32.426 --> 00:21:37.566
So that's the equation when we talk about digital roadmaps for procurement.
00:21:37.786 --> 00:21:41.286
Now, of course, nobody's going to admit to doing that.
00:21:42.446 --> 00:21:47.886
You think it's because the process is built incorrectly in these tools because
00:21:47.886 --> 00:21:50.886
the tools have been around for so long and they're monolithic and they're hard
00:21:50.886 --> 00:21:55.926
to... I mean, because I've seen your map of all these applications that have come out.
00:21:56.006 --> 00:21:59.566
And I think that happens in any, I mean, it's happening to ERP systems,
00:21:59.806 --> 00:22:03.086
happening to planning systems, it's happening to every freaking business process
00:22:03.086 --> 00:22:08.346
out there, where it's becoming more purpose built, right?
00:22:08.466 --> 00:22:11.926
Where you can plug and play all these different tools to make an ecosystem of
00:22:11.926 --> 00:22:17.046
products that you're composing a process based on best of breed technologies.
00:22:17.326 --> 00:22:21.106
Is that kind of where it's headed? Plus Gen AI kind of trickled in the gaps?
00:22:21.106 --> 00:22:23.586
Yeah. Let's put it into real terms.
00:22:23.766 --> 00:22:28.626
So my spider map's full of all these logos, but the end user doesn't care.
00:22:28.946 --> 00:22:35.746
They're going to say, I need a plane ticket from San Francisco to Newark, book it for me.
00:22:35.906 --> 00:22:39.146
And it's going to then go figure out what the best price is.
00:22:39.246 --> 00:22:44.026
We have a preferred agreement with United and Hertz and whomever else.
00:22:44.366 --> 00:22:47.786
So it's going to manage all that in the background because I don't care.
00:22:47.786 --> 00:22:53.966
But right now, to do a codebook that, it puts way too much burden on me as the end user.
00:22:54.206 --> 00:23:00.966
And so the reason I set that up is I think Gen AI will change how I interact
00:23:00.966 --> 00:23:06.266
with the system because it will do a good job of interpreting to understand that getting from,
00:23:06.366 --> 00:23:11.686
if I say I need to go from San Francisco to New York, it's going to know that
00:23:11.686 --> 00:23:13.266
I'm probably going to fly United.
00:23:13.566 --> 00:23:19.466
I'm going to want to go nonstop. It might ask me to what time I want to leave
00:23:19.466 --> 00:23:22.226
because it understands the context of my query.
00:23:22.526 --> 00:23:25.786
That's where I think we'll see it. And to your point, which I liked a lot,
00:23:25.926 --> 00:23:27.626
that business process change.
00:23:27.886 --> 00:23:35.166
In fact, there is no process because it's just me and the AI talking and interpreting.
00:23:35.346 --> 00:23:41.866
Whereas the problem with all procurement systems today is you have to pre-define the process.
00:23:42.206 --> 00:23:48.446
Well, humans don't fit well into predefined processes because I might be ordering
00:23:48.446 --> 00:23:52.846
a plane ticket and then in an hour I might need beakers or test tubes.
00:23:53.026 --> 00:23:55.786
And an hour after that, I might need a Salesforce license.
00:23:56.647 --> 00:24:00.927
To predefine and then hard code these processes, this is where it all goes wrong.
00:24:01.107 --> 00:24:03.167
And this is where I'm most excited about Gen AI.
00:24:03.487 --> 00:24:07.327
Yeah. I think everything's heading in that direction, which is exciting and
00:24:07.327 --> 00:24:10.707
terrifying at the same time. And it should be. Yeah. Yeah.
00:24:11.267 --> 00:24:14.567
But we're not doing a great job managing it now.
00:24:14.787 --> 00:24:20.027
And that's the best case. And the worst case is people are just bypassing the systems.
00:24:20.467 --> 00:24:24.467
So we've actually created multi-layered problems.
00:24:24.747 --> 00:24:30.587
I would take the chaos of the AI system where we put in various constraints
00:24:30.587 --> 00:24:33.647
than what we have today, because what we have today is unworkable.
00:24:33.807 --> 00:24:38.267
So if you could predict like one major shift in the procurement industry over
00:24:38.267 --> 00:24:42.467
the next, say, five years, what do you think that would be?
00:24:42.667 --> 00:24:46.107
Well, to answer that question, I have to give you another one of my pet peeves.
00:24:46.927 --> 00:24:48.667
I'm poking all your pet peeves today.
00:24:50.607 --> 00:24:54.067
Yeah, it's not hard. I have a lot of them. So what's a supply chain?
00:24:54.167 --> 00:24:57.367
We've all learned what what supply chains are over the last four years.
00:24:57.890 --> 00:25:04.910
Which is great. To me, supply chains are a national priority for any country
00:25:04.910 --> 00:25:11.010
and they're a strategic, something that we need to really have a better understanding.
00:25:11.350 --> 00:25:15.470
However, we don't have really good definitions as practitioners.
00:25:16.010 --> 00:25:19.810
You can ask a hundred practitioners and you're going to get a hundred different answers.
00:25:20.070 --> 00:25:26.810
And that's the immaturity of our our broader operations function.
00:25:27.210 --> 00:25:31.550
Set that aside for a second. So just to sort of give you my definition,
00:25:31.850 --> 00:25:34.290
because it would be irresponsible if I didn't give you mine.
00:25:34.410 --> 00:25:38.670
So to me, within a supply chain, you have planning,
00:25:39.010 --> 00:25:46.070
demand management, and intake of, whether it's the consumer or the internal
00:25:46.070 --> 00:25:51.650
users, you have some sort of intake mechanism that then needs to be fulfilled.
00:25:51.650 --> 00:25:57.910
Then you have sourcing, which is procurement, essentially, which is where you
00:25:57.910 --> 00:26:01.450
procure all the raw materials you need to produce a product.
00:26:01.710 --> 00:26:05.270
Then you manufacture it and then you deliver it.
00:26:06.150 --> 00:26:11.150
Now, of course, that all is great if you're building a car or a consumer packaged good.
00:26:11.250 --> 00:26:17.630
But if you are a tech company or a bank, you don't have you're not manufacturing anything. thing.
00:26:17.790 --> 00:26:24.470
And so that's where the sort of supply chain falls apart and we kind of get into different worlds.
00:26:24.890 --> 00:26:29.350
But you still have planning and intake and you still have procurement because
00:26:29.350 --> 00:26:34.910
there's things you procure and you still to some degree have distribution and sort of operations.
00:26:35.210 --> 00:26:38.570
So all of that to me is the supply chain.
00:26:38.630 --> 00:26:45.850
I have a whole longer definition in my book, but that's a short So as we evolve.
00:26:46.530 --> 00:26:50.470
Supply chains can be a competitive advantage.
00:26:50.830 --> 00:26:55.510
In fact, they can be the competitive advantage. And Amazon has built the best
00:26:55.510 --> 00:26:57.170
supply chain company ever.
00:26:57.818 --> 00:27:02.318
It's just, we don't see it that way because we're all consumers of the platform.
00:27:02.558 --> 00:27:07.618
But in essence, they've created this amazing supply and demand platform.
00:27:08.018 --> 00:27:13.338
And that's what's so powerful about it. And so the business is supply chain.
00:27:13.558 --> 00:27:20.798
And you now see the companies like FedEx and DHL, they want to be supply chain companies as well.
00:27:21.118 --> 00:27:26.458
And so I think my prediction, which was a long setup to get to the prediction,
00:27:26.638 --> 00:27:33.698
my prediction is we will see that take a big business like Ford or J&J or P&G,
00:27:33.818 --> 00:27:40.098
or it doesn't matter who, where the supply chain becomes not a back office afterthought,
00:27:40.338 --> 00:27:45.898
like improve the supply chain, but it becomes core to how the business is built.
00:27:46.218 --> 00:27:50.038
The business is not just selling the product or developing the product,
00:27:50.098 --> 00:27:54.578
but it's also delivering the product and sort of bringing that all All holistically,
00:27:54.698 --> 00:27:57.718
that's where I predict we're going. And we're well on our way.
00:27:57.978 --> 00:28:00.638
Another company that, Amazon's a really good example.
00:28:01.018 --> 00:28:05.418
You know, Walmart used to be the example. But I think now, and I hate to bring
00:28:05.418 --> 00:28:08.578
this up because the CEO is driving me crazy, but I have a Tesla.
00:28:08.718 --> 00:28:10.958
I love Teslas. Teslas are incredible cars.
00:28:11.198 --> 00:28:16.018
But one of the advantages they have versus Ford, you know, and everybody else
00:28:16.018 --> 00:28:19.718
is that they own, pretty much, they've gone backwards in the supply chain.
00:28:19.858 --> 00:28:21.038
They're creating the batteries.
00:28:21.218 --> 00:28:24.358
They're thinking about the motors themselves. They're doing all this stuff to
00:28:24.358 --> 00:28:27.778
ensure that every part of that car ends up in the car when they need it in the
00:28:27.778 --> 00:28:29.918
car, when they manufacture the car.
00:28:29.998 --> 00:28:32.478
And the quality is of high value.
00:28:32.578 --> 00:28:37.438
Whereas you look at a company like Boeing that stopped doing that.
00:28:37.558 --> 00:28:41.738
They stopped carrying up every part of the supply chain, and now they have all these issues.
00:28:41.938 --> 00:28:47.238
So it's evident in these large manufacturing companies where they're starting
00:28:47.238 --> 00:28:48.818
to kind of think about that.
00:28:48.918 --> 00:28:52.718
We have to worry about quality. We have to worry about when we're going to get the supply.
00:28:53.138 --> 00:28:57.998
And we also want to make sure it's going to be the best thing it can be in our product.
00:28:58.178 --> 00:29:00.878
And so you have to move backwards in the supply chain in order to do that.
00:29:01.038 --> 00:29:05.338
Yeah. And that's a great example. And there's a lot to unpack there because
00:29:05.338 --> 00:29:08.378
it is a very interesting sort of quote unquote procurement.
00:29:09.017 --> 00:29:12.177
Element there because first tesla the
00:29:12.177 --> 00:29:15.217
one thing that they did is they didn't try to take a regular
00:29:15.217 --> 00:29:17.977
gas engine car sort of
00:29:17.977 --> 00:29:22.777
adapt it to the software development something i forget there's a term for this
00:29:22.777 --> 00:29:27.777
where all the components of the car are managed by central software yeah and
00:29:27.777 --> 00:29:31.417
and they complete and credit to them and rivian's done this and i think the
00:29:31.417 --> 00:29:35.117
other electric car manufacturers done this too that that are sort of brand new
00:29:35.117 --> 00:29:37.957
where they just said okay everything's running
00:29:38.057 --> 00:29:41.157
from this core software, it's networked to everything.
00:29:41.477 --> 00:29:47.397
And when we're building new tires or braking systems or acceleration systems
00:29:47.397 --> 00:29:49.917
that are controlled by the software
00:29:49.917 --> 00:29:54.577
so that everything can be improved and managed with software updates.
00:29:55.037 --> 00:29:59.597
You're not, because in traditional cars, you have different computers in the
00:29:59.597 --> 00:30:04.137
seat recliner and different in the differential and like all that other components.
00:30:04.517 --> 00:30:07.957
So when you do that, it was a very clever move.
00:30:08.157 --> 00:30:12.817
Then you can start to control the supply chain. And I believe it was Tesla when
00:30:12.817 --> 00:30:17.517
we had the microchip shortage a couple of years ago, they detected that earlier
00:30:17.517 --> 00:30:22.797
and bought a whole bunch of them and they didn't have as much of a supply problem.
00:30:22.937 --> 00:30:26.117
Now, and this gets to back to the question of procurement, the other,
00:30:26.157 --> 00:30:30.937
you can flip this around and say, and Volkswagen just invested a lot of money
00:30:30.937 --> 00:30:33.077
in Rivian, the electric car maker,
00:30:33.317 --> 00:30:39.497
one of the benefits of that, if you're Rivian, is you can use the purchasing power of VW.
00:30:39.637 --> 00:30:44.857
Because if Rivian's only creating a couple thousand units or a couple hundred
00:30:44.857 --> 00:30:48.117
thousand units a year, they don't have purchase price leverage.
00:30:48.997 --> 00:30:51.657
But if you're going to a supplier with.
00:30:53.957 --> 00:30:59.737
10 million tires and Rivian just needs, I don't know, 50,000 or 100,000,
00:30:59.757 --> 00:31:05.497
you can now bundle that order and get a better price than Rivian going alone to the tire supplier.
00:31:06.097 --> 00:31:13.197
So this is a little bit of procurement making its way and back to the question
00:31:13.197 --> 00:31:14.677
of where we're going in the future.
00:31:14.937 --> 00:31:19.297
If you're designing this car, you have to look at the supply market,
00:31:19.377 --> 00:31:23.757
whether what Tesla did is owning more vertical, which is perfectly fine,
00:31:23.837 --> 00:31:29.237
or understanding how to get the leverage and engage the supply base.
00:31:30.317 --> 00:31:34.937
As you were talking about how important we're realizing supply chains are,
00:31:35.177 --> 00:31:38.457
the random thought just popped in my head and I have to share it.
00:31:38.517 --> 00:31:40.617
I wrote it down because I'm like, I don't want to forget this.
00:31:41.197 --> 00:31:45.377
Supply chain issues led to the discovery of America. That's how important supply chains are.
00:31:45.537 --> 00:31:49.457
Literally, they found new worlds. Right. Yeah. To plunder.
00:31:49.777 --> 00:31:53.617
But But actually, it goes back even further than that.
00:31:53.757 --> 00:31:57.897
Like, you can find supply chains being at the core of many of history's,
00:31:57.937 --> 00:32:00.117
I mean, look at imperialism.
00:32:00.377 --> 00:32:05.417
Imperialism is really just supply chain expansion and imperial possessions.
00:32:05.757 --> 00:32:11.197
And yeah, so, and I mean, if you look at it with a supply chain lens,
00:32:11.337 --> 00:32:12.277
I mean, it's right there.
00:32:12.437 --> 00:32:20.297
So yeah, no, I agree. So as someone who solves data issues for executives and
00:32:20.297 --> 00:32:25.577
leaders and teams, what should we be focusing on from a data perspective with procurement?
00:32:25.897 --> 00:32:30.017
Like what is the one thing that they're tackling today that they're challenged with?
00:32:30.077 --> 00:32:34.377
Is it really just realizing that transparency or is there something else now? Yeah.
00:32:35.052 --> 00:32:40.712
I like to joke that within 18 months, we'll have all the technology we can consume
00:32:40.712 --> 00:32:42.212
and enterprise can consume.
00:32:42.492 --> 00:32:48.292
I mean, if you look at the AI stuff that's coming out now, I mean, it's bonkers.
00:32:48.672 --> 00:32:55.392
Companies don't need more technology. They don't need more tools and even data.
00:32:56.072 --> 00:33:00.432
It's helpful, but we need to get a handle on what we have today.
00:33:00.732 --> 00:33:04.172
To me, it's all about upskilling. Because the reason I say that we have too
00:33:04.172 --> 00:33:07.732
much technology is we're not using the technology we have access to today.
00:33:07.832 --> 00:33:10.592
And forget the procure-to-pay and source-to-pay systems.
00:33:10.932 --> 00:33:15.652
Just write that stuff off. But everybody that has Azure or Google Cloud or Amazon
00:33:15.652 --> 00:33:23.712
has access to amazing libraries of machine learning and AI and everything else
00:33:23.712 --> 00:33:25.092
in there, and we don't use it.
00:33:25.092 --> 00:33:27.892
And we barely use Excel.
00:33:28.152 --> 00:33:34.632
So what I would like to see is just greater analytical competency and ideally
00:33:34.632 --> 00:33:39.952
greater algorithmic literacy because algorithms drive our lives.
00:33:40.252 --> 00:33:43.832
And in fact, your Tesla is driving you literally.
00:33:44.192 --> 00:33:49.252
And while you understand them, how many Tesla owners understand the algorithms
00:33:49.252 --> 00:33:51.332
that are literally driving them?
00:33:51.432 --> 00:33:54.272
And so that's what I want to see more of.
00:33:54.752 --> 00:34:00.812
So yes, we can get spend transparency and then we need to move to contract transparency
00:34:00.812 --> 00:34:03.492
and the ability to action those.
00:34:03.952 --> 00:34:10.552
We also have to pull in benchmarks and better sort of stitch our end-to-end data quality.
00:34:10.972 --> 00:34:14.472
But the other answer I would give you just in a more hopefully succinct way
00:34:14.472 --> 00:34:18.132
is if you have good spend transparency and contract transparency,
00:34:18.432 --> 00:34:22.372
the real work is to get better data connectivity with your suppliers.
00:34:22.552 --> 00:34:25.772
Because A, the supplier experience today is horrible.
00:34:25.912 --> 00:34:29.112
And B, we need more data than ever from the suppliers.
00:34:29.252 --> 00:34:34.192
So we need to start plumbing systems, at least to our top 100 suppliers in ways
00:34:34.192 --> 00:34:36.992
that we haven't thought about in years past. Why?
00:34:37.252 --> 00:34:42.372
Because the ERP was never designed for that. And so that's why we have to get rid of the ERP.
00:34:43.112 --> 00:34:46.732
There you go. Well, thank you, Eloise, for your time today. This has been a
00:34:46.732 --> 00:34:50.992
great conversation. We went from procurement to data, to supply chains, to history.
00:34:52.012 --> 00:34:56.252
Imperialism. Love it. I appreciate the time. It's always a pleasure chatting
00:34:56.252 --> 00:34:58.592
with you. I think we need to talk more.
00:34:59.112 --> 00:35:04.672
Indeed we do. No, it was my pleasure. And I was very happy to thank you for having me on.
00:00:00.017 --> 00:00:03.117
Welcome, welcome. Welcome back to How I Met Your Data.
00:00:03.257 --> 00:00:09.017
Sandy Estrada here, myself and my co-host Anjali Banzal. Could not be more excited to be back.
00:00:09.257 --> 00:00:13.477
I know we took a little bit of hiatus for the summer, but we're back and ready
00:00:13.477 --> 00:00:18.397
to go with two more episodes for you to wrap up our first season of How I Met Your Data.
00:00:18.397 --> 00:00:23.097
We are so proud of what we've created here, and we cannot wait to share the
00:00:23.097 --> 00:00:24.637
last two episodes with you.
00:00:24.777 --> 00:00:31.857
And for this episode, myself and Anjali have asked Dr. Eloise Epstein to join us. So Dr.
00:00:32.037 --> 00:00:37.457
Epstein is a Carney partner, a published author, a prolific keynote speaker
00:00:37.457 --> 00:00:42.777
at supply chain and procurement events, and a dear advisor to me.
00:00:42.777 --> 00:00:47.517
I have gotten to know her over the last four and a half years as Carney has acquired Cervelo.
00:00:47.897 --> 00:00:51.757
And I just love chatting with her. She's just so chock full of insights and
00:00:51.757 --> 00:00:55.277
has a lot of fun pet peeves, some of which we will touch upon today.
00:00:55.797 --> 00:00:59.157
She's also a digital futurist. So you're going to hear a little bit about what
00:00:59.157 --> 00:01:03.197
that means during this episode. We wanted to wrap up the season with Dr.
00:01:03.477 --> 00:01:09.177
Eloise Epstein primarily because our goal has always been for this podcast to
00:01:09.177 --> 00:01:15.417
showcase all the different aspects and the kaleidoscope view that is the data world.
00:01:15.757 --> 00:01:21.157
And regardless of where you're coming from, for example, we are data consultancies.
00:01:21.177 --> 00:01:25.457
We help data leaders and business executives get the most out of data.
00:01:25.637 --> 00:01:28.937
You have your data leaders. You have business executives perspectives.
00:01:29.237 --> 00:01:31.597
You have software vendor perspectives.
00:01:32.077 --> 00:01:37.297
You have the, you know, data consumer perspectives. You have others as well
00:01:37.297 --> 00:01:40.057
that are impacting what people need to do with data.
00:01:40.117 --> 00:01:42.357
One of those others is a management consultant.
00:01:42.537 --> 00:01:47.177
And Eloise gives you a really good insight into how they think and how they help their clients.
00:01:47.377 --> 00:01:50.657
I mean, it's just another aspect of that kaleidoscope. And we wanted to shine
00:01:50.657 --> 00:01:55.977
a light on that and ensure that we have the full breadth of voices that make
00:01:55.977 --> 00:02:01.877
data work so challenging and intriguing and interesting for us who are in it
00:02:01.877 --> 00:02:04.797
because it is a tapestry of personalities,
00:02:05.157 --> 00:02:10.377
a tapestry of point of views, a tapestry of knowledge that comes together to
00:02:10.377 --> 00:02:12.737
create insight for an individual.
00:02:12.877 --> 00:02:18.337
So with data. So with that said, here's our conversation with Dr. Eloise Epstein.
00:02:18.480 --> 00:02:37.680
Music.
00:02:37.524 --> 00:02:40.964
So thank you for spending some time with us to have this conversation, Eloise.
00:02:41.184 --> 00:02:44.844
I think when we started thinking about this podcast, Anjali and I made a whole
00:02:44.844 --> 00:02:47.984
list and your name was probably the first one I had put on the list,
00:02:48.044 --> 00:02:50.724
but wasn't the first person we reached out to. I don't know why.
00:02:51.064 --> 00:02:52.284
I'm honored to be on the list.
00:02:52.704 --> 00:02:57.164
So thanks for doing this with us. The first thought that comes to mind,
00:02:57.244 --> 00:02:59.704
for me, procurement is part of my world.
00:02:59.764 --> 00:03:04.884
I started my career in basically helping FP&A and all roads from a cost perspective
00:03:04.884 --> 00:03:05.724
start with procurement.
00:03:05.984 --> 00:03:10.544
I'm sure a lot of our listeners don't have a background focused on that topic.
00:03:10.744 --> 00:03:15.724
And I was showing Anjali a video that you had put together answering a video
00:03:15.724 --> 00:03:18.704
that John Oliver had, which was really comical.
00:03:18.824 --> 00:03:22.464
But I figured, could you explain to our listeners what procurement is?
00:03:22.704 --> 00:03:28.604
Yes. So absolutely everybody, or at least in the Western world,
00:03:28.684 --> 00:03:29.984
is a procurement person.
00:03:30.164 --> 00:03:34.964
We are procurement people in our personal lives. When we go to buy a car,
00:03:35.064 --> 00:03:37.924
we negotiate a price or we do various negotiations.
00:03:38.544 --> 00:03:43.984
We manage to some degree, some less or more than others.
00:03:44.144 --> 00:03:47.624
Our money, how it comes in, where we're spending it.
00:03:47.784 --> 00:03:51.864
We look for deals on whatever it is we need to buy.
00:03:52.004 --> 00:03:57.024
Or when we go to make a big purchase, we look at reviews, get recommendations.
00:03:58.164 --> 00:04:02.064
We buy products and look at the quality over time.
00:04:02.444 --> 00:04:08.424
And so all of those concepts, everything I just said, is us in our individual
00:04:08.424 --> 00:04:10.204
lives doing procurement.
00:04:10.384 --> 00:04:15.944
And it stands to reason, of course, that big companies as well do the same thing.
00:04:16.064 --> 00:04:18.424
They spend a lot of money and...
00:04:19.187 --> 00:04:24.167
Other than salaries, money that goes out the building goes to suppliers.
00:04:24.387 --> 00:04:28.747
And so looking for deals, looking for quality, looking for availability.
00:04:29.347 --> 00:04:31.947
Et cetera, et cetera, managing to budgets.
00:04:32.267 --> 00:04:36.527
That's pretty much what procurement does in the corporate environment.
00:04:36.807 --> 00:04:42.647
And you would be surprised or maybe not shocked, but surprised at how the bigger
00:04:42.647 --> 00:04:46.507
the company, the more they struggle to just understand where they're spending
00:04:46.507 --> 00:04:49.847
their money, much less control it. What do you think is driving that?
00:04:50.007 --> 00:04:51.467
Well, it can be a lot of factors.
00:04:51.787 --> 00:04:57.067
One is oftentimes growth mindsets. When you grow at all costs,
00:04:57.247 --> 00:05:01.387
grow, innovate, disrupt, that's not always cost saving.
00:05:01.667 --> 00:05:06.507
So when you look at the growth drivers of the economy, certainly big tech is
00:05:06.507 --> 00:05:11.607
there, even big oil, all of them are high growth.
00:05:11.987 --> 00:05:16.947
And so when you're in high growth mode, you're not really managing to the bottom line.
00:05:16.947 --> 00:05:22.027
And especially where you have industries with lots of mergers and acquisitions
00:05:22.027 --> 00:05:26.787
or the rise of private equity, all of those together, you are constantly adding
00:05:26.787 --> 00:05:29.947
and subtracting businesses. And this I'm sure you can appreciate.
00:05:30.247 --> 00:05:34.627
You have different accounting methods, different classifications,
00:05:34.907 --> 00:05:40.547
you're taking different ERP systems, and you're trying to bring all these companies
00:05:40.547 --> 00:05:44.767
together. These companies are not just single building entities.
00:05:45.127 --> 00:05:50.607
They are massive global conglomerates that have many, many, many subsidiaries
00:05:50.607 --> 00:05:53.667
in different operating companies.
00:05:54.007 --> 00:05:55.647
And so it can be hard.
00:05:56.564 --> 00:06:01.104
To bring all of that stuff together. Now, that's the positive side.
00:06:01.184 --> 00:06:07.724
The negative side is, in general, we have not had at least the resourcing or
00:06:07.724 --> 00:06:10.744
the capabilities to do that management.
00:06:11.104 --> 00:06:15.984
And procurement as a function is only like 25, 30 years old.
00:06:16.144 --> 00:06:22.424
So we're still in our infancy. So we haven't had generations of schools putting
00:06:22.424 --> 00:06:26.924
out homogenized skill sets that have come into the market.
00:06:27.204 --> 00:06:30.524
Yeah. It was definitely not a topic when I was in college.
00:06:31.424 --> 00:06:35.964
No, no, nor I. It wasn't. Yeah. Yeah. So Eloise, I'm curious, right?
00:06:36.064 --> 00:06:42.464
So if procurement is kind of in its infancy, where were those activities handled
00:06:42.464 --> 00:06:45.104
before or how are those activities handled before?
00:06:45.464 --> 00:06:51.284
Well, either they weren't or they were in finance. So oftentimes you'll see
00:06:51.284 --> 00:06:53.344
procurement still reporting to finance.
00:06:53.604 --> 00:06:57.424
At its most basic, procurement is cost control. To your question,
00:06:57.544 --> 00:07:02.884
historically, it has been this, okay, you've set your budget and now you're going to go buy.
00:07:03.144 --> 00:07:09.164
Well, you should probably buy with some strategic intention behind it or understanding
00:07:09.164 --> 00:07:14.224
so you're not overpaying for license or software licenses or buying duplicate
00:07:14.224 --> 00:07:17.884
items or introducing reducing needless complexity.
00:07:18.104 --> 00:07:21.764
So if you think about a warehouse, supplies that go into that warehouse,
00:07:21.864 --> 00:07:27.844
not the goods that come in, but the gloves and the safety glasses and Gatorade and whatever else,
00:07:28.024 --> 00:07:32.804
you might have six different suppliers coming and going into that warehouse
00:07:32.804 --> 00:07:40.524
on a daily basis when actually one supplier could service all of your needs to run that warehouse.
00:07:40.804 --> 00:07:45.284
And you would cut down on the number of traffic, the number of suppliers that you have to manage.
00:07:45.284 --> 00:07:48.944
So part of it's that or, and this is the one that just kills me,
00:07:48.964 --> 00:07:52.304
is you have a business unit in North America, one in the UK,
00:07:52.704 --> 00:07:57.964
buying the same software off two different contracts and paying two different prices.
00:07:58.584 --> 00:08:02.504
So a lot of procurement as we mature is looking at that and saying,
00:08:02.624 --> 00:08:08.124
you know, if we bundled off the same, bought off the same contract, then we can do more.
00:08:08.264 --> 00:08:11.844
Yeah, I mean, I think one of the things that we run into on the data side is
00:08:11.844 --> 00:08:14.684
multiple acquisitions of the same third party data sets.
00:08:15.289 --> 00:08:21.149
Yeah, yeah. Same thing. Same thing. So if you had a strong procurement function
00:08:21.149 --> 00:08:25.649
where you saw where you were spending your money, you would catch that right away.
00:08:25.809 --> 00:08:30.169
Like that would be low hanging fruit to to because because that that's exactly
00:08:30.169 --> 00:08:33.689
then that happens, especially with third party data all the time. For sure.
00:08:33.829 --> 00:08:37.909
So now Eloise, you described yourself as the procurement futurist.
00:08:38.009 --> 00:08:43.809
So can you help us understand what that means and what you focus on in your role?
00:08:44.009 --> 00:08:48.689
Yeah. So I actually have sort of rebranded to be more of a digital futurist.
00:08:48.729 --> 00:08:56.089
What I mean by that is I look at where we are today and where we could be in the future.
00:08:56.209 --> 00:09:01.109
So I look at it unconstrained and I work backwards to where we are today.
00:09:01.409 --> 00:09:06.649
Too often when we do roadmaps, too often when we do transformations.
00:09:07.589 --> 00:09:11.389
We look at where we are today and what we can do incrementally.
00:09:11.429 --> 00:09:16.689
And I try to pick a point, a North Star, whatever term you want to use and say,
00:09:16.909 --> 00:09:20.789
no, this is where we should be and how do we work backwards to get there?
00:09:20.869 --> 00:09:25.909
I don't do the whole, oh, we'll have electric city and autonomous cars and blah,
00:09:25.969 --> 00:09:31.009
blah, blah. I try to anchor very much into where we are today and where we could
00:09:31.009 --> 00:09:33.489
get to if we had a huge leap.
00:09:33.669 --> 00:09:39.169
Now, I know that we're never going to get there, but I feel like my job is to
00:09:39.169 --> 00:09:42.669
push us to think bigger and raise our trajectories higher.
00:09:42.909 --> 00:09:49.409
Yeah, I love that because the reality of most situations that you get into when
00:09:49.409 --> 00:09:52.909
an organization is trying to go through any kind of, even if it's a small transformation
00:09:52.909 --> 00:09:56.329
of a specific area or process or a technology,
00:09:56.509 --> 00:10:00.109
they work within the constraints or only think through within the constraints.
00:10:00.449 --> 00:10:05.089
And I often think about, you know, the whole, and everyone uses this metaphor
00:10:05.089 --> 00:10:10.289
to some extent even in marketing today, but the idea of going to the moon, right?
00:10:10.389 --> 00:10:15.389
And how wild that was at the time when that vision was put out there,
00:10:15.449 --> 00:10:17.629
but it required everybody to think outside the box.
00:10:18.098 --> 00:10:21.478
So when you think incrementally, you're always thinking inside the box in which
00:10:21.478 --> 00:10:24.738
you're living in and working in and with the people that you have to work with
00:10:24.738 --> 00:10:25.938
and the budgets that you have.
00:10:25.958 --> 00:10:31.798
But when you think unconstrained, sometimes solutions come out of nowhere that
00:10:31.798 --> 00:10:34.658
you couldn't think of before. Right. And I'll give you a perfect example.
00:10:34.938 --> 00:10:38.858
Look at everybody's quote unquote digital transformations these days.
00:10:39.098 --> 00:10:44.878
It's really just upgrading to the next version of the ERP system.
00:10:44.878 --> 00:10:48.518
But very commonly it's, hey, our digital transformation is going to be around
00:10:48.518 --> 00:10:53.858
consolidating our 20 or 50 or 100 ERP systems down to one S4 instance.
00:10:54.138 --> 00:10:56.198
And that's fine, but that's incremental.
00:10:56.518 --> 00:11:00.338
That's not transformational. And one, if you took a step back,
00:11:00.378 --> 00:11:08.598
one, me, might argue that the ERP is a deprecated technology. We are well beyond that.
00:11:08.638 --> 00:11:14.658
The way the modern enterprise works is not relevant to the way the world is today.
00:11:14.878 --> 00:11:18.598
So in my world, we don't start with the premise that you're going to build your
00:11:18.598 --> 00:11:20.158
transformation off the ERP.
00:11:20.198 --> 00:11:23.498
I question, do we even need the ERP anymore?
00:11:23.818 --> 00:11:27.198
And what would that post-ERP world look like?
00:11:27.338 --> 00:11:32.218
And then I draw it back to where we are today. day. So truly outside the box
00:11:32.218 --> 00:11:36.858
is challenging just the basic assumptions, because guess what?
00:11:36.978 --> 00:11:40.918
There's going to be billions, if not hundreds of billions spent on,
00:11:40.978 --> 00:11:47.458
oh, I want to pick on SAP today, but on SAP upgrades that are not going to transform anything.
00:11:47.698 --> 00:11:52.198
And that's okay. Like SAP will make money, systems integrators will make money,
00:11:52.358 --> 00:11:58.198
partners will get new Mercedes or Teslas, But don't confuse that with actually
00:11:58.198 --> 00:12:01.818
transforming the organization to become more digital.
00:12:01.958 --> 00:12:05.738
And even I will oftentimes just ask the more fundamental question.
00:12:06.638 --> 00:12:12.118
Are you sure you want to operate as a digital company? Because what you often get.
00:12:12.733 --> 00:12:17.593
Is these old companies that are, I don't know, 50, 100, 200 years old.
00:12:17.853 --> 00:12:21.833
And they look at Silicon Valley here and they're like, oh, I want to be like
00:12:21.833 --> 00:12:24.293
Google. So we're going to go be a data company.
00:12:24.573 --> 00:12:29.793
And all of a sudden you have, I don't know, 50,000 employees that are,
00:12:29.853 --> 00:12:35.593
and many of them probably mid-career or higher or older, and they're not going
00:12:35.593 --> 00:12:36.593
to make that transition.
00:12:36.593 --> 00:12:39.433
Position and and and i mean i'm sure you both
00:12:39.433 --> 00:12:42.513
see it your way oh we want to be data driven
00:12:42.513 --> 00:12:46.113
we want to be ai this we want to be whatever advanced
00:12:46.113 --> 00:12:51.753
analytics money ball blah blah blah but but the reality is there is you can't
00:12:51.753 --> 00:12:57.633
just wish that there that takes a long time to get people in that realm and
00:12:57.633 --> 00:13:02.113
so so i will encourage people to get there but i will also poke them with a
00:13:02.113 --> 00:13:04.973
stick yeah there's a realism to the situation, right?
00:13:05.153 --> 00:13:09.833
You can't get people to change overnight despite what their ambition may be.
00:13:10.213 --> 00:13:13.973
But there's tangible steps we can take along the way to at least get them a
00:13:13.973 --> 00:13:16.073
little bit closer to what you're hoping for.
00:13:16.373 --> 00:13:20.793
100%. So as you mentioned, procurement is 25, 30 years old.
00:13:21.073 --> 00:13:25.733
And I find, at least in the work that we've done for our clients,
00:13:25.973 --> 00:13:29.073
procurement and the problems procurement have and the challenges procurement
00:13:29.073 --> 00:13:34.413
have are often overlooked looked until there's actually a serious issue with cost management.
00:13:34.553 --> 00:13:39.693
I guess, what is the biggest myth or misconception you've come across regarding
00:13:39.693 --> 00:13:41.613
the importance of procurement?
00:13:42.053 --> 00:13:46.353
I don't know about misconception, but first I'll start with a story because
00:13:46.353 --> 00:13:49.073
the way you set that question up is perfect for the story.
00:13:49.173 --> 00:13:55.173
I live in the Bay Area, Silicon Valley, and every so often the big tech companies will.
00:13:56.124 --> 00:14:01.964
Ask us and other procurement folks to come pitch or to come give them a briefing or whatever.
00:14:02.324 --> 00:14:07.264
And you walk in and there's just this arrogance and there's like,
00:14:07.384 --> 00:14:09.644
yeah, well, we're just printing money.
00:14:09.744 --> 00:14:13.524
So it's cute what you're doing. That's really fun.
00:14:13.744 --> 00:14:18.044
I'm happy for you that you're doing that. And then something in the market changes, whatever.
00:14:18.284 --> 00:14:21.304
And then like all of that revenue doesn't like decline.
00:14:21.404 --> 00:14:25.704
It like goes off a cliff. And then all of a sudden they They become big believers
00:14:25.704 --> 00:14:29.844
in procurement because they have to cut costs fast.
00:14:30.224 --> 00:14:35.444
And you've seen that over the last few years up and down the West Coast.
00:14:35.804 --> 00:14:40.904
And so for a company to be profitable, you can either cut costs one of two ways.
00:14:41.004 --> 00:14:46.764
You can cut people or you can manage your external spend with suppliers and
00:14:46.764 --> 00:14:48.404
your contracts and so forth.
00:14:48.404 --> 00:14:53.904
And I like to do the working with suppliers to renegotiate or to negotiate better
00:14:53.904 --> 00:14:57.864
terms and manage payments versus firing people because firing people doesn't
00:14:57.864 --> 00:15:01.744
necessarily, well, first of all, it's not sustainable and it's not helpful.
00:15:01.824 --> 00:15:06.344
And it's a huge black eye in the public from a public relations point of view.
00:15:06.404 --> 00:15:10.904
Oh, is earlier this year, I'd worked with a client that was really trying to
00:15:10.904 --> 00:15:15.844
get their arms around understanding the spend of their sites around the globe.
00:15:15.844 --> 00:15:20.804
Like we're really looking into spend transparency for several hundred sites.
00:15:21.124 --> 00:15:25.764
And one of the things that was really clear as we're going through that process
00:15:25.764 --> 00:15:32.164
was the team that was looking for that transparency simply didn't have the data
00:15:32.164 --> 00:15:36.364
that they were looking for or were unaware of the data that was available to
00:15:36.364 --> 00:15:38.884
help them get that level of transparency. heresy.
00:15:39.124 --> 00:15:45.504
So as data leaders, whoever really worked closely with these types of teams,
00:15:45.604 --> 00:15:46.644
with these procurement teams,
00:15:46.904 --> 00:15:51.764
are there any sort of strategies or things that they should be thinking about
00:15:51.764 --> 00:15:56.784
in order to build better collaboration so there is that visibility and ability
00:15:56.784 --> 00:15:59.564
to use the data that's available to them?
00:15:59.744 --> 00:16:04.624
Okay. So this is my, I'll say fundamental mental pet peeve, but I probably have a thousand of them.
00:16:04.824 --> 00:16:11.244
In procurement, job one or job zero is understanding where you're spending your money.
00:16:11.404 --> 00:16:16.604
So any procurement organization that doesn't have good spend transparency is
00:16:16.604 --> 00:16:18.984
not doing their job and they should be fired.
00:16:19.164 --> 00:16:21.224
We can't talk about negotiating.
00:16:21.544 --> 00:16:26.104
We can't talk about contract management, relationship management until we actually
00:16:26.104 --> 00:16:27.584
know what we're spending where.
00:16:28.343 --> 00:16:34.463
And there is no excuse for not knowing where you're spending your money.
00:16:34.623 --> 00:16:40.543
Not only that, but if you have dirty spend data and supplier data,
00:16:40.903 --> 00:16:43.083
that's a procurement leadership failure.
00:16:43.223 --> 00:16:48.883
And I will call anybody out and I will go right after procurement executives
00:16:48.883 --> 00:16:51.683
for not having that data readily available.
00:16:52.063 --> 00:16:57.583
And I've heard every excuse in the book for the last 20, almost 25 years.
00:16:57.583 --> 00:16:59.563
But I'm not having it anymore.
00:16:59.883 --> 00:17:04.903
There are plenty of solutions, both you can buy, you can build.
00:17:05.143 --> 00:17:09.803
So there's no excuse for not having good spend transparency.
00:17:10.183 --> 00:17:15.043
What you have in the situation you described is intransigence,
00:17:15.323 --> 00:17:18.443
maybe incompetence. I don't want to be pejorative.
00:17:18.623 --> 00:17:24.003
But you certainly have people that are not taking the job seriously because
00:17:24.003 --> 00:17:30.383
it's not acceptable. And getting data out of those places, that's not hard.
00:17:30.563 --> 00:17:35.303
To me, you go all the way up to the CEO if you need that, if you're the procurement
00:17:35.303 --> 00:17:37.263
leader, because that's your job.
00:17:37.363 --> 00:17:42.183
If you don't have that, then we're not having a realistic conversation.
00:17:42.423 --> 00:17:44.083
We are just playing pretend.
00:17:44.423 --> 00:17:50.343
And well, that's not for me. Interesting, though, because I've met CPOs who,
00:17:50.443 --> 00:17:55.263
when asked directly, do you have category management spend figured out?
00:17:55.263 --> 00:17:57.223
Like, do you have it readily accessible?
00:17:57.643 --> 00:17:59.683
The answer is often no. Right.
00:18:00.263 --> 00:18:04.703
So I asked that same question and then, then my followup and I don't even give
00:18:04.703 --> 00:18:09.283
them a chance is like, so why, why not? That's your job.
00:18:09.963 --> 00:18:15.463
Like, like, what are you doing? Like, like, like, I mean, I say it more diplomatically,
00:18:15.503 --> 00:18:20.023
but, but there are no, like literally there is no excuse for not having that.
00:18:20.063 --> 00:18:22.783
I mean, even if you've only been in the job 60 days, Jesus.
00:18:23.167 --> 00:18:26.407
There's no reason you can't. And you have nothing. Like you walk in the door,
00:18:26.447 --> 00:18:30.307
there's nothing. In 60 days, you can have good spend data.
00:18:30.487 --> 00:18:34.487
There's spend transparency, I should say. I'm not buying that excuse.
00:18:34.747 --> 00:18:43.067
That to me, when they say that, like alarm bells go off because they are either scared,
00:18:43.367 --> 00:18:49.807
incompetent, and I don't mean that as pejoratively as that comes out, Or they're just lazy.
00:18:50.007 --> 00:18:55.127
You can't do procurement effectively if you don't even know where you're spending your money.
00:18:55.367 --> 00:18:57.727
Yeah. Is there a conundrum there, though?
00:18:59.087 --> 00:19:02.687
So as a procurement leader, their job is to lower costs, right?
00:19:02.787 --> 00:19:06.007
In order to solve this problem, there's a cost associated to it.
00:19:06.087 --> 00:19:07.567
Either you're buying or building something.
00:19:07.807 --> 00:19:10.347
Is that it? No, that's bullshit.
00:19:11.467 --> 00:19:16.627
No, that's just like, come on. Don't give me an excuse that it costs too much
00:19:16.627 --> 00:19:17.907
money. it takes too much time.
00:19:18.407 --> 00:19:22.827
Well, I have companies that have gone from zero to full spend transparency in
00:19:22.827 --> 00:19:26.547
three weeks, and that's nine ERP systems, eight GL codes.
00:19:27.007 --> 00:19:32.287
Don't give me excuses. This is a will, like you have to have the will to do it.
00:19:32.627 --> 00:19:37.347
So Eloise, I don't think we can let you go or let this conversation go without
00:19:37.347 --> 00:19:42.747
asking, are there use case for procurement teams to be leveraging Gen AI capabilities.
00:19:43.667 --> 00:19:47.567
Okay. So I'm going to answer this in a different way.
00:19:47.747 --> 00:19:51.847
So the question we always have in procurement was context.
00:19:52.927 --> 00:19:59.487
Procurement kind of came about 25, 30 years ago, and there were some various
00:19:59.487 --> 00:20:01.767
point solution tools that came about.
00:20:02.007 --> 00:20:06.507
And then we started to get consolidation and development of procure to pay,
00:20:06.847 --> 00:20:13.347
which is your raising of of requisitions, fulfilling the requisitions,
00:20:13.347 --> 00:20:15.047
and then paying the suppliers.
00:20:15.367 --> 00:20:18.207
And then we also have what's also known as source to contract,
00:20:18.467 --> 00:20:23.387
which is running sourcing events, running RFPs, awarding business,
00:20:23.967 --> 00:20:27.287
contracting, and managing all the contracts.
00:20:27.507 --> 00:20:31.307
And then taken together, we call it source to pay, which is all of that stuff together.
00:20:31.927 --> 00:20:39.187
So we have a couple decades of source-to-pay providers that built tools that
00:20:39.187 --> 00:20:44.747
are massive and expensive and have failed, absolutely failed to deliver on the promise.
00:20:44.967 --> 00:20:50.947
So we have all this tech debt that is just sitting around that nobody's using, everybody hates.
00:20:51.187 --> 00:20:56.447
And so, of course, what happens when you have a technology that is ineffective?
00:20:57.646 --> 00:21:02.866
We take the data that we can get out, we put it into Excel, and we run our operations.
00:21:03.266 --> 00:21:08.386
I still see RFPs coming in my email with an Excel file attached.
00:21:09.186 --> 00:21:16.426
Or worse, a particular sourcing tool, an RFP tool, which is just simply being
00:21:16.426 --> 00:21:21.866
used to distribute said Excel file, which to me is a double failure, but whatever.
00:21:22.206 --> 00:21:26.606
So the question, so if you take a step back, the question, the provocative question
00:21:26.606 --> 00:21:32.146
there is, is, well, if we have all this tech debt, why don't we just run the whole thing in Excel?
00:21:32.426 --> 00:21:37.566
So that's the equation when we talk about digital roadmaps for procurement.
00:21:37.786 --> 00:21:41.286
Now, of course, nobody's going to admit to doing that.
00:21:42.446 --> 00:21:47.886
You think it's because the process is built incorrectly in these tools because
00:21:47.886 --> 00:21:50.886
the tools have been around for so long and they're monolithic and they're hard
00:21:50.886 --> 00:21:55.926
to... I mean, because I've seen your map of all these applications that have come out.
00:21:56.006 --> 00:21:59.566
And I think that happens in any, I mean, it's happening to ERP systems,
00:21:59.806 --> 00:22:03.086
happening to planning systems, it's happening to every freaking business process
00:22:03.086 --> 00:22:08.346
out there, where it's becoming more purpose built, right?
00:22:08.466 --> 00:22:11.926
Where you can plug and play all these different tools to make an ecosystem of
00:22:11.926 --> 00:22:17.046
products that you're composing a process based on best of breed technologies.
00:22:17.326 --> 00:22:21.106
Is that kind of where it's headed? Plus Gen AI kind of trickled in the gaps?
00:22:21.106 --> 00:22:23.586
Yeah. Let's put it into real terms.
00:22:23.766 --> 00:22:28.626
So my spider map's full of all these logos, but the end user doesn't care.
00:22:28.946 --> 00:22:35.746
They're going to say, I need a plane ticket from San Francisco to Newark, book it for me.
00:22:35.906 --> 00:22:39.146
And it's going to then go figure out what the best price is.
00:22:39.246 --> 00:22:44.026
We have a preferred agreement with United and Hertz and whomever else.
00:22:44.366 --> 00:22:47.786
So it's going to manage all that in the background because I don't care.
00:22:47.786 --> 00:22:53.966
But right now, to do a codebook that, it puts way too much burden on me as the end user.
00:22:54.206 --> 00:23:00.966
And so the reason I set that up is I think Gen AI will change how I interact
00:23:00.966 --> 00:23:06.266
with the system because it will do a good job of interpreting to understand that getting from,
00:23:06.366 --> 00:23:11.686
if I say I need to go from San Francisco to New York, it's going to know that
00:23:11.686 --> 00:23:13.266
I'm probably going to fly United.
00:23:13.566 --> 00:23:19.466
I'm going to want to go nonstop. It might ask me to what time I want to leave
00:23:19.466 --> 00:23:22.226
because it understands the context of my query.
00:23:22.526 --> 00:23:25.786
That's where I think we'll see it. And to your point, which I liked a lot,
00:23:25.926 --> 00:23:27.626
that business process change.
00:23:27.886 --> 00:23:35.166
In fact, there is no process because it's just me and the AI talking and interpreting.
00:23:35.346 --> 00:23:41.866
Whereas the problem with all procurement systems today is you have to pre-define the process.
00:23:42.206 --> 00:23:48.446
Well, humans don't fit well into predefined processes because I might be ordering
00:23:48.446 --> 00:23:52.846
a plane ticket and then in an hour I might need beakers or test tubes.
00:23:53.026 --> 00:23:55.786
And an hour after that, I might need a Salesforce license.
00:23:56.647 --> 00:24:00.927
To predefine and then hard code these processes, this is where it all goes wrong.
00:24:01.107 --> 00:24:03.167
And this is where I'm most excited about Gen AI.
00:24:03.487 --> 00:24:07.327
Yeah. I think everything's heading in that direction, which is exciting and
00:24:07.327 --> 00:24:10.707
terrifying at the same time. And it should be. Yeah. Yeah.
00:24:11.267 --> 00:24:14.567
But we're not doing a great job managing it now.
00:24:14.787 --> 00:24:20.027
And that's the best case. And the worst case is people are just bypassing the systems.
00:24:20.467 --> 00:24:24.467
So we've actually created multi-layered problems.
00:24:24.747 --> 00:24:30.587
I would take the chaos of the AI system where we put in various constraints
00:24:30.587 --> 00:24:33.647
than what we have today, because what we have today is unworkable.
00:24:33.807 --> 00:24:38.267
So if you could predict like one major shift in the procurement industry over
00:24:38.267 --> 00:24:42.467
the next, say, five years, what do you think that would be?
00:24:42.667 --> 00:24:46.107
Well, to answer that question, I have to give you another one of my pet peeves.
00:24:46.927 --> 00:24:48.667
I'm poking all your pet peeves today.
00:24:50.607 --> 00:24:54.067
Yeah, it's not hard. I have a lot of them. So what's a supply chain?
00:24:54.167 --> 00:24:57.367
We've all learned what what supply chains are over the last four years.
00:24:57.890 --> 00:25:04.910
Which is great. To me, supply chains are a national priority for any country
00:25:04.910 --> 00:25:11.010
and they're a strategic, something that we need to really have a better understanding.
00:25:11.350 --> 00:25:15.470
However, we don't have really good definitions as practitioners.
00:25:16.010 --> 00:25:19.810
You can ask a hundred practitioners and you're going to get a hundred different answers.
00:25:20.070 --> 00:25:26.810
And that's the immaturity of our our broader operations function.
00:25:27.210 --> 00:25:31.550
Set that aside for a second. So just to sort of give you my definition,
00:25:31.850 --> 00:25:34.290
because it would be irresponsible if I didn't give you mine.
00:25:34.410 --> 00:25:38.670
So to me, within a supply chain, you have planning,
00:25:39.010 --> 00:25:46.070
demand management, and intake of, whether it's the consumer or the internal
00:25:46.070 --> 00:25:51.650
users, you have some sort of intake mechanism that then needs to be fulfilled.
00:25:51.650 --> 00:25:57.910
Then you have sourcing, which is procurement, essentially, which is where you
00:25:57.910 --> 00:26:01.450
procure all the raw materials you need to produce a product.
00:26:01.710 --> 00:26:05.270
Then you manufacture it and then you deliver it.
00:26:06.150 --> 00:26:11.150
Now, of course, that all is great if you're building a car or a consumer packaged good.
00:26:11.250 --> 00:26:17.630
But if you are a tech company or a bank, you don't have you're not manufacturing anything. thing.
00:26:17.790 --> 00:26:24.470
And so that's where the sort of supply chain falls apart and we kind of get into different worlds.
00:26:24.890 --> 00:26:29.350
But you still have planning and intake and you still have procurement because
00:26:29.350 --> 00:26:34.910
there's things you procure and you still to some degree have distribution and sort of operations.
00:26:35.210 --> 00:26:38.570
So all of that to me is the supply chain.
00:26:38.630 --> 00:26:45.850
I have a whole longer definition in my book, but that's a short So as we evolve.
00:26:46.530 --> 00:26:50.470
Supply chains can be a competitive advantage.
00:26:50.830 --> 00:26:55.510
In fact, they can be the competitive advantage. And Amazon has built the best
00:26:55.510 --> 00:26:57.170
supply chain company ever.
00:26:57.818 --> 00:27:02.318
It's just, we don't see it that way because we're all consumers of the platform.
00:27:02.558 --> 00:27:07.618
But in essence, they've created this amazing supply and demand platform.
00:27:08.018 --> 00:27:13.338
And that's what's so powerful about it. And so the business is supply chain.
00:27:13.558 --> 00:27:20.798
And you now see the companies like FedEx and DHL, they want to be supply chain companies as well.
00:27:21.118 --> 00:27:26.458
And so I think my prediction, which was a long setup to get to the prediction,
00:27:26.638 --> 00:27:33.698
my prediction is we will see that take a big business like Ford or J&J or P&G,
00:27:33.818 --> 00:27:40.098
or it doesn't matter who, where the supply chain becomes not a back office afterthought,
00:27:40.338 --> 00:27:45.898
like improve the supply chain, but it becomes core to how the business is built.
00:27:46.218 --> 00:27:50.038
The business is not just selling the product or developing the product,
00:27:50.098 --> 00:27:54.578
but it's also delivering the product and sort of bringing that all All holistically,
00:27:54.698 --> 00:27:57.718
that's where I predict we're going. And we're well on our way.
00:27:57.978 --> 00:28:00.638
Another company that, Amazon's a really good example.
00:28:01.018 --> 00:28:05.418
You know, Walmart used to be the example. But I think now, and I hate to bring
00:28:05.418 --> 00:28:08.578
this up because the CEO is driving me crazy, but I have a Tesla.
00:28:08.718 --> 00:28:10.958
I love Teslas. Teslas are incredible cars.
00:28:11.198 --> 00:28:16.018
But one of the advantages they have versus Ford, you know, and everybody else
00:28:16.018 --> 00:28:19.718
is that they own, pretty much, they've gone backwards in the supply chain.
00:28:19.858 --> 00:28:21.038
They're creating the batteries.
00:28:21.218 --> 00:28:24.358
They're thinking about the motors themselves. They're doing all this stuff to
00:28:24.358 --> 00:28:27.778
ensure that every part of that car ends up in the car when they need it in the
00:28:27.778 --> 00:28:29.918
car, when they manufacture the car.
00:28:29.998 --> 00:28:32.478
And the quality is of high value.
00:28:32.578 --> 00:28:37.438
Whereas you look at a company like Boeing that stopped doing that.
00:28:37.558 --> 00:28:41.738
They stopped carrying up every part of the supply chain, and now they have all these issues.
00:28:41.938 --> 00:28:47.238
So it's evident in these large manufacturing companies where they're starting
00:28:47.238 --> 00:28:48.818
to kind of think about that.
00:28:48.918 --> 00:28:52.718
We have to worry about quality. We have to worry about when we're going to get the supply.
00:28:53.138 --> 00:28:57.998
And we also want to make sure it's going to be the best thing it can be in our product.
00:28:58.178 --> 00:29:00.878
And so you have to move backwards in the supply chain in order to do that.
00:29:01.038 --> 00:29:05.338
Yeah. And that's a great example. And there's a lot to unpack there because
00:29:05.338 --> 00:29:08.378
it is a very interesting sort of quote unquote procurement.
00:29:09.017 --> 00:29:12.177
Element there because first tesla the
00:29:12.177 --> 00:29:15.217
one thing that they did is they didn't try to take a regular
00:29:15.217 --> 00:29:17.977
gas engine car sort of
00:29:17.977 --> 00:29:22.777
adapt it to the software development something i forget there's a term for this
00:29:22.777 --> 00:29:27.777
where all the components of the car are managed by central software yeah and
00:29:27.777 --> 00:29:31.417
and they complete and credit to them and rivian's done this and i think the
00:29:31.417 --> 00:29:35.117
other electric car manufacturers done this too that that are sort of brand new
00:29:35.117 --> 00:29:37.957
where they just said okay everything's running
00:29:38.057 --> 00:29:41.157
from this core software, it's networked to everything.
00:29:41.477 --> 00:29:47.397
And when we're building new tires or braking systems or acceleration systems
00:29:47.397 --> 00:29:49.917
that are controlled by the software
00:29:49.917 --> 00:29:54.577
so that everything can be improved and managed with software updates.
00:29:55.037 --> 00:29:59.597
You're not, because in traditional cars, you have different computers in the
00:29:59.597 --> 00:30:04.137
seat recliner and different in the differential and like all that other components.
00:30:04.517 --> 00:30:07.957
So when you do that, it was a very clever move.
00:30:08.157 --> 00:30:12.817
Then you can start to control the supply chain. And I believe it was Tesla when
00:30:12.817 --> 00:30:17.517
we had the microchip shortage a couple of years ago, they detected that earlier
00:30:17.517 --> 00:30:22.797
and bought a whole bunch of them and they didn't have as much of a supply problem.
00:30:22.937 --> 00:30:26.117
Now, and this gets to back to the question of procurement, the other,
00:30:26.157 --> 00:30:30.937
you can flip this around and say, and Volkswagen just invested a lot of money
00:30:30.937 --> 00:30:33.077
in Rivian, the electric car maker,
00:30:33.317 --> 00:30:39.497
one of the benefits of that, if you're Rivian, is you can use the purchasing power of VW.
00:30:39.637 --> 00:30:44.857
Because if Rivian's only creating a couple thousand units or a couple hundred
00:30:44.857 --> 00:30:48.117
thousand units a year, they don't have purchase price leverage.
00:30:48.997 --> 00:30:51.657
But if you're going to a supplier with.
00:30:53.957 --> 00:30:59.737
10 million tires and Rivian just needs, I don't know, 50,000 or 100,000,
00:30:59.757 --> 00:31:05.497
you can now bundle that order and get a better price than Rivian going alone to the tire supplier.
00:31:06.097 --> 00:31:13.197
So this is a little bit of procurement making its way and back to the question
00:31:13.197 --> 00:31:14.677
of where we're going in the future.
00:31:14.937 --> 00:31:19.297
If you're designing this car, you have to look at the supply market,
00:31:19.377 --> 00:31:23.757
whether what Tesla did is owning more vertical, which is perfectly fine,
00:31:23.837 --> 00:31:29.237
or understanding how to get the leverage and engage the supply base.
00:31:30.317 --> 00:31:34.937
As you were talking about how important we're realizing supply chains are,
00:31:35.177 --> 00:31:38.457
the random thought just popped in my head and I have to share it.
00:31:38.517 --> 00:31:40.617
I wrote it down because I'm like, I don't want to forget this.
00:31:41.197 --> 00:31:45.377
Supply chain issues led to the discovery of America. That's how important supply chains are.
00:31:45.537 --> 00:31:49.457
Literally, they found new worlds. Right. Yeah. To plunder.
00:31:49.777 --> 00:31:53.617
But But actually, it goes back even further than that.
00:31:53.757 --> 00:31:57.897
Like, you can find supply chains being at the core of many of history's,
00:31:57.937 --> 00:32:00.117
I mean, look at imperialism.
00:32:00.377 --> 00:32:05.417
Imperialism is really just supply chain expansion and imperial possessions.
00:32:05.757 --> 00:32:11.197
And yeah, so, and I mean, if you look at it with a supply chain lens,
00:32:11.337 --> 00:32:12.277
I mean, it's right there.
00:32:12.437 --> 00:32:20.297
So yeah, no, I agree. So as someone who solves data issues for executives and
00:32:20.297 --> 00:32:25.577
leaders and teams, what should we be focusing on from a data perspective with procurement?
00:32:25.897 --> 00:32:30.017
Like what is the one thing that they're tackling today that they're challenged with?
00:32:30.077 --> 00:32:34.377
Is it really just realizing that transparency or is there something else now? Yeah.
00:32:35.052 --> 00:32:40.712
I like to joke that within 18 months, we'll have all the technology we can consume
00:32:40.712 --> 00:32:42.212
and enterprise can consume.
00:32:42.492 --> 00:32:48.292
I mean, if you look at the AI stuff that's coming out now, I mean, it's bonkers.
00:32:48.672 --> 00:32:55.392
Companies don't need more technology. They don't need more tools and even data.
00:32:56.072 --> 00:33:00.432
It's helpful, but we need to get a handle on what we have today.
00:33:00.732 --> 00:33:04.172
To me, it's all about upskilling. Because the reason I say that we have too
00:33:04.172 --> 00:33:07.732
much technology is we're not using the technology we have access to today.
00:33:07.832 --> 00:33:10.592
And forget the procure-to-pay and source-to-pay systems.
00:33:10.932 --> 00:33:15.652
Just write that stuff off. But everybody that has Azure or Google Cloud or Amazon
00:33:15.652 --> 00:33:23.712
has access to amazing libraries of machine learning and AI and everything else
00:33:23.712 --> 00:33:25.092
in there, and we don't use it.
00:33:25.092 --> 00:33:27.892
And we barely use Excel.
00:33:28.152 --> 00:33:34.632
So what I would like to see is just greater analytical competency and ideally
00:33:34.632 --> 00:33:39.952
greater algorithmic literacy because algorithms drive our lives.
00:33:40.252 --> 00:33:43.832
And in fact, your Tesla is driving you literally.
00:33:44.192 --> 00:33:49.252
And while you understand them, how many Tesla owners understand the algorithms
00:33:49.252 --> 00:33:51.332
that are literally driving them?
00:33:51.432 --> 00:33:54.272
And so that's what I want to see more of.
00:33:54.752 --> 00:34:00.812
So yes, we can get spend transparency and then we need to move to contract transparency
00:34:00.812 --> 00:34:03.492
and the ability to action those.
00:34:03.952 --> 00:34:10.552
We also have to pull in benchmarks and better sort of stitch our end-to-end data quality.
00:34:10.972 --> 00:34:14.472
But the other answer I would give you just in a more hopefully succinct way
00:34:14.472 --> 00:34:18.132
is if you have good spend transparency and contract transparency,
00:34:18.432 --> 00:34:22.372
the real work is to get better data connectivity with your suppliers.
00:34:22.552 --> 00:34:25.772
Because A, the supplier experience today is horrible.
00:34:25.912 --> 00:34:29.112
And B, we need more data than ever from the suppliers.
00:34:29.252 --> 00:34:34.192
So we need to start plumbing systems, at least to our top 100 suppliers in ways
00:34:34.192 --> 00:34:36.992
that we haven't thought about in years past. Why?
00:34:37.252 --> 00:34:42.372
Because the ERP was never designed for that. And so that's why we have to get rid of the ERP.
00:34:43.112 --> 00:34:46.732
There you go. Well, thank you, Eloise, for your time today. This has been a
00:34:46.732 --> 00:34:50.992
great conversation. We went from procurement to data, to supply chains, to history.
00:34:52.012 --> 00:34:56.252
Imperialism. Love it. I appreciate the time. It's always a pleasure chatting
00:34:56.252 --> 00:34:58.592
with you. I think we need to talk more.
00:34:59.112 --> 00:35:04.672
Indeed we do. No, it was my pleasure. And I was very happy to thank you for having me on.