Operations
What it actually takes to run
The honest question behind every consolidation pitch: who does the work, and how much of it? Here is the answer before you ask.
Connected and looking
Point it at your directory and your HR feed. You can see who has access to what before you have changed a single thing.
First review finished
Run a real recertification campaign end to end. Reviewers see only what changed. The evidence pack exists at the end of it.
Numbers to show
Hours saved, accounts closed, the leaver gap measured and shut. That is the case for the next capability — or the reason not to.
Day two
The work after the launch
Most identity programmes do not fail at installation. They fail in month seven, when the reviews come round again and nobody has time.
They run themselves
Campaigns open on schedule, chase their own reviewers, and escalate when a deadline passes. Nobody chases a spreadsheet.
No new console to learn
Managers approve where they already work. They see what changed and why it matters, not a list of everything they approved last quarter.
It corrects itself
When reality and policy diverge, you are told, and it is put back. Drift is the thing that quietly undoes the first good quarter.
No integration team
The joins between tools were the headcount. Removing the joins removes the reason you needed the team.
Honestly
What we will need from you
Consolidation is not free of effort. It is just cheaper than the alternative, and here is where the effort actually goes.
One owner
Somebody who can decide what a role means. Not a project team — one person with the authority to say yes.
A trustworthy HR feed
Lifecycle is only as good as the signal that starts it. If HR data is unreliable, that is the first thing to fix — with or without us.
Patience for the second module
Land on recertification and let it prove itself. Teams that switch on everything in month one are the ones that struggle.