Plan three IAM labs around three distinct skills, then reuse the infrastructure where it makes sense.
Decide what each project must demonstrate before expanding the environment. Otherwise, a directory lab, SSO lab, and lifecycle lab can all turn into unfinished attempts to build a whole company.
You need time for setup, testing, and explanation—not every interesting feature. A clear question and finish line for each lab make the work easier to manage alongside your job and give your portfolio three genuinely different examples.
Give the directory, SSO, and lifecycle labs different goals
Write one sentence describing the finished evidence for each project:
| Lab | Question the evidence should answer |
|---|---|
| Directory access | Can the intended user read a resource while another user is denied? |
| Single sign-on | Can you explain a working sign-in and diagnose one controlled configuration error? |
| Identity lifecycle | Can you show appropriate permission changes after a fictional employee transfers? |
These questions prevent three projects from becoming the same user-management demonstration with different screenshots.
For each one, list the result you need to capture before opening a hypervisor or cloud portal. Then include only the components required to produce that result.
You can share a foundation without repeating the same lesson. The difference should be visible in the business problem, the test, and the explanation—not just the tools named in the title.
Reuse the foundation instead of rebuilding everything
Use the same fictional organization, naming convention, and basic documentation structure where practical. Reusing the foundation saves effort without making the learning objective repetitive.
A small directory environment can support one access test and later supply context for a lifecycle scenario. Your SSO exercise can use the same fictional employee while testing a different system boundary.
Keep the environments isolated from your employer and personal accounts. Reuse lab components, not production data or real permissions.
Also check licensing, supported editions, and resource requirements before deciding that a specific implementation is feasible. A plan that depends on a feature you cannot access is not a useful weekend plan.
Budget setup, testing, and documentation separately
Do not allocate all available time to installation.
For a hypothetical six-hour project, you might reserve two hours for configuration, two for testing and troubleshooting, one for documentation, and one for cleanup. These are planning estimates, not a guarantee that the work will fit.
When setup consumes the whole budget, reduce the scenario rather than sacrificing validation. A smaller test that you can explain is more useful than a large installation with an unknown result.
Keep a separate list of interesting improvements. That list is where extra dashboards, integrations, and automation belong until the core project is finished.
Define what you will not build
A directory access exercise does not need a full enterprise organizational structure. An SSO exercise does not need a production application. A lifecycle exercise does not need a commercial governance platform.
Your exclusions should be visible in the project notes. They explain the scope instead of making the lab look incomplete by accident.
For a practical example of stopping at the right point, see how to decide that a lab is finished enough to publish.
Stop when the evidence answers the question
Before moving to the next lab, check four things: the scenario is understandable, the intended behavior was tested, an unsuitable action was denied or failed as expected, and the result is documented.
Then write down one limitation. Perhaps you tested only one application or did not automate the workflow. An honest limitation helps readers interpret the evidence correctly.
A short handoff to your future self also helps: what works, what is deliberately broken, and which accounts are safe to use for the next test.
The Six-Figure IAM Career Playbook brings these three lab areas into a career plan rather than treating lab building as an endless hobby. The $9 guide connects the projects with role selection and positioning.
Your goal is not to own the most complicated home environment. It is to finish work that helps someone understand what you can do.