Are there any innovative processes that can accelerate a new software product introduction in enterprise?

I don't think "innovation" is the required component to accelerate a product introduction, I think a solid understanding of key metrics and processes to maximize their outputs will be more effective. I always make sure that my standardized processes aren't the bottle neck in the introduction phase by including the targeted end-users in its rollout.

Typically at POC first approach . Then this leads to identify key users for initial trainings and wider pilot . They then become the so what product champions or in some case a trainer depending on scale of deployment . We then roll out to sites one at a time. Follow up each with a survey asking about experience so we can adjust as needed . Continue survey after overall completion. 

Clear and Transparent communication as well as inclusion of key resources will help to accelerate the introduction and more importantly, adoption of new software.

Including key users in the decision making and thought process of selecting new users helps to ensure they are heard and feel included in making the selection and allows them to be more accepting of change.  They essentially become your champions and help be the voice of change because they were a part of the decisions early on and understand the problems the solution is going to solve.  In turn, they help to communicate the understandings to the rest of the Enterprise and it is always very meaningful to have end users and business users communicating consistently with the Enterprise Leaders.

The most important is to give the programmer the flexibility and work on their own. A lot of systems are constrained by the existing system (policy, procedure, out-of-date thinking, and regulations). Good ideas are often not valued if they are not in line with what the managers or old folks think. 

Change is never easy for people even if the change is for good. Effective change management is key or else “the good old days” syndrome kicks in.

So we used the following methodology:

Why are we introducing change (new software or technology)? This meant outlining clear problem statements and actually having the intended users vote on them so we truly understood the priority of the pain points. This also gave the actual users a voice in the process rather than just the key power users or influencers.

Launch communication should then address the WIFM (What’s in it for me). This will demonstrate that we heard their voice.

Tailor the education and training. There is no one size fits all. We did online, classroom-based, or self-learning training for major software rollouts. Also, set up a communication channel that they can easily get to during the early stages of adoption. We utilized Slack and created a dedicated channel where the users can ask questions as they encounter. This reduced the burden on the users for creating tickets and provided instant resolution. 

Post-launch check-up. It’s important to do a post-launch pulse check to see how things are going and did we live up to expectations. Also, this gives an opportunity to fine-tune things as well as generate new ideas for improvement or innovation.

Hope this helps.