Let’s start with a confession that a lot of people in operations quietly share: the reading list for an AIOps career skills plan grows faster than anyone can read it. Every few weeks there is a new framework to try, a new certification to sit, a new dashboard vendor to understand. When progress stalls, the reflex is to add one more course to the pile. This post argues for the opposite reflex. Before you add anything, look at what you could take away.

I know that sounds backwards for a field built on “more data, more signals, more models”. But careers are not models. A career has a fixed number of evening hours behind it, and the people who move forward fastest are rarely the ones who studied the most topics. They are the ones who decided what not to study.

Why the learning list keeps swelling

Adding is comfortable. Signing up for a course feels like progress even if you never open the second module. Bookmarking a tutorial feels like having learned it. Meanwhile, the real skills that make someone valuable on an operations team, such as reading a messy incident timeline, explaining a trade-off to a manager, and knowing which questions to ask of a system, get no new investment because they never show up as a purchase.

There is also fear underneath. AIOps is changing quickly, so people worry that skipping anything means falling behind. The fear is understandable, but it produces a study plan that looks like a grocery list written while hungry. Most of it will go off before you use it.

The subtraction audit: four things to look at first

Grab a piece of paper, or an empty note, and list everything you are currently “working on” in your skills. Then run each item through four questions.

1. Did I use it in the last month?

If you have a half-finished course on a topic that has not touched your real work in weeks, it is a candidate for removal. You can always pick it up again when a project demands it, and you will learn it faster then because you will have a real problem to attach it to.

2. Does it overlap with something I already know?

Three tools that all correlate events in slightly different ways teach you one idea three times. Pick the one your team actually touches, learn the idea well, and let the other two go. The concept travels with you; the product logos do not.

3. Can I explain it in two sentences?

If not, you may be collecting vocabulary rather than understanding. Drop the topics you cannot explain simply and keep the ones you can. Then deepen the kept ones.

4. Would my next role actually ask for it?

Read three real job descriptions for the position you want in a year. Highlight what repeats. Whatever you are studying that appears in none of them has to justify its place.

What a lean skill set looks like in practice

Here is a sketch of a trimmed-down plan for someone who wants to grow in AIOps. It is only an example; your own list will differ.

• Keep: one scripting language you can write without searching every line, the basics of how your monitoring data is collected, and a clear habit of writing short incident summaries.
• Keep: enough statistics to know when a graph is lying to you, such as why an average hides a bad tail or why a sudden change may just be a deploy.
• Park for later: the second and third observability products, deep-dive machine learning theory you will not use for a year, and any certification with no employer asking for it.
• Remove: the “someday” tab of fifty tutorials. If something matters, it will come back to you in a conversation.

Notice what happens after you cut. The plan fits into a normal week. You can finish things. Finishing, more than any single skill, is what hiring managers notice, because it shows up as a portfolio, a runbook you wrote, a small automation your team really uses.

Cutting inside your daily work, not only your study list

The same idea applies on the job. If you want to be seen as someone who understands AIOps, look at your team’s own routines and ask what could go. A weekly report nobody opens, a manual approval step that has never once been rejected, a meeting whose notes nobody reads. Removing one of those and writing down what changed is a better career story than adding a fourth dashboard.

If you are earlier in your journey, it helps to read how others describe a sensible starting path. This site has a step-by-step roadmap for people entering DevOps, and it is worth reading with a pencil in hand, crossing out what does not fit your situation instead of copying every item.

A story from a hallway conversation

A colleague of mine, a platform engineer with a few years behind him, once told me he felt stuck. His list had grown to include container security, a data-science course, two different cloud certifications, and a side project. He asked what to add so he could get promoted. I asked him what he would take off the list if he had to take off three things by Friday. He laughed, then went quiet, then named the data-science course, one certification, and the side project. Within two months he had shipped a small automation that cut an on-call chore, and that single piece of work became the centre of his promotion case. Nothing he added got him there. The space he cleared did.

Keeping a place where thoughts can breathe

One more subtraction worth trying is on the writing side. Many people in this field keep notes and half-drafts in six different apps. A simpler habit is to pick one quiet place to write down what you learned each week. One option is a blogging network like BlogOrbix, whose own pitch is a quiet writing space with the clutter stripped away. It can hold a plain public notebook for you. You do not need to publish anything impressive, and nobody is grading the prose. The point is that fewer tabs make it easier to think.

A simple monthly pruning routine

Make this a calendar habit, not a one-time cleanup. Once a month, set aside half an hour and do the following:

1. List your current learning items and cross out anything you did not touch.
2. Pick one item to finish properly in the next month, and only one.
3. Write one sentence on what you stopped doing and what you noticed afterwards.
4. Check that your real work still teaches you something. If your job gives you incidents to study, those beat any course.

If your day job already touches monitoring and events, you may find that the best learning source is sitting in your own logs. A beginner-friendly way to work through live IT problems can teach you more about correlation than a stack of videos, and it costs you no additional subscription.

When adding is still right

None of this means you should never add. Sometimes a real gap is blocking you: your team is adopting a tool next quarter, or a role you want clearly requires a skill you lack. In those cases, add deliberately, with a date and a reason attached. The test I like is simple. Can you name the project or conversation that will use this new skill within sixty days? If yes, add it. If no, put it on a “maybe later” list that you only revisit during your monthly review.

If you are introducing AIOps ideas to a team, the same discipline helps there. A plain walkthrough for introducing AIOps to your own operations group becomes much easier to follow when the team first agrees on what to stop doing, because the new practice then has room to land.

Questions to ask when the list feels too short

Sometimes, after pruning, people panic and think they have left themselves with too little. Give it two weeks before judging. Ask yourself whether you are making more progress on the things that stayed, whether your evenings feel lighter, and whether you can describe your current focus to a friend in a single breath. When all three come back positive, the list is not too short. It is finally the right size, and the same list will look bigger once you have actually finished what is on it.

The short version

When your growth feels slow, resist the urge to buy another course. Make a list, ask four honest questions, remove what fails them, and protect the time you free up. Your AIOps career skills will look smaller on paper and stronger in practice. Fewer topics, finished properly, tend to beat a long list that never leaves your bookmarks. Try one subtraction this week, then see what has room to grow.