Want to be a Guest? Click Here!
Episode 326: In the Dynamics Corner Chair: 30 Business Central Implementation Tips in 30 Minutes
Episode 326: In the Dynamics Corner Chair: 30 Business Cent…
Dynamics Corner
In this conversation, Brad, Kris, and Tess MacKay share 30 practical tips for a successful Microsoft Dynamics 365 Business Central implemen…
Choose your favorite podcast player
July 2, 2024

Episode 326: In the Dynamics Corner Chair: 30 Business Central Implementation Tips in 30 Minutes

Episode 326: In the Dynamics Corner Chair: 30 Business Central Implementation Tips in 30 Minutes
Apple Podcasts podcast player icon Spotify podcast player icon Youtube Music podcast player icon RSS Feed podcast player icon Amazon Music podcast player icon Audible podcast player icon YouTube Channel podcast player icon
Apple Podcasts podcast player icon Spotify podcast player icon Youtube Music podcast player icon RSS Feed podcast player icon Amazon Music podcast player icon Audible podcast player icon YouTube Channel podcast player icon
Season 3

In this conversation, Brad, Kris, and Tess MacKay share 30 practical tips for a successful Microsoft Dynamics 365 Business Central implementation. They cover many topics, including team involvement, the crucial role of communication, and the value of continuous improvement. They also discuss the importance of leveraging partners and consultants and the necessity of periodic reviews to ensure a smooth and successful implementation.

Send us a text

#MSDyn365BC #BusinessCentral #BC #DynamicsCorner

Follow Kris and Brad for more content:
https://matalino.io/bio
https://bprendergast.bio.link/

Chapters

00:00 - Dynamic Business Central Tips With Tess

07:16 - Ultimate Business Central Implementation Tips

20:11 - Effective Communication and Staffing Strategies

34:43 - Business Central Interview Process Optimization

40:44 - Effective Training and Communication Strategies

Transcript
WEBVTT

00:00:00.300 --> 00:00:06.971
Welcome everyone to another episode of Dynamics Corner, the podcast where we dive deep into all things Microsoft Dynamics.

00:00:06.971 --> 00:00:18.408
Whether you're a seasoned expert or just starting your journey into the world of Dynamics 365, this is your place to gain insights, learn new tricks and tips and hear from industry experts.

00:00:18.408 --> 00:00:19.964
I'm your co-host, Chris.

00:00:20.701 --> 00:00:21.445
And this is Brad.

00:00:21.445 --> 00:00:25.565
This episode is recorded on June 28th 2024.

00:00:25.565 --> 00:00:28.208
Chris, chris, chris, here we are.

00:00:28.208 --> 00:00:33.036
Another day, another episode, another information-filled episode.

00:00:33.036 --> 00:00:44.942
Today, we had the opportunity to learn 30 business central tips in approximately 30 minutes approximately 30 minutes.

00:00:44.942 --> 00:00:55.558
Maybe we went a little bit more, but we also had a little bit more than 30 tips, but we were able to talk about a number of things to consider and analyze whether you're pre or post Business Central implementation With us.

00:00:55.558 --> 00:00:57.607
Today we had the opportunity to speak with Tess McKay.

00:00:57.607 --> 00:01:18.206
Hello, she is hello good afternoon, good morning good evening.

00:01:18.227 --> 00:01:20.650
I don't know what it is, but can you hear me, can you hear me now?

00:01:20.671 --> 00:01:26.489
yes, yes, I can hear you, including the siren I was just going to say that I Wait really, oh gosh, it's okay.

00:01:29.762 --> 00:01:32.585
We're used to the New York City sirens.

00:01:32.585 --> 00:01:36.231
It's okay, it adds to the ambiance.

00:01:36.231 --> 00:01:37.233
The mystique.

00:01:37.233 --> 00:01:38.936
Yes, the mystique, I guess you could say.

00:01:38.936 --> 00:01:40.759
We all know where you are now.

00:01:40.759 --> 00:01:41.099
I love it.

00:01:41.099 --> 00:01:44.069
No other than the wonderful New York City.

00:01:45.840 --> 00:01:49.131
I'm setting the scene for you guys about what my background is like.

00:01:50.742 --> 00:01:51.504
Well, at least we know.

00:01:51.504 --> 00:01:54.325
Hopefully they're not coming for you.

00:01:56.631 --> 00:01:59.106
I don't know After our team night out last night.

00:01:59.106 --> 00:01:59.629
We never know.

00:02:00.840 --> 00:02:02.545
So you had a team night out.

00:02:02.545 --> 00:02:03.406
How was the team night out?

00:02:04.990 --> 00:02:10.187
It was good we did Beer Olympics, so it was quite something.

00:02:10.266 --> 00:02:13.364
I will say that Beer Olympics, what does?

00:02:13.384 --> 00:02:14.329
Beer Olympics.

00:02:17.185 --> 00:02:18.348
What happens in the Beer Olympics.

00:02:21.420 --> 00:02:26.831
So it depends on what your style is, but for us we did.

00:02:26.831 --> 00:02:27.834
We just restarted.

00:02:27.834 --> 00:02:32.370
I'm so sorry.

00:02:33.252 --> 00:02:37.664
I'm welcome back.

00:02:37.664 --> 00:02:39.326
Hopefully you don't disappoint us.

00:02:39.326 --> 00:02:46.955
I was going to say welcome back for the second time on the recording, but now welcome back to the same recording.

00:02:46.955 --> 00:02:54.973
And, as you know, we covered men's grooming tips and Rubik's cube solving on the intermission.

00:02:54.973 --> 00:02:57.268
And it is Friday.

00:02:57.268 --> 00:03:01.770
This is why we don't record on Friday, because something always happens.

00:03:02.522 --> 00:03:03.227
I wanted to.

00:03:03.227 --> 00:03:07.921
I wanted to have a dramatic exit, then come back in and be like all right, I'm ready to go.

00:03:07.921 --> 00:03:09.826
Unfortunately, my laptop is.

00:03:09.847 --> 00:03:12.211
That wasn't dramatic, that was just gone, yeah.

00:03:13.580 --> 00:03:17.185
I was also like mid my spiel about myself too, so I was like getting into it.

00:03:17.185 --> 00:03:20.566
And then my Dell, which is why we shouldn't have Dell laptops.

00:03:20.566 --> 00:03:25.610
Sorry, Dell Completely shut down and just restarted on me, so I apologize everybody.

00:03:31.420 --> 00:03:34.248
We're happy that you made it back Me too, but if you would, could you please tell us a little bit about?

00:03:34.288 --> 00:03:36.174
yourself and then we will jump into today's topic.

00:03:36.174 --> 00:03:36.495
I would love to.

00:03:36.495 --> 00:03:41.842
Before my Dell died on me, I was getting into a bit about me, so thank you again for having me.

00:03:41.842 --> 00:03:43.162
This is my second podcast.

00:03:43.162 --> 00:03:44.522
Very excited to be here.

00:03:44.522 --> 00:03:46.903
My name is Tess.

00:03:47.264 --> 00:03:56.168
I am a vice president at Frank Recruitment Group, where I specialize in business application Microsoft business application, so I should say recruitment.

00:03:56.168 --> 00:03:59.610
I have been doing it for seven years.

00:03:59.610 --> 00:04:01.070
This was my first job.

00:04:01.070 --> 00:04:08.274
Out of college I went to College of the Holy Cross Cross where I played lacrosse there Definitely a washed-up athlete.

00:04:08.274 --> 00:04:10.694
Now I could not pick up a stick if I even tried.

00:04:10.694 --> 00:04:13.575
I've been in New York for those seven years.

00:04:13.575 --> 00:04:15.116
Fell in love with this job.

00:04:15.116 --> 00:04:16.358
Fell in love with the IT world.

00:04:16.358 --> 00:04:17.557
So I've been here ever since.

00:04:17.557 --> 00:04:25.860
A little bit of fun facts about me, as you probably got from my beer pong and beer olympic spiel um, I'm insanely competitive.

00:04:25.860 --> 00:04:33.973
So board games, drinking games, card games, anything you name it, I am crazy competitive.

00:04:33.973 --> 00:04:36.661
Um, katan is my number one board game.

00:04:36.661 --> 00:04:39.689
So if you ever want to challenge me, feel free, but you will lose.

00:04:39.689 --> 00:04:42.062
Um, I'm also a big reader.

00:04:42.062 --> 00:04:44.007
I love anything fantasy.

00:04:44.007 --> 00:04:47.404
So lord of the rings, harry potter it's right up my alley.

00:04:47.404 --> 00:04:55.309
I have two harry potter tattoos, so definitely a little bit of a nerd alert there excellent what excellent

00:04:55.550 --> 00:05:00.002
yeah, I learned something new yeah, I didn't know, you played lacrosse.

00:05:00.002 --> 00:05:03.052
I played lacrosse as well for the.

00:05:03.312 --> 00:05:05.480
You have to be extremely competitive to play lacrosse.

00:05:05.480 --> 00:05:09.487
I enjoy lacrosse, I like watching lacrosse.

00:05:09.487 --> 00:05:14.307
I used to go to the games for lacrosse and that's something new that I learned from you.

