Building Ownership Through Crisis: The Accountability System They Created

We were two weeks from an inspection that could shut down all operations and remove the top three executives. I had just inherited responsibility for Arms, Ammunition, and Explosives accountability, a system I had never managed and knew almost nothing about.

The crisis demanded immediate action, but the lasting solution would come from the team, not from me.

The stakes were existential. Fail this inspection, and training operations would halt immediately. The command would face a complete external review of leadership. The top three officers would likely be removed. The optics would be catastrophic for the entire EOD community. We'd spend the next two years under intense scrutiny, fighting to rebuild credibility.

I had 72 hours to digitize our personnel qualification and certification system. It was the one piece I could control, and it had to be perfect.

The Arrival: No Plan, Maximum Chaos

I returned to the EOD Training and Evaluation Unit in June 2023 for what the Navy calls a "sunset tour," the final assignment before retirement in June 2025. I expected to teach, maybe mentor younger instructors, and coast toward the finish line with some dignity.

Instead, I walked into organizational chaos. The command was in the middle of a fundamental restructuring, transitioning from a division-based training model to a team-based approach. It was like rebuilding an airplane in flight, and everyone was focused on not crashing.

Because all leadership attention was consumed by the organizational transformation, there wasn't much thought given to where I should be placed or how I should be used. I wasn't assigned to lead a training team. I wasn't given a defined role. I was simply told: "We have an Arms, Ammunition, and Explosives inspection in two weeks. The current manager is leaving any day. You're taking over."

Throughout my 20-year career, I had been an end user of explosives and ammunition. I checked out materials, used them in training or operations, and returned them to the armory. I had never seen the administrative machinery behind the scenes. I wasn't a functional expert in AA&E accountability. I had to trust the people under me for the "truth" as they understood it and figure out the rest on the fly.

The Critical Vulnerability: Analog Records in a Digital World

The one piece of vital information I received was clear and urgent: our analog record keeping for personnel authorized to conduct AA&E operations had to be digitalized in a specific system before the inspection. This wasn't optional. It was a pass/fail requirement, and we were currently failing.

We tracked who was qualified and certified to handle explosives and ammunition through a combination of paper logs, individual training records, and institutional memory. It worked in the sense that we generally knew who could do what. But it didn't meet the standard for accountability in a formal inspection.

I needed to identify who had created the digital system the inspectors required, get detailed guidance on how to set it up correctly, and implement it across the entire command. I had three days.

I found out who had built similar systems at other commands and put our Qualifications and Certifications specialist in direct contact with them. No intermediaries. No bureaucratic approvals. Just: "Here's the expert. Here's the deadline. Make it happen."

He did a great job. With assistance from the inspectors themselves, who wanted us to succeed, he had the system operational in approximately three days. Every person authorized to handle AA&E was in the system with their qualifications, certifications, expiration dates, and authorization levels clearly documented and accessible.

When the inspection came, the pieces I had direct control over, particularly the qualification and certification process, were perfect. We passed that component without issues.

The other parts were not as clean.

The Accountability Gap: Where Systems Break Down

Tracking and recording Arms, Ammunition, and Explosives is similar to accounting. There's a secure software system that only one person in the office can access, and that person cannot be involved in any of the operations or physical movement of materials. The separation is designed to reduce the risk of theft or loss by ensuring the person who counts can't also be the person who moves things.

The system is old, breaks frequently, and takes significant time to update. This creates lag between physical reality and digital records, a dangerous gap in any accountability system.

As a training unit, people checked out gear regularly and returned it to the armory when finished. If the materials weren't firearms and teams had approved safes for secure storage, there was a process allowing them to check equipment out for a week at a time.

The last time our physical inventory had been fully updated in the system was about a month after the previous inspection—roughly 18 months earlier. We were able to account for all the gear and get physical eyes on it for the inspection, demonstrating we hadn't lost anything. But the records were a mess.

The inspection revealed a pattern of small clerical errors: incomplete documentation, missed follow through on administrative tasks, and failure to follow established processes. None of it indicated theft or loss. All of it indicated a lack of systematic accountability.

I understood this from an operator's standpoint. When you're focused on training teams for life or death missions, paperwork feels like bureaucratic overhead. There's always tension between what's sufficient for operational purposes and what's required for formal accountability.

But the systems shouldn't create unnecessary work, and they should provide immediate answers to questions. Our systems were doing neither.

Building Accountability From the Ground Up

