Identity work appears across IT whenever a person, device, or application needs an identity and permission to act.
Map the identity decisions around work you already understand. That can reveal a starting point for specialization even when your team isn't called IAM.
Use only information you're authorized to access and discuss. The exercise is to connect familiar responsibilities—not conduct an unofficial audit or inspect other teams' systems. A fictional version works well when you need to explore a question without exposing company details.
Look beyond employee passwords
Start with the familiar employee account, then ask what else needs access.
Administrators may use separate privileged identities. Applications may use service accounts or other non-human identities. External collaborators may need limited access. Customers may sign in to a service that has a different set of requirements from the workforce environment.
You don't need to master all of these areas. The point is to notice that identity is a category of responsibilities, not one screen in a directory console.
Keep the map conceptual. A public career exercise should not reveal real account names, secrets, or internal architecture.
Ask four questions about each type of identity
For a user, device, or application identity, ask:
- Ownership: Who creates it or sponsors its use?
- Authentication: How does it establish its identity?
- Permissions: What determines which resources or actions it can access?
- Lifecycle: How is its access changed or removed when it is no longer needed?
These questions can reveal different gaps. Creation may be well documented while ownership is unclear. An application identity may work reliably even though its retirement process hasn't been explained to you.
Treat an unanswered question as something to clarify with the appropriate owner, not permission to investigate beyond your role.
Use the answers to distinguish what you know from what you need to learn. Then choose an approved learning opportunity or a fictional lab around one of those gaps.
Mark the team boundaries
For each responsibility, note the owner or the kind of team likely to own it in your example.
A service desk may handle initial requests. An application team may define roles. Infrastructure administrators may maintain directories. Security or governance functions may establish review requirements.
The structure varies. What matters is recognizing that a technical change often depends on a decision made elsewhere.
A person who can explain those boundaries has a more useful understanding than someone who knows only where to click in one product.
Find the area closest to your current strengths
If you're comfortable investigating connectivity and system interactions, application authentication may interest you. If you already manage accounts and groups, directory or hybrid identity may be a natural area to explore. If you enjoy clarifying ownership and approvals, governance work may deserve attention.
Treat these as hypotheses, not career assignments. Choose one responsibility from the map and compare it with actual roles. What level of depth do those roles expect? Which parts can you already demonstrate? What would a small project help you understand?
That is a more grounded starting point than choosing a niche solely because a salary post made it sound attractive.
Turn the map into one learning decision
Don't finish with a giant diagram and fifteen new study goals.
Circle one area to investigate over the next few weeks. Write the question you want to answer and the evidence you will produce.
For example, you could model how a temporary collaborator receives and loses access to one resource. Or trace how an application uses a non-human identity, without exposing real credentials.
The map's purpose is to narrow your next action after showing the broader field.
My The Six-Figure IAM Career Playbook organizes the main identity lanes and connects them to practical career steps. It can help you turn the access decisions already surrounding your IT work into a direction you can investigate deliberately. The ebook is $9.