00:05:14.307 --> 00:05:18.408
And you went to the College of the Holy Cross in Massachusetts?

00:05:18.668 --> 00:05:19.752
Yes, in Worcester.

00:05:19.752 --> 00:05:20.612
I did not know.

00:05:21.300 --> 00:05:24.004
I've learned or relearned so much about you?

00:05:24.004 --> 00:05:28.211
Yes, because I spend a lot of time in Worcester these days.

00:05:28.432 --> 00:05:29.754
Oh, really, whereabouts.

00:05:31.545 --> 00:05:32.908
Yes, we'll connect afterwards.

00:05:33.410 --> 00:05:34.391
Okay.

00:05:36.180 --> 00:05:37.141
I don't want everyone to know where.

00:05:37.161 --> 00:05:37.523
I am to find me.

00:05:37.523 --> 00:05:41.531
I am a big reader as well, so you have to get on Goodreads so we can share books.

00:05:41.531 --> 00:05:48.725
I am not into the fantasy type books.

00:05:48.725 --> 00:05:52.619
I'm in more into the stoicism what people may call the self-help like time management and focus type books.

00:05:52.619 --> 00:06:00.923
The other challenge I have for you is the next time we meet at a conference we will have rubik's cubes and we're going to have a contest.

00:06:00.963 --> 00:06:06.769
See who can do it faster okay, I won't win that one, but I will be competitive while I'm doing it, so I'll at least try really hard.

00:06:08.651 --> 00:06:09.456
I am very slow.

00:06:09.456 --> 00:06:15.283
Chris and I were talking about this while we were waiting for you to return, so this is my new obsession, again for a couple weeks.

00:06:15.283 --> 00:06:16.682
It took me about a week to learn how to do it.

00:06:16.682 --> 00:06:18.790
Now I just do it every day, trying to get faster and faster.

00:06:19.651 --> 00:06:24.634
Okay, I have until San Antonio in a few months to learn how to do the Rubik's Cube.

00:06:24.935 --> 00:06:25.334
Correct.

00:06:25.334 --> 00:06:28.617
So we will bring lacrosse sticks and see if you still have it.

00:06:29.240 --> 00:06:31.946
So this is a challenge between you and I.

00:06:33.201 --> 00:06:33.824
I actually did.

00:06:33.824 --> 00:06:34.728
You'll find this amazing too.

00:06:34.728 --> 00:06:41.721
On the sports topic, I actually joined a men's beer hockey league a couple weeks ago, so I've been doing that as well.

00:06:41.721 --> 00:06:46.172
So if you want to play some hockey too while we're down there, we can do that that is.

00:06:46.291 --> 00:06:50.261
I did not know you were that athletic, not to say that I just didn't know.

00:06:50.261 --> 00:06:52.245
I think it is great that you are.

00:06:52.586 --> 00:06:53.610
It's a lot of fun.

00:06:53.610 --> 00:06:54.312
It's it's.

00:06:54.312 --> 00:06:54.994
It's a good time.

00:06:54.994 --> 00:06:55.641
Yeah, you gotta.

00:06:55.661 --> 00:07:04.108
You gotta blow off some steam from work, you know no, you definitely do, in new york city working with those dells and the sirens, but with today's episode?

00:07:04.108 --> 00:07:06.394
Does anybody want to know what today's episode is about?

00:07:06.920 --> 00:07:07.944
Yeah, guess the drumroll.

00:07:08.767 --> 00:07:12.610
Right, I'll do the drumroll, because that will be with 30 under 30?

00:07:12.610 --> 00:07:12.610
.

00:07:12.610 --> 00:07:15.026
Well, the under 30 will be good.

00:07:15.026 --> 00:07:21.427
But we had the United States presidential debate last night, which I did watch for a period of time.

00:07:21.427 --> 00:07:35.024
I won't make any comments on that, but, like the debate had, I am the moderator, brad, and in this episode we will have 30 Business Central implementation tips in 30 minutes.

00:07:35.024 --> 00:07:44.369
So I want to see if you and Chris can get us through these 30 tips in 30 minutes.

00:07:45.192 --> 00:07:45.954
Oh man, you both ready.

00:07:46.536 --> 00:07:47.300
In 30 minutes.

00:07:47.379 --> 00:07:48.444
There is no pressure.

00:07:48.444 --> 00:07:50.603
Like okay, okay, I just got to.

00:07:50.603 --> 00:07:52.228
I'm a talker, so I got to be concise.

00:07:53.242 --> 00:07:53.684
You got to do.

00:07:53.684 --> 00:07:55.108
Hey, you got a minute for each.

00:07:55.269 --> 00:07:55.951
A minute for each.

00:07:55.951 --> 00:07:58.889
Okay, it'll be like we'll be in like almost like a rap battle.

00:08:05.199 --> 00:08:06.605
Like I'll be like all right, you now and then back to me.

00:08:06.605 --> 00:08:07.369
So we'll do it in that sense.

00:08:07.369 --> 00:08:09.557
I don't have a timer, so we'll have to, and with that we have tip number one.

00:08:09.579 --> 00:08:12.930
All right, tip number one for business central implementations.

00:08:12.930 --> 00:08:18.939
One of the very first things I always tell my clients to look or to do is the gap analysis piece.

00:08:18.939 --> 00:08:26.851
So look at your internal business model, look at your system, what goals you're trying to achieve and what those gaps currently are within your system.

00:08:26.851 --> 00:08:33.010
So how can you evaluate that and come up with what you actually need to fill those gaps and to improve on those gaps?

00:08:33.010 --> 00:08:39.832
So then you can put together your project plan, your scope of work, your project team from there On to you, chris.

00:08:40.679 --> 00:08:42.344
All right, Chris, with tip number two.

00:08:42.663 --> 00:08:48.335
Tip number two you want to assess the data, your data quality.

00:08:48.335 --> 00:08:49.785
So what does that mean?

00:08:49.785 --> 00:08:56.749
The first thing you do is analyze your data, identify any data issues and, of course, you want to clean up your data.

00:08:56.749 --> 00:09:07.947
So that could also mean if there's anything that is maybe misspelled or some of the descriptions are incorrect or maybe some things like that, you want to start identifying those.

00:09:07.947 --> 00:09:11.571
Also, identify the things that you don't want to bring over as well.

00:09:11.571 --> 00:09:22.220
So make sure you give a little bit more exercise within your organization so that when you are migrating your data, you're not having to clean it up in the new system.

00:09:22.220 --> 00:09:25.989
It's like bringing trash from your old car to your new car.

00:09:25.989 --> 00:09:27.211
You don't want to do that.

00:09:28.620 --> 00:09:29.866
Those are two good tips.

00:09:29.866 --> 00:09:33.190
I'm excited to see what the remaining 28 tips are.

00:09:33.190 --> 00:09:36.306
Brings us over to Tess, tip number three.

00:09:36.988 --> 00:09:37.408
All right.

00:09:37.408 --> 00:09:50.740
Tip number three this one sounds very basic, but it's super, super crucial, whether or not you're a brand new Business Central customer or you're migrating from NAP to BC, gp to BC, a different ERP to BC but do your research.

00:09:50.740 --> 00:10:06.596
So make sure not only are you looking at what are the different resources out there so make sure that you're finding a partner that matches what you're looking for from a partner, from a business model but also make sure that you're doing your research when it comes to what you want out of Business Central model, but also make sure that you're doing your research when it comes to what you want out of business central.

00:10:06.596 --> 00:10:12.691
So look into the different modules, look into the different functionalities and features and third parties to figure out what your ideal system looks like for you.

00:10:12.691 --> 00:10:26.631
That way, you're not jumping into a project without actually doing your due diligence of what all of your options are, from support all the way through to, again, the functionalities and everything that business central can do research is important, you're.

00:10:26.692 --> 00:10:27.836
It does sound basic.

00:10:27.836 --> 00:10:32.609
A lot of these may sound basic, but that does not take away from the importance or what's involved in it.

00:10:32.609 --> 00:10:37.892
But research is extremely important when making the decision of which system to implement which.

00:10:37.892 --> 00:10:45.222
I'm not going to give away any of the tips, so I'm not going to say my next thing You're jumping ahead, come on, I'm trying, I'm trying.

00:10:45.222 --> 00:10:46.565
I'm excited to get through this list.

00:10:46.825 --> 00:10:55.816
Chris, tip number four, tip number four so when you're done with your data cleanup, then you choose a migration approach.

00:10:55.816 --> 00:10:59.923
How do you want to migrate your data?

00:10:59.923 --> 00:11:07.003
In many cases, just like everything else, when you're buying a brand new car, you may not want to bring everything over.

00:11:07.003 --> 00:11:07.825
You have a new car.

00:11:07.825 --> 00:11:18.620
Start with that and just bring the things that are necessary so you can either leave your existing legacy system for you to reference and run report against.

00:11:18.620 --> 00:11:35.596
You can also create a data warehouse to move over things that are important to you that you need to report against, or maybe bring in some of your information to maybe a custom table in your new ERP system, in this case, business Central.

00:11:35.596 --> 00:11:42.609
So there are different ways to approach that, but my recommendation, in my opinion start fresh.

00:11:42.629 --> 00:11:50.225
It's a brand new car Excellent in my opinion.

