Succeeding in deploying a new service is not an easy task, especially when dealerships are scattered all across the world. For the launch of its new Renault Pro+ concept, the company had to modify the brand of each dealership (logo, signs), enhance the commercial vehicles' visibility on all their sites and train their sales team on the new product line. And all of this had to be done, of course, within a very rapid timeline.
Renault-Nissan had always managed deployments the old school way: with Excel files. The problem with this approach is that we live in a world where agility and speed are essential to securing a successful deployment. It is imperative to have a single, up-to-date source of truth to make sure the right decisions are made throughout the process.
Christophe Koenig, former Renault Pro+ Network Manager, and current Consulting Director at One2Team, shares his top 4 tips on how to achieve success in your deployment projects:
Align your teams ASAP
The teams involved in the deployment must be aligned quickly. This step will guarantee that the deployment is ready to go and that all of the moving parts are in place to carry out the initiative and change management.
Put together a deployment kit
A deployment kit details tasks, methods, tools and desired results specific to unique business challenges. It should be shared during preparatory meetings with the deployment team's coordinators. This technique has the benefit of answering potential questions and aligning approaches. The kit should also be finalized and circulated one final time before the project actually starts. This way, stakeholder approval is garnered faster and the chances of seeing wrong or inappropriate tools in use are significantly reduced.
Pick the right KPIs
A project manager should be named in each country or region where a deployment project is planned. These managers' individual KPIs are linked to deployment quality (standards upheld, mystery shopping) or results (vehicles sold or client satisfaction quality) but not the number of sites deployed. Counting pins on a map is clearly counterproductive.
Forget about one-shot deployment
What is the difference between a successful and a failed deployment? An ongoing follow up. Even though new facility implementations, customer experience improvements or training on new workflows can be achieved in a short amount of time, you have to manage teams to sustain these changes in the long term. If needed, you’ll even have to update the action plan.
Following these 4 tips, Renault shortened its deployment timeline by 8 business days, completed more than 100 dealership deployments simultaneously, and was able to meet reporting requirements 4 times faster!