With five hours a week for an IAM career move, give each session an output before putting it on the calendar.
Otherwise, studying can absorb all the time while projects and applications remain permanently postponed. The work needs to connect: learn a concept, test it, explain the result, and use what you learn about the job market.
The example below is a planning option, not a five-hour promise of employment. Adjust it to your responsibilities and starting point.
Give the week one shared objective
Start with a specific requirement from a suitable role.
Suppose the gap is explaining and demonstrating group-based access. That becomes the week's focus. Your reading, lab, and interview practice should support the same objective instead of pulling you into three unrelated subjects.
Write a finish line: “By Sunday, I can show one allowed user, one denied user, and explain the group membership behind each result.”
That is narrow enough to complete and concrete enough to evaluate.
Monday: turn 45 minutes of study into the next lab question
Use the session for material directly relevant to the week's objective.
A practical sequence is:
- Read: Use appropriate documentation or course material for the concept.
- Question: Write three things the lab needs to establish.
- Prepare: Leave a concrete starting action for the next session.
For a group-based access lab, the questions might be: which identity is tested, which group grants permission, and what result would demonstrate that an unrelated user is excluded?
Don't spend the session recording every interesting feature mentioned along the way. Keep unrelated questions in a separate list.
End with a restart note such as “create the second fictional test account and record its expected access.” That prevents Tuesday's build time from disappearing while you reconstruct Monday's plan.
Tuesday and Thursday: spend two hours on the lab
Use two one-hour sessions rather than assuming you'll find one perfect uninterrupted evening.
In the first, establish the fictional users, groups, resource, and expected results. In the second, run the tests, investigate discrepancies, and save the evidence.
Keep the scope fixed. Don't add another platform because the original exercise feels too small.
If something breaks, preserve the state and write the next diagnostic step. A problem can be useful learning, but it shouldn't silently expand the project beyond the week you planned.
Wednesday: reserve 45 minutes for the job search
Read a few suitable postings and make one concrete career action.
That might be a targeted application, a revision to an existing application, or a question to a professional contact. It should not become an hour of collecting dozens of links you never revisit.
Check whether your week's learning still matches the work being requested. A posting may reveal that you need a different example or that you're already ready to apply.
Use applications as feedback during the plan, rather than waiting until every learning activity is finished.
Friday: use 45 minutes to document and explain
Turn the lab into a small readable record.
State the access requirement, show the relevant configuration, include the allowed and denied results, and explain one limitation. Then practice a two-minute verbal walkthrough without reading your notes word for word.
This session is important because building and communicating are different tasks. A working lab buried in private folders doesn't automatically help someone understand your capability.
Keep the document short enough that you can actually finish it.
Sunday: spend 45 minutes deciding what happens next
Review the week's result against the original finish line.
If the tests are complete, choose the next requirement. If the project remains unfinished, identify the smallest remaining action. Don't automatically restart the entire plan or buy another course.
Also check energy and scheduling. A plan that repeatedly clashes with your life needs adjustment, not a more aggressive motivational speech.
The total is five hours: concept study, two lab sessions, a career action, documentation, and review. Each block has a job, and the blocks support one another.
The Six-Figure IAM Career Playbook provides the role-selection process, three lab directions, and a 90-day structure behind this kind of weekly planning. It's $9 for a practical guide to choosing what matters next.
The calendar is useful when it produces evidence and decisions. Filling every square with study time is not the same thing.