THE TEN MINUTES THAT COST TWO HOURS

Years ago, we were working overnight optimization for a major wireless carrier in Michigan.

During the day, the carrier would drive-test the network, measuring signal strength, patterns, and other performance metrics. At night, when network traffic was lower, we would go into the field and make physical adjustments based on what they found—antenna azimuth, electrical downtilt, and other changes intended to improve performance.

On this particular night, we had a lot in front of us: probably twelve or thirteen sites, a lot of miles, and a limited overnight window. We needed to keep moving.

There was one simple rule on my crew when entering a telecommunications shelter: When you open the shelter, leave the keys in the outside door lock.

There was a reason. These shelters didn't have a lock you could simply leave unlocked. The key allowed you to open the door, but once that door closed, it locked again.

And these weren't ordinary keys. They were controlled security keys issued by the carrier. You had to be authorized to receive them. They weren't something you could take to a hardware store and duplicate, and we didn't have spare sets sitting in the truck.

So the procedure was simple: open the door and leave the keys in the lock. Everybody knew it.

We arrived at our first site, completed the required paperwork, opened the shelter and signed the site logbook. Then we walked back outside to the truck to get the laptop and software we needed.

The door closed behind us.

I looked at the technician. “Where are the keys?”

He reached for the carabiner where we normally carried them. Nothing. We both knew immediately where they were: inside the locked shelter.

And because those keys provided access to the other sites, we couldn't simply skip this one and move on. We were stopped at Site 1.

The first reaction was urgency. Grab some tools. Maybe take apart part of the door. Find some way back inside and keep moving.

No.

It was around eleven o'clock at night. We were standing outside a secured telecommunications facility. The last thing we needed was to start beating on a door with tools and hammers looking like we were trying to break into the place.

We had already made one mistake. We didn't need to create another one trying to fix it.

So we stopped, worked through the problem, communicated what had happened and found another way to regain legitimate access to the shelter. We recovered the keys and went back to work.

We still completed the sites that night. But that one missed step cost us about two hours.

And why did we miss it? I think we were rushing.

We knew how many sites we had ahead of us. We knew how many miles we needed to cover. We were already thinking about the next thing instead of paying attention to the small procedure directly in front of us.

We were trying to save time. Instead, we lost two hours.

THE LESSON WASN'T ABOUT KEYS

Everybody already knew the rule. That's what stuck with me.

Sometimes a procedure, requirement, or standard can seem unnecessary. Why do we have to do it this way? Why does management require this step? Why do we have to check this every single time?

Sometimes we don't know the history behind the requirement. There is usually a reason.

Something failed. Production stopped. Equipment was damaged. A customer was affected. Someone got hurt. Somebody learned something the hard way and created a standard so the next person wouldn't have to learn it the same way.

That night also taught me something else: Telling somebody a procedure once doesn't establish a standard.

After that night, I became repetitive about things that mattered. “Where are the keys?” Next site: “Where are the keys?” Another night: “Where are the keys?”

Eventually nobody had to ask anymore. The behavior became routine.

THE HABIT STAYED WITH ME

I still pay attention to keys today.

At home, my keys go in exactly the same place every day. I can walk through the house, glance at that spot and know they're there.

On a field crew, truck keys need a designated location that everybody knows. That isn't just about convenience.

If somebody gets hurt and another crew member needs that truck immediately, that's not the time to discover the keys are in somebody else's pocket.

A small personal habit can become an operational problem when other people depend on you.

The same principle applies well beyond keys. Important things need a known place. Important procedures need consistency. And the small disciplines are often what keep the larger operation moving.

There will always be pressure to move faster. But urgency doesn't make the standard less important.

That night in Michigan, we were probably trying to save ten minutes. It cost us two hours.

We recovered. We finished the work. But I never forgot the lesson.

Standards are lessons we shouldn't have to learn twice.