Six ITOps Myths Hospital Office Teams Should Retire

Health Tech

Administrative teams in specialty hospitals hear plenty of confident advice about technology, much of it contradictory. A supplier says everything needs a formal approval board. A consultant says a new platform will fix it all. A colleague swears the shared spreadsheet is fine. When it comes to ITOps, the day-to-day running of the technology that supports front desks, billing and scheduling, a handful of myths do the most damage. This is a non-clinical, no-nonsense look at six of them, tested against what the Ops Atlas says about the field.

To be clear about scope: nothing below touches treatment, outcomes or patient decisions. It is only about office systems and the routines that keep them dependable.

Myth 1: “Good practice means a review board must approve every change”

Reality: no. The Atlas lists this belief by name as a myth. Under ITIL-style practice, low-risk, repeatable changes are meant to be pre-authorised, which means approval is granted for the pattern once and the work then proceeds. Normal changes get assessed. Emergency changes are done immediately and reviewed afterwards. A team that sends a font update and a database migration to the same board will either choke the board or train people to avoid it.

What to do instead: write down your three lanes and put every recurring task into one of them. Revisit the routine lane if routine tasks begin to fail.

Myth 2: “More approvals make changes safer”

Reality: the evidence is thin. The Atlas reports that the DORA research programme found no evidence that external approval reduces failed changes, and it recommends peer review by people close to the work. It also lists “adding process after every failure” as a pitfall, because layers pile up while the real cause remains untouched. Peer review means a colleague who understands the system reads the plan before it goes live. That is cheap, quick and tends to catch the slip a lone author misses.

What to do instead: require a second reader for anything non-routine, and review failures to find which rule would have prevented them.

Myth 3: “Our ticketing software is our service management”

Reality: the software records the practice; it is not the practice. The Atlas separates the function (people and roles), the practices (ITSM) and the technical tooling (ITOM). Buying a tool without the habits behind it gives you an expensive inbox. A team that triages consistently, investigates repeats and reviews failures will get value from a modest tool, while a team that does none of these will not get it from a costly one.

What to do instead: define the routine first, on paper, then pick software that supports it. Write-it-down habits matter more than features, as this article on keeping a simple budget book and building steady money habits shows for household records.

Myth 4: “The inventory of systems must contain everything”

Reality: a record that tries to hold every item turns into something nobody trusts. The Atlas says a configuration database needs what decisions require. Its sample check on ten entries found nine complete, two stale for over 60 days, one with no links and one with a repeated serial number. In an office setting that translates to a short sheet naming the systems that would halt the front desk if they went down, each paired with an owner and a supplier contact.

What to do instead: shrink the list until you can verify it, then expand deliberately. A smaller, correct list beats a large, stale one every time.

Myth 5: “Alerts are a luxury; we will notice when something breaks”

Reality: users notice, but late, and often through a frustrated phone call. Monitoring exists to spot trouble first. The Atlas adds a twist: the alerting layer must itself be regarded as production. If it fails without a sound, outages hide behind a green dashboard. Teams should also group related alerts so a single fault does not generate a pile of messages. In the Atlas exercise, thirteen alert rows produced two incidents.

What to do instead: test one harmless alert every month and confirm a person receives it. Planning around busy periods helps too; the thinking in this household piece on planning festival-time gifts and bills with a budgeting app is a good model for scheduling work around peak demand.

Myth 6: “A fix-time target is just a number”

Reality: a target is a clock, and a clock has rules. The Atlas example sets four hours around the clock for the top priority, eight business hours for the next, twenty-four for the third and forty for the fourth, with no target for the lowest. It then shows a ticket that ran for 92.5 elapsed hours yet counted only 4.5, since weekend and holiday pauses applied. Of eight tickets in the exercise, six met target, or 75 per cent. Without the pause rules, nobody could explain why a ticket that looked ancient had still met its target.

What to do instead: publish the priority table and the clock rules together. Staff and suppliers should read the same page.

A bonus myth: “The two DORAs are the same thing”

They are not. The Atlas flags the mix-up explicitly: the first is research into how software teams ship, the second is an EU law on digital resilience for financial firms. Administrators in a hospital context should not assume either applies to them without checking with a qualified adviser.

Why the myths persist

Myths survive because they contain a kernel of sense. Approvals do reduce risk in some settings. Tools do help. Lists do matter. The Atlas does not dismiss the underlying concerns; it asks that each be applied in proportion. For a full view, read the Ops Atlas explanation of ITOps scope, practices and common anti-patterns, which lists several of these errors under their proper names.

A simple way to test your own beliefs

  1. Write down the three most common things your team says about IT processes.
  2. For each, ask what evidence supports it in your own logs.
  3. Change one rule based on what you find, and measure whether things improve.

That small experiment is the whole discipline in miniature: observe, adjust, record. Skip the folklore, keep the notes.