00:11:50.225 --> 00:11:50.667
Uh, start fresh.

00:11:50.667 --> 00:11:51.809
It's a brand new car excellent.

00:11:51.809 --> 00:11:53.192
You don't want to bring bad stuff in to your new car.

00:11:53.212 --> 00:11:59.288
Don't bring old bucket seats to your new ferrari or something like that okay, good, good, good, see that's.

00:11:59.427 --> 00:12:00.711
I can't do these on fridays anyway.

00:12:00.711 --> 00:12:03.764
I keep saying that I just get lost come on, you're doing great.

00:12:03.783 --> 00:12:07.149
You're doing great, you're doing great, best best moderator right here.

00:12:07.610 --> 00:12:09.552
Yes, yes, well, I'm just counting.

00:12:09.552 --> 00:12:11.081
Hopefully I can make it to 30.

00:12:11.081 --> 00:12:13.105
Tip number five All right.

00:12:13.205 --> 00:12:19.785
Tip number five everyone's favorite topic when it comes to projects is the budget, the money.

00:12:19.785 --> 00:12:35.571
So, after you've done your research, after you've looked at all the support areas that you're going to be looking at, so your partner, any consultants, the licensing, all of the different modules and third parties that you want, make sure that you are allotting that into the budget you have for your project.

00:12:35.571 --> 00:12:42.929
Nothing is worse than getting midway through your project and realizing your budget has run out and you still have 75% of the project to get through.

00:12:42.929 --> 00:12:52.467
So make sure you are looking at all the different scenarios what the licensing looks like, what the pricing looks like, what the scope of work looks like and how that's going to fall into your budget.

00:12:52.467 --> 00:13:11.244
And also take into account that, as much as we all love for things to fall exactly within the range of hours that we estimate, sometimes it does fall without that because of challenges or issues in the system or things that you end up wanting to add that you additionally didn't want to add, so that may fall outside your initial budget.

00:13:11.303 --> 00:13:22.104
So plan for anything, plan for everything and make sure it is in the budget that's extremely important to have a good understanding of how much this is going to cost you, just like a car.

00:13:22.104 --> 00:13:27.407
I always tell people it's important to know if I'm going to go to the Toyota lot or if I'm going to go to the BMW lot.

00:13:29.500 --> 00:13:36.206
Tip number six Tip number six, a very important one, a little tedious, but it is very important.

00:13:36.206 --> 00:13:43.111
It's going to save you a lot of time in the future Identify customizations, add-ons and integrations you have now.

00:13:43.111 --> 00:13:48.544
Sometimes a lot of those things may not be necessary on the first phase of a project.

00:13:48.544 --> 00:13:58.496
You may have a second phase but you need to identify those now, hoping that some of those customizations or add-ons are documented.

00:13:58.496 --> 00:14:00.562
In many cases people don't understand this.

00:14:00.562 --> 00:14:13.942
When you have a new employee or an employee that's worked for you for within a year they may not know if a certain field in your current erp system was customization or was it out of the box.

00:14:13.942 --> 00:14:14.783
They wouldn't know that.

00:14:14.783 --> 00:14:20.561
So sometimes those folks may not be the perfect subject matter experts.

00:14:20.561 --> 00:14:29.634
Hopefully you have things documented to identify those at the very beginning documentation is is one of those things that I can think.

00:14:29.693 --> 00:14:42.044
In all the years that I've been doing this, I've either had too much documentation to where it was meaningless, or zero modification excuse me, documentation, and I'd say primarily it was zero documentation.

00:14:42.044 --> 00:14:44.048
It's always oh, tess knows that.

00:14:44.048 --> 00:14:51.419
Then you go talk with Tess and Tess is like I don't know, I just do this, yep, and that ends up being a problem.

00:14:51.419 --> 00:15:03.672
So it is important to identify your customizations that you have in your existing system, if you have one, also, any additional add-ons or integrations that you have or potentially may need as you go through the process.

00:15:03.751 --> 00:15:09.514
Tip number seven Tip number seven is pretty basic one, but ask the team.

00:15:09.514 --> 00:15:15.149
So, when you are implementing Business Central, it's going to be ultimately the system that is running your day to day.

00:15:15.149 --> 00:15:19.833
So not only are you using it, but your entire team is most likely using it to some capacity.

00:15:19.833 --> 00:15:23.643
I love this car analogy that we've got going, so I'm going to kind of equate it to that.

00:15:23.743 --> 00:15:32.576
So if you have a family of five different people, you need to think about all the different activities or all the different things that the people in the family are going to be using the car for.

00:15:32.576 --> 00:15:34.528
So are they going to be traveling?

00:15:34.528 --> 00:15:37.028
Are they going to be putting a lot in the trunk?

00:15:37.028 --> 00:15:38.866
Are they going to be driving long distances?

00:15:38.866 --> 00:15:42.768
Are they looking for a cool car or a flashy car?

00:15:42.768 --> 00:15:45.153
So it's kind of the same thing with your system, right?

00:15:45.153 --> 00:16:01.626
You need to make sure that every single user is taken into account when looking at what you need to add, what different customizations like Chris just said, different modules, how big you need to have a system, what users need to have from their again, day-to-day, and how often they need to be using things.

00:16:01.626 --> 00:16:13.145
So, instead of just looking at it, a blanket approach for what needs to be in the system, you have to take into account what the users need and what the users would like to see in their next implementation or upgrade of a system.

00:16:14.261 --> 00:16:16.715
That is another extremely important tip.

00:16:16.715 --> 00:16:25.567
You need to make sure that your team is aware and involved, because I've gone through many implementations where someone assumed that one person knew everything.

00:16:25.567 --> 00:16:32.905
They went and put a system together and they had the individuals that use the application as part of their day-to-day business and they said, well, we don't do this.

00:16:32.905 --> 00:16:34.544
We don't do it this way.

00:16:34.544 --> 00:16:35.649
We don't need to do that.

00:16:35.649 --> 00:16:50.389
So it's important to make sure that you have a vehicle that can take your lacrosse gear to the lacrosse game, if you have a lacrosse player in the family Tip number eight, tip number eight you want to do an initial assessment and strategy.

00:16:50.500 --> 00:16:51.544
You've got to develop that.

00:16:51.544 --> 00:16:53.667
There's two key points from there.

00:16:53.667 --> 00:17:03.960
This in itself can have a longer conversation, but two key points is you want to establish objectives as you are building your strategy.

00:17:03.960 --> 00:17:13.414
You want to define the goals and outcomes you expect from this whole project, that you want to put together this whole change in the organization.

00:17:13.414 --> 00:17:15.886
So that's one key point.

00:17:15.886 --> 00:17:29.132
The second key point when you're building and you're assessing the strategy is identify your stakeholders, so list all parties who will be affected by this whole project.

00:17:32.040 --> 00:17:36.148
That's important Assessing and identifying your strategy.

00:17:36.148 --> 00:17:40.185
Tess, tip number nine Nine tips already.

00:17:40.500 --> 00:17:41.321
Tip number nine.

00:17:41.321 --> 00:17:43.508
So this kind of is another formula.

00:17:43.508 --> 00:17:45.881
I guess it's streamlined of the tips I've already given so far.

00:17:45.881 --> 00:17:58.211
But when thinking about the project team that you're going to have, or maybe even just additional support alongside your partner and your internal team, you need to add in additional support, gap analysis and everything you want out of the system.

00:17:58.211 --> 00:17:59.313
Doing your research, all that good stuff.

00:18:09.500 --> 00:18:13.193
Create a wish list If it is a consultant that is going to come in and help you, and what that wish list looks like for them to come in and support.

00:18:13.193 --> 00:18:18.388
Or create a job description if it's going to be a full-time employee coming in to help out on this project.

00:18:18.388 --> 00:18:30.546
Reason being it helps get the right candidate versus just throwing something out there and hoping you get applications, hoping you get the right person to come in.

00:18:30.546 --> 00:18:32.974
You really need to identify what you're looking for before you can actually find that right fit.

00:18:32.974 --> 00:18:43.923
So again, get together with the project team, get together with the internal team, create those lists, create that job description and then from there you can really attract the right talent pool to come in to fit all of those different things that you're looking for.

00:18:45.045 --> 00:18:47.128
That's a good point to create that wish list.

00:18:47.128 --> 00:18:48.633
I have a lot of wishes, Chris.

00:18:48.633 --> 00:18:49.153
Number 10.

00:18:49.859 --> 00:18:50.461
Number 10.

00:18:50.461 --> 00:19:04.104
This is actually a very important one when you are investing money towards this huge project, when you're implementing an ERP system in Business Central, leadership and sponsorship.

00:19:04.104 --> 00:19:05.227
I think this is important.

00:19:05.227 --> 00:19:15.881
You want to have an executive sponsor, so you want to secure that endorsement and active participation from senior leadership.

00:19:15.881 --> 00:19:24.183
There's been too many projects that I'm into where an executive shows up towards the very end and then not knowing what's happening.

00:19:24.183 --> 00:19:30.914
So you want to make sure that somebody is involved and aware of the current situation in your project.

00:19:30.914 --> 00:19:38.473
And, of course, you want to have a you know change management in place as well.

