Two focused lab sessions can teach more usable knowledge than ten hours of disconnected study when they answer one question and produce an explainable result.
That isn't an argument against reading. It is a reason to connect reading with a test.
Use a question such as why a user can read a project file but cannot edit it. Establish the baseline, study what you don't understand, then test one explanation and record what changed.
Define what you need to understand
Before studying, write the expected behavior in ordinary language.
A reviewer should be able to read project documents. A contributor should be able to update them. Someone outside the project should not be able to open them.
Now you have a learning target. You need to understand which identities and permissions produce those results, how to test them, and how to explain an unexpected result.
Without that target, it's easy to spend the evening moving between directory videos, security exam notes, and new tools without answering any of those questions.
Use the first session to establish the baseline
In an isolated lab with fictional accounts, create the smallest version of the scenario. Use a test resource and separate accounts for the roles you intend to compare.
Write down the permissions you expect each account to have. Then sign in as those ordinary accounts and attempt the relevant actions.
Do not treat your administrator session as proof of a regular user's experience.
Record what happened, including anything that differs from your prediction. A failed prediction is useful because it gives you a precise subject to investigate during the next session.
Let the result decide what you study between sessions
Suppose the reviewer can edit when you expected read-only access.
Now your reading has a purpose. Investigate the permission paths that could explain the result instead of watching an entire course unrelated to the problem.
Microsoft's access-control overview explains the relationship between security principals, permissions, and protected objects. Use documentation to understand the mechanism behind the behavior you're seeing.
Keep observations separate from guesses. “The edit succeeded” is an observation. “Another group grants write access” is a hypothesis until you check it.
Use the second session to test one explanation
Return to the same scenario and investigate the most plausible cause. Change one relevant condition at a time so you can tell what affected the result.
After the correction, repeat the original test and a control test. Confirm that the reviewer has the intended restriction and that the contributor can still complete the authorized task.
Then explain the sequence without looking at the tutorial: expected behavior, observed behavior, evidence, change, and retest.
That explanation is the learning outcome. A green check mark alone isn't enough.
Measure what you can now explain or predict
After the sessions, ask:
- Can I predict the access result under the tested conditions?
- Can I identify evidence that would challenge my explanation?
- Can I describe which part of the permission path matters?
- Can I state the limitation of the test?
These are stronger measures for this exercise than the number of tabs opened or hours a video played.
The demonstration-based approach to measuring study progress helps track those changes across several weeks.
You may discover an unresolved question rather than a finished explanation. That can still guide the next session if you record it precisely.
The goal isn't to declare all short lab work superior to longer study. It is to make the investment produce understanding you can use, verify, and communicate instead of activity you can only count.
Keep broader study connected to a purpose
Focused labs don't replace every kind of learning. You may need foundational reading before an exercise makes sense, and certifications can provide a useful structure.
The point is to connect that learning to a question. When reading exposes another gap, add it to a short backlog rather than rebuilding your entire plan around it immediately.
A completed experiment gives you a stopping point and a reason to choose the next one.
The Six-Figure IAM Career Playbook includes three practical IAM projects and a 90-day plan for connecting study with a target role. It's $9.
Use the plan to make your study sessions accumulate into capability instead of becoming separate evenings of information consumption.