IAM Projects Stalling - Quick Wins and Big Wins

Welcome. My name is Martin Koor I'm principal Analyst at Ko code. Today. I want to talk about identity management projects, stalling, and why they are stalling frequently. One of several videos in this series, there are many reasons. And the one I'd like to look at today is that frequently grow trips fail in delivering quick wins. That is the, I would say the more well known part, but they also fail to make their big wins visible.

And my experience is that from the very beginning aside of structuring a program into smaller project trips for identity access management, we know identity access management is complex. Aside from this splitting the bro trip up into smaller pieces. It's very important to have both well defined and, and reasonable and achievable quick wins planned from the very beginning, but also to define what are the big wins. What are the really big steps the project delivers, and these need to be visible. These need to be communicated. Start with the quick ones.

You need to have something as a result, which is visible to a broader community, so to speak relatively early in the project. Otherwise you're always in danger of failing and being asked question about, we spend so much money over the last 12 months, 18 months, or even longer. What is the result of that avoided show? Your quick wins define your quick win something which is positive benefit. So very well-known seeing here is improving the sign on experience of users, but you also need to have the big wins, the ones where you say, okay, this is where we really got better over the last.

However, it takes 6, 12, 18, 24 months where we made major improve improvements for the business. Either in running the business or doing things you need to do better or in changing the business or helping the business to move to the next level, what is very important for all of these types of wins that you can measure and prove them. So proof is based on measurement, which means you need to measure before you start. So how fast or how slow, how bumpy are your processes?

How many, whatever offered accounts do you have? How many different sign ons did you have at the beginning? Only if you have measured at the beginning, you can prove that you made an improvement. This is essential, but for every successful project, the first thing Is really to think about what are the potential quick ones, what are the big ones in this project? And how can you measure that? So you need to think about KPIs and K only them, your project will become a real success. Thank you for listening to me.