Identity Management Workshop: Critical Ingredients
An Identity Management Workshop can be a fantastic way to start an IdM Project - if it has all the right ingredients. Unfortunately, with the wrong ingredients an Identity Management Workshop could erode the valuable goodwill of the participants, making the critical starting phase of your Identity Management project all the more difficult.
We've compiled a checklist of some of the right ingredients for a successful Identity Management Workshop. Enjoy!
Give Yourself Some Prep Time
Prep time means gathering some information about your Identity Management initiative such as business drivers, technical drivers, high level business processes, budget parameters, current technology infrastructure, resource limitations, etc. If you get your hands on a Pre-Workshop Questionnaire, spending time with your team filling it out should help unearth some valuable information and help you set your parameters.
Heaps of Stakeholder Participation
A workshop should not be an IT-only initiative (since IT-only Identity Management initiatives tend to fail). The appropriate representation from various departments and business segments of your organization will ensure that the discussions will be balanced and couched in terms of real-life business processes. Do your level best identifying the stakeholders that should be present, and who in your organization best fits those roles.
A Pinch of Skepticism and a Bunch of Conversation
Too much skepticism can be a barrier to communication, but just a pinch might enhance the conversations during the Workshop. A few things to be skeptical about:
- A one-size-fits-all solution
- A 6 month roadmap
- A lecture (the value of the workshop is the conversation it initiates)
- Someone trying to sell you something. (This should be about your organization, not an "offering"!)
Mix in Some Business Processes Analysis
At the heart of an Identity Management project is enhancing identity-related business processes. The absolute wrong way to begin analysis of your environment is to start talking about data synchronization and go up. Start by analyzing the relevant business processes, then analyze how they impact the systems/applications in your environment, and finally analyze how those interactions impact the underlying data.
But Hold the Software Vendors
A workshop led by an Identity Management software vendor will most likely lead to skewing your requirements to match the vendor's capabilities. It would be more appropriate to use a neutral third party Identity Management Consulting firm that can help you unearth and refine your requirements first, and then provide you the relevant information regarding vendor capabilities to help you make an informed decision.
So there you have it. I'm sure we missed something, so feel free to add in the comments section!