Episode 419: 🧩 Revolutionizing Work through User Experience with Business Central 🧩

WEBVTT

00:00:00.840 --> 00:00:03.931
Welcome everyone to another episode of Dynamics Corner.

00:00:03.931 --> 00:00:06.105
How do you implement Business Central?

00:00:06.105 --> 00:00:07.509
Besides English?

00:00:07.509 --> 00:00:08.803
I'm your co-host.

00:00:08.842 --> 00:00:10.329
Chris, and this is Brad.

00:00:10.329 --> 00:00:14.252
This episode was recorded on April 16th 2025.

00:00:14.252 --> 00:00:19.472
Chris, Chris, Chris, day after tax day here in the United States.

00:00:19.472 --> 00:00:23.310
I hope you filed your taxes Last minute, I hope you filed your taxes?

00:00:23.310 --> 00:00:32.042
How do you implement Business Central in a different language and what considerations do you make for the user experience?

00:00:32.042 --> 00:00:37.860
Those are good questions and with us today we had the opportunity to talk about that with Terry Haryanto.

00:00:37.860 --> 00:00:56.435
Good morning, how are you doing?

00:00:56.435 --> 00:00:58.996
Hello, good morning, hi everybody.

00:00:59.796 --> 00:01:00.158
Hello.

00:01:01.261 --> 00:01:03.003
I always feel odd saying good morning.

00:01:03.103 --> 00:01:03.905
Good day, how about?

00:01:03.926 --> 00:01:04.626
good day.

00:01:04.626 --> 00:01:05.989
When it's evening.

00:01:06.450 --> 00:01:07.591
Greetings, greetings.

00:01:08.474 --> 00:01:08.995
Greetings.

00:01:08.995 --> 00:01:15.293
Everyone who listens to this must hate it when we always say, like you're coming to us from the future, but I'm always impressed.

00:01:15.293 --> 00:01:16.605
I understand time differences.

00:01:16.605 --> 00:01:19.930
But, our time difference is so large.

00:01:20.661 --> 00:01:25.873
It's like the other side of the world, right it literally is the other side of the world, right?

00:01:25.953 --> 00:01:34.370
it literally is the other side, it is it's when I I wish that we would just go to one time zone.

00:01:34.870 --> 00:01:38.981
I wish period or maybe I wish that there is no daylight saving.

00:01:38.981 --> 00:01:41.525
Okay, I will start with that.

00:01:42.387 --> 00:01:43.489
I would be happy with that.

00:01:43.489 --> 00:01:52.412
The daylight savings time is a whole other challenge, and in 2025, I don't understand the purpose of it and deleted.

00:01:52.412 --> 00:01:54.606
Let's solve that first.

00:01:54.606 --> 00:02:05.820
Then we can get on to one time zone, because if it's 6 in the morning, 0600, no matter where you live, you just adapt Exactly.

00:02:05.820 --> 00:02:07.623
So 0600's breakfast, 0600's bedtime, 0600, no matter where you live, you just adapt.

00:02:07.623 --> 00:02:10.948
So 0600's breakfast, 0600's bedtime, 0600's lunch, depends on where you live.

00:02:10.948 --> 00:02:19.127
And then we don't have to question are you available February 25th at 0600.

00:02:20.746 --> 00:02:27.567
I think when we scheduled this call, I thought it was going to be 9th, and then Daylight Saving hits and then, oh, it's 8.

00:02:27.807 --> 00:02:36.370
So yeah, yes, yes, you're required to do math, and just so much work.

00:02:37.259 --> 00:02:44.834
Well, you're required to do more math, because some places do not follow Daylight Savings time.

00:02:44.834 --> 00:02:49.444
Places do not follow daylight savings time.

00:02:49.444 --> 00:03:04.907
So when I do scheduling, when we're around this time of year, when we're talking about months in the future past daylight savings time, I have to double check to see if it's five hours ahead of me or four hours ahead of me, because not all regions honor daylight savings time, which is a whole other reason why we need to get rid of it, exactly, in my opinion.

00:03:05.590 --> 00:03:08.193
So that's where we are.

00:03:09.781 --> 00:03:10.882
I don't think we can.

00:03:10.882 --> 00:03:12.365
Well, we'll save that for another day.

00:03:12.365 --> 00:03:14.769
I'm sure I'll be long gone before they solve that battle.

00:03:14.769 --> 00:03:17.332
I think the world has many more issues besides that.

00:03:17.372 --> 00:03:25.193
We should have longer weekends, brian, I think that's you know certain places in the world they have longer weekends, do?

00:03:25.213 --> 00:03:26.278
they, we need to have longer weekends.

00:03:26.278 --> 00:03:30.810
Yeah Well, I think, the four-day work week would be wonderful.

00:03:30.971 --> 00:03:31.872
Four-day work week.

00:03:32.360 --> 00:03:33.645
They found people are more productive.

00:03:34.145 --> 00:03:35.469
Absolutely, it's proven.

00:03:36.240 --> 00:03:38.187
When you have the ability to rest your mind.

00:03:38.187 --> 00:03:52.341
It's not necessarily saying you're not working, you're going to be lazy, but from knowledge, work point of view, and I'm sure even physical labor, you get to rest.

00:03:52.341 --> 00:03:56.497
And I also noticed when I used to do a lot of hiking, a lot of my creativity would come to me or problems would be solved when I'm hiking the mountain.

00:03:56.497 --> 00:04:00.027
Right, because I wasn't thinking about work, I wasn't staring at it, I was hiking a mountain.

00:04:00.027 --> 00:04:00.871
So, chris, I like that too.

00:04:00.871 --> 00:04:03.507
Let's start a petition for a four-hour week.

00:04:04.028 --> 00:04:05.091
Yes, I'll send it for you.

00:04:05.091 --> 00:04:07.566
Absolutely, absolutely, absolutely.

00:04:08.500 --> 00:04:14.453
Well, thank you for taking the time to speak with us this morning, an hour earlier than we had planned.

00:04:14.453 --> 00:04:16.749
We appreciate you taking your time.

00:04:16.749 --> 00:04:19.749
Before we get into the conversation, would you mind telling a little bit about yourself?

00:04:20.139 --> 00:04:20.783
Oh, sure, sure.

00:04:20.783 --> 00:04:21.887
Well, thank you for having me.

00:04:21.887 --> 00:04:24.062
So my name is Teddy Haryanto.

00:04:24.062 --> 00:04:29.689
I'm working in New Zealand right now working for TITA as a lead consultant.

00:04:29.689 --> 00:04:35.495
So I've been working with well, nav or VC since 2006,.

00:04:35.495 --> 00:04:41.920
So it's almost 20 years.

00:04:41.920 --> 00:04:43.302
I've been well.

00:04:43.302 --> 00:04:47.629
I started as a technical consultant and then I move around right so I've become a functional and become an end user.

00:04:47.629 --> 00:04:59.814
So I do have a background on what around places I've also implemented across the country, such as Indonesia, japan, australia and New Zealand as well.

00:04:59.814 --> 00:05:02.822
I'm passionate about teaching and mentoring.

00:05:02.822 --> 00:05:04.923
I love learning, I love teaching.

00:05:04.923 --> 00:05:12.230
I'm passionate about teaching and mentoring, I love learning, I love teaching and I also love the user experience UX side of VC.

00:05:12.230 --> 00:05:19.956
That's what I'm passionate about basically delivering an ERP solution that people can enjoy.

00:05:19.956 --> 00:05:22.721
So that's pretty much it.

00:05:22.721 --> 00:05:26.591
Oh, I also have a blog called DeadNavGuy where I blog and I share my knowledge.

00:05:26.591 --> 00:05:29.624
So yeah, that's pretty much about me.

00:05:29.624 --> 00:05:32.411
I guess that's great New.

00:05:32.430 --> 00:05:32.771
Zealand.

00:05:32.771 --> 00:05:34.165
How did you end up in New Zealand?

00:05:35.420 --> 00:05:52.607
It's a long story, but to make it short, so I was in Japan, right, working in Japan, and then I was talking with my wife and we, well, japan is a good place, right, if you want to visit, if you want to work.

00:05:52.607 --> 00:05:59.723
However, we don't feel that it's a good place to settle because it's a fast pace.

00:05:59.723 --> 00:06:03.949
You know, everybody's busy, everybody's just working, working.

00:06:03.949 --> 00:06:09.331
So we kind of want to settle down, have a more balanced work-life balance.

00:06:09.331 --> 00:06:10.593
I don't know if there's a balance.

00:06:12.401 --> 00:06:13.884
You don't have the four days, right?

00:06:14.607 --> 00:06:24.113
No, yeah, but praise God that I managed to find a company that actually kind of like respect that.

00:06:24.113 --> 00:06:29.809
So it was okay for me to, you know, let my weekends be weekends, you see.

00:06:29.809 --> 00:06:36.687
So I didn't need to work late hours, I didn't need to work on weekends, but even then there's a lot of pressures, right.

00:06:36.687 --> 00:06:50.329
So we talked about it and then we decided that maybe it's better to find another place where we can have a better work-life balance and, you know, especially when we want to start a family and so on and so on.

00:06:50.329 --> 00:06:57.492
So, um, because my wife um grew up in new zealand, we just thought like maybe new zealand is a good place to live.

00:06:57.492 --> 00:07:00.927
So and here we are no, it's interesting.

00:07:00.947 --> 00:07:05.423
At least you have it, that work-life balance or what you could call that work-life balance.

00:07:05.423 --> 00:07:09.312
I think that's defined differently by many different people.

00:07:09.413 --> 00:07:16.161
And I've seen some say that there isn't a work-life balance or you can't define the work-life balance, it just has to become in your habit.

00:07:16.161 --> 00:07:18.526
But it is important.

00:07:18.526 --> 00:07:29.668
I realized it more as I got older and also from they understand the importance of it, because when I was younger I was eager to work, work, work, work and do all of this.

00:07:29.668 --> 00:07:52.576
But then, as personally, as I got older, I realized the importance of time and then also, just as we started talking about before, the importance of taking a break, because that break is important and working 16 hours doesn't mean you're more productive than someone who's working eight hours or even someone who's working four hours.

00:07:52.576 --> 00:07:58.821
It's what you can accomplish in the amount of time that you're working, versus just working at all that time.

00:07:58.821 --> 00:08:05.834
And then I know we all know when we're sleepy, our thought process is sometimes a little askew.

00:08:06.100 --> 00:08:09.781
There is a lot of variables in that, though, too, because that's a generational thing, you know.

00:08:09.781 --> 00:08:10.805
They just work, work, work.

00:08:10.805 --> 00:08:21.142
And then it could be a cultural thing too, where you work, work, work, and then, as you get older, you're like, yeah, it wasn't that as important, you know, like, yeah, you're hustling right.

00:08:21.142 --> 00:08:28.213
When you're early in your career, you want to maybe not prove to yourself, but prove others that you can.

00:08:28.213 --> 00:08:29.956
Hey, I can work as hard as anybody.

00:08:29.956 --> 00:08:39.474
And then you realize, you know what, I was much more productive if I just took the time for myself and, at the same time, just have different focuses as well.

00:08:39.474 --> 00:08:43.110
So that changes too.

