One of our core systems went down nine minutes before we opened.
My first reaction wasn't calm. It was frustration, followed by a quick spike of anxiety. This was the system that had to be up, and the clock was running. If you've ever had a system fail right before a deadline, you know the feeling.
Then I asked a different question: what is actually mine to fix here?
That one question changed the morning. I wasn't the person who could fix the hardware, so I stopped trying to be. I said it to myself plainly: this is beyond me. Do what you can, and let the rest go. Then I did the part that was mine. I reported it, found out who was already working on it, and kept the team moving. It got fixed.
Later that day, a different problem showed up. A system that normally gives clients a record of the transaction stopped producing one for a certain type of request. When the process leaves no audit trail, people are left saying "trust us," which is a poor substitute for a record. Meanwhile, the answer from support was a fair one: submit a ticket.
So I made the same sort of move again:
1. Is it mine to fix? If yes, fix it. If not, say so out loud. Naming what isn't yours is what keeps frustration from turning into a spiral.
2. Who owns it, and do they know in writing? A phone call disappears. A ticket or a dated email is a record that the problem was reported, when, and by whom.
3. What protects people in the meantime? When a system fails, ask what keeps clients and your team covered until it's fixed. Sometimes that's a manual log. Sometimes it's keeping a printed copy. It's rarely glamorous, and it's usually what matters most later.
Small specialist firms tend to handle this one of two ways. Some spiral, treating every failure as an emergency. Others shrug and hope somebody handles it. Both leave you without an owner and without a record, and that is where small problems turn into expensive ones.
Calm doesn't mean you don't feel it. I felt all of it that morning.
Some people take a system failure as a personal failure. Something breaks on their watch, and it lands like a verdict on them.
It isn't. It's a business emergency, and that's real. But a business emergency isn't always your emergency, and it doesn't always have to be yours right now.
Separating the two is what lets you act instead of spiral. The skill is in what you do next: sort the problem, name the owner, protect the people, and let go of the rest.
Next time something breaks, try asking: what is mine, who owns the rest, and what covers us until it's fixed?