00:19:38.473 --> 00:19:41.730
I know we'll talk about that a little bit further, but you want to build that team.

00:19:41.730 --> 00:19:49.290
You know you want to assemble that team internally, so they'll be your sponsor as you are moving along with this project.

00:19:50.662 --> 00:19:53.526
It is important to have leadership, sponsorship and ownership.

00:19:53.526 --> 00:19:57.223
It's very important to identify who owns.

00:19:57.223 --> 00:19:58.207
Who's responsible.

00:19:58.207 --> 00:20:00.886
When I use ownership, I use responsible for the implementation.

00:20:00.886 --> 00:20:04.548
Tip number 11.

00:20:09.559 --> 00:20:09.800
Tip 11.

00:20:09.800 --> 00:20:11.365
Alrighty, so that wishlist or that job description that I just mentioned?

00:20:11.365 --> 00:20:16.482
One key thing to think about is the must-haves and the nice-to-haves within those different lists.

00:20:16.482 --> 00:20:32.810
So as much as every single client I'm sure would love to have all of these different things accomplished at once, or all of these different skill sets, all of these different certifications and requirements, really look at what you actually need to have as an absolute and what would be sort of the cherry on top.

00:20:32.960 --> 00:20:36.550
So another analogy I'm going to throw out here is thinking about your Amazon cart.

00:20:36.550 --> 00:20:45.182
I know probably everyone's been here done that, but there have been so many times where I've added 30 different things to my Amazon cart and I'm like, all right, I actually don't need all of these 30 things.

00:20:45.182 --> 00:20:52.750
I really only absolutely need these five things because it's going to improve my day-to-day or it's dire for my health or whatever the case is.

00:20:52.750 --> 00:20:54.441
So really think about that.

00:20:54.441 --> 00:21:04.071
Versus adding everything to your cart at once, it will again limit the candidate pool and also most likely miss out on candidates that really do check all the boxes that you do need.

00:21:05.644 --> 00:21:14.000
So most likely miss out on candidates that really do check all the boxes that you do need no-transcript.

00:21:14.000 --> 00:21:35.472
What would you say is the average time it takes to source a position from in the consultant point of view or the full-time point of view for a project or for somebody looking for somebody coming in to manage their system, and then, on the flip side, how long would you say it takes to source the opportunity for a candidate that may be looking for a position on these wish lists?

00:21:35.893 --> 00:21:36.493
position on these wish lists.

00:21:36.493 --> 00:21:54.546
So I would say, depending on what that wish list looks like, I would say for consultants, anywhere from two hours to 24 hours is our typical turnaround time and I would say for full-time again depending on what that job description looks like and what the logistics are anywhere from 48 to a week long to turn around like five really good quality candidates.

00:21:54.546 --> 00:22:03.539
So that would be the typical delivery time I would say for consultants versus full-time, and then to get a consultant or a candidate, is that what you're asking?

00:22:03.539 --> 00:22:05.869
To get a candidate or a role?

00:22:07.574 --> 00:22:16.497
Yes, I'm looking to see what would somebody expect if they had an implementation they were going through and they determined their wish list of the candidate that they want.

00:22:16.497 --> 00:22:20.789
How long would they expect to take to be able to source that position to put in their scheduling?

00:22:20.789 --> 00:22:30.971
And then also, because we're talking about this way, on the flip side, if I were a candidate looking for an opportunity, what would be the turnaround time that I would expect to be one?

00:22:30.971 --> 00:22:38.128
Again, everything depends upon how there's an alignment of the skills versus the needs.

00:22:38.128 --> 00:22:44.496
What is the average time it takes to fill those positions on both directions?

00:22:45.155 --> 00:22:59.948
I would say so again, the delivery time anywhere from a couple hours to a week for a contract and for a permanent role, and then for the candidate side.

00:22:59.948 --> 00:23:02.016
That all depends really on the customer and what their interview process is, what their urgency is.

00:23:02.016 --> 00:23:09.967
So one big thing that as recruiters we always do the best we can is be fully transparent with the candidate what the customer is looking at from an urgency standpoint, from a timeline standpoint and from an interview perspective.

00:23:09.967 --> 00:23:15.188
So if it's a five-round interview process, obviously it's probably going to take, you know, a couple of weeks.

00:23:15.188 --> 00:23:22.848
But if it's a consultant role and it's a one-and-done interview, that can be turned around within a day.

00:23:22.848 --> 00:23:24.134
So it really does depend on what the customer is looking for.

00:23:24.154 --> 00:23:27.167
Again, that's something that we always try to work with both the candidate and the client on.

00:23:27.167 --> 00:23:39.317
If there is high urgency, trying to limit that interview process to shorter rounds or maybe like group panel interviews so that you can make the most of that time and still match what you're looking for in terms of that fast timeline.

00:23:39.317 --> 00:23:54.347
But if it is more of a long, drawn out process no real urgency, which is totally fine, we just make sure to educate our consultants on that and our clients to let them know like hey, that candidate may not be available, if you do take a month long to decide.

00:23:54.347 --> 00:23:58.236
But we try to have all the cards on the table and match the candidate and client energy there.

00:24:01.545 --> 00:24:02.788
I do want to add something on top of that.

00:24:02.788 --> 00:24:17.892
Once they decide who they're going with, you've got to take into consideration the onboarding component of that, because it may take them some time to onboard them to the culture or understanding their business, and so that could take a little bit of time.

00:24:17.892 --> 00:24:21.771
So when you're putting a project together, you take that into consideration as well.

00:24:22.787 --> 00:24:34.534
I just want to let you both know that so many staffing questions popped into my mind in that little dialogue that we've had, so I'm going to maybe interject a few more in the middle of these 30 tips in 30 minutes.

00:24:34.534 --> 00:24:36.952
So that brings us to tip number 12.

00:24:38.086 --> 00:24:38.868
Tip number 12.

00:24:38.868 --> 00:24:40.253
This is important.

00:24:40.253 --> 00:24:44.434
Talking about getting somebody in is the communication plan.

00:24:44.434 --> 00:24:45.678
What does that mean?

00:24:45.678 --> 00:24:54.309
When you are putting together the team, when you're putting together all the tips that we talked about is, how are you going to communicate that?

00:24:54.309 --> 00:24:55.933
That is very important.

00:24:55.933 --> 00:25:01.651
And how do you communicate the entire length of the project and even post-project as well?

00:25:01.651 --> 00:25:06.926
So when you're building the communication plan, you need to create a narrative.

00:25:06.926 --> 00:25:08.530
What does that mean?

00:25:08.530 --> 00:25:17.837
You want to clearly articulate why the change is happening, what will be its impact and how it aligns with your organization's goals.

00:25:17.837 --> 00:25:23.731
Will it be its impact and how it aligns with your organization's goals?

00:25:23.731 --> 00:25:25.757
The second key point in that is creating a multi-channel communication.

00:25:25.757 --> 00:25:26.198
What does that mean?

00:25:26.198 --> 00:25:36.623
Setting a schedule of meeting, create a cadence and, of course, how Either emails, meetings, maybe some SharePoint.

00:25:36.623 --> 00:25:43.999
Those are forms of communication so people can expect where they should be hearing from when you're creating a communication plan.

00:25:45.306 --> 00:25:49.257
Excellent tip which brings us into tip number 13.

00:25:50.205 --> 00:25:51.451
Tip number 13.

00:25:51.451 --> 00:26:05.535
So some people may love this one, some people may not like this one, but again, kind of going back to that wish list, kind of identifying the gaps, the must-haves versus the nice-to-haves, getting comfortable with remote is tip number 13.

00:26:05.535 --> 00:26:19.499
And the reason why I say that is because if you have this must-have list or you have a really high-level role that you're looking to fill, finding someone that's willing to be fully on site at that level is going to be difficult.

00:26:19.499 --> 00:26:20.400
It's not impossible.

00:26:20.400 --> 00:26:27.388
But again, something that I always like to say to my clients is I want to get you the right person, not just someone that can be on site five days a week.

00:26:27.388 --> 00:26:31.066
So again, if being on site outweighs everything else, that's a different story.

00:26:31.066 --> 00:26:35.217
But you really have to look at what's more important and why you need someone to be on site.

00:26:35.696 --> 00:26:46.413
Chris and Brad, I'm sure you guys can attest to the fact that you know so many consultants just like yourselves that do remote work and do fantastic remote work, which is a testament to the fact that remote work does in fact yield results.

00:26:46.413 --> 00:26:55.789
However, I'm sure everyone's had a horror story of someone that was remote and didn't do a great job, and it's really stressful to have that person kind of being behind the scenes and not really knowing what they're doing.

00:26:55.789 --> 00:26:57.553
So completely get that.

00:26:57.553 --> 00:27:07.636
But again, just looking at what you're requiring from a skill set, figuring out is remote, more important than the actual skill set because that will affect what kind of candidates you are getting.

00:27:07.636 --> 00:27:18.657
And maybe finding that balance of maybe once or twice on site a week or maybe even traveling throughout the project versus being on site 100% Again even opens up that candidate pool for you.

00:27:19.405 --> 00:27:22.635
That's why that communication plan is important for people who have remote.

00:27:23.546 --> 00:27:24.851
These all go together well.