00:08:43.110 --> 00:08:59.832
I know there's a lot of teachings or sessions out there about that work-life balance, but we also have to consider about the cultural background too, because I realized that growing up that you know, in my culture, you just have to work as hard as anybody.

00:08:59.832 --> 00:09:05.975
And then, as I get older, when I have kids, I'm like'm like, yeah, I'd rather spend my time over there, right?

00:09:06.620 --> 00:09:11.230
so yeah, exactly exactly, yeah, no, it is important to balance that.

00:09:11.230 --> 00:09:14.301
So how long have you been in new zealand?

00:09:15.482 --> 00:09:17.706
um, so maybe about seven.

00:09:17.706 --> 00:09:22.640
Now, seven years around that, yeah, six or seven take it a little bit.

00:09:22.681 --> 00:09:24.629
Yeah, was it all that you had thought it would be?

00:09:26.153 --> 00:09:27.679
um, slightly different.

00:09:27.679 --> 00:09:29.886
Here and there I I'm enjoying it.

00:09:29.886 --> 00:09:48.504
Um, like, for example, like in terms of work, right you, you kind of have a feeling like, oh, in new zealand I can dress more, which is true, but it also means, because you work let's say, eight to five you gotta need to make sure that you finish your work on time so you're more productive.

00:09:48.524 --> 00:10:06.931
That means you work more in a short period of time yes, so you're not exactly like relaxing over, so you actually do work more because you're more efficient and the, you know, decision making is quite fast, while if you work longer hours, people tend to stretch it.

00:10:06.931 --> 00:10:10.556
You know, like oh, let's wait until tomorrow, like later, and so on and so on.

00:10:10.556 --> 00:10:14.754
So I think there's a little bit of different in terms of productivity.

00:10:16.383 --> 00:10:17.366
It is, it's the output.

00:10:17.740 --> 00:10:18.686
The output is the important thing.

00:10:19.221 --> 00:10:20.426
That's what people need to measure.

00:10:20.426 --> 00:10:21.745
That's what we were talking.

00:10:21.745 --> 00:10:24.004
It's how do you measure someone's productivity?

00:10:24.004 --> 00:10:25.928
You don't measure it by the amount of time it took them.

00:10:25.928 --> 00:10:32.731
I mean, granted, the amount of time it took them has to be relative to the task, but it's what they produce in the time that they work on it.

00:10:32.731 --> 00:10:36.393
It's almost like that toothpaste, the tooth, the toothpaste.

00:10:36.393 --> 00:10:37.576
You know the toothpaste.

00:10:37.576 --> 00:10:38.821
You can work with toothpaste.

00:10:38.821 --> 00:10:39.822
It's a big toothpaste.

00:10:39.822 --> 00:10:42.886
You squeeze it comes out, you squeeze it comes out, you squeeze, comes out.

00:10:42.886 --> 00:10:54.253
And then, when it gets to that very end of it, it's almost like that very end that you're trying to push out and you're pushing in it lasts longer than like the first 90% of the tube.

00:10:55.360 --> 00:10:58.350
So it's just a matter of what you can do with what you have.

00:10:59.480 --> 00:11:00.523
And you know it's interesting.

00:11:00.523 --> 00:11:02.246
On that too, brad, in the toothpaste.

00:11:02.246 --> 00:11:09.849
You don't need a whole lot when you squeeze that toothpaste I don't know if you're aware of that you just need a small amount and that's good enough.

00:11:09.849 --> 00:11:16.951
That's a misconception when you watch an advertisement of like they have this big old piece of toothpaste on top of the toothbrush.

00:11:16.951 --> 00:11:18.014
That's too much.

00:11:18.014 --> 00:11:20.125
They said it's supposed to be like a quarter of that.

00:11:20.125 --> 00:11:20.729
That's all you need.

00:11:23.201 --> 00:11:25.568
It's not even commercial because it has those you know.

00:11:25.568 --> 00:11:30.509
They want you to consume it, right, they want you to use it.

00:11:30.528 --> 00:11:34.342
You don't need that to go back to moving to new zealand did.

00:11:34.342 --> 00:11:38.917
Did you get an opportunity to take a look at the, the scenery where they filmed?

00:11:38.917 --> 00:11:41.363
Uh, lord of the rings I did.

00:11:41.503 --> 00:11:44.870
I did so I went to like hobby turns and stuff like that, so that was awesome.

00:11:44.870 --> 00:11:50.179
I think that's one of the coolest thing about new zealand is the this, the scenery.

00:11:50.760 --> 00:11:57.947
It's just gorgeous yeah, you're living in the lord of the rings, so you know, I know it's definitely a time check.

00:11:58.788 --> 00:11:59.650
And how about the animals?

00:12:00.835 --> 00:12:03.503
um, the good thing is there's no dangerous animal in here.

00:12:03.543 --> 00:12:16.764
There's no snakes or anything, so I can go hiking and not be worried about anything like bears and stuff maybe new zealand's the next, maybe new zealand's next on my list, because I can't even walk out the door without seeing a snake, so forget that.

00:12:17.025 --> 00:12:19.856
Yeah, it's crazy so there's no worry about like spiders.

00:12:19.856 --> 00:12:22.683
Well, there's spider, but it's not dangerous, like it's not like poisonous or anything.

00:12:22.683 --> 00:12:28.394
Um, so, yeah, it's really safe country, um, it's it's nice to go venture and out, you don't.

00:12:28.394 --> 00:12:34.600
You don't feel like someone's gonna kill you or anything like animals and stuff I mean in terms of like animals are in the hiking.

00:12:34.600 --> 00:12:38.793
So, uh, it's really nice no, that's good.

00:12:38.833 --> 00:12:41.140
That's that's good, but it's not for everybody like.

00:12:41.321 --> 00:12:45.230
so if you, if you enjoy, like nature, new Zealand is really the best place.

00:12:45.230 --> 00:12:47.034
But if you don't I love nature.

00:12:47.034 --> 00:12:49.625
Well, there's not many things to do in here.

00:12:49.625 --> 00:12:50.889
You don't go shopping?

00:12:50.889 --> 00:12:52.726
Well, there is some shopping mall, but you don't.

00:12:54.203 --> 00:12:57.544
You probably get bored pretty soon, and what's the weather like?

00:12:59.864 --> 00:13:00.065
Is it?

00:13:00.105 --> 00:13:01.269
pretty temperate year-round.

00:13:02.321 --> 00:13:03.085
It's quite nice.

00:13:03.085 --> 00:13:05.667
The weather is changing all the time.

00:13:05.667 --> 00:13:10.870
Sometimes it's suddenly raining, Sometimes it's a bit windy, and sometimes it's sunny.

00:13:10.870 --> 00:13:18.307
Right now there's a cyclone going on outside, so it's very windy and rainy, but year-round it's rather temperate.

00:13:18.340 --> 00:13:21.947
You don't have extreme heat or extreme cold, no, it's not that extreme.

00:13:22.860 --> 00:13:26.750
I think I didn't use all my winter clothes fully.

00:13:26.750 --> 00:13:29.990
So it's just wow, just a nice checker, it's fine.

00:13:30.821 --> 00:13:34.187
All these places I have to check out, including the places in the United States.

00:13:34.187 --> 00:13:43.409
Well, one of the things that you had mentioned is you're sensitive to user experience and making sure that somebody has a good experience with ERP.

00:13:43.409 --> 00:13:49.472
In your opinion, what defines a nice user experience?

00:13:50.500 --> 00:13:54.390
Well, it's different from user to users, right?

00:13:54.390 --> 00:14:01.969
I think if you look at the user perspective, what they want to do is just to do their work.

00:14:01.969 --> 00:14:07.303
I would say to finish their work faster so they can go home, for example, if they're allowed to.

00:14:07.303 --> 00:14:16.464
So not having time to think about errors and stuff like that.

00:14:16.464 --> 00:14:18.950
I think that can consider a good user experience.

00:14:18.950 --> 00:14:21.547
When they see the screen, they know exactly what they need to do.

00:14:21.547 --> 00:14:23.966
Oh, I need to do this, I need to do that.

00:14:23.966 --> 00:14:24.808
There's no need to think.

00:14:25.980 --> 00:14:31.466
There's a lot of prevention being put in place to prevent them from making mistakes.

00:14:31.466 --> 00:14:43.899
For example, if error happens and error does happen, the error will tell you exactly hey, this is what you're supposed to do, so I'll guide you through the process.

00:14:43.899 --> 00:14:46.620
So that is part of the user experience.

00:14:46.620 --> 00:14:47.826
There's a lot more.

00:14:47.826 --> 00:14:57.806
So when people talk about user experience, people like to focus on the interface only, which is part of it, but it's more than that.

00:14:57.806 --> 00:15:06.951
It's basically the whole journey when you start opening your browser, I would say putting in business centrals and how they navigate things, and personalizing and so on and so on.

00:15:06.951 --> 00:15:11.432
It's all encapsulated into that and I can call it the user experience.

00:15:12.241 --> 00:15:22.511
Yeah, I like that you call out that the user experience is not just the interface they're interacting, but the full gamut of what they do day to day.

00:15:22.511 --> 00:15:50.133
You're calling out that when they're interacting with the application, that they should know what to expect in terms of results and, of course, how to properly get over any blockers quickly without having to figure out what does it even mean, because that kills the user experience, they get frustrated and so forth, and then they go look at Google stuff and then can create chaos after that.

00:15:51.179 --> 00:16:02.124
Yeah, it stops you from being productive as well, right, so it stops your workflow, and then you spend a lot of time searching, and then it's good if you found a solution, but if not, then you know it's frustrating, right?

00:16:02.124 --> 00:16:04.940
Yes, you know it's frustrating right yes.

00:16:05.961 --> 00:16:08.865
And what are some things from the Business Central point of view?

00:16:08.865 --> 00:16:13.089
You've been working with it quite a period of time and we'll talk about your journey.

00:16:13.089 --> 00:16:19.316
I'm interested to hear a little bit more about your journey as well, as we started to talk about previously when we were planning this call.

00:16:19.316 --> 00:16:33.173
But what are some things that you feel within Business Central help enhance the user experience, whether it's from the user interface point of view or from a coding point of view or a process point of view?

00:16:33.173 --> 00:16:39.432
Some of the things that you found made the journey for a user to be more pleasurable.

00:16:41.140 --> 00:16:45.072
You mean, in terms of standard, what Business Central offers, right.

00:16:45.072 --> 00:16:53.667
So there are certain things that is quite good, like the personalization, right, so you can personalize it, you can change your profile and so on.

00:16:53.667 --> 00:16:58.527
So I think that is pretty good, like having a role center, having a dashboard.

00:16:58.527 --> 00:17:01.048
So I think that's a pretty good user experience.

00:17:01.048 --> 00:17:07.164
It's more modern now and it's because it's browser-based, you can easily copy and paste.

00:17:07.164 --> 00:17:10.663
So I think that's a step improvement from previous Nav.

00:17:10.663 --> 00:17:20.106
And then I think it's more intuitive right now compared to before.

00:17:20.180 --> 00:17:31.230
I think back then, when they released BC, it was a bit clunky and I didn't like it, but after several versions I started to like it.

00:17:31.230 --> 00:17:35.750
I was like I think this is better and I don't want to go back to the Nav version anymore.

