When people hear that I reread my written goals once a month, the same handful of questions come up. Is it not overkill? What if I have no goals written down yet? Does it really change anything? Fair questions all. This page collects the most common ones from DevOps learners and working engineers, with short, honest answers. If you are new to the idea, think of it as a small appointment with yourself where you check whether the aims you set earlier still make sense.
So what is this monthly reread, in practice?
Picture a brief standing appointment, around half an hour, where you open your written goals and read them slowly. For each, you decide whether it should stay as it is, be reshaped, or be set aside. Then you write down what you decided and why. Nothing else is involved: no software and no special template. A plain text file or a paper notebook is fine.
Why monthly and not weekly or yearly?
Weekly is too frequent for most goals, because little changes in seven days and the review becomes a chore. Yearly is too slow, because by the time you look, an aim may have been stale for ten months. A month is long enough for real events to happen, such as a new project, a team change or a finished course, and short enough that you remember what you were thinking when you wrote the goals.
I have no written goals. Where do I start?
Write three. Choose one about your work, one about learning and one about how you spend your time. Keep each to a sentence, such as “Build a small automated deployment for a hobby project” or “Understand how my team’s alerts get routed.” Do not aim for perfection. A rough list you will reread beats a polished one you will not.
How do I know if a goal still fits?
Ask three plain questions. Would I write this goal again today? Did anything in the last month push me toward it or away from it? If I dropped it, what would I actually miss? If the answers are yes, yes and something specific, the goal fits. If you shrug at all three, it probably does not.
Is dropping a goal a bad sign?
No. Dropping a goal can be the most useful decision of the month, since it frees attention for what matters now. For example, you may have planned to study a particular configuration tool, only to find that your team has settled on another one. Letting the first aim go is an accurate response to new information, not a lack of discipline.
Can you give an example from an engineer’s week?
Certainly. Imagine someone whose goal in spring was “learn to write infrastructure templates.” By summer the person has written a few and found them comfortable. At the reread, the goal has outlived its usefulness as written. A better version might be “review other people’s infrastructure changes with confidence.” Same spirit, higher level, and now it matches the skill gap the engineer notices at work.
What about culture-related goals, like communicating better?
These are the hardest to check, because progress is hard to see. The reread helps by asking for a recent example. What was one conversation last month where you used the habit you wanted? If you cannot recall one, shrink the goal to something observable, such as “write a short summary after each incident review.” If you are interested in the people side of delivery, a related read is an article about steering culture change during a DevOps rollout, and it can help you word such goals more precisely.
Does the vocabulary matter?
More than you would think. Vague words make goals hard to test. If a goal says “understand pipelines” you cannot tell at the next reread whether you did. If it says “explain to a colleague, in five minutes, how our build moves to production,” you can. When a term in your own list is fuzzy, look it up. Something like a beginner-friendly glossary of core DevOps terms is useful when you are tightening the language.
Should I share my goals with anyone?
It is up to you. Some people prefer to keep the list private, and the habit works fine that way. Others tell one colleague or friend, and the monthly reread becomes slightly more reliable because someone might ask how it went. The point is not to perform for an audience but to make a regular check feel normal.
Where do outside courses fit in?
Course goals deserve the same scrutiny as any other. For a sense of how another profession arranges its study, take a look at the AirCrewU site, which presents an online learning platform for aviation professionals; it labels itself independent. You do not need to study anything from it to benefit from the comparison. The point is simply to ask, each month, whether the learning on your list is still the learning you need.
When will it start to feel worthwhile?
Expect a shift around the second or third session. The list gets shorter. The words get sharper. You find yourself saying no to something because it is not on the page. None of that is dramatic, but over a year it adds up to a calmer, more deliberate way of working.
How many goals is too many?
For one person, more than five or six active goals usually means some are decorative. Count only the ones you could name a recent action for. If a goal has no action in the last two months and you still cannot bring yourself to retire it, move it to a short “later” list and see whether you miss it. Often you will not, and the main list becomes much easier to read.
Can a team do this together?
Yes, with one adjustment. Individual goals are about preferences, while team goals are about agreements, so the reread needs everyone who owns the goal. Keep the session to the same half hour, read the goal text aloud, and ask whether the reason it was agreed still applies. Record any change in the place the team already uses for decisions, so the outcome does not live only in someone’s memory.
What if I skip a month?
Then do it next month. Do not punish yourself and do not try to make up for lost time with a giant session. If you skip two or three months in a row, that is information: perhaps the date is wrong, perhaps the list is too long, perhaps the format is a poor fit. Change the routine, not your opinion of yourself.
What does a good session look like from start to finish?
- Open the list and a blank note for decisions.
- Read each goal slowly. Pause on any that make you wince.
- Answer the three questions above, briefly.
- Mark each goal as unchanged, reworded or retired, and write one line of reasoning.
- Choose one goal to move in the coming week and write its first small step.
- Close the file and book the next date.
Anything else I should know?
Be patient with the first few rounds. The list will feel awkward until you have trimmed it a couple of times, and your sense of what a good goal looks like will sharpen with practice. Treat each session as a small experiment rather than a test, and remember that nobody else needs to approve of what you decide.
If you read this far, you already have enough to begin. Open a blank file, write three goals and set a date one month from now. Then, when that date arrives, come back to the questions above and use them as your script.