00:27:26.247 --> 00:27:29.167
And the remote is a key point you had mentioned.

00:27:29.167 --> 00:27:37.855
Yes, I think with anything, you can have some bad experiences with remote employees, but you can also have bad experience with on-site employees, as we call them.

00:27:37.855 --> 00:27:43.194
I think it's a matter of communication and management and working with the team that you have.

00:27:43.194 --> 00:28:10.935
I think the remote also again, if you're talking about the wish list and the skill set that remote versus on-premise requirement may limit the talent pool that you have to choose from, because you may have some really qualified candidates for a position as part of the implementation, that may be in a different state or a different country or a different region that you might not be able to get within the region you are for whatever you know reason or whatever location you are in.

00:28:10.935 --> 00:28:25.836
So that is an extremely important tip and, chris is like you had mentioned, the communication is key because that does ensure that you have a proper working relationship with whomever you have to staff your position, which brings us into tip number 14, which may be related to this.

00:28:25.836 --> 00:28:27.951
Yes, this is actually very important.

00:28:28.045 --> 00:28:32.176
A lot of people don't understand the importance of this is you want to establish a support system.

00:28:32.176 --> 00:28:37.657
There's been countless times where you know somebody in the organizations don't know who to go to.

00:28:37.657 --> 00:28:39.367
I have an issue, I have a problem on my.

00:28:39.367 --> 00:28:40.510
You know in the organizations don't know who to go to.

00:28:40.510 --> 00:28:41.773
I have an issue, I have a problem in the system.

00:28:41.773 --> 00:28:42.435
I can't do this.

00:28:42.435 --> 00:28:44.039
And what happens?

00:28:44.039 --> 00:28:44.821
They just Google it.

00:28:45.125 --> 00:28:48.972
So if you establish a support system, they know who to go to within your organization.

00:28:48.972 --> 00:28:51.893
So the first thing there's key points to this.

00:28:51.893 --> 00:28:57.204
The first thing is you want to make it easy to access the support that a person needs.

00:28:57.204 --> 00:29:08.316
So you want to establish that support system and consider organizing a team of experts assigning roles and responsibilities in developing an issue resolution workflow.

00:29:08.316 --> 00:29:10.071
How does that look like in your organization?

00:29:10.071 --> 00:29:17.164
You want to provide ongoing training for your support staff to keep them updated on the latest features and functionality.

00:29:17.164 --> 00:29:25.339
A well-trained support team ensures that your system runs smoothly, minimizing downtime and keeping stakeholders satisfied.

00:29:25.726 --> 00:29:27.352
So the first one again make it easy.

00:29:27.352 --> 00:29:33.617
Number two utilize your contributors or subject matter experts as they go to for support.

00:29:33.617 --> 00:29:42.380
That can also mean utilizing your partners, your specialists, your consultant, your contractor maybe, and, of course, your subject matter experts.

00:29:42.380 --> 00:29:45.473
The last key point to that is encouragement.

00:29:45.473 --> 00:29:51.917
When you are building a support system, you don't want to shame people for asking support.

00:29:51.917 --> 00:29:54.834
This is a brand new system that you're implementing.

00:29:54.834 --> 00:29:56.588
Some people are going to have questions.

00:29:56.588 --> 00:30:08.974
You want to encourage them to share the challenges that they may encounter so that when you're encouraging, you're minimizing that rogue processes, which creates bad data.

00:30:08.974 --> 00:30:16.835
So you want to make sure that you're encouraging that it's okay to ask, even though if it's an elementary questions.

00:30:18.498 --> 00:30:19.299
Oh, great tip.

00:30:19.299 --> 00:30:20.990
Okay, here we are.

00:30:20.990 --> 00:30:22.369
We're halfway there.

00:30:22.369 --> 00:30:25.326
I can't sing the song because I don't want anyone to come saying that I was.

00:30:25.326 --> 00:30:28.652
You know copywriting anything but Tess number 15.

00:30:29.605 --> 00:30:31.051
Tip number 15.

00:30:32.365 --> 00:30:33.912
Did you know the song, by the way.

00:30:34.333 --> 00:30:34.534
What.

00:30:35.305 --> 00:30:36.166
Oh, we're halfway there.

00:30:36.968 --> 00:30:39.471
Halfway there, you don't want to see me.

00:30:39.491 --> 00:30:40.232
My voice is terrible.

00:30:40.252 --> 00:30:44.019
You, don't want me to go there, I just wanted to make sure everybody got it.

00:30:44.058 --> 00:30:45.099
It's not karaoke night.

00:30:45.384 --> 00:30:48.946
Maybe I know if that came out before you went to the Holy Cross.

00:30:49.288 --> 00:30:50.469
Yes, or not.

00:30:50.469 --> 00:30:52.651
Yeah, you don't want to see me at karaoke night.

00:30:52.651 --> 00:30:56.795
It's not good, so don't ask me to do that.

00:30:56.815 --> 00:30:59.917
We will do Rubik's and karaoke in San Antonio.

00:30:59.917 --> 00:31:04.321
Anybody else that would like to participate, find us, yep.

00:31:05.825 --> 00:31:08.807
Please don't, but maybe All right.

00:31:08.807 --> 00:31:10.127
Tip number 15.

00:31:10.127 --> 00:31:11.650
So this one's extremely important.

00:31:11.650 --> 00:31:14.352
I think this is crucial from the very first stage.

00:31:14.352 --> 00:31:20.336
So, from scopes right From getting an actual quote of your project, Tip number 15 is get a comparison.

00:31:20.356 --> 00:31:33.827
So, even when you're getting that initial quote, if you're again a brand new customer, or maybe you're going from NAB to Business Central making sure that you're getting a comparing quote.

00:31:33.827 --> 00:31:34.608
So don't just rely on one quote.

00:31:34.608 --> 00:31:37.695
Definitely do your due diligence to look at what the other quotes could potentially be, so that you have something to compare to Again.

00:31:37.695 --> 00:31:40.501
You can crunch the numbers, look at what the best option is for you.

00:31:40.501 --> 00:31:45.553
Same thing with bringing in any full-time employees for a project team.

00:31:45.553 --> 00:31:55.271
Make sure that you're interviewing more than just one person, because you want to get different perspectives, different price points, different personalities, different experience levels.

00:31:55.291 --> 00:31:58.638
So it's really important to see again what is the best fit for you.

00:31:58.638 --> 00:32:09.244
And it may not be that first person, which is completely fine, or maybe it is that first person, but still do your due diligence to interview a couple more people after that, as a recruiter, we'll always be sure to give you options.

00:32:09.244 --> 00:32:15.548
On the full-time side, we always like to give at least four to five really qualified candidates to give you options to choose from.

00:32:15.548 --> 00:32:17.849
Same thing goes for a consultant.

00:32:17.849 --> 00:32:29.201
Again, you want to look at the different price points, but different business models, different previous projects that they've been, on, different personalities again, or different overall vibe, depending on what you're looking for.

00:32:29.201 --> 00:32:35.711
Just speaking to one person often limits the opportunities that you could have to see who can be that long-term fit for you.

00:32:35.711 --> 00:32:49.211
So again, as a recruiter, I'm always going to encourage my customers please speak to at least two to three people on the consultant side and again, at least four to five people on the permanent side, so you have ample options to choose from.

00:32:50.253 --> 00:32:50.555
Excellent.

00:32:50.555 --> 00:32:51.625
It's a great tip, Chris.

00:32:51.625 --> 00:32:52.430
Number 16.

00:32:53.105 --> 00:32:57.384
16, I would consider optimization and customization.

00:32:57.384 --> 00:33:10.494
One of the most significant advantages of Business Central is its ability to adapt to your business, so don't be afraid to customize and optimize your system to meet your workflows and processes.

00:33:10.494 --> 00:33:19.773
Now consider engaging a specialist or partner to review and optimize your system regularly, so not just you go live and you leave it alone.

00:33:19.773 --> 00:33:24.056
The purpose is for you to continue to optimize your system.

00:33:24.056 --> 00:33:31.932
There are two different things though optimization and customization, so I want to make sure that you're aware of that.

00:33:31.932 --> 00:33:40.972
Just because you want to optimize a process, it doesn't always mean to customize, so there's a few things that you can consider, some options for you.

00:33:40.972 --> 00:33:44.087
One is Power Platform, specifically the Power Automate.

00:33:44.789 --> 00:33:46.978
Take a look at the job queue in Business Central.

00:33:46.978 --> 00:33:59.646
Schedule those tedious reports or processes, review some add-ons in the app source, identify what challenges are you trying to solve, but just make sure you work with your partner With that.

00:33:59.646 --> 00:34:04.791
Not all apps are created equal and it may not fit for your business, so work with your partner.

00:34:04.791 --> 00:34:07.132
The other one is personalization.

00:34:07.132 --> 00:34:15.815
It's profiled within Business Central so that can help you improve your workflow by removing unnecessary fields that you don't need to see.

00:34:15.815 --> 00:34:20.556
And, of course, customization and extension as well.

00:34:20.556 --> 00:34:26.867
And then, the last but not least, when you're already live in Business Central, there are options to look at telemetry as well.

