Identity programmes usually begin with strong intent. Architecture is agreed, tooling is selected and early phases move quickly.
Momentum fades when enforcement begins. The work shifts from designing access to changing how people actually work, and that is where decisions become contested.
The blocker is rarely technology. It is the absence of an owner empowered to enforce.
What this means in practice
- Treat enforcement as a governance decision, not a configuration task.
- Assign a single owner with authority across identity, security and operations.
- Sequence rollout by risk, not by what is easiest to enable.



