ERP Modernization Without the Chaos with Alicia King [MVP]

1
00:00:00,000 --> 00:00:05,760
Welcome everybody to another edition of the M665FM podcast.

2
00:00:05,760 --> 00:00:09,440
Today we explore technologies, digital transformation AI,

3
00:00:09,440 --> 00:00:14,320
business application, and people driving innovation across the Microsoft ecosystem.

4
00:00:14,320 --> 00:00:19,440
Today's episode is going to be especially value for any involved in the ERP

5
00:00:19,440 --> 00:00:20,440
modernization.

6
00:00:20,440 --> 00:00:24,400
Finance transformation, Dynamics 365 for Enterprise Technology.

7
00:00:24,400 --> 00:00:26,640
I'm joined by Alicia King,

8
00:00:26,640 --> 00:00:33,600
pre-sales engineer director at RSM, US, LLP, Microsoft MVP, Speaker, and podcast host.

9
00:00:33,600 --> 00:00:39,840
Also, Alicia works closely with CFOs and CIOs, helping organizations reduce disruption,

10
00:00:39,840 --> 00:00:45,520
control cost, and successfully modernized and consolidated ERP systems using Microsoft Dynamics

11
00:00:45,520 --> 00:00:53,920
365 finance and supply chain. She has supported more than 100 Microsoft ERP transitions across

12
00:00:53,920 --> 00:00:59,040
more than 40 countries and bringing a unique perspective to the combination,

13
00:00:59,040 --> 00:01:03,440
finance, technology, executive strategy, and real-world implementation experience.

14
00:01:03,440 --> 00:01:05,360
Alicia, welcome to the podcast.

15
00:01:05,360 --> 00:01:08,480
It's a pleasure being here today. Thank you for having me.

16
00:01:08,480 --> 00:01:13,440
Yeah, thank you. Can you, can you, for the people who don't know,

17
00:01:13,440 --> 00:01:19,360
you can you a little bit tell us about your background and how you fit into the Microsoft ecosystem?

18
00:01:19,360 --> 00:01:23,840
Absolutely. So when he was Alicia King, I lived in Greenville, South Carolina,

19
00:01:23,840 --> 00:01:27,920
the United States. I've been in the Microsoft space since 2009,

20
00:01:27,920 --> 00:01:34,320
and my journey through the Microsoft channel has been an amazing journey.

21
00:01:34,320 --> 00:01:37,840
It's one of those things where you start out, you really don't know what you're getting into,

22
00:01:37,840 --> 00:01:43,120
right? When you first start out, and you start meeting people and having experiences,

23
00:01:43,120 --> 00:01:47,920
and I have to say that the Microsoft community is so welcoming,

24
00:01:47,920 --> 00:01:52,880
and friendly. You can go up to anybody and pretty much ask any question, and you're going to get

25
00:01:52,880 --> 00:02:00,000
some honest feedback. And so I started my journey in supply chain years ago,

26
00:02:00,000 --> 00:02:03,680
and then when I started doing Microsoft in 2009, I started doing finance.

27
00:02:03,680 --> 00:02:09,520
So being, I had that supply chain background and marrying it with finance has proved to be

28
00:02:09,520 --> 00:02:16,080
really, really powerful, and my implementations as well as in my sales demos that I'm currently doing.

29
00:02:16,080 --> 00:02:22,000
And then about three years ago, I became a Microsoft MVP, and that opened up a whole new

30
00:02:22,000 --> 00:02:29,120
world to me, a different circle, and put me in a level of influence. And so for that, I'm certainly

31
00:02:29,120 --> 00:02:36,240
grateful, and it's really opened up a lot of thought leadership and given me a platform to

32
00:02:36,240 --> 00:02:41,840
blog and podcast, and to go to speaking events. Awesome, that's really cool.

33
00:02:41,840 --> 00:02:50,240
What will you say when you look a little bit about your career, you have done 100 transitions?

34
00:02:50,240 --> 00:02:57,280
So what is this so much? So is that anything you have learned through these projects,

35
00:02:57,280 --> 00:03:02,960
where you say this was really amazing for me? One of the things that I've learned is that we're

36
00:03:02,960 --> 00:03:08,480
not in a technology business, we're in the people business. Whenever you go into a company,

37
00:03:08,480 --> 00:03:13,520
you start learning people and their culture, and it's so important to understand who they want

38
00:03:13,520 --> 00:03:20,000
to become as a company. So that way you as an implementer or as a thought leader inside of

39
00:03:20,000 --> 00:03:25,600
that company can start and help them get to where they're going to go. It's not about going in and

40
00:03:25,600 --> 00:03:29,920
showing them how smart you are. It's going in and showing them how you can help transform them

41
00:03:29,920 --> 00:03:34,400
and get them to where they want to go so they can serve their customers better. And I've had the

42
00:03:34,400 --> 00:03:40,160
privilege of working in about 14 different countries, so my platform and my experience is across

43
00:03:40,160 --> 00:03:47,200
this ecosystem of international type companies and industrial life sciences, service industries,

44
00:03:47,760 --> 00:03:54,160
and across those different platforms, you start to see a common thread. And it's really about how

45
00:03:54,160 --> 00:03:59,280
people want to view their business. So anytime you go into a project or you start talking to a

46
00:03:59,280 --> 00:04:03,680
potential client, you always want to say who is my audience and what's my business objective?

47
00:04:03,680 --> 00:04:09,520
And then when you get in alignment with that, you help create clarity. Once you have clarity about

48
00:04:09,520 --> 00:04:14,960
what you're going to do with a client and where they're going to go, that's where the magic happens,

49
00:04:14,960 --> 00:04:20,320
because now you're working in the state of flow. And there's a lot of trust between you and the client.

50
00:04:20,320 --> 00:04:25,280
And that's really where you start putting that momentum and you start seeing a huge value ad.

51
00:04:25,280 --> 00:04:36,320
Awesome. A little bit about Dynamics 365, Finishing Supply Chaites. Sorry. How have this over the years

52
00:04:36,320 --> 00:04:43,200
evolved from your perspective? And especially now we have co-pilot and AI. Is there

53
00:04:44,080 --> 00:04:45,760
a change? What did you see?

54
00:04:45,760 --> 00:04:54,880
D365 has always been a relational database, but it's not always been easy to get data out of D365.

55
00:04:54,880 --> 00:05:02,400
So back when I started, I was in a product called AX2009. And then 2009 became AX2012.

56
00:05:02,400 --> 00:05:09,520
And then AX2012 became D365, Finishing Supply Chain. So through the years, the systems

57
00:05:09,520 --> 00:05:18,080
you became easier to get the information out of, but not just that Microsoft's platform for

58
00:05:18,080 --> 00:05:24,800
meeting their customers needs is to go and buy ISVs or Integrated Software Winners applications

59
00:05:24,800 --> 00:05:31,440
and bring it into the core application of D365. So when I started out in 2009, people went out

60
00:05:31,440 --> 00:05:37,760
about best of breed software and then integrated them together. So for example, they may go out and get

61
00:05:37,760 --> 00:05:44,640
AX2009 for finance and maybe manufacturing, but they would go out to some other third party system

62
00:05:44,640 --> 00:05:50,160
for like AP automation. And then they would integrate that in our warehouse management back in the day

63
00:05:50,160 --> 00:05:55,360
and integrate that with Microsoft. And then Microsoft then in AX2012 without

64
00:05:55,360 --> 00:06:00,160
bottom warehouse management system and made that part of the core application. So then you no longer

65
00:06:00,160 --> 00:06:05,040
had to go out and buy a warehouse management system. It was part of the core application. Then in