00:17:35.750 --> 00:17:39.028
So there are improvements in terms of that.

00:17:39.028 --> 00:17:46.404
I think it's nicer right now, so you have a click and then you have a shortcut and so on and so on.

00:17:46.404 --> 00:17:51.266
So those are the things that probably simple things, but improve.

00:17:51.266 --> 00:17:54.046
I think there's also one thing that they recently added.

00:17:54.046 --> 00:17:58.643
Like they say on the sales line, normally the quantity shift.

00:17:58.643 --> 00:18:01.932
You cannot click on it, so you just, but now you can click and then it pops up.

00:18:01.932 --> 00:18:05.609
So there's a simple, nice like.

00:18:05.609 --> 00:18:07.012
But now you can click and it pops up.

00:18:07.012 --> 00:18:14.527
So there's a simple, nice enhancement, but it makes the experience a little bit better because you can now go through a lot of different places in just a few clicks.

00:18:17.142 --> 00:18:32.631
Yeah, I'm a big fan of the personalization and one of the things that I still see quite a bit is that there's a lot of development on some of those personalizations where I see requests for hide this field, move this field.

00:18:32.631 --> 00:18:33.740
Can you do all of this?

00:18:33.740 --> 00:18:56.292
And I always say there's a difference between customization and personalization, because the personalization will stay with you, whereas the customization becomes, in my opinion, technical debt, because now it's code that's hiding the fields and moving the fields around, which requires some sort of development versus a configuration within the application.

00:18:56.292 --> 00:19:05.094
From what I've seen, personalization is underutilized in that sense, but I'm not certain outside that way.

00:19:05.094 --> 00:19:06.767
Has that been your experience as well?

00:19:07.340 --> 00:19:10.630
Yes, but I do wish there's a bit of more layer into it.

00:19:10.630 --> 00:19:16.689
So, for example, a variant, for example, some companies use variants, some people doesn't.

00:19:16.689 --> 00:19:28.487
Right, if there's only a toggle that says I'm using variant and it pops up on all variant-related pages, because if they use variant, they're probably going to use it on all variant-related pages, because if they use variant they're probably going to use it on all pages, there's no reason they need to personalize it.

00:19:28.487 --> 00:19:30.307
Right, we need to personalize it one by one.

00:19:30.307 --> 00:19:42.020
But if there's a way we can just say, oh, you know, this company is variant, I'm toggling it, maybe using application area or whatever, and then suddenly all variant pops up on every single pages, I would be happy with that.

00:19:42.020 --> 00:19:44.865
So there's another layer on top of that personalization.

00:19:44.865 --> 00:19:49.673
Even like lot, serial, if you use lot, then it shows up lot.

00:19:49.673 --> 00:19:51.355
If you use serial, it shows up serial.

00:19:55.529 --> 00:19:56.513
That would be awesome.

00:19:56.513 --> 00:19:57.799
I would think I do like that.

00:19:57.799 --> 00:19:59.839
That little subtle experience, as you had mentioned, is valuable.

00:19:59.839 --> 00:20:10.114
As you had mentioned, instead of having to go to every page and make the variant visible, you can do a global setting to say I'm using variants, make it visible.

00:20:10.114 --> 00:20:12.598
That would be an interesting modification.

00:20:12.700 --> 00:20:15.388
It's not like oh I want this page to have a variant, but not the other page.

00:20:15.388 --> 00:20:17.587
You will definitely need to have it on both pages.

00:20:17.587 --> 00:20:21.686
I think it makes sense to have it as a global.

00:20:22.630 --> 00:20:23.050
I like it.

00:20:23.050 --> 00:20:26.250
I like those little features like that.

00:20:26.250 --> 00:20:29.208
They should put that almost as a feature within feature management.

00:20:29.208 --> 00:20:31.784
Yeah, they could turn it off and on that.

00:20:31.784 --> 00:20:40.189
The lot numbers are a feature or even, as you'd mentioned, I know serial numbers and lot numbers may be slightly different based upon tracking code of the item.

00:20:40.759 --> 00:20:48.287
But, as you had mentioned, in essence, if you're going to use it, you would use it throughout the system, hopefully.

00:20:48.287 --> 00:20:50.588
Yeah, it's a little difficult.

00:20:50.588 --> 00:20:53.671
I've seen challenges where some didn't track serial numbers, a lot of numbers.

00:20:53.671 --> 00:20:56.594
Throughout the entire process they allowed it to be entered or not entered.

00:20:56.594 --> 00:20:57.795
That's one of those things.

00:20:57.795 --> 00:20:59.856
If you use them, in my opinion, should just be mandatory.

00:21:02.319 --> 00:21:04.028
Yeah exactly.

00:21:04.028 --> 00:21:10.269
And if you use them, for example, right example, if a new user comes in and they don't know about it so they don't put the variant code and it stares out and then it frustrates them.

00:21:10.269 --> 00:21:21.605
But if you show them in the page from the beginning, they probably notice something Rather than oh, I need to personalize first to show the variant.

00:21:21.605 --> 00:21:26.145
I think it's better to just show it there from the very beginning.

00:21:27.642 --> 00:21:29.361
No I like that, do you find it?

00:21:29.361 --> 00:21:30.163
So?

00:21:30.163 --> 00:21:33.371
You've implemented Nav and you've implemented Business Central.

00:21:33.371 --> 00:21:43.070
You know there's some similarities of the UI itself, but one thing that Nav I enjoyed was the buttons, the big buttons, the colorful buttons.

00:21:43.070 --> 00:21:44.782
Business Central not so much.

00:21:44.782 --> 00:21:45.344
Did you?

00:21:45.344 --> 00:21:54.865
Do you find that people um that are new to either nav or business central in your experience um, there's a quicker adoption?

00:21:54.986 --> 00:22:07.795
in business central versus nav, uh, or or even even to a point where someone moving from nav to business central their adoption is it a lot quicker now or it's a little bit more difficult in terms of finding things?

00:22:09.882 --> 00:22:10.605
I think it's.

00:22:10.605 --> 00:22:17.261
There are certain things that Nav is actually better and there are certain things that PC actually I think there's.

00:22:17.261 --> 00:22:31.075
I would think that PC is faster because it's more modern, but maybe for older people they might find that nav is more preferable because it matched with their previous old system, for example.

00:22:31.075 --> 00:22:32.707
So there's not much difference, right.

00:22:32.707 --> 00:22:42.069
But if they're new, they haven't used ERP or they use this quite similar modern ERP, then they probably find it's quite easy to adopt.

00:22:42.069 --> 00:22:46.027
So I guess it's different from person to person.

00:22:46.027 --> 00:22:49.519
Yeah, that makes sense.

00:22:51.073 --> 00:22:58.257
Yeah, and with user adoptions, it's always going to be a challenge to use a new system, right, especially an ERP system.

00:22:58.257 --> 00:23:01.955
So I think our job as a consultant is to make it easier for them.

00:23:01.955 --> 00:23:09.079
I normally told them that you know what new system is going to be a challenge.

00:23:09.079 --> 00:23:14.238
You'll spend like I don't know, a month or two or three to get used to it, uh, but after that it get better.

00:23:14.238 --> 00:23:15.761
That's something that I promise you.

00:23:15.761 --> 00:23:19.739
If you, if you cannot, if it's not getting better, talk to me and then we'll sort things out.

00:23:20.982 --> 00:23:34.782
Um yeah, that's very good and that's one of the things that I see in many implementations is they start to use the system day one and they think and you had mentioned this could be with any new system.

00:23:34.930 --> 00:23:36.897
It's not necessarily just business central.

00:23:36.897 --> 00:23:42.102
The first day they start using it they think it's cumbersome, they think it's slow.

00:23:42.102 --> 00:23:50.417
It takes them a long time because they're still using the system, getting used to it or getting comfortable with it.

00:23:50.417 --> 00:24:16.380
And to me I see so many requests for changes at that point, before they even had a chance to settle in, that sometimes, I'll deny it, I purposely will hold off on some of those because you know that they won't need them or they'll forget about them the enhancements because once they get fluid in the system, in the process of the system, some of those things that they thought were difficult before, because they're now comfortable, are no longer an issue.

00:24:17.009 --> 00:24:23.259
It's not because they accepted it and they accepted the time, it's just they thought it was inefficient at first, but it really is more efficient.

00:24:23.259 --> 00:24:28.236
They just didn't realize they were pausing to remember every single thing they needed to do before doing it.

00:24:28.236 --> 00:24:31.160
So that's where a lot of the time has come into play.

00:24:31.289 --> 00:24:57.721
But that's a very good right, and unlearning things takes time, um, and then yeah oh, yes, I, I remember going from a conversion and somebody was migrating from an old as400 system into, uh, nav, business central, whatever you'd like to call it, and this this one woman that's all she would ever say is oh, in the old system we could do this, in the old system we could do this.

00:24:57.721 --> 00:24:59.031
Oh, in the old system it was this.

00:24:59.031 --> 00:25:07.659
And in reality it was a system that somebody had built for them internally, so there weren't a lot of business rules.

00:25:07.659 --> 00:25:17.205
But she was making that claim periodically, over and over and over again, and basically just saying she wanted to go back, she wanted to go back, she wanted to go back.

00:25:17.247 --> 00:25:21.842
I think anybody who's worked with an implementation has experienced someone in an organization that was like that.

00:25:21.842 --> 00:25:33.342
Then, fast forward a period of time and they were making an acquisition and they had to use the other company's system to help, you know, through the transition.

00:25:33.342 --> 00:25:41.898
And it was funny that same woman that was complaining about moving to Business Central was now saying well, in Business Central we can do this.

00:25:41.959 --> 00:25:42.760
I can't do this.

00:25:42.760 --> 00:25:43.321
I can't do this.

00:25:43.321 --> 00:25:45.157
She did.

00:25:45.157 --> 00:25:46.854
She became the biggest advocate.

00:25:47.054 --> 00:26:05.681
after she started using it and seeing the benefits of the interface and the experience with it that I just sat back and I laughed because she was one of the more challenging users to bring forward, but then also, now that she was using it, was the biggest advocate for it.

00:26:06.211 --> 00:26:08.318
So they can someone in those situations.

00:26:08.318 --> 00:26:09.162
Those are superpowers, man.

00:26:10.530 --> 00:26:12.656
Just be an advocate for whatever she was using.

00:26:12.656 --> 00:26:13.859
That's a good superpower.

00:26:14.240 --> 00:26:14.521
Yeah.

00:26:14.521 --> 00:26:20.403
So I'm curious how do you handle users like that?

00:26:20.403 --> 00:26:33.371
Right, like you can clearly know what Business Central can do for you and it works and there's a lot of opportunities for growth, of opportunities for growth.

00:26:33.371 --> 00:26:38.061
But when you're dealing with end users like that, or users of Business Central it doesn't have to be an end user how do you overcome that?

00:26:38.061 --> 00:26:40.554
Like, how do you get them over that hump?

00:26:40.554 --> 00:26:42.679
Yeah, how do you get over the hump?

00:26:42.679 --> 00:26:50.906
I mean like for you know, like you know, everyone may understand the process, you know, and they're learning along the way.

00:26:50.906 --> 00:27:06.422
It's a little bit difficult, but then you have that one person that can, you know, create chaos with everybody that understands it and they just cannot grasp.