00:34:26.867 --> 00:34:42.005
There's lots of contents out there Brad talks about this all the time that can help identify your usage of Business Central and how can you optimize, get the most out of your Business Central, which is common that we get those a lot when we're working with clients.

00:34:43.606 --> 00:34:59.652
I feel like I'm not using Business Central to the max, so telemetry can help you identify where you're not using it, it's important to get the application to fit your needs and, as you'd mentioned, to make sure you get the most out of the application.

00:34:59.652 --> 00:35:07.025
Sometimes, when you're doing the requirements gathering, it's also important to take a moment to think of what could we be doing differently.

00:35:07.025 --> 00:35:20.414
Sometimes people focus on what I'm doing today versus what I need to be doing or some other efficiencies I could gain from an application that's robust and feature rich, which takes us into tip number 17.

00:35:21.146 --> 00:35:21.728
All righty.

00:35:21.728 --> 00:35:25.398
Tip number 17 is defining an interview process.

00:35:25.398 --> 00:35:28.266
So I look at this in three different categories.

00:35:28.266 --> 00:35:33.987
So the first is urgency, the second would be availability and then the third would be who's involved.

00:35:33.987 --> 00:35:43.869
So these are three really important questions when you are defining what your interview process will look like internally, whether that is for a consultant, whether that is for a full-time employee.

00:35:43.869 --> 00:35:48.327
So when it comes to urgency, how quickly do you need to have this role filled?

00:35:48.327 --> 00:35:50.717
What's going to happen if you don't get this role filled?

00:35:50.717 --> 00:35:52.927
When do you need this role to be filled by?

00:35:52.989 --> 00:36:02.347
So asking yourself these questions are going to be super important, because that will determine how quickly you need these candidates to be turned around and how quickly you need to be available to interview these candidates.

00:36:02.347 --> 00:36:04.170
That brings me to availability.

00:36:04.170 --> 00:36:19.628
If you do have a really high turnaround, and when you need this person to start, really make sure that internally you're getting everyone's availability ahead of time so that we can make those calendar invites a lot easier and get those interviews booked a lot faster for you to match the timeline that you're looking for.

00:36:19.628 --> 00:36:22.559
And then the last one would be who's involved.

00:36:22.559 --> 00:36:34.065
So when thinking about what you're going to be bringing in from a consultant perspective or a full-time employee perspective, who needs to be involved in that process, who actually is signing off on the process?

00:36:34.065 --> 00:36:38.746
That's really important to identify so you can understand who needs to be on these interviews.

00:36:39.387 --> 00:36:40.731
Do they need to be multiple rounds?

00:36:40.731 --> 00:36:42.396
Do they need to be a panel-style interview?

00:36:42.396 --> 00:36:44.469
Does it need to be a one-and-done interview?

00:36:44.469 --> 00:36:46.034
So all those things are super important.

00:36:46.034 --> 00:36:52.829
Again, it'll help us, as recruiters, give you the right resources that can match that timeline or urgency you need.

00:36:52.829 --> 00:37:11.014
But also, from an internal perspective, you do want to have any key players on those interviews so that they can ask questions, they can hear other questions that maybe someone else is asking and also the consultant or that full-time employee can paint a full picture about what value they can add to you and everyone involved can hear that from them.

00:37:11.014 --> 00:37:18.875
So they can really feel that when they do decide on a resource, everyone is comfortable, everyone is on board and everyone is excited to have that person join the team.

00:37:20.356 --> 00:37:33.411
I have a question on the interview process which comes up and we're talking about looking to staff in this case a business central implementation and to talk with candidates to fill a need or fill a role that you have that you define.

00:37:33.411 --> 00:37:51.295
What about the cases where I may not know what I need or can validate or verify that the candidate fits the position, meaning I may not be technically capable enough if it's a technical position, or business savvy enough to use the word loosely to be able to determine?

00:37:51.295 --> 00:37:53.907
This is for anybody, chris, you as well.

00:37:53.907 --> 00:37:59.887
I may not be able to determine myself a proper assessment for the candidate to see if they'll fit that role.

00:37:59.887 --> 00:38:02.331
What options would I have?

00:38:03.153 --> 00:38:11.773
That's a really great question and that's actually something we get quite a lot of customers coming to us being like, hey, we don't really know what we need, we just know we need something, totally fine.

00:38:11.813 --> 00:38:26.996
So I always suggest in that, obviously, talking through a conversation with us first or your partner first, just to kind of uncover some of the questions or some of the challenges you feel like you have, from there can come up with sort of a again that wishlist or that ideal description to start.

00:38:27.036 --> 00:38:30.679
So that could be just leveraging your partner or a recruitment consultant like myself.

00:38:31.300 --> 00:38:43.612
But even just speaking with candidates, you can just talk about the situation that you're going through internally, you can talk about your project, you can talk about the gaps or the challenges that you're facing, and these consultants will be subject matter experts.

00:38:43.612 --> 00:38:55.019
They can talk through those scenarios with you and oftentimes connect a lot of dots for you by just giving you different scenarios or giving you previous projects where one of their customers went through something very similar.

00:38:55.019 --> 00:39:00.949
You can actually paint that picture for you and give you, oh okay, this is actually what the system can do.

00:39:00.949 --> 00:39:05.909
So that's something that, again, an interview can really just clear up a lot of that for a customer.

00:39:05.909 --> 00:39:15.248
But then again, anytime a consultant comes in, typically the very first step they're going to do is do a deep dive into the system and kind of put together a project plan.

00:39:15.248 --> 00:39:17.532
That also is going to help clear up a lot of gaps.

00:39:17.532 --> 00:39:24.831
For any customers that's not really sure what that should look like, the candidate will do that for them, if that is what's required.

00:39:25.425 --> 00:39:28.896
I will kind of, if I could put a little bit of an analogy here.

00:39:28.896 --> 00:39:33.744
So, in many cases, a great question, brad.

00:39:33.744 --> 00:39:38.893
I think this whole part of this could be a longer conversation in the future.

00:39:38.893 --> 00:39:45.157
But if you look at it from a, let's say, for example, I'm not a painter, right, but I have a vision.

00:39:45.157 --> 00:39:52.059
I know what kind of what I want to look, right, I'm going to hire somebody that knows how to paint.

00:39:52.585 --> 00:39:59.221
I don't know what kind of brushes they would use, I don't know what kind of paint they're going to use, but I know what I want to see.

00:39:59.221 --> 00:40:18.644
At the very end, right, if I can share and try to describe exactly what I want at the very end, I'm going to rely on that expert to know okay, this is the paint you want to use, this is the brush we're going to use, this is the canvas, this is the material they can deal with.

00:40:18.644 --> 00:40:19.027
That.

00:40:19.027 --> 00:40:22.731
I just want to make sure that what I want is painted accordingly.

00:40:22.731 --> 00:40:31.768
No different of designing a kitchen, right, I know what I want, but I don't know the kind of materials that the process is going to take to deliver that Same process.

00:40:31.768 --> 00:40:37.715
So that's when you start having that conversation, the whole dialogue.

00:40:37.755 --> 00:40:38.376
Great, thank you.

00:40:38.376 --> 00:40:44.902
Thank you, and that takes us to tip number 18 of our Business Central implementation tips 18,.

00:40:44.922 --> 00:40:45.646
So you want to create Guys.

00:40:45.646 --> 00:40:46.490
Can you speed it up a little bit?

00:40:46.490 --> 00:40:47.355
Yeah, I do.

00:40:47.355 --> 00:40:49.827
We do need to create a.

00:40:49.827 --> 00:40:54.748
You need to create a structure for end-user training and adoption.

00:40:54.748 --> 00:40:56.967
So this is when you're already in business central.

00:40:56.967 --> 00:41:05.552
You want your end users to feel confident in using your new system, so you want to provide with training tailored for their specific roles and responsibilities.

00:41:05.552 --> 00:41:07.405
It's going to take a little bit of time to build this.

00:41:07.405 --> 00:41:15.967
Of course, you want training ensures that they remain competent and productive in the areas, while also ensuring system-wide consistency.

00:41:16.380 --> 00:41:20.309
So there are four key points that I wanna mention here.

00:41:20.309 --> 00:41:31.206
Establish consistent scheduling or schedule for training, whether this is a monthly, quarterly or even in line with the wave releases of what's new in Business Central.

00:41:31.206 --> 00:41:41.710
Second key point is easy access for your end users to stay informed of the new updates and changes Again, sharepoint, sop or simple email.

00:41:41.710 --> 00:41:45.909
Third key point is communication is key, right?

00:41:45.909 --> 00:41:47.666
We mentioned this earlier.

00:41:47.666 --> 00:41:50.268
You want to establish effective communication.

00:41:50.268 --> 00:41:52.547
Don't just talk and just say the words.

00:41:52.547 --> 00:41:55.141
You have to create actionable items after that.

00:41:55.141 --> 00:42:04.768
And then number four again make it easy, tailor it to the way your staff can easily learn, provide an opportunity to share ideas as well for improvement.

00:42:04.768 --> 00:42:08.385
Don't just you know, don't just train them for something?

00:42:08.385 --> 00:42:10.271
Listen for some of that feedback.

00:42:11.539 --> 00:42:13.789
Oh, perfect Tip number 19.

