Mid-level managers don't usually get to make the call on the big, sweeping decisions. What we do get is the weekend-by-weekend reality of keeping equipment, schedules, and people aligned when one missed step threatens to take down all three. Here's what one bad weekend that turned into two taught me about the job.

The short version: a circulating water make-up pump motor needed replacing. A factory verification step got missed, my electricians improvised a fix, and we thought we were done by Friday. We weren't. The motor vibrated when we ran it, which meant balancing it with dampening weights, which meant losing the following weekend too plus a scramble for a vendor we almost couldn't get on short notice.

Here's what I'd tell another manager sitting where I was.

A week before the motor even arrived, my electricians flagged that someone needed to physically visit the factory and confirm the new motor's coupling would mate with the pump's. That task belonged to engineering. It didn't get done not because anyone refused, but because it was never anyone's job in a way that had real consequences attached to it.

Takeaway: when a verification step crosses departments, don't let it live as an assumption. Either the owning department is on-site to actually do it, or maintenance owns it outright. A task with no named consequence for skipping it will get skipped.

My electricians found old bolts that fit when the new ones didn't, and we had the motor bolted in by Friday. That felt like the finish line. It wasn't. The moment we ran it, a resonating vibration told us the real work… balancing the motor hadn't even started yet.

Takeaway: closing out the visible task isn't the same as confirming the system actually works the way it's supposed to. Before calling a repair done, ask what you haven't tested yet, not just what you've installed.

None of us had ever balanced a motor with dampening weights before. We needed a vendor, and we needed one immediately which meant calling around hoping someone could break away from other commitments. We got lucky. We almost didn't.

Takeaway: the moment a job has any chance of needing outside expertise, start that conversation early, even if it turns out you don't need it. Lead time is cheap when you have it and expensive or unavailable when you don't.

I didn't go on-site that weekend. I delegated coverage to my on-duty supervisors and stayed reachable by phone the entire time. At one point we lost supervision coverage for a stretch because a supervisor believed operations had released the crew, without confirming that with the duty maintenance manager first. Nothing went wrong in that gap but it could have.

Takeaway: delegating responsibility doesn't mean delegating the verification of that responsibility. A handoff between teams or shifts needs an explicit confirmation, not an assumption that someone else already covered it.

If you manage people who execute work that crosses departments, shifts, or outside vendors, here's where to spend your attention before the next job turns into two:

None of these are dramatic changes. They're small, unglamorous checks — which is exactly why they're easy to skip, and exactly why skipping them is what turns one rough weekend into two.