If you were talking to someone whose organization is considering SailPoint IdentityIQ, what would you say?
How would you rate it and why? Any other tips or advice?
The project that I worked on involved an on-premises deployment, although it can also be deployed on the cloud or in a hybrid cloud environment. My advice to anybody who is implementing this solution is to not begin without having the specification written and documented in advance. If you are implementing it for a client then you want to understand everything that the client wants to use, in advance of implementing. SailPoint is very good when it comes to Identity Management, although I would appreciate it more if it were simpler to use. I would rate this solution an eight out of ten.
I would rate it a seven out of ten. Not a ten because of the support and because of the high price.
We have some old processes in place that need to be revisited and updated. Those, of course, made our implementation a little bit late and we ran into some issues. One of the hurdles has been that people are used to the old method and when a new change comes in, a lot of people are not very open-minded to it. So it takes a lot of training and convincing about this new technology. We need to make changes to the way the form looks, the process. We had to make a lot of changes to the current processes. We had very outdated processes that were not working well for us because we had to get a lot of exceptions. And any exceptions you make, you tend to break automation and start doing manual processes, and that slows down productivity. That was a little bit frustrating and a lesson learned. Feedback from the client and explaining to them why we're changing some of the processes, policies, and standards was challenging. But we had to do a lot of cleanup before doing the implementation. We had an old system that was there for more than seven years. So that product was almost at the end of its life and we had a lot of complaints from the client that they were fed up with it. They wanted a change. But they were not expecting a change to the forms and the processes. They were expecting us to just solve the issues and move on, not a big system change. So we're training people. We created a lot of videos for them to play back when they request things. That helped a lot. We created a blog for them to give us any of their feedback. So we can make improvements because we are still in phase two of our implementation. We still have three more phases to go. For advice, I would say to make sure you gather your requirements first. Make sure you have more thoughts, make sure you know what your pain points are and what are you expecting to get out of the product that you select. That will help you a lot in selecting the right vendors. Secondly, have some solid use cases, and when you use those use cases, most of the time you should know the answer to the questions. That will help you in identifying who can meet your requirements. Do your diligence in terms of getting some references. Specifically, references for a current implementation from another customer. Getting that information from that customer will help you a lot in terms of how their implementation went, and what their pain points were in implementation. I would give the solution a nine out of ten. When every possible manual process we have right now can get automated, I'll give it a ten. We still have some processes that we have to do manually.