Talent Locker's Dynamics 365 Recruitment Consultant Simran Bhatti spoke with F&O Specialist Ejaz Ahmed in the latest edition of the DynaMic Series.
In this Q&A, Ejaz, a seasoned F&O specialist, dives deep into the world of ERP and Dynamics 365 projects, sharing valuable advice on navigating the selection process, building a winning team, and ensuring a smooth implementation.
What are the 3 top tips you would give to someone embarking on an ERP or Dynamics 365 project?
#1: Align your project plan with the overall business strategy.
Ensure your project is part of a broader digital transformation plan, and make sure this plan aligns with your overall business strategy.
#2: Keep stakeholders engaged.
Follow these principles:
- Create a sense of urgency so everyone can see the need for the project.
- Make sure you have enough support from management.
- Develop a vision for the project and communicate it to the wider organisation.
- Create short-term benefits so people can see the positive outcome of the project.
- Anchor the project in a strong culture.
#3: Your team is key to success.
Always have in-house resources that has experience with implementing the system you have chosen. Ideally mirror the software vendors delivery team.
What is your advice or top tips for comparing ERP Vendors at selection stage?
#1: Work backwards.
I always recommend reverse engineering. Start by identifying your desired outcomes and the benefits you want to achieve with the ERP system. Then, work backwards to determine the necessary functional requirements. Ensure the vendor can confirm that their system supports these needs.
#2: Do a background check.
Obtain references from the vendor and reach out to them. Consider visiting their site to observe first-hand how the system is utilised.
#3: Qualify your vendor.
Request that the vendor arranges meetings with the individuals who will be assigned to the project. Conduct due diligence on their skills and experience to ensure they are well-qualified.
We see so many projects in trouble where the Client has been over reliant on SI/Partner resource.
What is your advice whilst resource planning for a project for a healthy mix of internal resource v’s SI / Partner resource?
My advice is to mirror the partner's team. This approach allows you to check and balance the partner, ensuring that knowledge stays in-house. Additionally, you'll remain the decision-maker with a critical eye on the process and solution, which ultimately enhances the end result
What advice would you give to an end user considering using a MS partner/SI/Vendor?
Choosing a smaller partner has advantages. They are likely to give you more personalised attention and dedicate themselves more fully to the project, as they are focused on building their brand.
Apart from your position what other role/s do you see as crucial for a ERP to be successful?
Implementing an ERP system is a team effort, and every role is important. However, at a minimum, you need an internal Project Manager and an Internal Solution Architect with implementation experience.
The Project Manager ensures a smooth implementation process, while the Solution Architect ensures the solution meets acceptance criteria and aligns with the business needs. Relying solely on a partner is risky.
Where do you see / or what are the most common mistakes, that can be avoided
A common mistake I have encountered is involving the end users too late in the project. They should have hands-on experience very early on and continuous training throughout the project. Training should not be an after-thought.
What input did you have on your most memorable project?
For me, it's the small things that matter most. The gratitude from an end-user when you take a late call and solve their problem is unforgettable. It's not the work itself but the smile on their face that sticks with you. In those moments, you feel part of something larger than life.