66
00:06:05,040 --> 00:06:11,360
D365, Finishing Supply Chain, you've seen that with credit collections. And again, with warehouse

67
00:06:11,360 --> 00:06:16,000
management, some of the other features, they've gone out in asset management, for example.

68
00:06:16,000 --> 00:06:20,480
They went out and bought these different solutions and made it part of the core product.

69
00:06:20,480 --> 00:06:25,440
So now when people go buy the product, they're no longer looking to say, hey, what's the best of breed?

70
00:06:25,440 --> 00:06:33,040
They're looking to say, what holistic system best fits, fits, what holistic system best fits my

71
00:06:33,040 --> 00:06:41,040
business department. So now D365 is kind of that one stop shop where you can get really fantastic

72
00:06:41,040 --> 00:06:47,360
financials, manufacturing asset management, least management, project management, all of those

73
00:06:47,360 --> 00:06:52,480
different components inside of one ecosystem. There are still some times where you do need to go out

74
00:06:52,480 --> 00:06:59,840
and get a best of breed to integrate in. But largely D365 is really that holistic system. So everyone is

75
00:06:59,840 --> 00:07:05,360
working out the same database, working out the same system from business to business in processes.

76
00:07:05,360 --> 00:07:15,120
Interesting. That's really, really cool. You worked directly with a lot of CFO, CIOs.

77
00:07:15,120 --> 00:07:23,040
What are the biggest mistakes organizations make when they approach an ERP organization?

78
00:07:23,040 --> 00:07:28,960
Most companies, when they come to us, they've already done their homework. They're no longer trying

79
00:07:28,960 --> 00:07:35,440
to say, what is D365? Or who are you as an organization? They've already done their homework and

80
00:07:35,440 --> 00:07:41,760
found out who D365, the financial supply chain is, the functionality inside of it. They already

81
00:07:41,760 --> 00:07:46,240
knew who I am. Usually when I get to the door, they've already looked at my LinkedIn profile.

82
00:07:46,240 --> 00:07:52,240
They already know about company. We are. So I work for RSM. And they've done that homework. So when

83
00:07:52,240 --> 00:07:58,480
you walk in the door, you're no longer introducing yourself. You're really validating what they

84
00:07:58,480 --> 00:08:03,840
already know to be true. So when you walk in the door, it's no longer saying, "Microsoft's a great

85
00:08:03,840 --> 00:08:09,120
product. RSM is a great company. I have all this experience." They're really wanting you to make

86
00:08:09,120 --> 00:08:14,800
sure that you're in alignment with what they already believe to be true about you. And it's really

87
00:08:14,800 --> 00:08:21,760
about mitigating risk because used to it was a CIO and the CFO that were the decision makers, but now

88
00:08:21,760 --> 00:08:27,280
you have buying committees. So it's no longer resting on one person to make the decision.

89
00:08:27,280 --> 00:08:38,000
Yeah, I understand. I think a little bit, we have this, yeah, this executive alignment.

90
00:08:38,000 --> 00:08:42,240
How important is this before the project starts?

91
00:08:42,240 --> 00:08:51,120
Alignment is key because alignment shows clarity. Whenever you go into a company, they're not

92
00:08:51,120 --> 00:08:57,920
looking for guarantees. They're looking to make sure that there's clarity around what you're going

93
00:08:57,920 --> 00:09:03,440
to deliver. And when you run into difficulties, how are you going to manage those difficulties?

94
00:09:03,440 --> 00:09:09,280
Because everybody knows ERP implementations are hard and they're long because it's literally like

95
00:09:09,280 --> 00:09:15,600
heart surgery, right? You're going in and you're removing or replacing this core element of the

96
00:09:15,600 --> 00:09:22,240
business because ERP literally runs the business. So you have to go in very strategically to replace

97
00:09:22,240 --> 00:09:26,800
the ERP system with the currently on and putting in the new one to make sure that you can still

98
00:09:26,800 --> 00:09:31,840
deliver product to your customers on time. You don't have negative impact on cash flow,

99
00:09:31,840 --> 00:09:37,760
that your inventory levels stay where they're supposed to be. All those pieces are very, very important.

100
00:09:37,760 --> 00:09:42,800
And so going into this, they want to know like, hey, when we do run into a problem, how are you

101
00:09:42,800 --> 00:09:48,080
going to manage it? How are we going to share this risk together and communicate and mitigate risk?

102
00:09:48,080 --> 00:09:56,000
Yeah, that's I think the topic is here, organization should a little change. How,

103
00:09:56,000 --> 00:10:06,720
what impact have a modernized or modernizing ERP on the organization and how can they handle

104
00:10:07,440 --> 00:10:15,440
the change, yeah, especially in the company to the employees or to their processes?

105
00:10:15,440 --> 00:10:22,080
Change management is key. We can go in and do an amazing implementation, have error, all the bills

106
00:10:22,080 --> 00:10:30,320
and whistles working, everything tested. But if the users don't adopt the change, it will fail.

107
00:10:30,320 --> 00:10:36,560
So if you were to go out right now and do a search and say how many ERP implementations are deemed

108
00:10:36,560 --> 00:10:43,360
successful, you will see that only 50% of ERP implementations are deemed successful. And that's

109
00:10:43,360 --> 00:10:48,640
across all applications, it's not just Microsoft, it's all of them collectively. So you have to

110
00:10:48,640 --> 00:10:56,400
step back and ask yourself why. In the reason why most of the time that it's true is because there has

111
00:10:56,400 --> 00:11:02,240
not been good change management inside of the organization. And as a result, the users have not

112
00:11:02,240 --> 00:11:09,360
adopted the change. So one of the things that is key in doing that is one is leadership

113
00:11:09,360 --> 00:11:16,400
has to make sure that the users feel safe. And the reason that's so important is if I've been doing

114
00:11:16,400 --> 00:11:22,400
my job on a green screen, say an AS-400 type application for the past 30 years, and now let us say,

115
00:11:22,400 --> 00:11:28,800
near handing me this software is a solution, Windows based or internet based application.

116
00:11:30,240 --> 00:11:37,680
That's scary because I myself, one, can I do it? If I can do it, what how am I going to do my job?

117
00:11:37,680 --> 00:11:44,560
Someone has literally shifted my world. So in many cases, it's easier for people to get

118
00:11:44,560 --> 00:11:50,400
defensive and talk about how the system won't work for them instead of how the system will work for

119
00:11:50,400 --> 00:11:56,400
them. And until they actually start using the language of how the system will work for them,

120
00:11:56,400 --> 00:12:00,560
you're going to get that resistance. If you're getting resistance, it's not you're not going to get

121
00:12:00,560 --> 00:12:06,960
adoption. So I would say, for the folks listening to this podcast, if you're in a leadership position,

122
00:12:06,960 --> 00:12:15,040
make sure that your users feel valued and they feel safe and they have the confirmation that they

123
00:12:15,040 --> 00:12:21,760
can do it, that they can own the system and they can be successful. So there's one component of it.

124
00:12:21,760 --> 00:12:27,120
The other component of it is during the training and during the implementation process,

125
00:12:27,120 --> 00:12:32,400
one of the beautiful things about a D365, I don't know, supply chain, is the fact that you can

126
00:12:32,400 --> 00:12:38,000
personalize your screens. Whenever you go in and look at the core application, it can be so

127
00:12:38,000 --> 00:12:43,680
overwhelming because it is huge. It's a huge application. There's so many different modules and

128
00:12:43,680 --> 00:12:48,960
so many different workspaces and thousands of fields on the screen, right? So from an implementation

129
00:12:48,960 --> 00:12:55,040
perspective, go in and find out how that individual needs to use a system. Then hide everything they

