IAM LESSON LEARNED #3: DOCUMENTING THE CURRENT STATE IS CRITICAL
In our last entry we talked about determining the true current state of your IAM Processes and Technology. Uncovering the true current state and documenting the details are often not one and the same. If assessing the true current state is the natural starting point, then the next logical step is documenting the details so that you can begin the process of building an ideal future state.
Lack of clear documentation has a domino effect on your IAM program:
> Organizations routinely have poor documentation of both the technical environment and the associated business
> When there is a lack of detailed documentation, information cannot be accurately communicated from one party to the next.
> As a result, organizations end up with staff who do not fully understand their own processes, procedures, or technology they have implemented within the environment.
> This lack of technical and/or procedural knowledge creates roadblocks to successful IAM program deployments,
expansions, or improvements.
We recommend that you document the current state in a way that allows you to capture not only technical details and the business processes, but the wants, needs, and desires for the people, processes, and technologies in the future. Knowing where your business wants to go will serve you well down the line when you’re ready to design the ideal IAM future state that details the future business processes and technology.
With documentation, the devil’s in the details. You don’t want to be automating a broken process. We’ve been in dozens of situations where customers have wasted A LOT of time and money building in-house solutions or implementing vendor technology to automate a workflow based on a manager’s magical thinking. Only later realizing that technicians have created workarounds to get their own jobs done, or have been manually entering data outside of any automation or corporate policies.
Here are a few tips as you document your current state to keep you on track and ensure you end up with documentation that will provide you with the ability to design an ideal future state and develop business and technical requirements.
> Document use cases and workflows in a logical word document AND in pictures (e.g. Visio diagrams).
> Ensure you have all of the right actors in the room for an accurate portrayal of use cases and workflows. Technicians/workers must be involved, NOT just the managers.
Wrangling all of the details for documentation can feel overwhelming. Reach out to us if you’d like help facilitating, managing, defining, or documenting your organization’s true current state.
IDMWORKS Lessons Learned Series
After 750+ IAM engagements, IDMWORKS has compiled what organizations need to know before, during and after implementing an IAM program. We polled our customers and our 150 IAM engineers, architects, and PMs responsible for their success, to draw from what they see on the job every day and boiled that down to a series of lessons learned. Every organization in any stage of IAM maturity will find value in these highly-accessible, technical jargon-less, universal rules-to-live-by to make your IAM program successful.