00:42:15.340 --> 00:42:18.369
All right, I'm going to combine tip 19 and 21 to speed things up a little bit here.

00:42:19.273 --> 00:42:28.847
So tip number 19 is speak to multiple options, which I already kind of touched upon, and tip number 21 is give and discuss feedback to tailor searches.

00:42:28.907 --> 00:42:42.248
So what I mean by that is again back to kind of the painting analogy If you don't know what you want right off the bat, you may want a Van Gogh, you may want a Leonardo da Vinci, you may want a Pablo Picasso, who knows?

00:42:42.248 --> 00:42:43.746
So speak to each of those.

00:42:43.746 --> 00:42:48.623
You can really start to narrow down what you do want for a consultant or a full-time employee.

00:42:48.623 --> 00:43:07.615
And then, based on that, if you do speak to the painters of the world right and you get feedback internally with your team, make sure you're communicating that, whether it's to the candidates, to the recruiter, to the partner, so that from there the search can be tailored even further to figure out okay, maybe we didn't like this, all right, great, let's tweak it from there.

00:43:07.615 --> 00:43:21.914
Or maybe we love this, but this just person isn't the right fit Awesome, but this just person isn't the right fit Awesome, we'll go with that route of at least that consultant or that background to give you more candidates that kind of are more in line with what you're looking for Great, excellent.

00:43:22.000 --> 00:43:23.686
So now we have tip number 20.

00:43:23.686 --> 00:43:27.510
You have to jump to 22 as well, because we did 19 and 21.

00:43:27.579 --> 00:43:30.248
20 and 22 go hand in hand.

00:43:30.248 --> 00:43:34.244
So when you're in business central already, you know you want to optimize that.

00:43:34.244 --> 00:43:34.907
We talked about it.

00:43:34.907 --> 00:43:38.045
It's data management and reporting.

00:43:38.045 --> 00:43:41.570
And then, of course, the 22 is continuous improvement.

00:43:41.570 --> 00:43:42.976
This goes hand in hand.

00:43:42.976 --> 00:43:55.829
You want to make sure that you validate data periodically, use proper reporting tools there's plenty of them out there Power BI I'll say that from you know, just easy and and, of course, built-in analysis view as well.

00:43:55.829 --> 00:44:01.945
And of course, you wanna make sure you review your report relevance, just because someone's been running it.

00:44:01.945 --> 00:44:07.246
There's been countless times where someone runs a report and is like, oh, we've always run this, but no one ever takes action against it.

00:44:07.246 --> 00:44:15.762
It's just a report that someone runs and then tip number 22 is continuous improvement, just like everything else maintaining that reporting.

00:44:16.403 --> 00:44:20.130
You want to set the continuous improvement.

00:44:20.130 --> 00:44:21.681
So there's four key points here.

00:44:21.681 --> 00:44:26.561
You want to streamline workflows, identify things that are tedious how can you streamline those?

00:44:26.561 --> 00:44:30.431
And then the second bullet point is training and skill development.

00:44:30.431 --> 00:44:39.144
You want to give your users opportunity to learn new skills around your business, around your business, not just training the application, but understanding your business and what you're trying to do.

00:44:39.144 --> 00:44:40.885
Number three create a feedback loop.

00:44:40.885 --> 00:44:53.646
Feedback loop might refer to the process of taking action based on your user feedback, then revisiting the user to understand how well the action work and then refining the action based on this new feedback.

00:44:53.646 --> 00:44:55.628
So you want to create that feedback loop.

00:44:55.628 --> 00:44:58.409
The fourth one is create an ideas platform.

00:44:58.409 --> 00:45:08.846
It's a place for users to submit some ideas of improvement and make it easy for them to be heard as well, because again, they're in the trenches, they're the ones using the application.

00:45:08.846 --> 00:45:11.782
They're going to know what's the best way or things to improve.

00:45:12.682 --> 00:45:15.206
I'm picking up on a lot of communications key in life.

00:45:15.206 --> 00:45:17.528
Tip number 23, Tess.

00:45:17.809 --> 00:45:20.833
Tip number 23 is match the urgency.

00:45:20.833 --> 00:45:31.710
So there's two separate parts to this, the first part being if you're thinking about a project deployment and when you actually want to kick things off, let's say the kickoff date is August 1.

00:45:31.710 --> 00:45:38.262
Putting together your project team on July 30 is probably not going to be the move.

00:45:38.262 --> 00:45:51.268
So making sure that you're planning ahead for that kickoff and making sure that everyone internally is on the same page there is part number one and then part number two is based on that urgency that you and the internal team have put together.

00:45:51.268 --> 00:45:54.364
Ensure that you have the internal infrastructure to support that.

00:45:54.384 --> 00:45:57.902
So, again, thinking about booking interviews how quickly do you need to do that?

00:45:57.902 --> 00:45:59.047
Who needs to be on it?

00:45:59.047 --> 00:46:01.498
When does this candidate need to be onboarded?

00:46:01.498 --> 00:46:03.664
Do they have the right people internally to be there?

00:46:03.664 --> 00:46:05.228
Are people on vacation?

00:46:05.228 --> 00:46:08.141
Do you understand that the onboarding may take two weeks?

00:46:08.141 --> 00:46:10.246
What does the ramp-up time look like?

00:46:10.246 --> 00:46:21.929
So, if it is a longer, longer ramp up time, but you really need this person to be at full capacity September 1, making sure that they're getting started earlier so that they can match that urgency, or needing for them to be ramped up.

00:46:21.929 --> 00:46:30.128
So again, timeline is so important and understanding what everyone internally needs to do to match that timeline and urgency is going to be super important.

00:46:31.190 --> 00:46:33.867
Great, chris, take us into tip number 24.

00:46:34.019 --> 00:46:34.541
24,.

00:46:34.541 --> 00:46:37.766
What we'd all be talking about this whole time is communication is key.

00:46:37.766 --> 00:46:44.090
I will leave a quote for you, a quote that I did not do a chat GPT.

00:46:44.090 --> 00:46:46.547
I've been using this for years.

00:46:46.547 --> 00:46:53.068
So knowledge empowers, but communication elevates.

00:46:53.068 --> 00:47:11.166
Through training and open dialogue within your organization, you can unlock the full potential of the tool not only the tools that you're utilizing, but also your entire team, uh, within your organization communication is important in every part of life, which takes us to tip number 25.

00:47:11.226 --> 00:47:12.387
We are almost there.

00:47:12.748 --> 00:47:16.945
Tip number 25 is again kind of streamlining with communication.

00:47:16.945 --> 00:47:24.266
The perfect, I would say, structure for a project team, which is tip number 25, identifying your project team.

00:47:24.266 --> 00:47:29.445
I'd say a perfect picture of what that would look like would be a triangle.

00:47:29.445 --> 00:47:33.260
So the triangle would be at the top is, of course, your internal team.

00:47:33.260 --> 00:47:38.213
Obviously, the foundation of who's going to be utilizing the system On one of the sides.

00:47:38.213 --> 00:47:48.106
It's going to be, of course, your Microsoft partner, who you're going to be leveraging heavily throughout the entire project, and then over here in this little other triangle point, is going to be an independent consultant.

00:47:48.106 --> 00:48:03.291
I think finding the perfect internal team, leveraging your partner and also leveraging an outside consultant, is the perfect match for a project and, of course, all three of those points need to be communicating throughout the entirety of the project to lead to a successful implementation.

00:48:04.360 --> 00:48:10.409
And just like a triangle, you need three strong sides 100% To keep this triangle strong.

00:48:10.409 --> 00:48:12.722
I tried to do some fancy quote there and I didn't do a good job.

00:48:12.722 --> 00:48:13.003
That was good.

00:48:13.204 --> 00:48:13.684
That was really I'm.

00:48:13.704 --> 00:48:14.186
Inspired do a good job.

00:48:14.186 --> 00:48:14.806
That was good, that was really.

00:48:14.806 --> 00:48:15.507
It's Friday, I'm inspired.

00:48:15.527 --> 00:48:16.989
I'm inspired 26.

00:48:17.411 --> 00:48:17.751
Chris.

00:48:18.333 --> 00:48:19.835
All right, 26.

00:48:19.835 --> 00:48:21.206
I'll put two and two together.

00:48:21.206 --> 00:48:23.306
One is change management.

00:48:23.306 --> 00:48:27.179
Yes, change management and leveraging a partner.

00:48:27.179 --> 00:48:41.260
I think one of the things that's very important when you are implementing something this big within your organization, you have to make sure that the rest of the organization is aware of this change while you're doing it.

00:48:41.260 --> 00:48:51.726
So, again, a quote that kind of combines the 26 and 28 is having a clear vision and aligning the organization is key.

00:48:51.726 --> 00:48:59.516
So choosing the right vendor partner, whatever and having an internal implementation team increases the chance of success.

00:48:59.516 --> 00:49:03.992
So that goes together there with that quote 26,.

00:49:04.052 --> 00:49:05.456
change management, 28,.

00:49:05.456 --> 00:49:08.706
Leverage your partner, which gives us to tip 27.

00:49:08.706 --> 00:49:14.789
I guess we should say that's really 26 and 27, and we could have renumbered these, but anyway we'll go to 27.