130
00:12:55,040 --> 00:12:59,200
don't see, you need to see move things around so that their tabs are in a certain order,

131
00:12:59,200 --> 00:13:07,280
do the things to make their day-to-day life easy. Once you make something easy, people start to

132
00:13:07,280 --> 00:13:12,160
believe that they can do it and once they believe that they can do it, they will adopt. And then

133
00:13:12,160 --> 00:13:19,840
that's how you get success and adoption during an ERP implementation. I see often in my space,

134
00:13:19,840 --> 00:13:25,600
Microsoft Fabric, a lot of companies say, "Oh, we need this technology, IT, do does it for us,

135
00:13:25,600 --> 00:13:37,520
but for my feeling, it's they don't do business process redesign, how can look up this business,

136
00:13:38,240 --> 00:13:46,480
the process redesign and dynamics are in ERP systems." You always have to say, what is my business

137
00:13:46,480 --> 00:13:51,600
objective? So let's say for example, I was working with a company and we were looking at the chart

138
00:13:51,600 --> 00:13:57,840
of accounts, just as an example, in financial dimensions. The first thing I would start asking is,

139
00:13:57,840 --> 00:14:03,520
how do you want to see your reports? You always start with the end in mind and you say,

140
00:14:03,520 --> 00:14:08,640
how do you want to run your business? Do you want to be able to see region in your trial balance?

141
00:14:08,640 --> 00:14:14,560
So now let us say, if I can say for this particular region, this was my cost-lit-as-sold and this is

142
00:14:14,560 --> 00:14:20,880
my revenue. Now let us say, and I can measure profit margins by region. If I want to say, maybe it's

143
00:14:20,880 --> 00:14:26,720
by product group, that way you can figure out which product group is making you the most profit.

144
00:14:26,720 --> 00:14:31,840
Because in every business, you have money-makers and money-takers. So you have to figure out which

145
00:14:31,840 --> 00:14:36,960
products are going to give you the biggest profit margins, but you can't do that if you don't

146
00:14:36,960 --> 00:14:42,240
configure the system right. If you don't configure the system with certain financial dimensions or

147
00:14:42,240 --> 00:14:48,240
certain fields being populated. But if you set the system up in a certain way, now of a sudden

148
00:14:48,240 --> 00:14:54,080
everything is easy. So it's always starting with the end in mind and working backwards into the

149
00:14:54,080 --> 00:14:58,080
configuration of the system. That's how you're going to get the information that you're looking for.

150
00:14:59,520 --> 00:15:05,760
I think another topic with especially important is data quality and ERP success.

151
00:15:05,760 --> 00:15:13,680
What experience have you collected in the year? And the year you working with ERP and companies

152
00:15:13,680 --> 00:15:21,120
especially about data quality? You know, it's funny. I worked on so many different projects and

153
00:15:21,120 --> 00:15:25,520
most of them do costing because a lot of the projects I've worked on have been in manufacturing.

154
00:15:26,160 --> 00:15:31,600
And it's so interesting to me at how many times people put costing off to the end. They're like,

155
00:15:31,600 --> 00:15:36,800
oh, it's just costing. And I'm like, do you hear yourself? You're saying it's just costing. Do you

156
00:15:36,800 --> 00:15:41,520
realize if your cost is wrong? Your profit margins are wrong? If your profit margins are wrong,

157
00:15:41,520 --> 00:15:48,080
you don't know how much money you're making. It is so, so, so important. So it's one of those things that

158
00:15:48,080 --> 00:15:53,440
if your data is wrong, you're going to run your business wrong. If you go in and you're setting up

159
00:15:53,440 --> 00:15:58,240
your customers and you don't pay attention to the addresses that are being brought into the system,

160
00:15:58,240 --> 00:16:02,480
guess what? The wrong address is going to get put on the sales order or the person putting in

161
00:16:02,480 --> 00:16:08,880
the sales order isn't enough what address to pick. The customer has to own the data. That doesn't

162
00:16:08,880 --> 00:16:15,520
mean the partner can't help you transform the data into D365, but it is so, so critical that you go

163
00:16:15,520 --> 00:16:21,440
through different iterations of that data migration to make sure your data is clean because I can tell

164
00:16:21,440 --> 00:16:27,520
you from experience, if your data is dirty and you go live, it is so much harder to fix.

165
00:16:27,520 --> 00:16:33,440
It is well worth the time to go through that process during your user acceptance testing, during

166
00:16:33,440 --> 00:16:39,360
your mock go lives, make sure your data is clean, then you're going to have to set yourself up for a

167
00:16:39,360 --> 00:16:43,920
high level of success at go live. But again, if your data is dirty, you're going to suffer.

168
00:16:45,440 --> 00:16:54,320
Yeah, yeah, I think that's through a lot of company, yeah, a little bit wrong, but so when you see

169
00:16:54,320 --> 00:16:59,520
this, this projects, did you think companies become more realistic about timelines and

170
00:16:59,520 --> 00:17:06,480
express stations actually or? One of the things that I've seen is a lot of companies don't

171
00:17:06,480 --> 00:17:13,520
provide enough resources on their side. So they'll look at the finance team or the supply chain team

172
00:17:13,520 --> 00:17:18,960
and they'll be like, "Oh, well, you can do this on top of your existing job." Well, guess what?

173
00:17:18,960 --> 00:17:23,920
These people are already working 40, 50 hours a week, sometimes more, and now you're going to ask

174
00:17:23,920 --> 00:17:29,520
them to do this European implementation on top of it. It's just you're really setting people up for

175
00:17:29,520 --> 00:17:35,120
burnout and failure, and that's part of why you get the resistance as well because they're so burned

176
00:17:35,120 --> 00:17:41,040
out and so overworked that they don't have the capacity to get excited about the new processes and the

177
00:17:41,040 --> 00:17:47,360
new business opportunities for doing the European implementation. I would highly recommend to an

178
00:17:47,360 --> 00:17:54,400
organization to pick your key users, your smager, or subject matter experts, and they start off-loading

179
00:17:54,400 --> 00:17:58,640
some of their work before the project starts because they obviously have to keep doing part of their

180
00:17:58,640 --> 00:18:03,200
existing job. It's not like you're going to free up your whole team to do this, but it starts off-loading

181
00:18:03,200 --> 00:18:08,640
different pieces of their work. So they have some bandwidth and capacity to take on the work of the

182
00:18:08,640 --> 00:18:14,080
European project because if your people aren't involved, your implementation is going to struggle. It

183
00:18:14,080 --> 00:18:18,720
doesn't matter how good your implementation partner is because your implementation partner does

184
00:18:18,720 --> 00:18:25,440
not know your business the way you do period. We know the system, we know best practices, we know

185
00:18:25,440 --> 00:18:30,560
how things are, how folks should work, but you know your business and you're going to own it.

186
00:18:30,560 --> 00:18:36,000
So make sure you give your people some bandwidth to actually do the process with you and with the

187
00:18:36,000 --> 00:18:45,520
partner. What are typical, are seeing roles on company side you need to work with and how they

188
00:18:45,520 --> 00:18:52,240
have a different look on on the project? You need to make sure that both sides, your

189
00:18:52,240 --> 00:18:58,800
implementation partner and the customer has a strong PM project manager. The project managers have

190
00:18:58,800 --> 00:19:05,200
to really be in alignment and there cannot be any ego or any guarded, like I'm going to hide

191
00:19:05,200 --> 00:19:12,720
information, type mentality. It's okay to have risk on your raid log. It's okay, you should have

192
00:19:12,720 --> 00:19:18,080
risks. I worked on projects before and we want to start notitating potential risks and the client

