Begin with the environment.
The first task is to define the operating reality: the services that matter, who depends on them, the technical and commercial constraints, what has already been tried and what outcome the organisation is actually seeking.
Only then should products, platforms or delivery routes be compared. This prevents the available solution from quietly redefining the problem.
Identity architecture should make legitimate work easier while reducing ambiguity, unnecessary privilege and fragile exceptions.
Questions worth answering
- Role and privilege design
- Joiner, mover and leaver reality
- Exceptions, service accounts and legacy dependencies
- Authentication, recovery and break-glass paths
- What evidence would change the current direction?
- Who will own and operate the outcome?
A useful output
The result should be more than a list of observations. It should describe the decision, the evidence, the viable options, the trade-offs, the recommended direction and the work required to make that direction succeed.
