Anyone have any stats on the typical or average duration of time it takes once a product or service is successfully presented to actual implementation and delivery
?
Does it depend on what the product or service is? Is there any tips out there on how to make it a simpler process and/or one that allows for an easier and smoother implementation?
There’s an old adage that goes something like this: If you want it done quickly and with high quality, it’s not going to be inexpensive; if you want it well and inexpensively, it’s going to take a while (i.e. “ain’t gonna happen fast”); if you want it fast and “on the cheap” it’s not going to be done well/with high quality… So the first thing to decide is do you want to get it done fast or is it more important for your company to analyze current business processes, determine where improvements need to be made, consider your long-term goals, etc.
Some additional thoughts: Don’t scrimp on training and education. If you are investing in new technology, invest in your people too.
In order to determine average project duration begin with the end in mind. If you have current software licenses expiring or a trainer about to go on maternity leave, you may need to consider outsourcing the implementation tasks and initial new user training. Adult learners need more repetition and exposure to new concepts than their younger counterparts. When planning your training classes, bear this in mind; also limit the ratios in your hand-on computer classes to no more than 12 students per instructor to ensure the best possible environment.
With this in mind, get out the calendar; most training is preferred/delivered mid-month. So, if you plan to train with in-house/corporate personnel, and you have one trainer and 60 trainees, that’s five sessions. Depending on how long the sessions need to be, the number of additional support staff your company has on hand, and the amount of behind the scenes work that needs to be done concurrently (i.e. data conversion), you can back into the number of sites or locations that can be brought up or implemented each month.
Jonathan - to address the first question, I think I'll address the second question ("Does it depend on what the product or service is?)...
My feeling is that it absolutely makes a difference what you are talking about. Are you implementing something that is more of a back end process? Is it something that requires extensive training or buy-in from your people? The answer to questions such as those will largely determine the amount of time implementation will take. I'd find it hard to believe that generic statistics exist. There are so many factors that would make each situation unique.
That being said, I believe that you can generalize when it comes to your last question. "Is there any tips out there on how to make it a simpler process and/or one that allows for an easier and smoother implementation?" I think that getting the people that will need to use this new solution to buy-in is critical. Show them how they will benefit, how their job will be easier, how/why this new solution makes sense... Of course, planning ahead and allocating the proper time and resources to training is very important as well.
Did you have a specific product or service in mind?
You are echoing what I kind of felt was the situation. When it comes to implementing a new product or service, all of the factors you stated are necessary.
On my end of the world, I have noticed that every company is truly different. For the type of service we provide, there is quite a bit of process involved in order for a final decision to be made. Where the difference comes into play is on how quick the decision comes and the various individuals involved. With some clients its a no brainer, and where do I sign process and others it takes considerable time and various chains within the corporate structure that need to be consulted with.
I try to be cautious and show due diligence knowing that there are so many different decision making structures out there. At the same time I am working hard to strike the balance between regular reminders of the service that a management company is interested in, and not being an aggravating vendor.