193
00:19:18,080 --> 00:19:24,080
will tell us, no, no, no, we can't go to the board with any risks. And I'm like, do you realize what

194
00:19:24,080 --> 00:19:32,320
kind of exposure that is? By having a risk on your actual status sheet shows your leadership that

195
00:19:32,320 --> 00:19:37,280
you've identified potential risk and you thought through how to mitigate the risk in the event that

196
00:19:37,280 --> 00:19:43,360
it happens. If you go to your board and they're upset that you have risks on there, there's like a

197
00:19:43,360 --> 00:19:48,720
cultural problem inside the organization. It's actually a good thing to have risks on your status

198
00:19:48,720 --> 00:19:54,080
reports because again it's showing them that you're thinking ahead, you're mitigating risk by

199
00:19:54,080 --> 00:19:59,040
anticipating potential risks so that you can think through how to fix those. On the project

200
00:19:59,040 --> 00:20:03,920
management side, that's why it's so important to be fully transparent because we're humans and

201
00:20:03,920 --> 00:20:10,000
we make mistakes and that's okay but the finger pointing can't happen. You've got to go in and just

202
00:20:10,000 --> 00:20:15,280
be honest, say hey, this happened and now let's work together to fix it or to mitigate the risk.

203
00:20:15,280 --> 00:20:23,440
So the other thing too, on the D365 side as a project manager, we know what we're doing but we don't

204
00:20:23,440 --> 00:20:29,440
always know what's going on inside the organization so it's important for the clients project manager

205
00:20:29,440 --> 00:20:35,360
to share with the D365 project manager other things that are going on in the business. It doesn't

206
00:20:35,360 --> 00:20:41,600
mean you have the the D365 project manager has to know all the details but it's good for the D365

207
00:20:41,600 --> 00:20:46,880
project manager to know that these other projects are going on or maybe some of the resources that

208
00:20:46,880 --> 00:20:52,640
are working on ERP are also working on other projects which again is not highly desirable but that

209
00:20:52,640 --> 00:20:57,760
does happen sometimes but it's important that everyone's just very open and honest and there's a lot of

210
00:20:57,760 --> 00:21:08,560
trust. And other roles are I think sea level or IT, what's their role in this project? The sea

211
00:21:08,560 --> 00:21:16,240
level must, it's really really important that the sea level has is an alignment and excited about

212
00:21:16,240 --> 00:21:23,840
the project. Years ago I worked on a project at a large company and it didn't matter what was broken,

213
00:21:23,840 --> 00:21:28,000
it didn't matter if their printer didn't work or their email didn't work, oh the systems broken

214
00:21:28,000 --> 00:21:32,800
and then they would run into the to the boss's office and be like, oh the systems aren't working,

215
00:21:32,800 --> 00:21:38,240
the systems aren't working. And the reason they did that is because the manager didn't want the

216
00:21:38,240 --> 00:21:45,600
project and so he would sit there and listen to them and not tell them that they needed to get

217
00:21:45,600 --> 00:21:51,440
an alignment and help things work together. And then one day something shifted, somebody went and

218
00:21:51,440 --> 00:21:59,120
talked to that particular individual and said, hey the system is here to stay on it, let's make it

219
00:21:59,120 --> 00:22:03,920
work. The next time that someone went into the individual's office and started complaining they

220
00:22:03,920 --> 00:22:08,640
told them, no, no, okay, you know what, this is our system, let's own it, let's make it the best we

221
00:22:08,640 --> 00:22:16,640
can make it and immediately all the problems went away. Leadership sets the tone, so if you're in a

222
00:22:16,640 --> 00:22:22,400
C level, make sure that your the level below you is fully supported and make sure that your

223
00:22:22,400 --> 00:22:28,000
directors and your managers are fully supporting the team below them. Once people feel safe and they

224
00:22:28,000 --> 00:22:32,480
realize that they're doing all of this in the best entrance of their customers because again,

225
00:22:32,480 --> 00:22:36,960
people do ERP implementation so they can learn their business better so they can service their

226
00:22:36,960 --> 00:22:43,280
customers better. So I would say always keep the end customer in mind and make sure that everyone's

227
00:22:43,280 --> 00:22:49,440
in alignment and understanding why they're doing this project and understanding the impact is going

228
00:22:49,440 --> 00:22:53,760
to have on their end customers because now they're believing it's something bigger than themselves,

229
00:22:53,760 --> 00:22:59,120
they're seeing the big picture. And once that happens, which again is done by the leadership,

230
00:22:59,120 --> 00:23:03,280
once that happens, you're going to see an entirely different project and entirely different

231
00:23:03,280 --> 00:23:09,200
implementation. It'll actually be fun for the users.

232
00:23:09,200 --> 00:23:18,400
It's cool. I think a little bit about the thing, how we can call it, I've been a shared transformation

233
00:23:18,400 --> 00:23:28,160
vision, I call it so how important is to have a vision of the transformation and that it's also

234
00:23:28,160 --> 00:23:34,080
shared with the company or with the employees there are involved and how can it look?

235
00:23:34,080 --> 00:23:40,480
Sometimes people think if they do an ERP implementation is going to magically fix everything in

236
00:23:40,480 --> 00:23:46,560
their business and that's just not reality. As a leader, so if you're in that C-suite, you need to

237
00:23:46,560 --> 00:23:52,400
take a look at your business and say where do I want to go and once you understand where you want

238
00:23:52,400 --> 00:23:58,800
to go, then you start saying do I have all the elements to get there? Because it could be a cultural

239
00:23:58,800 --> 00:24:05,200
problem. Just like say, for example, if a particular company has a cultural issue around conflict

240
00:24:05,200 --> 00:24:09,200
and they're always having conflict, conflict, while hiring a conflict coach to come and

241
00:24:09,200 --> 00:24:15,600
do a two-day workshop is not going to fix it. Right, sometimes people think, oh, if I pay enough money

242
00:24:15,600 --> 00:24:19,840
and I get the right person here is going to magically fix it, you have to go to the root cause.

243
00:24:20,400 --> 00:24:25,280
You have to understand why you're having the issues you're having, then bring in the right people,

244
00:24:25,280 --> 00:24:30,720
bring in the right software, bring in the right tools to fix your business. ERP is a tool.

245
00:24:30,720 --> 00:24:39,280
It's not going to fix all your issues. So I would suggest if you are a leader in a company, figure out

246
00:24:39,280 --> 00:24:46,080
who you are as a company. Are there any internal issues that need to be resolved? Find out as a

247
00:24:46,080 --> 00:24:55,040
company who you want to become, then go find a partner to help you get there. I see often the people

248
00:24:55,040 --> 00:25:05,600
in the company, they're a communication gap. And the people, I get mental sick, they have to go to

249
00:25:05,600 --> 00:25:12,960
a mental asylum or so. What's your tip, how organizations better bridge the communication gap

250
00:25:12,960 --> 00:25:19,360
between business and technology teams? It's getting an a room together. Your CIO, your CFO,

251
00:25:19,360 --> 00:25:24,560
your CO, they need to get an a room together. They need to make sure that they are in alignment.

252
00:25:24,560 --> 00:25:30,560
Because as an organization, you may have a CIO that's like, how do we need to go this particular

253
00:25:30,560 --> 00:25:35,760
path, but then you may have a CFO that has an entirely different vision or a CO that has an

254
00:25:35,760 --> 00:25:41,360
entirely different vision. And a lot of times because everybody's so busy and there's just

255
00:25:41,360 --> 00:25:46,000
the kind of life gets in the way, these individuals don't necessarily get an a room and talk all the

