Hi, everyone. Welcome back to lesson 10. In our final lesson, we are going to look at some ideas on setting yourself and your team up for success. I'm Jennifer Nicholson. defining success for an IT project seems to be inherently more difficult than defining successful financial expectations or manufacturing objectives. Yet without an articulated set of post go live expectations, the success of your IP RP implementation becomes a matter of opinion.

And in the worst case, a matter of a lot of opinions in an organization that is lazy and adopts a default metric of how many people are complaining about the new earpiece system, you're most certainly going to be considered to have been a failure. It is essential for the focus of the implementation team for the health of the organization, and for appropriate allocation of resources that a set of measurable criteria you put in place prior to go live which is the final arbiter of eruption. Success. The litmus test of a successful definition is one that no matter what else additional happens, or a said, you will feel that the implementation was well done. For example, a simple success statement could be, we converted over to the new new earpiece system. But if you couldn't ship anything for two days without success, how about converted to the new earpiece system with no significant business disruption?

That's better? How about converted to the new earpiece system with no significant business disruption and no negative impact on customers? That's even more specific. It's also perfectly acceptable if success criteria are time phased and represent a sequential Lee higher bar over time. If you read a thought about each of these success steps, you're probably feeling a combination of intimidation and disbelief, intimidation because this stuff is hard work. And almost none of it is something for which many people have natural skill or previous training.

It's In this final lesson, let's review a few key takeaways from this course as you embark on your journey. First, if you take nothing else from this course, believe that these success steps are real unnecessary. underestimating the difficulty of an MRP implementation is a big mistake. Find people who've been down a road like ear pee before, and whose opinions you trust IT professionals, consulting partners, software vendors, other project managers and ask them if the items on this list are critical for your project success. Number two, stay intimidated every single day of your implementation project. Don't be paralyzed with fear.

Just remain respectful of the multitude of ways in which your project can derail and use that respect to motivate the effort to make sure it doesn't. Third, learn early on you can trust without reservation to help you with these steps and lean on these people heavily. By now you recognize that these success steps are much more of a philosophical anchor Then test items that can be crossed off a to do list. Fourth, you need to make sure everyone can see you were staying involved in the change management data cleansing and business process change efforts. The paradox you face is that even though you have no training or previous experience, really no qualifications at all, people expect that you will have a successful implementation. The only logical way out of this paradox is for you to assimilate as quickly as possible with the cumulative knowledge of the many who have also done what you're doing.

And by doing so, begin building your qualifications. Because we European mentation is difficult does not mean it can't be both fun and create an enormous sense of satisfaction. Thank you for your time and interest in this topic. My name is Jennifer Nicholson. Please feel free to reach out to me if you have further questions on this topic.