Once you've implemented your solution, these 5 points will help the adoption and longevity of your program.
January 7, 2020
It’s easy to feel exhausted after a CPQ software implementation project; you may begin to not remember why you got started in the first place. Implementation expert, Nikhil Karwhal, Group Head of Practice EMEA at 4C, explains this phenomenon:
“You know sometimes you go on a holiday to escape things or clear your mind? Halfway through the holiday, you forget why you started it. You fall into your daily routine, and you forget why you booked that holiday. By the time the holiday comes to an end you realize ‘wait, why did I book this holiday?’”
Don’t forget why you started your CPQ project in the first place. In order for successful adoption, it may take reminders to your team, and yourself, why you started. For example:
Whatever the reasons are, you need to stay positive. Here are 5 ways to ensure success after you’ve implemented CPQ software at your organization and avoid post-implementation exhaustion.
It’s not enough to reach the finish line of implementation. Think beyond initial launch and about what end-users of CPQ software will need to be successful in their roles. To start:
Preparing your team is essential to maintaining internal buy-in for new processes, and software.
It’s emphasized that a c-suite champion should be identified long before your project starts. Along with your team, this executive sponsor needs to stay bought into the use and growth of CPQ at your organization post-launch. Make sure that you:
Without proper training, asking your team to adopt the use of CPQ software is a lot to ask of them. Your training shouldn’t begin post-launch but instead, it should be delivered in small chunks throughout your implementation timeline to get current team members involved early and not overload them with too much information.
You’ll also want to establish a training process for onboarding new employees into your CPQ software as well. You may consider:
When creating budgets post-launch of CPQ there may be line items that you need to maintain. Don’t assume that a CPQ tool will be a “set-it-and-forget-it” asset. You may need technical support teams to manage to make modifications to the configurator and maintain the product(s).
Technical support needs for CPQ are both internal and external; you may need to add both support roles depending on the complexity of your products and how often changes are made to them.
Lastly, in order to remember why you started and avoid post-CPQ blues, you’ll want to measure against the goals you set out to accomplish. Whether the goal was to reduce manufacturing delays, or decrease production timelines, or to increase sales, you should think about how you’ll measure against past performance.
You are sure to see the benefits of a successful CPQ software implementation if you stay proactive with preparing and training your team, maintain executive buy-in, and account for maintenance. Ready to implement CPQ at your organization? Read our full implementation guide to understand where to start.
In her role as the Senior Implementation Engineer at KBMax, JoAnna is responsible for scoping, designing, and implementing projects for our customers. Her life goal is to save all pit bulls everywhere.