Give the first two weeks of your IAM pivot a concrete goal: choose a provisional target role and produce the first useful lab result.
You don't need to settle your entire career direction before starting. A small set of plausible jobs and one relevant skill gap are enough to guide an initial project.
Use the schedule below to limit research, prepare only the required environment, and test something by the end of the second week. Then decide whether the work still fits before committing to more training.
Days 1–3: collect a small set of plausible roles
Choose a few openings that fit your location and working preferences. Read what the person will do, not just the technology list.
Write down the responsibilities that repeat. Separate them from requirements that appear specific to one employer.
Then make an honest inventory of your related experience. Include work you've performed, work you've assisted with, and concepts you've only studied. Those categories keep familiarity from quietly turning into an unsupported claim.
By the end of this step, you should be able to explain why one identity lane deserves investigation.
Days 4–6: choose one gap and one project
Pick a responsibility that matters to your target and is small enough to practice.
For a directory-focused move, that might be explaining and testing group-based access. For an application-focused move, it might be tracing a working sign-in flow. For a governance direction, it could be modeling a role change with justified access additions and removals.
Write the expected output before selecting tools. Include the business question, the minimum environment, the tests, and the documentation you want to finish.
This brief should fit on one page. If it requires several pages of architecture before you can state the question, reduce the scope.
Days 7–10: prepare only the required environment
Check the prerequisites, available resources, licenses or evaluation access, and the recovery options for your chosen setup.
Use fictional identities and a dedicated lab. Keep ordinary personal files and work systems outside the experiment.
Build the minimum foundation and verify it works before adding the project-specific configuration. Record the baseline so you can distinguish a setup problem from a problem introduced by the exercise.
Don't let preparation become a hardware-shopping project. If the environment exceeds what you can reasonably run, simplify the scenario or choose another way to demonstrate the same responsibility.
Days 11–14: complete one test and record the next action
Run a test tied to the original requirement. Save a short record containing:
- Condition: The account, resource, and relevant setup you tested.
- Expectation: What should have happened and why.
- Observation: What actually happened, with supporting evidence.
- Next action: The specific correction or additional test needed.
A failed test can still be useful progress. “Something is broken” isn't much to resume from; identifying the component or assumption to investigate gives your next session a purpose.
Write a short explanation of what you understand so far. It doesn't have to be the final portfolio page, but it should show that the project has moved beyond planning.
Before ending the second week, leave a restart note. A clear next test is more helpful than opening the lab later and trying to remember where you stopped.
Review direction before increasing commitment
Ask three questions: does the work interest you, does it connect to the roles you saved, and is the project small enough to finish?
If one answer is no, adjust the plan now. Early changes are not wasted effort when they prevent months of unfocused study.
You can also apply to a suitable role during these two weeks if your existing background already supports it. The plan shouldn't create an artificial waiting period.
My The Six-Figure IAM Career Playbook supplies the broader role, lab, and positioning structure around these early decisions. The first fortnight is successful when you know what you're working toward and have started producing evidence, not when you've collected the most comprehensive roadmap. The ebook is $9.