Hana (an invented name, standing in for many real people) started her career answering phones on a service desk. Three years later she was designing the rules by which that desk decided what to fix first, and a year after that, engineers on other teams were asking her how to write a change request that would not be bounced. She never changed employer. She simply learned the craft of ITOps, one skill at a time, and that craft is among the most portable foundations a technology worker can own.
This piece follows her path as a way of showing which skills matter, in which order, and how to prove them. Her story borrows its vocabulary from xOps School’s Ops Atlas, where the page on the ITOps discipline sketches a field responsible for keeping IT services up, with duties spanning requests, incidents, repeat-cause removal, change control and an estate map.
Year one: learning to listen and to sort
On her first day Hana expected technical puzzles. What she got was a queue of people describing their problems badly. “The system is down” could mean one user’s expired password or an entire building without a network. Her first real skill was interviewing: asking what changed, who else is affected and what the person was trying to do.
Her second skill was sorting. A forgotten password is a routine request; a payroll screen that loaded yesterday and fails today is an incident. The difference matters because they follow different lanes with different clocks. The Atlas gives a sample of how priority can be calculated, where impact plus urgency minus one yields a rank in one popular platform. Hana kept the principle and ignored the product. Ask how many people are hit, ask how fast the damage grows, and combine the answers in a written rule.
A skill that rarely appears in job ads, but that Hana credits for her first promotion, was writing a ticket note that a stranger could pick up at 3 a.m. and continue without calling her. Practise this early. It costs nothing and shows up in every performance review.
Year two: understanding the clock
By her second year Hana was handed the service targets. The company’s desk used a table with five priority levels. In the Atlas lab, the first has four hours around the clock, the second eight business hours, the third twenty-four hours, the fourth forty hours and the fifth has no target at all. The numbers themselves matter less than the discovery she made: tickets often looked late when they were not, and looked fine when they were not.
The reason is calendar rules. One Atlas example has a ticket spanning 92.5 hours of wall time that only used 4.5 hours of its allowance because weekend and holiday pauses stopped the count. In the same lab, six of eight tickets met their targets, giving 75 percent. Hana learned to read any percentage with a question: which tickets, measured how, with which pauses?
If you are building a similar skill, practise by taking any ten tickets from your own team and recalculating their elapsed time by hand under the written rules. You will find at least one surprise, and finding it yourself is more convincing than being told.
Year three: change, risk and the art of the short meeting
Then came change. Hana joined the weekly review and quickly noticed that the meeting did two different jobs. Half the items were routine, such as adding an account type or rotating a certificate by a known recipe. The other half were genuinely risky. The Atlas sorts them into standard (pre-authorised), normal (assessed) and emergency (immediate) changes, and her proposal to the board was almost embarrassingly simple: stop discussing the first group.
She then helped draft a score. Three factors, a number for each, a threshold. The Atlas teaching example has a score of 6 from 3 for a high tier, 2 for a schema change and 1 for working outside the window. Her own version used different factors but the same logic, and meetings dropped from ninety minutes to twenty. The career lesson: people who reduce meeting time without reducing safety get noticed fast.
Hana also learned a harder truth. Process added in anger after an incident tends to stick forever. The Atlas names that reflex as an anti-pattern, and her reviews now ask whether any new rule replaces an old one.
Year four: the map and the argument about scope
Her next project was the register of what the company owned. She expected a big technical migration and got a negotiation. Every team wanted its own items listed, and nobody wanted to maintain them. Hana fought for a narrow design: only items that influence decisions, each with an owner and a confirmation date. The Atlas supports this view, noting that a register should hold what decisions need rather than everything imaginable. Its sample health check found nine of ten records complete, two stale, one orphan and one duplicate serial number, and Hana’s first audit looked remarkably similar.
For readers on a similar track, this is a good moment to look at the wider shape of a career in this area. Our guide on fifty essential terms for beginners in the field is a solid vocabulary companion while you build up to that level.
The habit that ties the years together
Looking back, Hana says every stage rewarded the same habit: writing down what she decided and why. Early on that meant ticket notes, later it meant score sheets and register entries. Managers rarely remember who fixed a particular outage, but they remember the person whose documentation made the next outage shorter. If you can only invest in one skill this quarter, invest in clear, dated, honest records.
Credentials, frameworks and what employers actually ask
Hana never chased every certificate, but she learned which ones signal what. According to the Atlas timeline, ITIL began in 1989, published by a British government body and eventually spreading across about thirty books. The fourth edition arrived in 2019 with practices replacing the older lifecycle, and its publisher announced a fifth edition in January 2026, to be released in phases. The earlier edition stays available, and the Atlas calls the framework optional.
For organisations that want an auditable standard, ISO/IEC 20000-1 is the certifiable option, with the 2018 version amended in 2024. COBIT 2019 from ISACA frames governance as forty objectives. FitSM, a free standard from an EU project that ran between 2012 and 2015, suits small teams. Knowing these four names and what each is for lets you speak to hiring managers across industries.
On the tooling side, the Atlas lists several platforms in use in October 2026, including two commercial service-management products and two open-source ones. Do not try to learn them all. Learn the practices, then pick one tool and build a small sandbox with realistic tickets. Employers care that you can explain why a record exists, not only where to click.
Regulation as a career accelerator
One more thread worth knowing: regulated sectors need people who can talk operations and compliance in the same sentence. The Atlas mentions the European financial-sector resilience regulation, in force since 17 January 2025, and the NIS2 directive with its staged reporting duties. Understanding the idea behind these rules, such as independent approval and documented incident handling, makes you valuable on projects where operations and legal teams must cooperate. Treat this as background reading rather than legal guidance.
A skills ladder you can copy
- Interviewing and sorting: separate requests from incidents and record both clearly.
- Clock literacy: calculate elapsed and counted time under written rules.
- Change judgment: place work into pre-approved, assessed or emergency routes.
- Register keeping: maintain a small, confirmed list of what matters.
- Facilitation: run a twenty-minute review that ends with named owners.
- Translation: explain operations choices to developers, managers and auditors.
People who move across teams will also benefit from reading about managing culture change when delivery practices shift, because most of Hana’s wins were about habits rather than tools.
Where Hana is now
Today she coaches newcomers at the same service desk where she began. Her advice is plain: write notes for the next person, learn the clock rules before you quote a percentage, and never let a tool’s vocabulary replace your own understanding. The craft is learnable, the ladder is visible, and each rung teaches something you can show in an interview.









