3 Lessons Learned from My Own Software Implementation
If you are a technology user at your organization (i.e. you actively use a talent management system), I’m sure you’ve heard claims regarding how important the implementation process for that technology is. Here at iCIMS, we understand that and embrace it. But, I have to admit, never has that point been made as clear and poignant as when I myself became a technology user - for a marketing automation system.
Obviously, I’m not an HR professional - I’m in marketing. However, implementing software meant to aid you in your daily responsibilities is a universal experience, regardless of the job function. So, I’d like to share some of my thoughts and takeaways from my recent experience implementing software.
- You really, really need a true implementation process mapped out: And when I say this, I don’t mean a single document outlining the next 4 weeks and what you are responsible for learning in the system by that time. This is what I received, and I’ll tell you right now it’s not helpful in the slightest. Instead, a project plan should be crafted around a targeted go-live date, with meetings and milestones set to ensure the date is met. Furthermore, your technology vendor should work with you throughout this time to understand your needs and translate your organizational processes into system configurations.
- You need a go-to guy: From my experience, having one, dedicated implementation specialist to go to is crucial. This ensures total commitment to your account, and that you are receiving the time and attention you deserve. It also means you are working with one person who is knowledgeable of your organizational processes, and thus able to implement the new system as quickly and painlessly as possible (you know, avoiding multiple e-mails back and forth with the vendor as they try to determine where you are in the implementation process).
- You’re going to want to know how the other folks are doing it: Plain and simple, you are not only going to want, but frankly need, some best practice advice (especially when you’re a newbie to the technology like I was). And shouldn’t your vendor, who’s worked with hundreds of similar organizations and helped them map out their processes, be able to provide that consultation? When vendors are able to provide you with best practice recommendations, you’re more likely to have your organizational goals and objectives met at all levels.
So there you have it, my big takeaways. What do you think? What do you find to be the most important elements during the implementation of software?