In the immediate aftermath of the inspection, we made cultural and systemic changes designed to improve accuracy while working within the established frameworks. The crisis had given us a burning platform, but the lasting solution would come from the team designing a system they believed in.

I wasn't interested in imposing solutions from above. I wanted the people running day to day operations to build the accountability framework they knew would work in their environment. This wasn't about me being the hero who fixed everything. It was about creating ownership so the system would survive long after I was gone.

I facilitated an in depth review of current processes and asked the team to decide how the system needed to function. I had the inspection criteria ready and asked questions designed to test their proposals:

• Does this meet the intent of the requirement?

• Would this pass the inspection?

• Is this a system or process you can actually maintain?

• What are the consequences if I find you're not living up to your own standard?

That last question was the most important. I asked the team to determine the punishments or repercussions for accountability failures. This was their system, so they needed to define what happened when it wasn't followed.

They didn't like it at first. Nobody wants to be responsible for potentially punishing their colleagues or themselves. But creating the standards together built something more powerful than compliance. It built ownership.

The accountability system they designed had escalating consequences, each level chosen specifically by the team based on what they thought would be effective without being career ending:

• First infraction: Root cause analysis to identify exactly what went wrong and who was responsible. Immediate correction of the error. Assignment as "Duty Armorer," the on call person who had to respond after hours to let people into the armory and safes. This was inconvenient enough to be a deterrent without being career damaging.

• Second infraction: Written documentation in the individual's record.

• Third infraction: Command-level punishment, potentially affecting evaluations and career progression.

The brilliance of this approach was that it created internal accountability. People didn't want to let their teammates down, and they definitely didn't want to be stuck with duty armorer responsibilities because of sloppy paperwork. More importantly, because they had designed the system themselves, they couldn't claim it was unfair or unrealistic when it was enforced.

Within two weeks, we had the new system operational. Over the next 12 months, I conducted a pop inspection each month, unannounced accountability checks to verify the system was working. The team passed every single time.

The Broader Impact: Ownership Creates Sustainability

The qualification and certification digitization was a tactical win that prevented immediate disaster. The team designed accountability system was a strategic win that changed the culture.

By the time I retired in June 2025, the command had transitioned from reactive compliance, scrambling before inspections, to proactive accountability as a daily practice. The systems we built weren't about satisfying inspectors. They were about ensuring we always knew the truth about our readiness and could answer any question immediately.

More importantly, because the team had designed the accountability standards themselves, they owned them. This wasn't leadership imposing bureaucracy. It was professionals defining what excellence looked like in their domain and holding themselves to that standard. That ownership meant the system continued working long after the crisis passed and long after I had moved on to other responsibilities.

The inspection that could have collapsed the command instead became a catalyst for building sustainable systems that outlasted my tenure and continue operating today.

The Insight

A system people create becomes a standard they'll enforce. A system imposed on people becomes a standard they'll game.

Civilian Translation

Every organization facing an accountability crisis faces the same temptation: bring in the expert, build the framework, mandate compliance. It feels like leadership. It usually isn't.

The organizations that come out of compliance crises with sustainable systems are the ones that turned the crisis into a design problem and gave the people closest to the work the authority to design the solution. Your analysts, technicians, and operators know where the process breaks down. They also know which fixes are realistic and which will be ignored the moment you stop watching.

The leader's job in a technical crisis isn't to demonstrate expertise. It's to create the conditions for the people who have that expertise to move fast, make decisions, and own the outcome. That ownership is what makes the system survive after the inspection, the audit, and the emergency is over.

The Takeaway: Ownership Beats Compliance

I wasn't an AA&E expert when I took over. I'm still not. But I didn't need to be the expert to lead effectively through the crisis. I needed to identify the people who understood the technical requirements, empower them to build solutions, and hold them accountable to the standards they set for themselves.

The qualification and certification crisis was solved in 72 hours because I connected the right people and gave them the authority to act. The accountability system worked for the next two years and beyond because the team designed it based on their operational reality, not because I imposed a theoretical framework from above.

When people create the standards they'll be held to, compliance transforms into ownership. They can't claim it's unfair because they designed it. They can't say it's unrealistic because they built it around their actual work. And most importantly, they'll maintain it because it's theirs, not mine.

This is the leadership challenge in any technical domain: you won't always be the subject matter expert. But you can create the conditions for experts to succeed by removing obstacles, providing clarity on requirements, and most critically, giving them ownership over the solutions.

In my next role, I'm looking for organizations facing similar challenges: technical complexity, high stakes, and the need to build accountability systems that people will actually follow not because they're required, but because they make sense and because the team created them.