00:27:06.422 --> 00:27:09.578
Do you just continue to move forward?

00:27:09.578 --> 00:27:12.259
Or is that when you start personalizing?

00:27:12.259 --> 00:27:15.356
Personalizing, um, you know the role.

00:27:15.356 --> 00:27:17.582
How do you go about that one teddy?

00:27:19.026 --> 00:27:21.771
um, I think it's uh, it's case by case, right?

00:27:21.771 --> 00:27:39.796
So, um, and and I think with any implementation, like you, you cannot make everybody happy, unfortunately um, so you, you try your best to explain things and then you try to reason like, oh, this is what it is, and then you try to help.

00:27:39.796 --> 00:27:42.759
Right, let me personalize it for you, or let me hear.

00:27:42.759 --> 00:27:57.611
So I think one of the first steps that you do is basically to hear their side of the story, because I've been an end user as well, I've been frustrated with my system as well, so I know how they feel, or more or less.

00:27:57.611 --> 00:28:03.178
So, talk to them first and then see, or maybe they actually have a good point, right?

00:28:03.178 --> 00:28:04.575
Oh, this is how you do it before.

00:28:04.816 --> 00:28:12.630
Oh, okay, so then maybe let's try to do it this way first for a few couple of days, and then, if you think that it's still not, let's try to do it this way first for a few couple of days, and then, if you think that it's still not, let's talk again.

00:28:12.630 --> 00:28:18.942
And there will be a time when there's nothing else you can do, right?

00:28:18.942 --> 00:28:26.897
So that's that's when you start talking with, like, like the, the other project managers, for example, to see if there's any way you can actually do it.

00:28:26.897 --> 00:28:38.980
So you, you, you bring other people in and then you try to solve, you know on how to tackle this issue, and then sometimes maybe you just need to keep moving forward, unfortunately.

00:28:39.630 --> 00:28:54.063
But I think initially I would try to persuade that person and then try to explain, and then sometimes we do go to the customization part if it does make sense.

00:28:54.063 --> 00:29:03.817
Right, if that person say that, oh, this is this and this is the reason why I'm doing this, and then they say, okay, that does make sense, let me bring that first, let me talk to that for our team.

00:29:03.817 --> 00:29:09.221
We have a team and then we discuss it, and then it turns out that that person does make a good point.

00:29:09.221 --> 00:29:12.559
So let's go to the customization part.

00:29:12.559 --> 00:29:22.920
But that's probably towards the end, because ideally you don't want to do customization, but there are times when you do and you need to acknowledge that that person is right.

00:29:24.611 --> 00:29:30.962
Yeah, I think that's a great call out because I think that people should have that conversation.

00:29:30.962 --> 00:29:42.278
Whether it's a tough one from you're dealing with a user that is very adamant and you know you hit a good point about just listening to them and understanding.

00:29:42.278 --> 00:29:45.505
Okay, what is the reason why you're apprehensive?

00:29:45.505 --> 00:29:58.435
And a lot of times in my experience where they're so used to the old system, they're not realizing that it was also customized to do a specific process and so from their experience they think like why can't Business Central do this?

00:29:58.435 --> 00:29:59.595
It did it over here.

00:29:59.595 --> 00:30:09.256
Then once you unravel and you realize actually it was automated for you and that's why it seems to do it that way and so it is okay to do that.

00:30:09.509 --> 00:30:18.369
It's okay to have the conversation Whether we invest in that automation right at the get-go or could we do that after.

00:30:18.369 --> 00:30:22.501
Because a lot of times they also have to understand how to do things manually.

00:30:22.501 --> 00:30:24.296
Again, this is my experience.

00:30:24.296 --> 00:30:27.861
They have to learn how to do things manually if the automation doesn't work.

00:30:27.861 --> 00:30:37.883
There's been countless times where the automation or the job queue stopped working and then nobody knows how to create the sales order because sales orders just come in.

00:30:38.611 --> 00:30:43.601
It just does it, you know, does it for me, and then it stops working and they're like I don't know how to create a sales order.

00:30:43.601 --> 00:30:51.142
So it's really important for you know users to it's not only you can still automate things, but also understand if it doesn't work.

00:30:51.142 --> 00:30:59.436
You should learn how to fly a plane right If autopilot doesn't work.

00:30:59.477 --> 00:31:01.869
You should still at least be able to land the plane Exactly.

00:31:01.869 --> 00:31:07.194
I'm hopeful that the pilot knows how to land a plane.

00:31:07.194 --> 00:31:19.788
The communication is important because, as you had mentioned, someone may have a system that may not have as stringent rules or they may not understand something as part of the process.

00:31:19.788 --> 00:31:41.565
But I also have found sometimes they need to make sure that they understand what they're doing and why, because one if you talk with them and they feel like you understand them and you listen to them, that helps give them some reassurance, but also sometimes saying you have to enter this field here because it impacts the picking process in the distribution center, for example.

00:31:41.565 --> 00:31:48.082
So if they have an understanding of the importance of what they're doing or why they're doing it, sometimes it's also a little less challenging.

00:31:48.142 --> 00:32:14.022
I have found, yeah, yeah, On top of the points that you had both made about listening to what they're looking for and, chris, your point is it's understanding the process, how to do the process, but also it's just to put on top of that why they're doing the process sometimes can bring that user adoption level up a little bit higher, because now they realize they may be helping someone else, because I have been through implementations where they want to make a small change on the sales order.

00:32:14.022 --> 00:32:28.163
But that change they make on the sales order created several different steps for somebody else in the cycle or the life cycle of the order or the fulfillment of the order, and it made one person's job easier but it made a whole warehouse a little bit less efficient.

00:32:28.163 --> 00:32:35.953
So those are some things to keep in mind as they go through that so it's a lot.

00:32:36.536 --> 00:32:39.882
It's a lot, I think, to do the implementations is.

00:32:39.882 --> 00:32:49.753
It can sometimes be challenging and you had mentioned you were a customer before a user, before a system, before you made the transition over to doing consulting.

00:32:49.753 --> 00:32:55.064
How do you feel that has helped you in your consulting career?

00:32:56.512 --> 00:32:57.416
It helps me a lot.

00:32:57.416 --> 00:33:02.376
So I started as a technical consultant right Fresh out of uni.

00:33:02.376 --> 00:33:05.278
I went into partners.

00:33:05.278 --> 00:33:13.730
I had no knowledge about business process, right, so they just handed me a pdf manual.

00:33:13.730 --> 00:33:16.775
It's like learn this about nav, like 4.0.

00:33:16.775 --> 00:33:28.281
So that's the official manual, um, and then I, as much as I tried to learn from that, I didn't know much about I.

00:33:29.042 --> 00:33:35.896
I think back then, when I, when I designed, when I um developed something, it's always feels that this is the best way.

00:33:35.896 --> 00:33:38.001
This is the one that I came up is the best way.

00:33:38.001 --> 00:33:38.509
You use it.

00:33:38.509 --> 00:34:03.903
So, and then, yeah, that was a bit arrogant from my part, um, but when I switched to use the site, I start to understand how they feel, how they think, how sometimes they don't like their partner, but, yeah, so you, you get to, you get to see their business process, their thought process, like this is what I do and I think, at the end of the day, they just want to do their work efficiently and as much as possible.

00:34:03.903 --> 00:34:07.438
So that shifts my perspective.

00:34:07.438 --> 00:34:12.981
So now, whenever I implement something, I start to think, oh, how are they going to use this?

00:34:12.981 --> 00:34:14.163
Are they going to?

00:34:14.163 --> 00:34:15.233
So that's why it's in.

00:34:15.375 --> 00:34:26.681
On information, I think it's a good idea for your consultant I mean mostly a dev to actually get to know the user, if possible, so you know visiting them.

00:34:26.681 --> 00:34:31.253
And then even, like, when you're designing a warehouse solution, you need to know how their warehouse works right.

00:34:31.253 --> 00:34:39.840
You need to know, like, whether they do this, whether there's a lot of like bins or whether they're wearing gloves, for example, and then how do they?

00:34:39.840 --> 00:34:46.804
Are they a super user or are they just user who just want to click a button, and so on and so on.

00:34:46.804 --> 00:34:50.260
So that changed my perspective.

00:34:50.260 --> 00:34:57.954
And then now, whenever I got a task for example, so, teddy, can you make this?

00:34:57.954 --> 00:35:01.800
I'll start asking questions like oh, why do you need to do this?

00:35:01.800 --> 00:35:04.137
Like, what happens if I don't do this?

00:35:04.137 --> 00:35:06.438
What happens if we don't do customization?

00:35:06.438 --> 00:35:08.250
It's like, why are we going this path?

00:35:08.250 --> 00:35:19.842
So I keep asking questions to get to know why we need to discuss, why we need a solution, and it puts me in a better way on when I design it.

00:35:19.842 --> 00:35:21.576
It fits them better.

00:35:21.576 --> 00:35:22.358
That's how I feel.

00:35:23.610 --> 00:35:32.512
And then I start also asking feedback because I think, as an end user, you just want to.

00:35:32.512 --> 00:35:44.396
I mean, partner comes, asks you what's your requirement, and then they leave and then they just give you during the UAT, for example, without asking you anything, right, and this is the solution that we designed.

00:35:44.396 --> 00:35:47.655
And then the end user will look at it and it's like that's not what we asked.

00:35:47.655 --> 00:36:03.077
So giving a feedback, like asking for confirmations throughout the implementation, I think, is also a good way of doing it, because I think, as an end user, that means that you will feel that you're being listened and your opinion is valuable.

00:36:04.860 --> 00:36:10.858
And then sometimes, when doing the requirement gatherings, you miss something.

00:36:10.858 --> 00:36:13.222
As an end user, you say, oh, I need this, I need this.

00:36:13.222 --> 00:36:18.538
But then throughout the implementation, you realize that, oh, there's actually something more that I haven't actually talked to you.

00:36:18.538 --> 00:36:22.981
So it's always good to actually go back to the customers.

00:36:22.981 --> 00:36:25.594
It's just clarifying so, do we have building this?

00:36:25.594 --> 00:36:34.335
This is what you want, and so on, so you don't go too far ahead, and yeah, that is a good point on the perspective and from listening to what to say, is something.

00:36:34.376 --> 00:36:37.818
Chris, it's what we've been saying now for I can't tell you how long.

00:36:37.818 --> 00:36:42.262
The most important part of implementations now is the relationship.

00:36:42.262 --> 00:36:44.644
It's the relationship that you build with the customer.

00:36:44.644 --> 00:36:52.992
It's not we're going to tell you how to manage the system, tell you how to do the system.

00:36:52.992 --> 00:36:54.275
In this space I always mention it's called partner for a reason.

00:36:54.275 --> 00:36:56.121
You're partnering with someone to help them with the implementation.

00:36:56.121 --> 00:36:59.695
You're not doing it for them, You're not owning it.

00:36:59.695 --> 00:37:04.293
They have to own it, and part of that is through the communication and the conversation.

00:37:04.333 --> 00:37:23.978
So, whether if you're a partner or a customer, you should be engaged through the design process, through the UAT process with each other so that there's an understanding of why we're doing things, how we're doing things and working together to make sure it's what's right for the individuals using it within an organization.

