Implementation methodology is broken and very biased against the client. I’m probably going to get a lot of flak for this. Hear me out.
I have been involved in many implementation projects over the years, and I have noticed some common issues that often lead to failure or dissatisfaction. In this article, I want to share my insights and suggestions on how to avoid these pitfalls and achieve success.
One of the main issues is that the implementation methodology is not aligned with the client’s needs and goals. The methodology is usually developed by the vendors and their partners, who have their own interests and agendas. They tend to focus on the quickest and easiest way to go-live, without considering the full impact and benefit of the implementation for the client. They often overlook or skip important steps, such as data analysis, business process mapping, current and future state documentation, and system integration testing. They apply a generic and cookie-cutter approach, without customizing and adapting it to each client and situation. This can result in poor quality, missed opportunities, and wasted resources.
Another issue is that the clients are not fully engaged and committed to the implementation project. They sometimes delegate or outsource the responsibility and decision-making to the vendors and partners, without doing their own due diligence and homework. They do not invest enough time and effort to understand their current state, define their requirements, plan their future state, and communicate their expectations. They do not have a clear vision of what success looks like, and how to measure and evaluate it. They do not have a dedicated and skilled team to support the implementation, and to fill the gaps in their knowledge and capabilities.
These issues can lead to many problems, such as delays, conflicts, errors, and dissatisfaction. The project can become a source of frustration and blame, rather than a catalyst for improvement and innovation.
So, how can we avoid these pitfalls and achieve success? Here are some of the best practices that I have learned and applied in my implementation projects:
- Define success. Before starting the implementation, have a clear and shared understanding of what success means for you and your stakeholders. What are your goals and objectives? What are the benefits and outcomes that you expect? How will you measure and evaluate them? What are the risks and challenges that you anticipate? How will you mitigate and overcome them?
- Establish requirements consensus. Work with your vendors and partners to agree on the scope, timeline, budget, and quality of the implementation. Make sure that your requirements are clear, complete, and realistic. Prioritize and categorize them according to their importance and urgency. Document and validate them with your stakeholders. Avoid changing or adding requirements during the implementation, unless absolutely necessary.
- Plan ahead. Create a detailed and realistic project plan that covers all the phases and activities of the implementation. Assign roles and responsibilities to your team members, vendors, and partners. Define the deliverables and milestones that you need to achieve. Allocate the resources and tools that you need to support the implementation. Monitor and track the progress and performance of the implementation, and adjust the plan as needed.
- Communicate effectively. Communicate frequently and consistently with your team, vendors, partners, and stakeholders. Use the appropriate channels and methods to share information and feedback. Establish regular meetings and reports to update and review the status and issues of the implementation. Resolve any conflicts or disputes quickly and constructively. Celebrate and acknowledge the achievements and contributions of the implementation team.
- Evaluate and improve. After the implementation, conduct a thorough and honest evaluation of the results and outcomes. Compare them with your expectations and criteria. Identify the strengths and weaknesses of the implementation. Learn from the successes and failures. Document and share the lessons and best practices. Implement and sustain the changes and improvements that you have achieved.
I hope that these tips will help you to avoid the common pitfalls and achieve success in your implementation projects. I also recommend having someone dedicated to managing the testing phase. I would love to hear your thoughts and experiences on this topic. Please feel free to comment and share your feedback. Thank you for reading.