256
00:25:46,000 --> 00:25:51,600
time. And so you'll see them kind of pushing and pulling against each other. And sometimes there's

257
00:25:51,600 --> 00:25:58,320
a lot of conflict amongst the circle. So it's important if they get in a room together and they

258
00:25:58,320 --> 00:26:04,320
have a conversation and they have a vision board saying who are we to become in and then talk

259
00:26:04,320 --> 00:26:09,200
about how you're going to get there, but they need to be in alignment first. If they're in alignment,

260
00:26:09,200 --> 00:26:16,240
we're going to see so much more progress in success. So just to give you a story, I worked on a

261
00:26:16,240 --> 00:26:22,880
project one time with a very large company and we were working with the IT team. Yeah, when we started

262
00:26:22,880 --> 00:26:27,040
working with them, we talked to the IT director and he said, this is an IT project and we're going to

263
00:26:27,040 --> 00:26:33,600
push it on to the business. I immediately rift flag started flying up all over my head. And

264
00:26:34,480 --> 00:26:40,560
their mentality was is that sales order processing, invoicing, all these different components,

265
00:26:40,560 --> 00:26:47,520
inventory management was going to be an IT function. So it was going to be, it was an IT solution

266
00:26:47,520 --> 00:26:53,280
to a business problem and they were going to tell the business how to do it. Well, needless to say,

267
00:26:53,280 --> 00:26:58,240
I went to my partner at the time and like this has got failure written all over it. And the other

268
00:26:58,240 --> 00:27:02,720
thing that they also did is they said, because this is an IT project, we're not going to do any kind

269
00:27:02,720 --> 00:27:07,280
of solution verification at the beginning. We're just going to start picking away at stuff and we'll

270
00:27:07,280 --> 00:27:12,560
eventually get it all done. Well, they worked on this project. We were probably the second or third

271
00:27:12,560 --> 00:27:18,800
partner they pulled in on this particular project. And they have been working on this air quote IT

272
00:27:18,800 --> 00:27:25,280
project for five years. I can't even imagine how many millions of dollars they had. Long story short,

273
00:27:25,280 --> 00:27:30,000
we went in and we told them like before you start you have to do a solution verification, you have

274
00:27:30,000 --> 00:27:34,400
to know where you're going, you have to document these processes, otherwise you're never going to go

275
00:27:34,400 --> 00:27:40,000
anywhere. And that's what ended up happening. The the leadership in the business that we've already

276
00:27:40,000 --> 00:27:44,240
spent X and R millions of dollars and until you actually change how you're going to do the project

277
00:27:44,240 --> 00:27:51,200
or shutting it down. So it's so important because again, the CIO, the CFO did not get in a room

278
00:27:51,200 --> 00:27:55,280
together and have a collaborative conversation about where they wanted to take the business.

279
00:27:56,400 --> 00:28:01,440
And it failed. We actually pulled out. We're like, we can't this isn't this isn't this is got failure

280
00:28:01,440 --> 00:28:06,800
and all over. So we actually pulled out of the project. So that's what has to happen. There has to be

281
00:28:06,800 --> 00:28:16,960
internal alignment before you can hit external success. Awesome. I you have these these international

282
00:28:16,960 --> 00:28:25,360
experience with the 14 countries. So I like it a little bit to ask what challenges come with

283
00:28:25,360 --> 00:28:33,280
with global EAP projects? Depends on what country you're working in. So if you're working in Latin

284
00:28:33,280 --> 00:28:40,640
America versus Europe, it's very different from a cultural perspective and on the timing of things.

285
00:28:40,640 --> 00:28:47,360
Years ago when I first started working in Latin America, I remember I was working on a project in El Salvador

286
00:28:47,360 --> 00:28:53,600
and being in America were typically very proud. So I would usually get there a little bit early to

287
00:28:53,600 --> 00:28:58,080
the meetings. I would make sure it's fully prepared. So whenever we got in the room, we would start the

288
00:28:58,080 --> 00:29:05,760
project. I started the conversation and I remember I showed up and no one was there and I'm like,

289
00:29:05,760 --> 00:29:12,640
oh no, I'm in the wrong room. So I sat there for like 10 or 15 minutes and again, no, we came and I'm

290
00:29:12,640 --> 00:29:17,040
like, okay, what's wrong? So I actually got up and started asking. So I'm like, hey, you know,

291
00:29:17,040 --> 00:29:23,200
I'm in the right room, like, oh yeah, yeah, yeah, they'll come. And I'm like, okay, and so I sat there

292
00:29:23,200 --> 00:29:31,760
and sure enough and about an hour people started twinkling in. And I was just like, okay. And then I

293
00:29:31,760 --> 00:29:40,640
noticed that that happened quite frequently. So this whole concept of time, I think is perceived

294
00:29:40,640 --> 00:29:46,640
differently in different cultures. I remember you also worked on a project in Puerto Rico and

295
00:29:46,640 --> 00:29:51,600
everything was urgent, urgent, urgent, urgent. And so you would be like, okay, you know, and I get it

296
00:29:51,600 --> 00:29:56,160
done and I give it to them. And then they would literally sit on it for like a year or two years. And so

297
00:29:56,160 --> 00:30:03,360
it's this mentality of everything's urgent, but then there's no action lots of times. And I don't

298
00:30:03,360 --> 00:30:10,560
mean that in negative context. I mean that in the sense of knowing, being an American, thanking a certain

299
00:30:10,560 --> 00:30:17,520
way and then going to these different countries and learning how they think. So I just had to get

300
00:30:17,520 --> 00:30:23,280
myself in alignment with what they did. And then once I did, then I understood how things flowed and

301
00:30:23,280 --> 00:30:27,120
then everything was good. So I'm not saying that one culture is good and one culture is bad. It's just

302
00:30:27,120 --> 00:30:32,800
different. So learning how to work inside of that. I also, once I worked on a project in Turkey,

303
00:30:32,800 --> 00:30:40,080
I remember no one wanted to make a decision because for me, again, my mindset is you do a

304
00:30:40,080 --> 00:30:44,800
risk reward value ad analysis. You look at your options and you pick one and then you do it.

305
00:30:44,800 --> 00:30:52,320
For me, it's just, it's kind of cut and dry. You know, you do the analytics and you then pick the

306
00:30:52,320 --> 00:30:58,800
the path of highest success probability. And when I was in Turkey working on this project, I kept

307
00:30:58,800 --> 00:31:03,280
I'm doing that. I'd provide them with this options and I'm like, okay, what do you want to do?

308
00:31:03,280 --> 00:31:09,440
And I want to make a decision and I was like, okay, so literally you would do this

309
00:31:09,440 --> 00:31:13,520
probably like five or six meetings later and then someone would finally make a decision.

310
00:31:13,520 --> 00:31:21,040
So it's that thought process of learning how they analyze data differently or how they go about

311
00:31:21,040 --> 00:31:30,000
making decisions differently. I've worked on projects in Europe as well and the, their mindset is

312
00:31:30,000 --> 00:31:36,960
a bit more similar to probably what I'm used to. But again, it's more of a collaborative type approach

313
00:31:37,520 --> 00:31:42,560
to business than some of the other cultures that I've worked at. I've also worked in the UK

314
00:31:42,560 --> 00:31:50,880
and going through the process of things is a little bit different. It's very similar in a lot of ways.

315
00:31:50,880 --> 00:31:57,520
But really for me as a consultant, it's making sure that I get an alignment with them. I don't look

316
00:31:57,520 --> 00:32:03,440
at them as a hey you need to get an alignment with me. Okay, it's their business. So I'm there to bridge