00:37:23.978 --> 00:37:33.757
So them feeling like they're also participating in the implementation also gives them some ownership in it and they want it to be successful.

00:37:33.757 --> 00:37:34.572
They want it to work.

00:37:34.572 --> 00:37:43.050
Versus if someone like you said you go through, send me your requirements, Okay, this is how we're doing it, we're setting it up this way, Then they're more likely to be well.

00:37:43.070 --> 00:37:44.353
I don't like the way this works.

00:37:44.353 --> 00:37:56.701
It doesn't work properly, they give you a little bit more resistance on it and also, when you're a partner, you're helping someone implement it, so from the user's perspective, they're the ones that have to use it every day.

00:37:56.701 --> 00:38:05.516
Exactly when we set up a system as a partner for someone, we're doing it one or two times, training them, show them how to use it, but it's not the day in and day out.

00:38:05.516 --> 00:38:24.340
So that feedback loop is extremely important during those processes and I know one of the challenges that I have seen and I'm just curious your thoughts on the amount of time that someone has to use and test the application.

00:38:24.340 --> 00:38:34.996
I see a lot of implementations where I feel that there's not a lot of testing time because they have their regular job to do.

00:38:35.056 --> 00:38:43.896
I guess you could say and not all organizations can afford to hire new people to do temporary jobs for a period of time and they may be able to offset it.

00:38:43.896 --> 00:38:51.704
But what are your thoughts or approaches on how to have an effective UAT or testing plan or process?

00:38:52.630 --> 00:38:56.400
Well, we definitely need more tests, right?

00:38:56.400 --> 00:38:58.737
I think testing is always good to make sure.

00:38:58.737 --> 00:39:07.262
And then they need to test it, not the developer, not the consultant, because the consultant can only test as much as they know, right?

00:39:07.262 --> 00:39:09.277
But the one who's going to use it is the user.

00:39:09.277 --> 00:39:19.358
So it's always good to ask them to perform the test, so you can assign what you call it like a super user or a champion to test it.

00:39:21.731 --> 00:39:26.362
And then, yeah, I mean, they do really need to invest on it.

00:39:26.362 --> 00:39:28.255
There's no going out of it.

00:39:28.255 --> 00:39:31.304
It's not like, I mean, if they don't test it, they'll pay it later on.

00:39:31.304 --> 00:39:41.137
So I think that's something that we need to make sure that we need a dedicated team from your side to test, like, if you don't test it, you'll pay.

00:39:41.137 --> 00:39:51.974
I mean, we try our best to make sure that the solution works, you know, as intended, and there will be no issue, and so on, but there will always be a gap.

00:39:51.974 --> 00:40:04.304
And then it's always better for your site to test it, because if you don't test it after we implement it, then you'll have a lot of issue.

00:40:04.304 --> 00:40:15.434
And then, because you have a lot of issue, you have a bad user experience and that frustrates users, and because you have more frustration, it will lead to more resistance.

00:40:15.715 --> 00:40:23.353
So invest early, I would say that is an interesting thing, brad, you're calling it out of.

00:40:23.353 --> 00:40:26.742
They have their day-to-day job and then they're expected to test.

00:40:26.742 --> 00:40:42.085
One thing that I don't see often is adding that as part of the budget towards your project, you have to budget the time of people have to take away to spend time on the project for UAT because it is an investment.

00:40:42.085 --> 00:41:04.382
So if you invest on user adoption, that means you're going to get your quicker ROI on Business Central because now your people will be, you know, quickly utilizing it as best as possible right away, versus not spending time of UAT and a lot of times you have to step away from that and then allow them to spend time of testing.

00:41:04.382 --> 00:41:06.552
So people that is one thing I'm not.

00:41:06.552 --> 00:41:07.472
I don't see often.

00:41:07.472 --> 00:41:17.306
You know when you're budgeting for project, not only budgeting for the implementation and the application costs but they don't ever budget the time internal time.

00:41:17.851 --> 00:41:18.817
That's a great point.

00:41:18.817 --> 00:41:21.278
That is a great point.

00:41:21.278 --> 00:41:41.838
It's because estimates often go with what would it take from the partner point of view to help with the implementation Exactly, even if someone doesn't know the number, to see a line item on that to say your internal testing, just so that they have in their mind that they need to allocate for that internal testing.

00:41:41.838 --> 00:41:43.101
I like that idea.

00:41:43.349 --> 00:41:44.556
I have not seen that.

00:41:44.556 --> 00:41:46.617
I've had the conversations, chris, but you're right.

00:41:46.617 --> 00:41:58.342
I think putting something like that on that proposal, just so that they're aware of it and they know that they also have to participate in this, may be helpful as well yeah, and you see that.

00:41:58.443 --> 00:42:12.278
You see that on a statement of work, maybe you know 40 hours of uat, but that's 40 hours of maybe me sitting down with them, of testing, or or 40 hours just my side, but it doesn.

00:42:12.278 --> 00:42:24.719
But it doesn't calculate on their side as well that they also have to do that 40 hours right, it's not just me, they're paying, but it's 40 hours is taking quote-unquote productivity of people getting their job done.

00:42:24.719 --> 00:42:27.599
They tend to forget that as well.

00:42:27.599 --> 00:42:40.965
So if you look at it from an analytical perspective, if you're really into those numbers, I think it's important for end users or clients of Business Central to maybe consider that.

00:42:40.965 --> 00:42:48.784
So then you can see the true cost of your Business Central implementation, not just partner.

00:42:50.251 --> 00:42:54.222
And that testing I'm not talking we could talk about if it's relevant.

00:42:54.222 --> 00:42:58.599
It's not automated testing or any programmatic testing.

00:42:58.599 --> 00:43:00.083
This is the user acceptance test.

00:43:00.083 --> 00:43:04.541
That's when they go through the process, but that's also a training experience.

00:43:04.541 --> 00:43:11.855
So, chris, to your point, the 40 hours and that's the point I was trying to make when I was talking about it's on the cost that they'll get from a partner or an estimate.

00:43:11.855 --> 00:43:19.534
It's the partner's time, but I would say, even if the partner is 40 hours, the customer should be spending more than 40 hours.

00:43:19.615 --> 00:43:20.760
Absolutely, absolutely.

00:43:20.800 --> 00:43:26.420
Maybe not one person, but collectively across the different departments or the different groups, depending upon the size of the organization.

00:43:26.420 --> 00:43:34.304
I would say it's much more than that, because what Teddy's proud of is the user experience.

00:43:34.304 --> 00:43:38.159
Getting them in to test and use it makes them more comfortable with it as well.

00:43:38.159 --> 00:43:47.005
So day one when they go to use it, they can get some productivity back as well, because now they have a sense of what they're doing and they don't have to wait for someone to show them how to do it.

00:43:47.005 --> 00:43:55.724
So to keep up with the shipping, to keep up with the collections, to keep up with the orders having that time up front also saves you time during the implementation.

00:43:55.724 --> 00:43:58.458
These are a lot of things that I think go hidden.

00:43:59.230 --> 00:44:05.195
And a lot of times people say Chris gave me an estimate it's going to be a week of UAT.

00:44:05.195 --> 00:44:10.556
I'm done, yeah, with no ownership.

00:44:10.556 --> 00:44:15.157
And Teddy, you brought up a big point and I like the word you use resistance.

00:44:15.157 --> 00:44:31.036
Even if it's not intentional, they will automatically start to resist because they're running into challenges, they're out of their comfort zone, so they're going to want to resist going to something new because they're going to want to withdraw and go back to what they're comfortable with and they start not liking the system.

00:44:31.269 --> 00:44:35.619
So they start giving excuses like oh, that's because they start finding fault on the system, right?

00:44:35.619 --> 00:44:40.139
So it triggers a chain of reaction of resisting the system.

00:44:41.369 --> 00:45:02.634
Yeah, and you made a point too, teddy, about creating the feedback loop, because people tend to forget that when the user experience doesn't end once you go live, right, your partner goes away and maybe they're there to support from time to time, but it's a consistent, you know, improvement in getting the feedback Is it still working?

00:45:02.634 --> 00:45:03.498
Is it still working?

00:45:03.498 --> 00:45:10.103
And then sometimes partner will give you like, oh, we'll be around for 30 days to make sure there's no support needed.

00:45:10.103 --> 00:45:12.737
But it shouldn't be that.

00:45:12.737 --> 00:45:17.436
In that case, it should be a long-term partnership, as Brad noted earlier.

00:45:17.436 --> 00:45:20.869
That's why we don't use the word VAR anymore, right, because it's value-added reseller.

00:45:21.371 --> 00:45:44.809
We're just not a reseller, we're a partner, so it needs to be a long-term plan and one of the things that an end user or a business can do is, you know, have a consistent, maybe monthly, follow up or feedback, or maybe work with your partner to do additional training as a, you know, just to validate the process is still working.

00:45:44.809 --> 00:45:51.561
It may work at that time, but then in the next 30 days or next I don't know six months, there could be changes.

00:45:51.561 --> 00:45:57.500
That requires you to make adjustments as well, and you know, I see that too often.

00:45:57.500 --> 00:45:58.481
They just kind of move on.

00:45:59.271 --> 00:46:07.300
And then the user experience they get frustrated and what happens and I've used this term before is rogue processes, where someone gets frustrated.

00:46:07.300 --> 00:46:31.876
They Google stuff and then they read a document somewhere and they're like I'm going to do this here too, and then it doesn't fit their business, right, they start populating records where they shouldn't, and now, now you have technical debt, right, but to your point, yeah, you have to do this as a full gamut of, you know, user experience, not just from that moment on and that's it.

00:46:32.679 --> 00:46:35.755
Yeah, that's a good point, yeah.

00:46:37.393 --> 00:46:48.740
Teddy, what are the biggest resistance, the most common resistance you get in terms of the user interface or user experience when they're getting on there.

00:46:48.740 --> 00:46:50.929
Is it typically the navigation component?

00:46:50.929 --> 00:46:54.715
What are the most common ones that you've encountered?

00:46:56.269 --> 00:46:59.996
Well, like Brad says, normally people compare with the old system.

00:46:59.996 --> 00:47:03.655
You know, like, oh, in my old system I can do this, in my old system I can do this.

00:47:03.655 --> 00:47:06.318
So it's always like that, the biggest part of it.

00:47:06.318 --> 00:47:13.755
And also there are some parts where they don't understand why they need to fill in certain things, right, well, and also there are some parts where they don't understand why they need to fill in certain things.

00:47:13.755 --> 00:47:14.610
Right, I've never filled in posting group before.

00:47:14.610 --> 00:47:15.954
Why do I need to fill in the posting group now?

00:47:15.954 --> 00:47:17.219
And so on and so on.

00:47:18.952 --> 00:47:29.699
And then sometimes even like with personalizations, right, if I don't need it, why don't you just hide it from me from the very beginning, for example, even though we teach them that you can actually personalize.

00:47:29.699 --> 00:47:33.637
So those are some of the resistance.

00:47:33.637 --> 00:47:45.452
And then sometimes, because the nature of the way is the central work, maybe like for auditing, so you need to do a certain way, you actually have more steps compared to the previous system, right?

00:47:45.452 --> 00:47:50.956
Oh, in the previous system we can just edit, for example, our lecture entry.