00:49:15.371 --> 00:49:15.932
27.

00:49:15.932 --> 00:49:16.782
So 27,.

00:49:16.782 --> 00:49:18.188
Honestly, I was going to have a two-parter here too.

00:49:18.188 --> 00:49:21.490
Mine was going to be leverage your partner and then leverage your independent consultant.

00:49:21.490 --> 00:49:28.050
So Chris already touched upon leveraging a partner completely key and then, on the other side, leveraging an independent consultant.

00:49:28.050 --> 00:49:40.280
This is something that I think is so important when thinking about a project, because your internal staff is so busy with so many different things, tossing on a full-blown implementation on that as well can be really time-consuming.

00:49:40.280 --> 00:50:01.284
So think about what potential gaps you may have internally and maybe where someone like an independent consultant or an SME can come in and really help take some of that weight off of your internal team to work again alongside them and your partner for a smooth implementation to ensure that you have sort of that even weight and that triangle of success that I mentioned.

00:50:02.947 --> 00:50:06.094
Excellent, excellent, which gives us to tip 29.

00:50:06.094 --> 00:50:08.862
That's for you.

00:50:08.963 --> 00:50:10.248
Oh, that's me, oh gosh.

00:50:10.268 --> 00:50:10.809
Sorry guys.

00:50:12.621 --> 00:50:14.784
Chris did 28 and you both did leverage.

00:50:14.784 --> 00:50:16.829
It's great, it's been the beer.

00:50:16.829 --> 00:50:19.333
The Beer Olympics are settling in there on you.

00:50:19.333 --> 00:50:20.114
I know, I know.

00:50:21.942 --> 00:50:23.103
All right, tip 29.

00:50:23.103 --> 00:50:26.027
So this is obviously very specific to recruitment.

00:50:26.027 --> 00:50:35.885
But if you do get a consultant or a full time employee from a recruiter like myself, you always really encourage something we call post-placement follow-up.

00:50:35.885 --> 00:50:50.461
So if we place a consultant with you or if we place a full-time employee with you again back to that communication piece it's super, super key to continue that communication throughout the project, if it's a consultant, or throughout the initial few months of that employee.

00:50:51.003 --> 00:50:52.565
We always are looking for feedback.

00:50:52.565 --> 00:51:09.565
We're always looking to make sure that that candidate has joined the team flawlessly, they've been able to get up and running, they've been able to get involved with the team on a good note and, on the consultant side, making sure that they are bringing the skill set that you're looking for, they are moving the project along, they're giving you the support that you're needing.

00:51:09.565 --> 00:51:11.929
Any feedback is good feedback.

00:51:11.929 --> 00:51:24.632
So consistent communication with us as recruiters is so important and we'll continue to do that as well with our customers to make sure that everyone is happy, the candidates happy, the customers happy, and then I'll be happy.

00:51:24.632 --> 00:51:26.742
You know, pretty simple.

00:51:27.003 --> 00:51:28.586
We just need to have a happy world.

00:51:28.586 --> 00:51:33.284
Communication will make us a happy world, which takes us to our final tip.

00:51:34.125 --> 00:51:46.143
Final tip is periodic review, basically going back to some of the tips that we've provided here on this recording, and it also goes hand in hand with continuous improvement.

00:51:46.143 --> 00:51:54.375
So periodic review, create a schedule behind that in reviewing your entire organization in terms of business process, the applications using and even team members.

00:51:54.375 --> 00:52:06.726
There's a quote around that it says progress is not about grand leaps but the consistent steps forward In the space of continuous improvement.

00:52:06.726 --> 00:52:12.451
For example, every day is an opportunity to be better than yesterday, to be better than yesterday.

00:52:13.940 --> 00:52:22.585
That periodic review is extremely important because once you transition into a new system or transition to anything, you may get settled in, you start to become comfortable with it.

00:52:22.585 --> 00:52:24.106
You just don't set it and forget it.

00:52:24.106 --> 00:52:38.713
You can continuously review what you can do to improve that implementation, whether it's additional staffing needs, whether it's additional operational efficiencies or many other aspects to make your business more streamlined, more cost effective, more efficient.

00:52:38.713 --> 00:52:44.322
In turn will make you more profitable, because I think that's what everybody's looking for when they're trying to do this.

00:52:44.322 --> 00:52:55.405
So that periodic review is one thing that is often overlooked in implementations, because everybody goes through this whole process and they think that they're done, which to me you're never done.

00:52:55.405 --> 00:52:57.291
It doesn't mean you need to do a lot of work, it just needs.

00:52:57.291 --> 00:53:01.369
It's just like a child you know you raise it, you know you have it.

00:53:01.369 --> 00:53:02.110
It grows.

00:53:02.110 --> 00:53:05.081
You need to continually nurture it, have it grow.

00:53:05.081 --> 00:53:08.146
Bad analogy I know it's Friday.

00:53:08.545 --> 00:53:09.106
You started.

00:53:09.106 --> 00:53:10.907
You started off with a good one there.

00:53:10.987 --> 00:53:14.112
I know, and I just lost it this Friday, chris.

00:53:14.112 --> 00:53:17.856
We cannot do Friday recordings, I'm sorry.

00:53:18.737 --> 00:53:19.016
I know.

00:53:19.581 --> 00:53:21.487
Chris was saying some great quotes there.

00:53:21.487 --> 00:53:22.625
I don't know what you're talking about.

00:53:23.440 --> 00:53:25.989
Yeah, but I'm the one that fumbles on Friday.

00:53:25.989 --> 00:53:27.947
To me, every Friday is a fumble Friday.

00:53:27.947 --> 00:53:34.753
So with that, tess, thank you very much for taking the time to do this 30 in 30.

00:53:34.753 --> 00:53:41.954
I'm looking forward to San Antonio where we can have the Rubik's Challenge and possibly watch you do some karaoke.

00:53:41.954 --> 00:53:51.407
I will not participate in the karaoke, I will watch, but the Rubik's I will do, and hopefully by then I'll be able to do it quite a bit faster than I can do it today.

00:53:51.407 --> 00:54:06.521
If anybody would like to reach out to you to talk with you about some of the tips that you had mentioned, or maybe find some talented individuals to assist them with their implementation project, or even post implementation project, how can they get in contact with you?

00:54:07.344 --> 00:54:09.228
Yes, anyone is welcome to reach out.

00:54:09.228 --> 00:54:16.452
You can reach me on LinkedIn or you can reach me at tzmckay at natural frankcom.

00:54:16.452 --> 00:54:24.771
I will definitely be posting this podcast on the LinkedIn when it comes out, so feel free to also drop me a little comment, uh, on there and we can connect up.

00:54:25.860 --> 00:54:26.521
All right, great.

00:54:26.521 --> 00:54:27.224
Thank you very much.

00:54:27.224 --> 00:54:28.829
Uh, have a good weekend.

00:54:28.829 --> 00:54:35.211
Hope you enjoy and you get to rest and recover from the beer Olympics and I look forward to seeing you soon.

00:54:35.211 --> 00:54:35.532
Thank you.

00:54:38.146 --> 00:54:38.527
Take care.

00:54:39.900 --> 00:54:47.048
Thank you, chris, for your time for another episode of in the dynamics corner chair, and thank you to our guests for participating.

00:54:47.320 --> 00:54:48.806
Thank you, brad, for your time.

00:54:48.806 --> 00:54:51.347
It is a wonderful episode of dynamics.

00:54:51.347 --> 00:54:55.769
Corner chair, I would also like to thank our guests for joining us.

00:54:55.769 --> 00:54:58.809
Thank you for all of our listeners tuning in as well.

00:54:58.809 --> 00:55:13.405
You can find Brad at developerlifecom, that is, d-v-l-p-r-l-i-f-e dot com, and you can interact with them via Twitter D-V-L-P-R-L-I-F-E.

00:55:13.405 --> 00:55:26.746
You can also find me at matalinoio, m-a-t-a-l-i-n-oio, and my Twitter handle is matalino16.

00:55:26.746 --> 00:55:30.373
And you can see those links down below in their show notes.

00:55:30.373 --> 00:55:31.740
Again, thank you everyone.

00:55:31.740 --> 00:55:33.282
Thank you and take care.
Tess MacKay Profile Photo

Tess MacKay

Senior Vice President - Microsoft Business Applications

New to Dynamics Corner?

Episode 353: In the Dynamics Corner Chair: The Role of AI: Ethics, Insights, and a Path Forward
Dec. 24, 2024

Episode 353: In the Dynamics Corner Chair: The Role of AI: Ethics, In…

The Role of AI in Business Processes: Ethics, Insights, and a Path Forward 💻+ 🙋 How is AI shaking up business processes, especially in ERP systems like Business Central? In the latest episode of the Dynamics Corner podcast, K...

Listen to the Episode
Episode 348: In the Dynamics Corner Chair: Source Code Management and You in Business Central
Nov. 19, 2024

Episode 348: In the Dynamics Corner Chair: Source Code Management and…

👨‍💻Join hosts Kristoffer Ruyeras and Brad Prendergast in the latest episode of the Dynamics Corner Chair , where they pick Steve Endow 's brain on risk mitigation and source code management in the #BusinessCentral ecosystem. ...

Listen to the Episode