This is a very informative video...I am seeing that many companies are implementing new systems such as ERP, communications platforms, CRM, ect. Many should watch this video.
Our business analyst team spends a considerable amount of time and effort working with our clients to define/diagram/document the current state, the future state, and completes a configuration workbook which is supposed to spell out how we will install and configure the software in order to achieve future state. These deliverables are handed off to the client and to the installation and configuration engineers. In theory this sounds pretty good, but not so much I’m practice. The clients are providing info and answering questions without having any practical feel for the software. To me, it feels like we are asking the client to decide on designing every nut and bolt of a formula 1 race car by just talking to them about how their formula 1 race car could work. In most cases the clients probably saw a demo of the software but the demo may have been 3 months prior and the demo system is a demo system - sanitized and unrealistic. I’d love to hear your ideas on how to overcome these challenges.
Thank you very much for the highly informative video (webinar in its original). Complimentary to the case studies, overviews and reviews, I appreciate the insights you have provided and do provide on the subject of technical and organisational change programs and implementations (and many more). As someone being involved in change programs for more than a decade now, you can never underestimate enough the human factor as either a promoter or a resistance to change.
doing a program, using the book IT Architecture for Dummies. Some standardization of enterprise platform which they advocate, have parallels to the talk here
You have to start right at the bottom, first work in support projects, testing projects , then gradually move to implementation projects , self learning, earning certifications through out this journey. And then move to consulting.
Thanks Erik for your time, very informative. I have a silly question, when we implement ERP in our two different branches, how are they going to be connected with each other? do we need to go through routers or internet alone is sufficient? i am sorry if i sound stupid here.
it depends. The best case is the software handle easily branches and you have consolidated information on the fly (both branches on same server) or maybe some older software will have their own server and then have a consolidation process. But at the end "internet" would be your answer.
![Top 10 Manufacturing Execution Systems [Best Manufacturing Software]](http://i.ytimg.com/vi/Gdgz94vjH50/mqdefault.jpg)
![Top 10 Manufacturing Execution Systems [Best Manufacturing Software]](/img/tr.png)
![How Do ERP Systems Work? [The Mechanics of ERP Software]](http://i.ytimg.com/vi/zI2eCVrUTvU/mqdefault.jpg)
The useful stuff starts at 22:29. Before that it's just background info.
Okay, how is it that a video this good doesn't have a SINGLE comment?
Thank you for being the first on this video!
@@erickimberling Always up to Cheer for the good work!
This is a very informative video...I am seeing that many companies are implementing new systems such as ERP, communications platforms, CRM, ect. Many should watch this video.
Thank you RJ!
This is an excellent video… I’ve unfortunately seen some of these failures in action!
Our business analyst team spends a considerable amount of time and effort working with our clients to define/diagram/document the current state, the future state, and completes a configuration workbook which is supposed to spell out how we will install and configure the software in order to achieve future state. These deliverables are handed off to the client and to the installation and configuration engineers. In theory this sounds pretty good, but not so much I’m practice. The clients are providing info and answering questions without having any practical feel for the software. To me, it feels like we are asking the client to decide on designing every nut and bolt of a formula 1 race car by just talking to them about how their formula 1 race car could work. In most cases the clients probably saw a demo of the software but the demo may have been 3 months prior and the demo system is a demo system - sanitized and unrealistic. I’d love to hear your ideas on how to overcome these challenges.
Thank you very much for the highly informative video (webinar in its original). Complimentary to the case studies, overviews and reviews, I appreciate the insights you have provided and do provide on the subject of technical and organisational change programs and implementations (and many more). As someone being involved in change programs for more than a decade now, you can never underestimate enough the human factor as either a promoter or a resistance to change.
Thank you Mike - I’m glad you enjoyed the video!
Lessons start at 23:00
Great content as always! Thanks a lot
doing a program, using the book IT Architecture for Dummies. Some standardization of enterprise platform which they advocate, have parallels to the talk here
Great content!
Thanks A LOT!
can you give advice on how to to formulate survey questions to identify pockets of resistance in advance?
wheres the sheet with the 20 steps
You mentioned that you don’t hire juniors and train them. What’s the best way to start in this industry as a consultant if you have no experience?
You have to start right at the bottom, first work in support projects, testing projects , then gradually move to implementation projects , self learning, earning certifications through out this journey. And then move to consulting.
Thanks Erik for your time, very informative. I have a silly question, when we implement ERP in our two different branches, how are they going to be connected with each other? do we need to go through routers or internet alone is sufficient? i am sorry if i sound stupid here.
it depends. The best case is the software handle easily branches and you have consolidated information on the fly (both branches on same server) or maybe some older software will have their own server and then have a consolidation process. But at the end "internet" would be your answer.
all the reasons that u have listed are very generic like " failures can be avoided" " be realistic" etc, disappointed by ur presentation