00:47:50.956 --> 00:47:52.592
No, no, no, no, no, no, no, no.

00:47:52.592 --> 00:47:55.612
Yeah, so there's a reason behind it.

00:47:55.652 --> 00:48:00.231
So trying to, I mean trying to make them understand, I think that's sometimes.

00:48:00.231 --> 00:48:09.329
This is quite a challenge, um, and then sometimes, yeah, you kind of need to say this is the way the system works, this is, there's a reason behind it, it's for auditing purpose and so on.

00:48:09.329 --> 00:48:10.311
You're not supposed to edit.

00:48:10.311 --> 00:48:13.739
If you make a change, you need to do a credit and then you need to do invoice and so on and so on.

00:48:13.739 --> 00:48:19.079
So I think that's that's probably the yeah, quite common resistance.

00:48:19.099 --> 00:48:19.498
Yeah, that's.

00:48:19.498 --> 00:48:20.300
That's funny.

00:48:20.300 --> 00:48:24.001
You're calling out like being able to edit, like that's common too.

00:48:24.001 --> 00:48:26.369
Coming from another erp system to business central.

00:48:26.369 --> 00:48:28.413
We're like why do I have to create an order in an invoice?

00:48:28.413 --> 00:48:30.275
Can I just create an invoice, you know?

00:48:30.315 --> 00:48:31.016
what if I just credit.

00:48:31.056 --> 00:48:32.298
Can I just reverse an invoice?

00:48:32.298 --> 00:48:47.177
No, you got to create maybe a sales return order, right, and then I'll create a credit memo, like there's still all of those things that you do have to take the time to educate and slow down, right, um, and not just so quickly, you know.

00:48:47.177 --> 00:48:52.525
Uh, uh, be brash about it and then, like they get frustrated, exactly.

00:48:53.547 --> 00:48:56.358
Yeah, I think of everything you're saying.

00:48:56.358 --> 00:48:57.496
I just it's.

00:48:57.496 --> 00:49:02.998
It's when you start to get older, you start to reminisce a lot, and I think this week I don't know, maybe I hit a point.

00:49:03.369 --> 00:49:05.639
I'm starting to reminisce about a lot of things.

00:49:05.639 --> 00:49:16.838
Chris is involved in some of the chats I'm in about reminiscing about things from before, but I was just thinking of so many implementations that I have gone through and some of the conversations I've had and going through it.

00:49:16.838 --> 00:49:20.590
Then I started thinking I spent my life doing ERP software.

00:49:20.590 --> 00:49:28.639
You wouldn't even think that people would go through that whole process of implementing ERP software systems as well.

00:49:28.639 --> 00:49:32.699
So it's, it's's safe.

00:49:32.699 --> 00:49:35.588
Now I'm gonna you know, there's a I had a conversation.

00:49:35.608 --> 00:49:51.440
We just came back from a conference so I had a conversation, somebody about, um, you know, making erp or have an erp class at universities, oh have you guys heard about that.

00:49:52.661 --> 00:50:01.987
There's been a push, or at least an idea out there, that they should make it as a curriculum at universities of how to utilize ERP.00:50:01.987 --> 00:50:14.532


It doesn't have to be business central, it could be just whatever ERP, because nobody realizes that a lot of business requires ERP, not just a finance software, and so I thought that's pretty interesting.00:50:14.532 --> 00:50:24.702


A great idea for future talent you know, utilizing Business Central or some form of ERP is to have an ERP curriculum.00:50:24.702 --> 00:50:26.375


You guys heard about that.00:50:27.130 --> 00:50:28.394


I haven't heard anything about that.00:50:28.394 --> 00:50:31.847


I'm trying to think I haven't heard anything about that.00:50:31.847 --> 00:50:32.250


I'm trying to think.00:50:32.250 --> 00:50:46.625


I understand understanding core financials if you're a finance major or even a business major, but I agree now that, thinking as part of a business major, would they also cover inventory and proper processing?00:50:46.625 --> 00:50:50.829


I think some of the other majors maybe as an elective would be beneficial.00:50:50.829 --> 00:50:52.637


I could see it in the curriculum of the majors.00:50:52.637 --> 00:50:54.045


Maybe as an elective would be beneficial.00:50:54.045 --> 00:50:55.090


I could see it in the curriculum.00:50:55.090 --> 00:51:06.494


But to be honest with you, I think the whole educational system will change soon because now we have tools online to help us learn things, versus the studies which give us the discipline of showing up, I guess you could say in learning things.00:51:06.494 --> 00:51:08.940


But that is interesting.00:51:08.940 --> 00:51:23.679


I would like to see that in some business classes to make sure you have the full suite of how to properly operate a business utilizing the software yeah yeah, I think that's an interesting because it's everywhere, right, erp is everywhere.00:51:23.778 --> 00:51:27.474


I mean, if you go, if you go work somewhere, they're using some kind of erp software.00:51:27.474 --> 00:51:40.481


So, um, getting to know that, uh, in in in a school in uni, that would be a great, you know, um, it helps you get into that company as well, because you already have the basic knowledge.00:51:40.481 --> 00:51:44.097


Right, because when I, when I, when I joined as a partner, I have zero.00:51:44.097 --> 00:51:46.822


So it's like what is customer ledger?00:51:47.692 --> 00:51:51.057


well, even even as a career, right, like you know.00:51:51.057 --> 00:51:54.603


You know getting into the for me, I just stumbled upon it.00:51:54.603 --> 00:52:02.559


You know it's like oh, this is actually awesome, this is fun, and you build a career and you build a good livelihood.00:52:03.990 --> 00:52:16.777


And for many that don't realize that until later in life, but if this was an opportunity for them, for them to understand, like even just learning how to implement erp, you can build a career out of that.00:52:16.777 --> 00:52:18.141


You know why?00:52:18.141 --> 00:52:21.431


Why isn't that not part of you know an option?00:52:21.431 --> 00:52:25.239


Uh, in in schools, I think it would be amazing.00:52:25.239 --> 00:52:32.543


Then, when we're looking for talent, it's like, oh yeah, we can, we can focus on people that took ERP curriculums and classes.00:52:33.992 --> 00:52:34.876


I think that would be great.00:52:34.876 --> 00:52:49.221


It's something targeting a functional consultant, for them to understand business processes in the sense of the applications that you use, versus the theory of it, similar to the reskill program where they go through how to use Business Central.00:52:49.221 --> 00:52:52.336


I agree with you, teddy, some of the terms now to me are like standard terms.00:52:52.998 --> 00:52:53.981


And some people don't know.00:52:53.981 --> 00:52:56.177


Like, try to explain to somebody what a posting group is.00:52:56.177 --> 00:52:57.755


You mentioned posting groups earlier.00:52:57.755 --> 00:53:00.610


I'd love to hear everybody's definition of a posting group.00:53:00.610 --> 00:53:16.079


I would ask either one of you, just to not put you on the spot, but maybe one of the future guests, chris will have to put on the spot to see if they were listening and they rehearsed, because what is a posting group?00:53:16.099 --> 00:53:17.402


but but you know, I'm saying like it's, it's.00:53:17.402 --> 00:53:21.213


I think it's important to educate earlier, because now they have ai um curriculums in school, like why not erp?00:53:21.213 --> 00:53:27.010


I don't know, I, I don't know man, like it's, uh, I think it'd be amazing if we could get that.00:53:27.010 --> 00:53:30.592


Then we could be to teddy brad, you could be to Teddy Brad, you could be professors.00:53:30.592 --> 00:53:37.637


Man, that could be a shift for a career for some of us.00:53:38.639 --> 00:53:47.864


I would take a position in a university teaching ERP software, absolutely, but just the processes behind ERP software.00:53:47.864 --> 00:54:07.271


We can pick different applications to show how they do it differently and understanding the concepts of PICS consolidations that would be amazing good retirement plan right if they make it available once I retire?00:54:07.311 --> 00:54:08.619


maybe I just want to become a professor.00:54:09.983 --> 00:54:24.219


Chris, I think you should start a university, ku Chris University ah, there you go, you can start start doing an 8 weekweek course or something and then eventually you can break it up into having semesters.00:54:24.219 --> 00:54:39.590


I'm sure there'd be plenty of individuals that would help teach the basic core concepts and again, it's just the core concepts of running ERP software and going through an implementation.00:54:43.840 --> 00:54:44.601


Let's see all these interesting things.00:54:44.601 --> 00:54:47.630


Whoever's listening to this is probably gonna go ahead and, like I'm gonna, that's my next move.00:54:47.630 --> 00:54:49.282


I'm out of here.00:54:49.382 --> 00:54:59.226


I'm just gonna teach yeah, training or teaching whatever you'd like to use, is becoming more and more popular.00:54:59.387 --> 00:55:09.764


I we do have tools online, such as Copilot a lot of individuals share Teddy will talk about your blog in a few moments as well share a lot of information.00:55:09.764 --> 00:55:17.431


But, chris, you mentioned the conference that we just came back from and I know you and I discussed one of the things I left from the conference, which was amazing.00:55:17.431 --> 00:55:26.090


The conference was amazing I left with seeing where there is a need for we have all these features.00:55:26.090 --> 00:55:32.632


We have all this documentation that tells us what it is, what it does, but I don't see a lot of how do I apply it?00:55:32.632 --> 00:55:37.213


All right, so we have these features and functionality where it's now.00:55:37.213 --> 00:56:04.204


We have a group of individuals implementing ERP, whether it's on the customer side or the partner side or even somewhere else, I guess, if that even exists, let's just think how do we implement, how do we apply, how do we have our critical thinking so that, to go through, to solve somebody's problem, how do we know which feature, which function to use, how do we know which feature, which function to use?00:56:04.204 --> 00:56:06.150


And I'll say it I sat in one of Jen Claridge's sessions.00:56:06.170 --> 00:56:08.076


I gave her a plug again for this.00:56:08.076 --> 00:56:19.320


Don't tell her I don't want to tell her that I enjoyed it, but she did the projects versus production orders, which is great, because she started off saying, okay, projects were added, well, renamed or whatever, and this is what it does.00:56:19.320 --> 00:56:21.224


Production orders, this is what it does.00:56:21.224 --> 00:56:29.492


But she actually took that and made an exercise in her session of okay, this is what the customer's requirement is, which would you use?00:56:29.492 --> 00:56:31.182


And then she went into the why.00:56:31.925 --> 00:56:40.572


So it fostered the thought of we have all these features and functionality within the ERP software, but how do we know when to apply what?00:56:40.572 --> 00:56:44.949


And to me, that's where I'm starting to realize there is a big gap.00:56:44.949 --> 00:56:59.650


I guess you may say in sort of the implementation process or the training process is the critical thinking piece of okay, these are the scenarios of when you may want to do that, and then you could have some similarities and extract from there.00:56:59.650 --> 00:57:07.911


Or just shows you that sometimes you have to take a step back and think is this the best process or is the other process the better process?00:57:10.320 --> 00:57:10.501


Yeah.00:57:10.501 --> 00:57:13.780


And so I guess that leads to my question for you, teddy.00:57:13.780 --> 00:57:19.413


You know, being in New Zealand, do you normally work around?00:57:19.413 --> 00:57:23.471


I think you had mentioned you have clients in Japan, indonesia and so forth.00:57:23.471 --> 00:57:34.992


