Majority of mid range ERP implementations fail due to the scope creep. I am not putting up a argument that only mid-range ERP's fail due to the scope creep. There is a thick line between the mid-range and the tier I applications. Let me put out my views on the 4 major questions:
1) Who plays a major role in setting the right expections?
The whole process starts from the customer inquiry. Inquiry can be in any form like Tenders, RFP, IT providers sales team, presales, telemarketing etc., Once the customer engages himself with the team and start the discussions on product functionality, cost, time and the support process, the presales expertise plays a major role in bridging the gap between the sales team and the customer. The Presales consultants role becomes vital in setting up the right expections. Moreover, the sales team inclusive the presales should give the right commitments. One of the research says "Truth plays a vital role in ERP implementation success". Yes, this is pretty much true and the most critical success factor for a project success
In continuation with the above subject - I would strongly recommend, the presales team to get the Functional consultant's on board during the important discussions and mapping the business process and setting up the right expectation. Before we could engage the customer and sign up our legal contracts / agreements, the POC needs to be done and identify the potential risks which may cause damage to the project during the execution phase. POC and mapping plays a major role in your win.
2) How will you arrive at your SoW during the presales level?
Million $ question, the reason behind, the presales & the sales team would be under termendous pressure in closing the sales cycle. This is where, the stakeholders loyalty and the commitments comes in to picture. Agreed, that the pre award SoW can't be a elobrated SoW. However, during the kick off meetings and handing over from sales to projects team, the functional / presales team should be (mandate) involved and set the customer expectation right and define the SoW. This will really help the projects team to work within the boundary and arrive at the SoW.
3) How the handing over takes place from Presales to the Project execution team
The process of project kick off - both internal and external plays a major role. As discussed in my earlier question, the presales / functional team should be made available in the process of handing over and define the clear cut SoW and the boundaries set. The pre-award SoW needs to be attached in your legal / agremments and should be signed off by all the stake holders. Involving the projects team in all levels would be a ideal suggestion. Again, if your processes are clear and agreed by all the stake holders, project won't give you any surprises during the execution.
4) What makes the customer unhappy? Your bills on the change requests? Or your strict processes?
Yes, these are very few examples of why your customer is unhappy. Also, during the execution phase, if you find a GAP between the customer core business process and the mapping, you tend to create a Change request. As soon as, the customer hears the word Change request, he would immediately start thinking about the budget and the other constraints. I have personnly experienced the issue of Changes during the execution which makes the customer most unhappy. However, even though there is a change request during the execution, the customer should be aware that it is a core document which clearly state the functional consultants understanding of the process. It is not a rule that all the change requests would be charged. This should be explained very clearly in your kick offs and the review meetings.
Post implementation support is a major challenge for almost all the mid range ERP companies. In most of the cases, the support team is detached from the Projects team during the execution phase. While handing over the project to the customer, the support process and the team would be introduced. However, in back of the customers mind there would be a question whether the support consultant is aware of their business process and how would the Knowledge transfer would take place ?? Yes, before the handing over process, and at the warranty expiry period, the support team should also get involved. This would also give confidence to the customer and the relationship would be built between the support team and the customer.
Apart from this, keeping the customer informed about the status of their support call/bugs reported / issues reported is a key success to retain your customer and always remember ERP implementations are gifts, if you maintain well, it would always pays you back! ! !
While this may have been true at one time, the days of BI requiring a dedicated team of experts to implement are over. Self-service solutions are making it possible for everyone, including small, local businesses, to easily implement BI in their decision making process. more
A contact center often brings about a prospect’s first real-time interaction with your company. As such, if it’s not a positive one, they’ll likely look elsewhere for help. With 69% of Americans more inclined to recommend a company to friends and family after a positive customer service experience, you’ll need to exceed expectations on the following fronts. more
It was a painstaking process, but to help B2B companies start 2017 off on the right foot, we recently compiled a comparative list of the top 34 business phone vendors in the world. In one, easy-to-reference location, we’ve neatly outlined the information you need. more
There’s a very good chance that your contact center is underperforming. With consumer preferences continuously changing, strategies that were once effective now result in too many unsatisfied customers. Fixing this problem involves reviewing your current procedures and optimizing them to drive better results. more
Many businesses rely on a collection of communication tools that they adopt to address specific needs as they arise. This strategy may seem to work in the beginning, but eventually will lead to a system that is cumbersome to use, difficult to explain to new hires, expensive, and effective in some areas, but full of gaps. more