317
00:32:03,440 --> 00:32:08,080
the gap and to try to make sure things move along and then I work with it's within the parameters of

318
00:32:08,080 --> 00:32:12,400
what their culture and their businesses. So there are differences, but I think it's going into

319
00:32:12,400 --> 00:32:18,960
with an open mind and loose hands, meaning I'm not going to go in there in white knuckle or get all

320
00:32:18,960 --> 00:32:23,520
been out of shape because I don't do something the way that I do. I start getting curious and asking

321
00:32:23,520 --> 00:32:30,640
questions and then I adapt accordingly. And how different are the finance processes between

322
00:32:30,640 --> 00:32:36,080
the regions? So it depends on what country you're in. So I can France and China, they actually have

323
00:32:36,080 --> 00:32:44,160
statutory chartered accounts. Also they do IFRS, International Financial Standards reporting. In the US,

324
00:32:44,160 --> 00:32:50,160
we have GAP, you know, acceptable accounting practices. So they're very similar. They're

325
00:32:50,160 --> 00:32:54,320
the reporting is a bit different. Sometimes they're chartered accounts are a bit different.

326
00:32:54,320 --> 00:33:00,480
You'll notice there's other kind of posting differences on how everything sit on the trial

327
00:33:00,480 --> 00:33:06,320
balance. Whenever you look at some of the financial reporting for some countries, like in the United

328
00:33:06,320 --> 00:33:11,360
States, when you look at a trial balance, for example, it gets from the most liquid asset to the least

329
00:33:11,360 --> 00:33:18,160
liquid asset. And then in some countries, that's flip-flopped. So the finance piece of it is different,

330
00:33:18,160 --> 00:33:25,200
but similar in many ways. So setting up the posting profiles and different things inside of E365

331
00:33:25,200 --> 00:33:29,840
is somewhat similar, but I always ask the questions because I'll come at it from the approach of

332
00:33:29,840 --> 00:33:35,120
what I think it should be based upon my experience. And then I obviously lead on the client

333
00:33:35,120 --> 00:33:38,560
for verification, for that put it where country to happen to be in.

334
00:33:38,560 --> 00:33:46,240
Awesome. I think a little bit about the importance of localization and dynamics deployment.

335
00:33:46,240 --> 00:33:47,840
How do you see this?

336
00:33:47,840 --> 00:33:55,840
Microsoft has done a lot to get the localizations expanded across more countries. So like in the

337
00:33:55,840 --> 00:34:04,000
United States, we do not do e-envoicing. E-envoicing is the rest of the world type functionality. So e-envoicing is

338
00:34:04,000 --> 00:34:11,200
whenever you send a customer invoice to a customer, it actually has to go through that local government

339
00:34:11,200 --> 00:34:16,640
to get registered with a token before it actually gets sent to the customer to ensure that you,

340
00:34:16,640 --> 00:34:21,680
the company actually pay the correct amount of tax or value out of tax to that government.

341
00:34:22,400 --> 00:34:28,000
So there's localizations around that piece of it. There's some other localizations that get around

342
00:34:28,000 --> 00:34:34,000
the chart of accounts, for example. VAT or value out of tax is significantly different than

343
00:34:34,000 --> 00:34:40,480
U.S. sales tax just to give you an idea in the United States. We have about 15,000 tax codes

344
00:34:40,480 --> 00:34:46,560
in the rest of the world. You have like six ballpark. So you have standard reduced, you're rated

345
00:34:46,560 --> 00:34:52,880
in some special ones. So tax is significantly different. So Microsoft is doing a good job in

346
00:34:52,880 --> 00:34:59,520
expanding that footprint because also the other thing around taxes, you have value out of tax on

347
00:34:59,520 --> 00:35:04,400
transfer orders, purchase order, sales orders, and some different things, which we don't typically do

348
00:35:04,400 --> 00:35:10,320
like tax in the United States on transfer orders. And you can, there's some certain rules around it.

349
00:35:10,320 --> 00:35:17,360
But the localizations, Microsoft's continually expanding that particular footprint. There are still

350
00:35:17,360 --> 00:35:24,960
some gaps in D365 for some countries, but Microsoft is expanding that footprint pretty subtedally.

351
00:35:24,960 --> 00:35:30,720
That's I think why tax advisor earns so much in the U.S.

352
00:35:30,720 --> 00:35:34,720
Yeah, there's a lot to it.

353
00:35:37,840 --> 00:35:47,360
What have you learned from all your international projects, especially what teaches you in leadership?

354
00:35:47,360 --> 00:35:56,160
From a leadership perspective, I think it's to again make sure that there's clarity and alignment

355
00:35:56,160 --> 00:36:01,520
with where the company wants to go. I recently talked to a publishing company in the UK and they're

356
00:36:01,520 --> 00:36:07,200
actually, they're a global type company or it's a publishing company. And understanding what's

357
00:36:07,200 --> 00:36:13,680
important to them is key. So I think the same human elements are pretty much the same across

358
00:36:13,680 --> 00:36:19,920
countries in the sense of the CFO and the CIO and the CIO and the C-suite need to be in alignment

359
00:36:19,920 --> 00:36:25,840
with each other. I mean, that's true regardless what country you're going into. But understanding

360
00:36:25,840 --> 00:36:31,840
what kind of nuances are related to their particular countries is important. So I worked on another

361
00:36:31,840 --> 00:36:36,800
project. It was a life science company and we expanded them into eight different countries.

362
00:36:36,800 --> 00:36:43,840
So just understanding how the companies across the different countries interact with each other

363
00:36:43,840 --> 00:36:49,600
because lots of times you do intercompany transactions. And so if I'm maybe making a product in the

364
00:36:49,600 --> 00:36:54,960
Netherlands and I'm sending it to Germany, for example, or I'm sending it to France or I'm sending it to

365
00:36:54,960 --> 00:37:01,280
UK or sending it to Asia, that intercompany transaction can attract different types of requirements

366
00:37:01,280 --> 00:37:07,120
like certificates of compliance. And there's different kinds of things that are associated with

367
00:37:07,120 --> 00:37:11,920
each one of those countries. So it's really important to understand how that fits together.

368
00:37:11,920 --> 00:37:17,040
From a leadership perspective though, a lot of the companies I've worked with are in Europe or

369
00:37:17,040 --> 00:37:21,520
just somewhere else like Canada or somewhere else in the world, but they will also have a US footprint.

370
00:37:22,160 --> 00:37:27,920
So it's important to make sure that we understand from the implementation perspective

371
00:37:27,920 --> 00:37:33,040
how the companies are going to run differently versus US first and compared to some other

372
00:37:33,040 --> 00:37:37,840
country or how they're going to be similar. And again, that comes into leadership. Leadership has to

373
00:37:37,840 --> 00:37:42,400
talk to each other across these different countries so that they have a big vision of where their

374
00:37:42,400 --> 00:37:48,960
business is going to go so that they can serve as their clients better. Yeah, actually I think we put

375
00:37:48,960 --> 00:37:58,880
in every product, we have the word AI, AI, ERP, Dynamics, co-pilot, so it's really the same.

376
00:37:58,880 --> 00:38:01,360
What does that actually mean in practice?

377
00:38:01,360 --> 00:38:13,680
So co-pilot is your companion or your buddy or your friend largely. So there are independent agents.

378
00:38:13,680 --> 00:38:17,760
So let's kind of break this down into two separate buckets. Buckets, there's co-pilot,

379
00:38:17,760 --> 00:38:21,920
which is going to help you do things. So let's talk about the supplier agent,

380
00:38:21,920 --> 00:38:28,160
inside of D365, finance and supply chain. The supplier agent inside of D365 actually has two different

