{"id":1179,"date":"2026-11-16T06:10:00","date_gmt":"2026-11-16T06:10:00","guid":{"rendered":"https:\/\/pilottrainingus.com\/blog\/?p=1179"},"modified":"2026-11-18T11:10:00","modified_gmt":"2026-11-18T11:10:00","slug":"itops-six-myths-flight-deck","status":"publish","type":"post","link":"https:\/\/pilottrainingus.com\/blog\/itops-six-myths-flight-deck\/","title":{"rendered":"Six ITOps Myths Tested Against the Evidence, Flight-Deck Style"},"content":{"rendered":"<p>Aviation has a long tradition of testing folklore against the data: a rule of thumb survives only until an accident report or a maintenance trend contradicts it. Information technology operations deserves the same scepticism. ITOps, the work of keeping an organisation&#8217;s services dependable day after day, is surrounded by slogans that people repeat with great confidence, and several of them fall apart when you read what the published frameworks and research actually say. Six slogans follow, each weighed against what the Ops Atlas entry reports and against everyday experience, written for anyone who runs the systems behind an instructor-led school, a charter operator or a pilot-training portal.<\/p>\n<h2>Myth one: &#8220;The framework demands a committee for every change&#8221;<\/h2>\n<p>It is a popular belief that the main ITIL guidance forces every alteration through a review board. The entry summarised at <a href=\"https:\/\/www.xopsschool.com\/itops\/\">xOps School&#8217;s ITOps page<\/a> says otherwise: changes come in kinds. Standard changes are low-risk, repeatable and pre-authorised, so nobody convenes anything for them. Normal changes are assessed. Emergency changes happen immediately, with a review afterwards.<\/p>\n<p>Think of how a flight department treats a wheel-chock swap compared with an engine component replacement. Nobody calls a meeting about the chock. The myth survives because organisations apply one slow path to everything, and the Atlas lists that habit of treating every change the same among its warning signs, and rightly so, because it wastes effort on trivia while starving the risky items of attention. The evidence-led reading is that the framework asks you to sort changes by risk, and the review board is for the genuinely uncertain ones.<\/p>\n<h2>Myth two: &#8220;More approval means fewer failures&#8221;<\/h2>\n<p>This one feels obvious, which is why it deserves data. The Atlas reports that the long-running DORA research programme found no evidence that approval by an external body reduces the rate at which changes fail, and that it points toward peer review instead. The same entry describes the review board&#8217;s role as moving from gatekeeper toward designing the process and sharing information.<\/p>\n<p>There is a wrinkle worth stating precisely. A different DORA, the European Union regulation on digital operational resilience, is law, not research, and it still requires an approval function that is independent from the people who build the change, plus after-the-fact approval of emergency changes. The Atlas is explicit that the two should not be confused. So the careful conclusion is that in the absence of a legal duty, a second pair of eyes from a colleague gives more value than a distant signature, while where the law applies, you follow the law.<\/p>\n<h2>Myth three: &#8220;ITSM is the ticketing software&#8221;<\/h2>\n<p>Buy the tool, the thinking goes, and the discipline arrives with the box. The Atlas separates three things: the function of people and roles, the set of practices they follow, and the technical tools that observe machines. The ticketing product only records the practice. If the practice is muddled, an expensive tool will faithfully record the muddle.<\/p>\n<p>The aviation parallel is a flight-planning app. It stores your route, fuel and weights beautifully, but it cannot make a poor plan into a sound one. Vendors, the entry adds, even disagree among themselves about where the borders lie: one large vendor places monitoring tools inside ITOps, while another elsewhere calls the terms interchangeable. Treat vendor vocabulary as marketing and the frameworks as a shared language.<\/p>\n<h2>Myth four: &#8220;A good inventory contains everything you own&#8221;<\/h2>\n<p>Completeness sounds like diligence. A register of every cable and licence goes stale within weeks, and then nobody trusts it, which defeats the purpose of keeping one. The Atlas calls out the opposite principle: the configuration records should hold what decisions require. If you never decide anything based on the colour of a monitor stand, do not record it.<\/p>\n<p>A small worked check in the entry shows how to measure health. Take ten records and count the problems: in the sheet&#8217;s example the tally was nine fully filled in, two untouched for over two months, a lone record with nobody responsible and a pair sharing one serial number. That is a manageable, quantified picture. A register with fewer, correct entries beats a sprawling one that nobody has the energy to audit. Compare it with an aircraft parts log: it has to be accurate for the components that affect airworthiness, and it does not need to catalogue the coffee machine.<\/p>\n<h2>Myth five: &#8220;An alerting system is a side project&#8221;<\/h2>\n<p>Teams treat monitoring as a convenience that can be switched off during maintenance, rebuilt at leisure, or left unwatched at weekends. The Atlas warns that the event layer is part of production. When it fails silently, outages stay invisible, and the first notice is an angry message from a user.<\/p>\n<p>The data-minded takeaway: measure the alarm itself. The entry&#8217;s worked lab takes thirteen alert rows and shows how grouping rules turn them into two incidents inside a fixed window, with three late arrivals opening three more after the window closes. Two things follow. First, grouping rules change how many incidents your team sees, so they are a configuration decision with consequences. Second, you should test that the alarm fires by tripping it deliberately every so often, as you would test a stall warning on the ground.<\/p>\n<h2>Myth six: &#8220;A clever model can predict which changes will break things&#8221;<\/h2>\n<p>Prediction is seductive. One preprint noted in the Atlas, from a Canadian bank&#8217;s research group and not yet peer reviewed, describes a machine-learning model that caught nearly two-thirds of the changes later tied to serious outages, while the bank&#8217;s existing questionnaire caught about one in five. The numbers are real, but the same entry applies the base-rate arithmetic: precision was 0.55 on 203 changes, of which 35 caused major incidents. If you applied such a tool to ten thousand changes at a one per cent failure rate, only around six per cent of the flags would turn out to be real.<\/p>\n<p>Read that as an aviator reads a new warning system: useful as an extra input, dangerous as the only input. A model that catches many of the bad changes will still raise a pile of false alarms when failures are rare, and people stop believing it. The sensible position is to keep a written risk score with weights, use any model as a second opinion, and review every failed or emergency change.<\/p>\n<p>There is one more habit from the evidence worth borrowing from flight safety: write down why a decision was made while it is fresh. When a change fails, the review is far more useful if the record says what the team believed, which risk score it received and who looked at it. Without that, the post-mortem turns into recollection and blame, and the same myth quietly returns the following quarter. Aviation learned this lesson through incident reporting cultures, and operations teams can copy it for nothing.<\/p>\n<p>Likewise, keep the numbers you do publish honest. If you claim that your help desk meets its targets, say how the clock works and which tickets were paused. In the entry&#8217;s service-level lab, one ticket stayed open nearly four calendar days across a weekend and a public holiday yet used under five hours of its target clock, and a set of tickets where six of eight tickets met target gave seventy-five per cent. Both figures are right; they just measure different things, and a reader deserves to know which one they are looking at.<\/p>\n<h2>How to apply the evidence, not the folklore<\/h2>\n<p>What do the six corrections share? Each swaps a blanket rule for a question about risk and evidence. Sort changes by kind. Prefer peer review. Let the tool record and not replace the practice. Keep the inventory to the decisions it supports. Test the alarm. Treat predictions as odds, not verdicts. These are habits a training organisation can adopt without a large budget.<\/p>\n<p>If you are reading this because your school or club has grown beyond what one volunteer can manage, start with the smallest step: write down your three most frequent faults and how you fixed them last time. The discipline of removing repeat faults is where the evidence is strongest. For related reading on staying methodical in training, our notes on <a href=\"https:\/\/pilottrainingus.com\/blog\/weather-study-tips-for-student-pilots\/\">study routines for weather theory<\/a> and the walkthrough on <a href=\"https:\/\/pilottrainingus.com\/blog\/complete-guide-to-building-flight-hours\/\">planning how to accumulate flight hours<\/a> show the same pattern of replacing hunches with logged evidence.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Six popular beliefs about IT operations checked against published frameworks and research, with parallels from aviation maintenance and flight planning.<\/p>\n","protected":false},"author":6,"featured_media":1180,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[664],"tags":[],"class_list":["post-1179","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-aviation-tech"],"_links":{"self":[{"href":"https:\/\/pilottrainingus.com\/blog\/wp-json\/wp\/v2\/posts\/1179","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pilottrainingus.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pilottrainingus.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pilottrainingus.com\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/pilottrainingus.com\/blog\/wp-json\/wp\/v2\/comments?post=1179"}],"version-history":[{"count":1,"href":"https:\/\/pilottrainingus.com\/blog\/wp-json\/wp\/v2\/posts\/1179\/revisions"}],"predecessor-version":[{"id":1290,"href":"https:\/\/pilottrainingus.com\/blog\/wp-json\/wp\/v2\/posts\/1179\/revisions\/1290"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pilottrainingus.com\/blog\/wp-json\/wp\/v2\/media\/1180"}],"wp:attachment":[{"href":"https:\/\/pilottrainingus.com\/blog\/wp-json\/wp\/v2\/media?parent=1179"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pilottrainingus.com\/blog\/wp-json\/wp\/v2\/categories?post=1179"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pilottrainingus.com\/blog\/wp-json\/wp\/v2\/tags?post=1179"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}