Is there any knowledge requirement in terms of like localizations and and country specific when you're implementing Business Central?00:57:36.221 --> 00:57:36.583


Are there any?00:57:36.603 --> 00:57:37.206


challenges there.00:57:38.539 --> 00:57:45.429


Oh, yes, absolutely Like when I first came to Japan, I obviously had to know about the Japanese requirement.00:57:45.429 --> 00:57:51.505


So that's when I need to rely on my colleague to explain to me.00:57:51.505 --> 00:57:55.407


You know, how do they do things, is there any specific requirements?00:57:55.407 --> 00:57:58.250


So that's something that you just kind of need to learn.00:57:58.250 --> 00:58:05.248


And obviously, um, with this kind of limitations, you, you can be upfront to your client as well.00:58:05.248 --> 00:58:11.449


Um, I think that's always my um approach is like you, you bring honesty and integrity into your implementations.00:58:11.449 --> 00:58:21.251


So let's say, oh, I want to implement a us, for example, I'll tell them I don't know much about us, but I'll try it, I'll try to gather some knowledge and, um, I need your help as well to get that right.00:58:21.251 --> 00:58:31.052


So, like in the financial side as well, I can try as much as I can from my side, but I also need your cooperation in order for us to implement this successfully.00:58:32.063 --> 00:58:52.746


So, yes, there are certain things, like in Indonesia or in Japan, that requires you to learn, and especially like in Japan, for example, they do have their own language right, so they use kanji, for example, and BC, I think last time I checked, didn't have support for that language.00:58:52.746 --> 00:58:57.027


So normally, partners implement their own language for Japanese.00:58:57.027 --> 00:59:10.889


So if you're supporting a customer that has a different partner, you'll see that there's a different term that's being used, like for sales order they use this one, but for the other partner they use that one.00:59:10.889 --> 00:59:14.222


Sometimes it feels like hmm, and sometimes they just use English.00:59:14.222 --> 00:59:19.431


So they use katakana to represent the English characters.00:59:19.431 --> 00:59:21.353


So sometimes some partners actually use that.00:59:21.353 --> 00:59:23.847


So this is to support them.00:59:24.059 --> 00:59:27.471


It's easier to read yeah, see, it's older.00:59:30.666 --> 00:59:32.490


So, those are a challenge as well right.00:59:33.702 --> 00:59:41.731


So when you actually take over other partners' work, for example, and then you look at it, it's like, oh, they, they used two different terms.00:59:41.731 --> 00:59:44.376


That's just a language issue, right.00:59:44.376 --> 00:59:46.202


Oh, they use a different term for it.00:59:46.202 --> 00:59:48.106


So I need to make sure that they they are.00:59:48.106 --> 00:59:48.648


This is that.00:59:48.648 --> 00:59:51.103


That's not the terms that we use in in this partner.00:59:52.067 --> 01:00:17.389


Yeah, you know I'm always curious about that because you know it sounds like you're working with a lot of businesses within those surrounding countries and for me, you know, most of my clients if not all of my clients have worked with is just always been using, you know, english and so you know I've never been involved in an implementation where it's, you know it's an entirely different language, you know.01:00:17.389 --> 01:00:27.641


So I'm always curious from your perspective, like the difficulty in the translation and you have to work with a partner that translates the language you know.01:00:27.641 --> 01:00:33.012


In Indonesia, for example, do they use English or do they have language extension?01:00:33.012 --> 01:00:33.893


Oh, they use English, okay.01:00:34.440 --> 01:00:36.027


But they do have language extensions.01:00:37.961 --> 01:00:39.507


I don't know that they have an Indonesian language.01:00:39.507 --> 01:00:45.827


I haven't implemented in Indonesia for a while, so maybe they have, maybe they they, maybe they just rely on partners.01:00:45.827 --> 01:00:52.168


But I'm pretty sure because most Indonesians are quite comfortable using English as like, as a system right.01:00:52.168 --> 01:01:02.527


So they they are quite comfortable using English system, so we normally can keep it as it is and they quite quick to learn, while in Japan it's very different.01:01:02.527 --> 01:01:09.385


They are used to Japanese systems and they even have their own Japanese ERPs, like Kanjou Bugyou.01:01:09.385 --> 01:01:25.327


So in order for them to really utilize the system properly, they actually need to have a Japanese language installed and that's why most partners are actually offering a Japanese extension language.01:01:26.409 --> 01:01:35.070


But then when you do a custom solution, you need to start thinking how do I translate this?01:01:35.070 --> 01:01:47.387


So you start digging like, let's say, if you build a new table and then you refer to sales order number, you need to find out that sales order which terms that we used to talk about sales order.01:01:47.387 --> 01:01:48.875


I was like, oh, two month order.01:01:48.875 --> 01:01:51.585


That means I need to put the two month order as part of my translation.01:01:51.585 --> 01:02:00.951


So you got to need to go all around the places to make sure that you have a consistent terms when you're building a solution Right, because otherwise if your terms is different?01:02:01.010 --> 01:02:02.112


it's not yeah.01:02:02.460 --> 01:02:05.085


You know I feel blessed that.01:02:05.085 --> 01:02:17.494


You know we just deal with difficult end users sometimes and we speak English, right, and I can't imagine having to deal with a difficult user and a different language at the same time.01:02:17.494 --> 01:02:21.606


And then there's cultural differences as well and how they do business.01:02:21.606 --> 01:02:23.731


That that's fascinating.01:02:23.731 --> 01:02:26.103


I'd love to sit in one of those implementation one day.01:02:26.103 --> 01:02:35.168


I'm like just to just to feel humble, yeah, yeah, like hey, man, we're lucky that we're dealing with some of these uh implementation.01:02:35.168 --> 01:02:36.351


I'll take that in a day.01:02:36.351 --> 01:02:45.346


Um, again, we're isolated, like at least for me, isolated is just doing English-speaking implementation and it's just like how do they do it?01:02:45.346 --> 01:02:48.610


How do they take Business Central on all the different languages?01:02:48.610 --> 01:02:50.568


How does that translate in business?01:02:50.568 --> 01:02:52.085


That's fascinating to me.01:02:52.085 --> 01:02:53.088


It is.01:02:53.168 --> 01:03:02.934


It is and it has its own challenge Even implementing it, especially if you don't speak the language right.01:03:02.934 --> 01:03:11.807


So then you start having a problem of here and there, and I think when I first came to Japan I had zero knowledge of Japanese, so well, maybe a little bit like ordering food.01:03:11.807 --> 01:03:15.789


So I tend to ask someone else to translate it for me.01:03:15.789 --> 01:03:18.956


Once I'm finished, I ask a functional consultant or a deaf who actually can speak Japanese to translate it for me.01:03:18.956 --> 01:03:22.385


Once I'm finished, I ask a functional consultant or a deaf who actually can speak Japanese to translate it for me.01:03:22.385 --> 01:03:27.306


So I'm copying and pasting it without realizing what's the whole meaning about it.01:03:27.306 --> 01:03:32.672


I just hope that I copy and paste the right thing and it's true.01:03:33.679 --> 01:03:44.170


Translations are tough, because sometimes context is important, because the same word can be translated a few different ways to English and from English.01:03:45.994 --> 01:03:46.434


Exactly.01:03:48.306 --> 01:03:49.313


It's something to take in.01:03:49.740 --> 01:03:55.914


And sometimes the word doesn't show up properly because you know like we have a double byte characters and so on.01:03:55.914 --> 01:04:01.253


So sometimes, even though you type everything, sometimes when you compile it and show it on the pages, it doesn't show up.01:04:01.253 --> 01:04:08.688


So you kind of need to check the whole things and make sure that everything and every word actually shows up properly.01:04:10.061 --> 01:04:18.628


Yeah, that's true, and it kind of leads me to my next question about the market in New Zealand or even in that Asia area.01:04:18.628 --> 01:04:29.980


You know, microsoft recently announced that they have 45,000 business central customers, or more than 45,000 business central customers, but they don't actually break it down right.01:04:29.980 --> 01:04:42.146


So from your perspective, I mean, is there a lot of clients using business central in New Zealand or maybe within the Asia area?01:04:45.822 --> 01:04:46.827


I think there's quite a lot.01:04:46.827 --> 01:04:49.248


I'm pretty sure it keeps on increasing.01:04:49.248 --> 01:04:52.289


We've got more and more customers.01:04:52.289 --> 01:05:00.793


So I think it's a trend now that we have more and more business central customers and we have more partners right?01:05:00.793 --> 01:05:07.920


So obviously it's not, probably it's not as big as US or Europe, but we do have an increase of people.01:05:08.019 --> 01:05:09.807


Okay, so there is an opportunity.01:05:09.807 --> 01:05:21.097


You know, I know that there is a huge user base in terms of even GP, for example, like Dynamics GP, in terms of even GP, for example, like Dynamics GP.01:05:21.097 --> 01:05:28.987


So you know, I had an opportunity a year ago to build a community or Dynamics community out in the Philippines, for example.01:05:28.987 --> 01:05:45.320


And in Philippines, you know, being part of the Asia area, you know they use a lot of Dynamics products and they, you know, I see the trend of using Business Central as an ERP as well.01:05:45.320 --> 01:05:55.635


So I was just curious, countries outside of that, it sounds like from your answer, there is definitely growth, a steady growth, of utilizing Business Central.01:05:55.635 --> 01:06:04.981


So my dreams of moving to the philippines may still be, you know, possible, do it?01:06:05.682 --> 01:06:07.269


do it while you can do it.01:06:07.269 --> 01:06:12.387


When I mean by can is while you're physically able, because exactly and then build a university there.01:06:12.889 --> 01:06:14.393


You can build the philippines.01:06:14.414 --> 01:06:16.099


You can build ku in the philippines.01:06:16.300 --> 01:06:44.518


But we talk with many individuals and maybe it seems a little more dramatic to us in the United States, because the United States is large and we have states and some individuals will move from one state to another fairly regularly, but when you start talking with individuals such as yourselves and we meet other individuals that we've spoken with both on the podcast and in person at events they pick up and move to a totally different country.01:06:44.518 --> 01:06:49.916


It just sounds like a different experience and I think I think it's something to do.01:06:49.916 --> 01:06:53.974


Chris, I think you should move to the philippines and we'd be on a bigger time difference.01:06:53.994 --> 01:07:07.905


But that's okay, we could figure out it's like 18 hour, I think, difference it's almost the same, as I think it's the same as new zealand's, like they're ahead yeah, yeah you'd be in the future, the things like that.01:07:07.945 --> 01:07:28.213


I think everyone should have the experience of moving to a different place to see a different culture, or at least immerse themselves into a different culture for a period of time, because I think it's interesting to see how other people live, in a sense of what they they do from their day to day.01:07:28.213 --> 01:07:32.077


As you had mentioned, a different culture you started we started the conversation with.01:07:32.077 --> 01:07:40.382


In japan, they may be a little more busy, work a little bit more, whereas new zealand, to say they may not be as busy doesn't mean they're not as productive.01:07:40.382 --> 01:07:45.826


I'm always careful to say that, because just because you're not as busy all the time doesn't mean you're not productive.01:07:45.826 --> 01:07:48.076


So I think it's nice to see.01:07:48.076 --> 01:07:55.641