381
00:38:28,160 --> 00:38:34,720
components to it. It has the, they're both AI, but one's a genetic component to it, and another one

382
00:38:34,720 --> 00:38:41,280
is just more of like an informative piece to it. So the AI part of this informative allows you to go

383
00:38:41,280 --> 00:38:48,080
through it and re-sthrough all of your, your purchase orders to say, hey, when is this purchase order

384
00:38:48,080 --> 00:38:53,680
going to be late? For example, and you set this up in your query so you could say, show me all purchase

385
00:38:53,680 --> 00:38:58,160
orders that are supposed to be delivered on Friday that have a, that I, that I want to follow up with

386
00:38:58,160 --> 00:39:04,400
the vendor. So you maybe you want to be proactive. So today is Thursday and so we want to make sure that

387
00:39:04,400 --> 00:39:09,120
you know everything is going to deliver tomorrow, just as an example. So you can set up this AI

388
00:39:09,920 --> 00:39:14,480
agent of sorts to go through and re-through all your purchase orders to see what should be delivered

389
00:39:14,480 --> 00:39:19,120
and then email your vendor, say, hey, is this going to be delivered tomorrow? Just as an example.

390
00:39:19,120 --> 00:39:23,120
Or if you're being retroactive, you could say, show me everything that was supposed to been delivered

391
00:39:23,120 --> 00:39:29,920
on Monday that hasn't been delivered yet and send an email to that particular vendor. So D365,

392
00:39:29,920 --> 00:39:34,960
on the agent side, who actually draft the, re-through all your purchase orders based on that criteria,

393
00:39:35,520 --> 00:39:43,440
draft a per, an email for you to that vendor. So you have two options. It'll draft the email so you

394
00:39:43,440 --> 00:39:49,200
the human can go through, look at it, tweak it, change the verbiage, whatever you want to and then send it.

395
00:39:49,200 --> 00:39:56,480
Or you could tell the agent component of it to actually draft the email and automatically send it.

396
00:39:56,480 --> 00:40:04,640
So again, isn't it's doing work that I would manually have to do for me? So it's surfacing all

397
00:40:04,640 --> 00:40:10,480
that information. It's calming through the data, it's surfacing that so that me, the human can then look

398
00:40:10,480 --> 00:40:14,480
at it and say, yep, that needs to go. And then when I'm comfortable with it and I get used to

399
00:40:14,480 --> 00:40:21,280
how the system works, that could have it go automatically. So there's also, so every time I'm an MCP,

400
00:40:21,280 --> 00:40:26,720
right? So MCP is allowed you to go out and kind of do what a human does, but you can do it from

401
00:40:26,720 --> 00:40:30,880
like teams, for example. So if I wanted to put in a purchase order, I could go into teams and say,

402
00:40:30,880 --> 00:40:35,920
credit purchase order for this particular, the vendor for this particular item in the system will go

403
00:40:35,920 --> 00:40:44,720
generate that data for me. It's a tool, AI is a tool and it's very powerful, but from what we're saying,

404
00:40:44,720 --> 00:40:50,480
as people are coming up to us and saying, how can I use the AI to get information out of the system?

405
00:40:50,480 --> 00:40:55,680
And then how can I use AI to once I look at something to tell it to update the system? So there's not

406
00:40:55,680 --> 00:41:00,800
a lot of autonomous agents being implemented yet, at least not from what I've seen, but we are

407
00:41:00,800 --> 00:41:07,200
starting to leverage AI a lot as a tool to surface data. So I'm not having to go manually look for

408
00:41:07,200 --> 00:41:13,840
information. I can give it a human language, a large language model, LLM command and let it go

409
00:41:13,840 --> 00:41:22,400
to the database and get that information sent back to me. And what's the topic I think about governance?

410
00:41:22,400 --> 00:41:29,920
What are the risk of implementation these group pilots, AI without strong governance?

411
00:41:30,400 --> 00:41:36,960
So I think it depends on what industry you're in. So I think the governance can be a little bit

412
00:41:36,960 --> 00:41:44,400
looser for some industries versus others. But again, the way D365 is configured, whenever you're

413
00:41:44,400 --> 00:41:52,640
using MCP, for example, or you're using AI, it looks at your security permissions. So D365 has

414
00:41:52,640 --> 00:41:57,680
role-based security permissions. So it's looking at Alicia's permissions, to say does Alicia have

415
00:41:57,680 --> 00:42:03,840
permissions to see or to write to this data or to this table. So it's fully governed. So if I'm in

416
00:42:03,840 --> 00:42:09,920
teams and I'm actually telling the system credit purchase order, ND365, using a command profit in teams,

417
00:42:09,920 --> 00:42:16,400
it's looking at my Alicia's roles to say does Alicia have permissions to do this? So it is fully

418
00:42:16,400 --> 00:42:23,920
governed inside of the Microsoft umbrella of those different pieces. But you do have the capacity

419
00:42:23,920 --> 00:42:30,800
to pull in external resources from like SharePoint files or other external applications.

420
00:42:30,800 --> 00:42:35,360
And that's where governance could get a little bit more tricky. But inside the Microsoft umbrella,

421
00:42:35,360 --> 00:42:42,000
as far as D365 goes, when I'm using AI to pull data or to push data into the application,

422
00:42:42,000 --> 00:42:50,080
it is fully governed by my security role. And what do you think will AI reduce ERP complexity or

423
00:42:50,080 --> 00:42:58,400
actually increase it? I think it's going to shift it. So before we had a lot of human effort going out,

424
00:42:58,400 --> 00:43:03,680
mining data and looking at again, like just like with the supplier agent, a person

425
00:43:03,680 --> 00:43:08,160
would use to, would go run a report to say, show me everything that was supposed to be delivered

426
00:43:08,160 --> 00:43:13,520
on Friday. And then they would have to go through there and manually send an email to those 20

427
00:43:13,520 --> 00:43:17,520
different vendors that have product that should have been delivered or is going to be delivered.

428
00:43:18,160 --> 00:43:26,400
So by the system doing that, now me the user is streamlining my processes. I'm still gathering

429
00:43:26,400 --> 00:43:31,360
the same information, but the system is actually gathering the data for me. So it's making

430
00:43:31,360 --> 00:43:37,600
freeing up my time so I can do other tasks. So I don't necessarily see it getting rid of people. I mean,

431
00:43:37,600 --> 00:43:42,960
there's some capacities like if I persons job is simply to sit there to mine data out the system and do

432
00:43:42,960 --> 00:43:49,440
kind of repetitive work, it could be replaced by AI. There is going to be some of that. But I think

433
00:43:49,440 --> 00:43:54,400
we're going to see that you're going to see this AI is going to free people up so that they can make

434
00:43:54,400 --> 00:44:00,240
more decisions and do more with the information that they have. So I think it's going to be a shift of

435
00:44:00,240 --> 00:44:04,400
work, not necessarily an elimination of work, even though there will be some elimination of work

436
00:44:04,400 --> 00:44:10,960
depending on the role. And when you say, I have looked into a little bit of dynamics and

437
00:44:10,960 --> 00:44:20,080
there are so cool AI things, I think I really love this predictive forecasting. What's your favorite

438
00:44:20,080 --> 00:44:27,040
thing in dynamics? You know, I think this apply region is pretty cool actually because I think

439
00:44:27,040 --> 00:44:32,560
it really takes a lot of work out of doing that follow up in that form of communication. Demand

440
00:44:32,560 --> 00:44:39,360
planning does have a lot of really good analytics and co-pilot functionality, AI functionality inside

441
00:44:39,360 --> 00:44:45,120
of it. The other thing where AI is really going to start taking off, I think, is leveraging the data

