INSURV / Information Architecture on the Deckplates

A Chief Petty Officer told me something in 1990 that my peers thought was strange.

We were at SWOS-DOC — what the fleet called baby SWOS — and he told a room full of new Ensigns that the best Surface Warfare Officers were jacks of all trades and masters of none. Not because depth didn’t matter. But because your people were the masters. Your job was to understand their work well enough to know what your decisions cost them — and to scope your expectations accordingly.

I stopped repeating it out loud after my peers looked at me sideways. But I never stopped using it.

It took four INSURV inspections to prove it.

What INSURV actually tests

The Board of Inspection and Survey is the hardest readiness event in the surface Navy. Five days. Every system. Every maintenance record. Every space. Ships that struggled — and many did — started losing ground on days one and two.

Not because of technical ignorance. The crews knew their equipment. What came apart was the coordination layer — parallel work streams drifting out of sync under pressure, each team focused on their own problem, nobody watching the whole picture. Time passed. The inspectors moved on. The ship never got it back.

I watched it happen to other ships. I never let it happen to mine.

What I built instead

Months before the inspection, I started spending a few minutes every week at PB4T (Planning Board For Training) and a few mornings each week at khaki call on a single theme: follow your PMS cards. Every time. To the letter. Regardless of how well you know it.

I made clear that I didn’t want to hear about anyone showing off their knowledge by doing maintenance from memory. The card wasn’t a test of whether you knew the procedure. It was the shared reference — the canonical description of the task that made every report up the chain mean the same thing. One maintainer improvising from memory breaks the coordination layer above him, even if the maintenance itself is perfect.

When there was time, I took my chiefs and officers to visit the INSURV team. We split up. We asked questions. We built a picture of what the inspectors needed to see — before the inspection — so we could sequence our work against it rather than react to it.

And then I got the chiefs to designate a tiger team.

The tiger team didn’t do maintenance. They set up on the mess decks and ran the information layer. They tracked status across every parallel work stream. They kept the inspectors moving to the next space. They made parts runs when something needed to be repaired or replaced. They received reports as maintenance completed, maintained the picture, and escalated exactly one category of problem: the things that needed CO or XO authority to resolve. Everything else they handled.

A few weeks before the event, we rehearsed the whole thing. Not the actual maintenance — the information flows starting with grabbing the cards, getting the tools together, reporting completion. I needed to know the coordination layer would hold under load before the inspectors arrived.

It held. Four times, across four ships. All four finished with remarks I’ll leave out of this post because they’re the kind of thing that sounds like bragging. The chiefs who ran those tiger teams earned every word.

The CO’s bet

My CO on USS Patriot was stressed. Genuinely stressed. He’d seen ships fall apart during INSURV and he couldn’t see, from the outside, why mine would be different.

So he made a bet. If it goes as easy as you say it will, he said, I’ll buy dinner for you and your wife.

It was a very nice dinner.

I like to believe that he thought he was paying for was my confidence. What he was actually paying for was the tiger team — and the Chief Petty Officer who taught me to build one, and the Chief at SWOS-DOC who explained why officers needed to understand their people’s work well enough to design the system around it.

The architecture wasn’t complicated. It just had to be built deliberately. Most ships never built it.

Most ships lost the plot on day one and didn’t get underway on day three.