Watch out for these pitfalls before implementing an IAM solution

A good IAM solution can make operations both easier and more secure for the organization. However, there are some important points to be mindful of along the way.

Feel free to contact us to discuss how we can best assist you

Implementing a new Identity and Access Management (IAM) solution involves a transformation on several levels, both technical and organizational. While the benefits are numerous and significant, there are also some common pitfalls that can lead to unnecessary time consumption, costs, resistance, and uncertainty.

Start off on the right foot

Many companies start by purchasing an IAM system before they have mapped out their needs and the potential technological possibilities. They might then begin to implement some quick wins, only to find out that the system doesn't actually meet their real needs – they are essentially heading into a dead end.

It is important to ensure that you acquire technological solutions that are tailored to your needs – so that you avoid trying to fit your needs to the technology.

→ Maximize the value of your IAM solution with a needs analysis

Avoid tunnel vision

An IAM solution should make things easier for the company, but it's easy to develop tunnel vision focusing on the needs and requirements of oneself or one department. For instance, optimizing one part of the process at one level may result in a lot of extra manual work at another level.

It's crucial to see the whole picture and optimize across the organization – so that efficiency improvements in some parts of the company do not come at the expense of others.

Size ≠ Complexity

Be realistic when assessing the scope of the project. A smaller organization does not necessarily mean less complexity. A good example is municipalities. There is approximately the same breadth in the variety of services and processes regardless of whether it is a small or a very large municipality. All have health services, social services, daycare and schools, technical services, administrative positions – and so on.

There may be hidden complexity in your organization as well, regardless of its size. Map out the diversity and complexity of the processes before you create the project plan.
CW_illustration

Be open to new paths

The way tasks, processes, and workflows are organized in the company has likely evolved gradually over time. Often, things are built upon and expanded little by little as new functions, applications, positions, and needs arise – resulting in a bit of a patchwork. This is not necessarily the optimal structure for implementing an IAM system.

View an IAM project as a golden opportunity to optimize the overall structure and organization of processes – rather than blindly setting up the IT system based on how it is now.

Don't restrict vendors

When you are ready to acquire an IAM system and have spent a significant amount of time mapping out your requirements and needs, it's easy to have a very clear picture of the solution you want. The downside is that you might miss out on the possibilities that vendors have, which you were unaware of.

To avoid locking a vendor into a specific – and possibly suboptimal – way of addressing a need, try not to be too detailed in the requirements specification. Instead, keep the needs descriptions at a high level to get the best solutions. Hold heller behovsbeskrivelsene på et overordnet nivå for å få de beste løsningene.