Skip to content

Reread Your DevOps Career Goals in Eight Practical Steps

Published November 21, 2026 by Beena Yadav

Here is a procedure you can finish in a single lunch break and repeat every month: reread the goals you wrote for your DevOps career and decide which ones deserve your next four weeks. No theory, no frameworks. You need a list, a timer and a willingness to be straight with yourself. The steps below assume you work in or near operations, delivery or infrastructure, but they apply to anyone who writes goals and then loses track of them.

What you need before you start

  • Your goal list in one place. If it is scattered across notes apps, chat messages and a paper pad, gather it first.
  • A timer set to thirty minutes.
  • A second note, empty, titled with the date. This is where decisions go.
  • One recent task from your job, fresh in your memory, to test the goals against.

Step 1: Read the whole list without touching it

Hold back from correcting anything yet. Read from top to bottom, once, at a normal pace. Notice which items provoke a small reaction: relief, boredom, guilt or interest. Those reactions are data. Jot a single word beside each in your decision note, but do not edit the list yet.

Step 2: Mark what has already happened

Some goals have quietly come true or been overtaken by events. Perhaps you wrote “learn the basics of a cloud provider” and then spent three weeks on exactly that during a project. Perhaps you wanted “be considered for a senior role” and your manager has since discussed it with you. Mark these as done or changed, and move them out of the way. This alone often removes a third of the list.

Step 3: Test each remaining goal against a real task

Take that recent job task and ask, for every goal, whether it would have helped. If you debugged a failed release, would your goal to learn a particular scripting language have made it easier? If a goal is unrelated to anything you did or wanted to do last month, it is a candidate to set aside. If it would have made the task clearly easier, it is a strong candidate to keep.

This step is deliberately concrete. A reread based on feelings alone tends to protect old goals out of loyalty. A reread tested against recent work tells you what your job is actually asking of you.

Step 4: Sort into three piles

  1. Still right. The goal fits and the wording works. Leave it alone.
  2. Right aim, wrong shape. The goal needs a smaller scope, a clearer end or a different pace. Rewrite it now, in one sentence.
  3. No longer mine. Cross it out, date it and write why in a line. Do not apologise for it.

If you are moving between roles, this sorting is particularly useful. Someone shifting from a sysadmin background toward delivery engineering, for example, may find that goals about manual server care belong in the third pile while goals about automation belong in the second. For context on that kind of move, a walkthrough of moving from sysadmin and support into DevOps sets out what the transition often involves.

Step 5: Limit the survivors

Count what remains. If you have more than five active goals, pick the five that matter most this month and move the rest to a “later” section at the bottom. Fewer lines do not mean lower ambition; they mean you plan to act on every line left standing.

Step 6: Write the next step for each goal

Beside every surviving goal, write one action that takes under an hour and could happen this week. Be specific: “Read the first two chapters of the networking book,” not “work on networking.” Specific steps are easier to schedule, and at the next reread you can see whether they happened.

Step 7: Check the load

Add up the likely time needed for the next steps. If the total is more than you can realistically spare, drop the lowest-priority step, not the whole goal. Many monthly plans fail here, because they are written for an ideal month in which nothing goes wrong. Plan for the month you actually have, including the on-call week and the deadline you already know about.

Step 8: Book the next reread

Before you close the file, put the next session in your calendar, with a reminder, at a fixed time. First Sunday evening, last Friday lunch, whichever you will actually keep. Skipping this step is the main reason the habit fades. If the date is not booked, the reread is a wish.

A short example run

Suppose your list holds six goals. After step 2, one is already achieved and one has been replaced by a company decision to use a different tool. Four remain. In step 3, two clearly connect to your recent task and one connects loosely, while one connects to nothing. In step 4, you leave the two strong ones, rewrite the loose one so it relates to a concrete project and cross out the unconnected one. You now have three goals, each with a small action for this week, and you are done in twenty-five minutes.

Some people like to see how a long arc of progress is usually described before they set their own targets. A readable overview can be found in an account of how people progress from junior to senior roles in DevOps, which is a useful backdrop when you wonder whether a goal is pitched at the right level.

A word on how to word the next steps

Good next steps share three traits. They start with a verb you can picture, such as read, write, build, ask or compare. They name a thing small enough to finish, such as one chapter, one script or one conversation. And they carry a day, even loosely, like “Wednesday evening.” Steps without those traits tend to turn into reminders of what you did not do.

It helps to keep the steps honest about difficulty as well. If a step is something you have avoided for two months, say so in the note and make it smaller still, perhaps just opening the document and reading the first page. Nobody grades the size of the step. What matters is that the goal moves, and that your next reread has something real to look at.

Where outside learning fits

If your list includes courses, treat them like any other goal and test them at the reread. As a neutral example of how a specialist field organises its learning online, AirCrewU runs a website for aviation professionals and describes itself as an independent platform. You do not need that content to use these steps; the point is that whichever source you choose, the monthly test asks the same question: does this still fit my work?

Troubleshooting the routine

  • The list keeps growing. Add a rule that every new goal must replace an existing one.
  • Everything feels equally important. Return to step 3 and rank by how often a goal would have helped in the last month.
  • You skip the session. Shorten it to fifteen minutes and run only steps 1 to 4 until the habit sticks.
  • You keep rewriting the same goal. It is probably too big. Split it, and keep only the first half.

One last habit worth adding: keep every dated decision note in the same folder. Reading three of them in a row, usually around month four, shows you which kinds of goals you keep retiring and which kinds you keep finishing, and that pattern is more useful than any single session.

The procedure is plain on purpose. Run it for three months and compare your list to the one you began with. You will most likely find fewer lines, clearer wording and a better sense of where your evenings are going.