Another year in IT can add responsibility, or it can repeat work you already know. The two experiences may prepare you for different next jobs.
Choose the responsibility you want to be trusted with next. That is more useful than simply deciding to gain another year of experience.
Look at the assignments available now and ask what each would let you demonstrate afterward. Then discuss a bounded opportunity with your manager, including the support and approval needed, before treating time in the role as your growth plan.
Describe the responsibility you want to add
Suppose you currently fulfill approved access requests. A useful next responsibility might be investigating why those requests regularly fail, documenting the causes, and proposing a safer process.
That is a specific change in scope. You would move from completing a known procedure to understanding and improving a recurring problem.
Another person might be ready to support application onboarding. Someone else might need experience explaining access decisions to business owners.
The right choice depends on the work you want next. There is no universal ladder where every technician must collect the same experiences in the same order.
Compare assignments by the experience they would produce
Imagine two available assignments:
| Assignment | What it might help you demonstrate |
|---|---|
| Another familiar support queue | Prioritization, consistency, and service ownership at greater volume |
| A bounded access-change project | Investigation, proposed changes, testing, and documentation |
The project may be more relevant to an engineering-oriented goal. That doesn't make additional operational work worthless; it answers different questions about your capability.
Write one sentence for each option describing what you'd be able to explain when it is finished. “Handled more requests” and “evaluated a change with tests and a rollback plan” point toward different responsibilities.
Choose the experience that addresses your next gap rather than the assignment with the more impressive name. Also check that the project offers realistic supervision and authority, not simply extra accountability without support.
Ask for a bounded opportunity, not a vague promotion
A manager can respond more easily to a small proposal than to “I want to do more security.”
Try: “I would like to document the recurring access failures for this application, identify the common causes, and review a proposed improvement with the application owner.”
State the scope, the expected output, and who would approve changes. Make clear that you are not asking for unrestricted administrator access or permission to experiment on production.
An effective development opportunity can begin with observation and documentation. Ownership should grow with demonstrated capability and the organization's actual needs.
Check whether the environment can support the move
Your manager may agree with the goal but have no project, mentor, budget, or opening available.
That information matters. It means you should distinguish a preparation problem from an opportunity problem.
You can still build a lab, study a relevant topic, or apply elsewhere. What does not help is treating an unavailable internal path as evidence that you need another unrelated qualification.
For a structured way to evaluate the employer side, see the signs that a role has stopped offering useful growth.
Set a review date and define progress
Choose a reasonable checkpoint. At that point, ask whether you have gained a new responsibility, completed a relevant project, or gathered evidence that supports an application.
Do not measure progress only by how busy you felt. You can be exhausted without being better prepared for the role you want.
Also leave room for life. A stable job can be a deliberate choice while you handle family, health, or financial priorities. The problem is not staying. It is staying without understanding the tradeoff.
The Six-Figure IAM Career Playbook connects role selection, skill gaps, and portfolio work so that “get more experience” becomes a practical plan. It is a $9 guide, not a promise that tenure or a project automatically produces a raise.
Before planning another year, decide what you want that year to make you capable of owning.