442
00:44:45,120 --> 00:44:51,760
and the data lake. It's for like Power BI type information. So if you have multiple data sources and

443
00:44:51,760 --> 00:44:58,240
you pull it into a data warehouse like data lake or something like that, you're going to be able,

444
00:44:58,240 --> 00:45:05,040
you can do like anomaly type AI analysis on it, you could have it look at the data and make

445
00:45:05,040 --> 00:45:12,240
decisions on it and propose certain activities. So I think that it's the footprint. So Microsoft's

446
00:45:12,240 --> 00:45:19,120
actually doing this whole thing with co-pilot where it's, I forgot what it's called, it's called

447
00:45:19,120 --> 00:45:23,520
iWork, I think, I think it's called iWork, I may have that wrong. But anyway, but it's going to be

448
00:45:23,520 --> 00:45:31,200
co-pilot that reaches across word, outlook, Excel, Teams, T365 because it could be that I got an

449
00:45:31,200 --> 00:45:36,320
email from a vendor, right, they emailed me and I can't remember where it came from, like, oh gee,

450
00:45:36,320 --> 00:45:41,760
I know Bob emailed me about that, but where is it? So the co-pilot is actually going to reach across

451
00:45:41,760 --> 00:45:46,880
all of your applications, your Microsoft applications and pull that information. So when I query

452
00:45:46,880 --> 00:45:52,400
on something, it's not just looking at D365, it's actually coming through my Teams chats and through

453
00:45:52,400 --> 00:45:58,320
outlook and those different components. So I think it's really about servicing data in a meaningful

454
00:45:58,320 --> 00:46:07,200
way so you make better decisions. Awesome. Well, yeah, in every podcast I do a ref at Fireground,

455
00:46:07,200 --> 00:46:15,680
I ask a short question and you say first what comes in your mind. So the biggest ERP move,

456
00:46:15,680 --> 00:46:25,600
the biggest ERP, the biggest ERP move, is that what you said?

457
00:46:26,160 --> 00:46:37,680
It means I pronounce it the most bastards. What shall they do about ERP? What shall they,

458
00:46:37,680 --> 00:46:45,440
yeah, look like when it's about topics, what do people think wrong or say wrong?

459
00:46:45,440 --> 00:46:51,120
So when people think about ERP, what is the thing that they think about that might not be correct?

460
00:46:53,600 --> 00:46:57,840
So when people think about ERP, I think lots of times they think it's going to fix everything,

461
00:46:57,840 --> 00:47:07,200
that somehow it's going to fix things inside of their business that ERP is not intended to fix.

462
00:47:07,200 --> 00:47:13,040
So ERP again has a huge impact on the culture of the business, ERP has a huge impact on how

463
00:47:13,040 --> 00:47:19,280
your business processes run, but again, it's a tool. So it depends on how you leverage the tool

464
00:47:19,280 --> 00:47:28,000
to get the desired outcomes. One thing every CFO showed pre-orrorized now. Prioritize what you want your

465
00:47:28,000 --> 00:47:35,680
business to look like in five years. Oh, let's also address that. What skill future consultants need?

466
00:47:35,680 --> 00:47:48,720
Say that again. What is the, yeah, what one skill consultants need in the future?

467
00:47:49,360 --> 00:47:53,840
The main skill that people need for the future is to be flexible.

468
00:47:53,840 --> 00:47:59,600
Take, understand AI, understand the things that are changing in our world and don't resist the

469
00:47:59,600 --> 00:48:05,040
resistance, but don't blindly accept everything. That's not what I mean by that. What I mean is

470
00:48:05,040 --> 00:48:12,240
get curious about what and how you can leverage the tools like AI that are coming out to actually

471
00:48:12,240 --> 00:48:17,120
increase the quality of life for your clients and how you can deliver product to your clients.

472
00:48:18,320 --> 00:48:20,640
One Microsoft technology more people should learn.

473
00:48:20,640 --> 00:48:36,880
I think that one of the things that people should learn inside of Microsoft is really how the

474
00:48:36,880 --> 00:48:45,120
whole ecosystem can work together. Microsoft is not working as silo, idea before, like in the past,

475
00:48:45,120 --> 00:48:50,640
but Microsoft is really connecting all of its different components together. So whenever you think

476
00:48:50,640 --> 00:48:56,080
about Microsoft, don't think about ERP, somehow being independent from your other, your other

477
00:48:56,080 --> 00:49:01,920
Microsoft applications, think about it as holistic system. So I think it would really, the skill people

478
00:49:01,920 --> 00:49:06,640
need to do is like, mind shift a bit and start thinking how the Microsoft ecosystem actually works

479
00:49:06,640 --> 00:49:14,240
together. Coffee tea or energy drink during your life. Say that again.

480
00:49:15,200 --> 00:49:21,440
Coffee tea or energy drink during your life. Coffee tea or energy drink. You know, for me it's

481
00:49:21,440 --> 00:49:29,760
probably coffee. What was the best career advice you ever received? The best career advice I ever

482
00:49:29,760 --> 00:49:35,840
see was to stretch myself. When an opportunity comes up, don't feel like you don't have the skills

483
00:49:35,840 --> 00:49:42,480
to do it, grow into it. There's always good on the other side of hard, and that does not mean

484
00:49:42,480 --> 00:49:47,200
fake it till you make it. I am not a believer in a fake it till you make it mentality. I believe

485
00:49:47,200 --> 00:49:53,600
that whenever someone gives you an opportunity, you learn the skills that you need to actually accomplish

486
00:49:53,600 --> 00:49:59,760
it and to do it well and get curious. No one expects you to have all the answers. Figure out what you

487
00:49:59,760 --> 00:50:04,480
need and ask questions and learn from other people. That was the best career advice I ever got.

488
00:50:04,480 --> 00:50:11,360
And is there any upcoming speaking event podcast or project you would like to

489
00:50:11,360 --> 00:50:16,480
yeah, addition? Yeah, so we just came out of Donnie and Max Kahn, so I had three different speaking

490
00:50:16,480 --> 00:50:23,360
events there and then this fall, we'll be speaking at Microsoft Summit in Nashville, Tennessee. So

491
00:50:23,360 --> 00:50:30,160
super excited about that. So then my last question is when the people show thing or

492
00:50:30,160 --> 00:50:34,400
one information should take from this session, what should it be?

493
00:50:36,800 --> 00:50:41,440
Be comfortable being uncomfortable. So as you're going through your career whether you're implementing

494
00:50:41,440 --> 00:50:46,880
an European implementation or you're just in life or personal growth, the best advice that I can

495
00:50:46,880 --> 00:50:51,920
give you and what I want you to walk away with is learn how to mind shift, learn how to be comfortable,

496
00:50:51,920 --> 00:50:59,680
being uncomfortable because on the other side of that is so much joy and so much success. So stretch

497
00:50:59,680 --> 00:51:05,520
yourself, learn how to network, input your surround yourselves by people that you want to become like.

498
00:51:05,520 --> 00:51:12,480
Yeah, so Alicia, thank you so much for joining the AMC65 podcast. This was an incredible, insightful

499
00:51:12,480 --> 00:51:19,840
conversation around ERP modernization dynamics 365 finance AI, executive leadership and the future

500
00:51:19,840 --> 00:51:25,840
of enterprise transformation. So thank you so much for being here. This was really amazing. Thank you.

501
00:51:25,840 --> 00:51:29,920
Thank you for having me. It's been a pleasure. But I have a good day.

502
00:51:29,920 --> 00:51:30,740
Okay.

503
00:51:30,740 --> 00:51:40,740
[BLANK_AUDIO]