And then also the different weather, and then, chris, I'd have some place to go visit yeah, yeah, it's a it is a tropical island.01:07:55.661 --> 01:07:58.485


There's like 7 000 islands, and then you can choose whatever you want.01:07:58.485 --> 01:08:03.751


So, yeah, okay, and that's how you can.01:08:03.771 --> 01:08:12.541


You can yeah yeah, sorry I mean, especially if you, if you pick a country where you don't speak the language, that's even more awesome, because now you start to need to learn the language.01:08:12.882 --> 01:08:13.963


Yeah, and the?01:08:13.963 --> 01:08:18.591


I think the language shapes the way you think as well.01:08:18.591 --> 01:08:43.563


I think I've found a lot of foreigners, for example, like US, when they go to Japan, they start speaking more slowly and try to let other people to understand as well, so they try to articulate it better, for example, instead of just speaking fast, because for the Japanese people, it's hard for them to catch up if you're speaking too fast.01:08:43.563 --> 01:08:51.161


So the way you speak also started to change, so your English language started to change as well, the way you speak, and so on.01:08:51.161 --> 01:09:00.305


So it helps you better, I feel, in terms of articulating and communicating, because you want to make sure that the other party actually understands you.01:09:00.305 --> 01:09:18.908


And then the way their language also works differently, like a Japanese language, for example, there's a lot of times where they actually don't have the subject, because the subject is considered like it's a common knowledge for you to know.01:09:18.908 --> 01:09:20.271


It's an action or something like that.01:09:20.220 --> 01:09:21.197


No, so it's more towards like it's a common knowledge.01:09:21.197 --> 01:09:21.591


You know it's an action or something like that.01:09:21.612 --> 01:09:23.520


No, so it's more towards like we don't.01:09:23.520 --> 01:09:40.386


It's more like passive, like the work is done or information will be doing so, because it is understand between the world party that who's going to do it, so there's no need to actually use the subject, so most of the time it's used as a passive.01:09:40.386 --> 01:09:56.905


Like this works needs to be done by this, so the so you, you kind of need to learn how to like captures the intention, like yeah yeah, it's really hard.01:09:56.966 --> 01:10:00.475


And then I think, when I first um, learn it, I think so.01:10:00.475 --> 01:10:06.466


I had a discussion with a colleague of mine and then we start talking about all this, this, this, this, this, and then by the end it's like, oh, we agree.01:10:06.466 --> 01:10:10.706


And then at the end of the conversation I was like, so who's going to do it, you or me?01:10:10.706 --> 01:10:12.527


Yeah, it's implied, right?01:10:12.527 --> 01:10:14.085


So there are implications.01:10:14.125 --> 01:10:21.600


It's implied Like they.01:10:21.619 --> 01:10:24.922


They don't have to tell you, it doesn't have to be part of the language communication.01:10:24.922 --> 01:10:26.123


It is implied that you're going to do it.01:10:26.123 --> 01:10:27.104


So you start to read people's.01:10:27.104 --> 01:10:33.088


You gain that ability to kind of read people, because when you study Japanese that's how they do.01:10:33.088 --> 01:10:37.091


So I think it's a good learning opportunity.01:10:37.091 --> 01:10:50.569


When you move to a country that you don't know the language, you don't have to be good to go extreme, like to go to China or to go to Japan where they don't use the same characters.01:10:50.569 --> 01:10:54.431


But yeah, I mean it's a very good learning experience.01:10:54.431 --> 01:10:59.146


If you start to learn the cultures and the way the language works, then you can start understanding them better.01:11:05.819 --> 01:11:31.860


Yeah, I think that's important, important, I think a lot of times, everyone has a viewpoint of what something may be like until they go through it and live it and experience it, and it may change your perspective if I could plug something really quick, brad, I I think it's very important to have your team to be as different backgrounds I know Brad and I have worked with different individuals with different backgrounds, but it does help in terms of communicating because we, you know, we've worked with.01:11:31.860 --> 01:11:45.668


We work with people that are from Japan and have no clue, but we, you know, we happen to work with somebody that can speak the language and so that a little bit of you know the ability to speak different languages.01:11:45.668 --> 01:11:54.016


It's like chef's kiss, because then you know you have a better way to communicate, especially when you're trying to help a business implement Business Central.01:11:54.016 --> 01:11:55.623


So I just want to put that out really quick.01:11:55.623 --> 01:11:56.225


So thanks, brad.01:11:58.069 --> 01:11:58.612


No, thank you.01:11:58.612 --> 01:12:02.948


I think it is important and that you'd get different perspectives with the different backgrounds.01:12:02.948 --> 01:12:06.627


So it helps you have a better implementation or a better experience.01:12:06.627 --> 01:12:10.121


A few months ago, when we talked, you mentioned about your blog.01:12:10.121 --> 01:12:12.367


What types of information do you share in your blog?01:12:13.529 --> 01:12:19.167


I share everything about Nav and Business Central, basically functional side, technical side.01:12:19.167 --> 01:12:24.595


I guess it started because I want to share the knowledge.01:12:24.595 --> 01:12:29.658


It's also because I also want to remember how to do certain things.01:12:29.658 --> 01:12:36.810


So I put it there as well for me so I can always go back to it and read it and then do it.01:12:36.810 --> 01:12:44.431


But yeah, so I think in the beginning I just want to share.01:12:44.431 --> 01:12:53.502


So that's why I started my blog, so I started sharing things like small things like oh, this is how you do this, this is how you do this.01:12:53.502 --> 01:12:58.527


And then it's kind of grow from there and then right now I'm just sharing tips.01:12:58.527 --> 01:13:03.185


So every Friday I try to share tips like this is how you do certain things in Business Central.01:13:03.185 --> 01:13:04.670


This is how you do this, this is how you do this.01:13:04.670 --> 01:13:10.551


Now sometimes people will say, oh, that's a common knowledge.01:13:10.551 --> 01:13:17.207


But I believe that common knowledge is not that quite common, and then, especially for new users, right.01:13:17.729 --> 01:13:31.430


You hit it right, you hit that nail right on the head and that's what I say, and that's one of the things, even when we talk about session planning at conferences and such common knowledge to who, because somebody is always at a different point in their journey.01:13:31.430 --> 01:13:40.069


Some organizations, some individuals that may be working with partners are just at the very beginning of their journey of business central.01:13:40.069 --> 01:13:41.791


So how to enter a customer?01:13:42.452 --> 01:13:50.347


or what is a posting group is new to them, whereas someone who's been working with it for some time they already understand it and they know it.01:13:50.347 --> 01:13:58.907


And that goes with perspective, and sometimes you have to take a step back and say the perspective of I know this, but somebody else may be new.01:13:58.907 --> 01:14:04.012


And as to your point, it's not so common because somebody's starting out their journey.01:14:04.052 --> 01:14:17.185


We all have to learn somewhere, exactly or at some point you're not just born with the knowledge of what a customer posting group is, what a vendor posting group is, what an inventory posting group is we're going to keep going uh-huh.01:14:17.185 --> 01:14:22.189


What a general business processing group is, what a general product I can't even speak right now.01:14:22.189 --> 01:14:23.336


General product posting group.01:14:23.336 --> 01:14:24.180


Do you know other posting groups?01:14:24.180 --> 01:14:30.842


There's all these different types of posting groups bank account yeah and it also helps me as well, right.01:14:31.023 --> 01:14:37.104


So because when I, when I write, that means I need to think, because you you cannot explain what you don't understand.01:14:37.104 --> 01:14:41.592


So by writing it down, you you start to think, oh, how do I explain it?01:14:41.592 --> 01:14:45.985


And it helps me also in the future when I try to explain it to someone, because I already know how to explain it.01:14:45.985 --> 01:14:47.882


So it does help.01:14:47.882 --> 01:14:52.472


When you started helping people, you actually help yourself to be better.01:14:55.243 --> 01:15:07.863


So that's why I actually do blogging as well and sharing the knowledge we do appreciate that, sharing that knowledge, because there are times where you, you research, you know, look, look it up on the internet and then your, your blog shows up.01:15:07.863 --> 01:15:10.371


You know, I just had somebody a couple of weeks ago.01:15:10.371 --> 01:15:12.646


It's like, oh, I was stuck in this and I found your blog.01:15:12.646 --> 01:15:13.951


I appreciate that.01:15:13.951 --> 01:15:16.847


Or even for me, like I, I forgot about something.01:15:16.927 --> 01:15:25.280


I looked it up and it's like, oh, yeah, I wrote that, that's I was just about to say that that's what happened to me is I was searching for something one time and I found something I had.01:15:25.280 --> 01:15:28.788


I said, I wrote that yeah so it's, uh, it's helpful.01:15:28.788 --> 01:15:37.483


Well, teddy, thank you for taking the time to speak with us oh, I think this morning yeah this evening, this afternoon, depending upon where the three of us are located.01:15:38.505 --> 01:15:39.546


We do appreciate your time.01:15:39.546 --> 01:15:42.810


I always say and I mean it time is the currency of life.01:15:42.810 --> 01:15:43.733


Once you spend it, you can't go back.01:15:43.733 --> 01:15:53.945


So anytime anyone spends with us, we greatly appreciate, because it's a part of your life, that you could be doing something else, but you're sharing it with us and sharing it with the members of the community or anyone that listens with this.01:15:53.945 --> 01:16:03.528


If anyone would like to get in contact with you to learn a little bit more about you or some of the things that you do, or talk about business, central implementations, what's the best way for them to get in contact?01:16:04.060 --> 01:16:05.346


They can reach me through LinkedIn.01:16:05.346 --> 01:16:07.587


I think that's the best way because I normally look at LinkedIn.01:16:07.587 --> 01:16:08.904


I can respond better.01:16:08.904 --> 01:16:11.591


Yeah, so LinkedIn is one way.01:16:12.380 --> 01:16:16.666


And we'll have a link with how to reach you on LinkedIn with the episode.01:16:16.666 --> 01:16:20.530


And we again, we thank you for your time and we look forward to speaking with you again soon.01:16:20.530 --> 01:16:22.033


All right, thank you, all right.01:16:22.253 --> 01:16:22.434


Ciao, ciao.01:16:22.434 --> 01:16:23.015


Thank you for having me.01:16:23.015 --> 01:16:24.256


Bye, thank you, bye.01:16:26.822 --> 01:16:33.887


Thank you, chris, for your time for another episode of In the Dynamics Corner Chair, and thank you to our guests for participating.01:16:34.220 --> 01:16:35.726


Thank you, brad, for your time.01:16:35.726 --> 01:16:39.230


It is a wonderful episode of Dynamics Corner Chair.01:16:39.230 --> 01:16:42.695


I would also like to thank our guests for joining us.01:16:42.695 --> 01:16:45.725


Thank you for all of our listeners tuning in as well.01:16:45.725 --> 01:17:00.251


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.01:17:00.251 --> 01:17:13.612


You can also find me at matalinoio, m-a-t-a-l-i-n-o dot I-O, and my Twitter handle is matalino16.01:17:13.612 --> 01:17:17.307


And you can see those links down below in the show notes.01:17:17.307 --> 01:17:18.671


Again, thank you everyone.01:17:18.671 --> 01:17:20.225


Thank you and take care.