How to Adopt RTC EE - Part 3 "Process"
If you've done a pilot, people will listen. Nobody wants to go into something blind. We want proof that not only does it work, but it works in our environment. At one of our clients, we spent an entire year running a pilot project. This amount of time is completely non-standard, but required because we:
- Decided on global best practices (includes stream strategy, SCM organization, and process template role configuration)
- Built automated scripts for import
- Created custom training
- Wrote necessary extensions to the product
- and much more
Armed with a recipe that allows us to onboard a new team into RTC from start to finish in just a few short weeks, we set out to rinse and repeat. As we move through the organization, we have our wins to reference and our early adopters to enable. Our process is simple...automate everything we possibly can and standardize everything we possibly can. We still run into new scenarios from time-to-time, but our experience and ability to think out of the box makes for finding a solution quick and easy.
A pilot is always a good idea when working with a new client. Our process has proven to be successful and can be implemented in no time at all.
Do you agree with our approach?