I spent 12 years in the U.S. Navy as a submarine service member, qualifying for my Silver Submarine Dolphins and earning six Navy and Marine Corps Achievement Medals along the way. When people ask me what the Navy taught me, they usually expect me to talk about teamwork or leadership. And while those matter, the most transferable thing I took away was simpler and harder than either of those: the ability to perform under pressure without letting the pressure show in your work.
Pressure Is the Standard, Not the Exception
On a submarine, there is no such thing as a low-stakes moment. Every system, every procedure, every checklist exists because someone before you learned the hard way what happens when standards slip. You aren't just following rules — you are part of a chain of accountability that keeps everyone alive. That context changes how you approach your work. It stops being about what's convenient and starts being about what's correct.
Early in my career, I managed personnel records and pay for sailors while simultaneously standing watch at battlestations. Missing a pay transaction or filing the wrong document wasn't an abstract error — it affected real people under real stress. Getting it right the first time wasn't a goal. It was a baseline.
"The Navy didn't teach me to work harder under pressure. It taught me to work the same — because that's what pressure-proof operations actually look like."
Systems Thinking Before I Had a Name for It
Submarines run on interdependency. Every department — engineering, navigation, weapons, supply — is connected. A failure in one area ripples into every other. Long before I sat in a supply chain classroom learning about upstream and downstream dependencies, I lived them. If a part wasn't logged correctly, maintenance got delayed. If maintenance got delayed, readiness dropped. If readiness dropped, the mission changed.
That experience gave me an instinct for thinking in systems rather than silos. In operations and supply chain work, that instinct is one of the most valuable things you can bring to a team. It's the difference between solving the symptom and solving the problem.
Accountability Without Excuses
One of the most direct lessons the Navy taught me is that accountability is not something you perform after something goes wrong — it's something you build into how you work every day. In my third award citation, I processed 71 post-patrol awards and 15 chief evaluations in 21 days from draft to final signature, in the middle of a command change. There was no option to ask for more time. The deadline existed because the mission required it, and my job was to meet it.
That mindset — own the outcome, find the path, deliver — is something I carry into every academic project, every role, every team I'm part of. It doesn't mean being perfect. It means not using imperfection as an excuse to stop moving forward.
What This Means in a Civilian Operations Role
When I transitioned out of active duty and into college studying Product and Supply Chain Management, I noticed something quickly: the technical skills were learnable, but the operational mindset I had was rare. A lot of people learn supply chain as a set of frameworks. I had already been living supply chain as a set of consequences.
That's the real lesson from 12 years of submarine service. It's not that the Navy made me tougher — it's that it made me more precise. Precise about documentation, precise about process, and precise about what it means to be accountable to the people who depend on your work being right. In operations, that precision is everything.
AI Use Attribution
AI assisted me in structuring this post and refining the flow between sections. The experiences, details, and perspective reflected here are entirely my own — drawn directly from my service record and personal history. AI helped me organize my thoughts into a readable narrative and suggested transitions between ideas, but all content was reviewed, adjusted, and verified against my actual experience before publishing.