The Zebra in the Server Room: Why Experienced IT Pros Don’t Stop at the First Answer

In IT, there’s an old saying:
“When you hear hoofbeats, think horses, not zebras.”

The idea is simple: start with the most likely explanation before jumping to rare possibilities.
And honestly? That’s good advice.
Most of the time, the problem is the obvious thing.
The user forgot their password.
The cable isn’t plugged in.
The printer is offline because someone turned it off.
The server issue is actually a power issue.
But after 30 years in IT, I’ve learned something:
Sometimes the zebra is standing right there wearing a name tag.
The danger of assuming the obvious
One of the biggest differences between a newer technician and an experienced one isn’t how many commands they know.
It’s how they think.
A newer tech might see:
“Users cannot access the application.”
The immediate assumption:
“The application is down.”
An experienced tech starts asking questions:
– Who is affected?
– When did it start?
– Did anything change?
– Is it everyone or only certain users?
– Is the application actually down, or is something underneath it failing?
Because IT problems are often like an iceberg. The thing people notice is usually just the part sticking out of the water.
The real problem is hiding underneath.
Troubleshooting is not guessing
Good troubleshooting is not throwing solutions at a problem until something works.
That’s called “trying random things and hoping.”
(Also known as the IT version of turning it off and back on again 47 times and pretending it was a strategy.)
Real troubleshooting is investigation.
You gather evidence.
You create a timeline.
You eliminate possibilities.
You test your theory.
You document what you learned.
That last part matters.
Because fixing a problem once is great.
Making sure nobody has to solve the same problem six months later is even better.
The experience you can’t Google
Technology changes constantly.
The tools change.
The platforms change.
The interfaces change.
But the fundamentals stay the same.
A good IT professional develops a sense for when something doesn’t quite add up.
You notice patterns.
You remember that weird issue from five years ago that looked exactly like this one.
You know that the error message is not always the problem. Sometimes it’s just the messenger.
That instinct comes from experience.
It comes from being the person standing in the server room at 2 AM wondering why production is down.
It comes from supporting users who say:
“It was working yesterday.”
(Which, in IT, is basically the opening line to a mystery novel.)
The best IT people know when to look for zebras
The goal isn’t to assume every problem is some rare, complicated issue.
That wastes time.
The goal is to know when the obvious answer doesn’t fit.
Because sometimes the problem isn’t the application.
Sometimes it isn’t the server.
Sometimes it isn’t the network.
Sometimes there’s a zebra in the server room, and your job is to notice the hoofprints.
After 30 years in IT, I’ve learned the most valuable troubleshooting tool isn’t a command prompt.
It’s curiosity.
Because the best IT professionals don’t just fix what’s broken.
They figure out why it broke in the first place.
Promptly Melissa 💻✨
30 years in IT. Still annoyed.