It was 0630 in Iraq, and I was staring at a $47 million discrepancy.

Not missing. Not stolen. Just... wrong. Someone, somewhere in the chain, had coded a massive equipment purchase to the wrong account. The funds were there. The equipment was real. But the accountability trail was broken.

In combat finance, a $47 million error isn't just embarrassing. It's a congressional inquiry waiting to happen. It's a general's career on the line. It's ammunition for critics who claim we waste taxpayer dollars.

My team had 72 hours to find it, fix it, and document every step.

We found it in 48.

Not because we were brilliant, but because we'd built a culture where accountability wasn't a yearly audit—it was a daily discipline.

Accountability Is Not Blame

Let's start with what accountability is NOT.

It's not a witch hunt. It's not a gotcha game. It's not about punishment or public shaming. And it's definitely not about finding someone to blame when things go wrong.

I learned this as a young enlisted airman making $23,000 a year. I made a mistake—transposed two digits on a payment authorization. Not a huge error, but enough to delay a contractor payment by two weeks.

My supervisor could have crushed me. Instead, he sat me down and asked three questions:

  • What happened?
  • Why did it happen?
  • How do we prevent it from happening again?

No yelling. No threats. Just a calm debrief focused on process improvement.

That's accountability.

The goal isn't to find fault—it's to maintain standard. To ensure everyone understands their role, knows the expectations, and has the tools to meet them.

The Accountability Triangle

At Malmstrom Air Force Base, commanding a 140-person finance squadron, I developed what I call the Accountability Triangle. Every functional system has three components:

1. Clear Standards

You can't hold people accountable to vague expectations.

When I took command at Malmstrom, I inherited a team that was working hard but getting inconsistent results. The problem wasn't effort—it was clarity.

People didn't know exactly what "good" looked like.

We fixed it by documenting everything:

  • Processing timelines: Not "as soon as possible" but "travel vouchers completed within 5 business days"
  • Quality standards: Not "accurate" but "zero critical errors, less than 2% minor errors"
  • Communication protocols: Not "keep me informed" but "brief me on issues within 4 hours of discovery"
  • Decision authorities: Not "check with leadership" but "you own decisions up to $X, brief me on anything above"

Clear standards do two things: they tell people exactly what success looks like, and they remove ambiguity when things don't meet standard.

2. Consistent Measurement

Standards without measurement are just suggestions.

In Iraq, we tracked everything. Not because we enjoyed paperwork (trust me, we didn't), but because measurement drives behavior.

We measured:

  • Timeliness: How long from request to completion?
  • Accuracy: What percentage required rework?
  • Customer satisfaction: What did our internal customers say about the service?
  • Compliance: Were we meeting regulatory requirements?

Here's the key: we measured the same things the same way every time. No moving goalposts. No selective enforcement. Consistency builds trust.

When someone's performance was below standard, they saw the same data I saw. There was no argument about whether there was a problem—only discussion about how to fix it.

3. Rapid Feedback

Accountability dies in the annual review cycle.

If you wait six months to tell someone they're not meeting standard, you haven't built accountability—you've built resentment.

At Peterson Air Force Base, overseeing $7 billion in space programs, we implemented weekly check-ins. Not formal reviews—just 15-minute conversations:

  • What went well this week?
  • What didn't go as planned?
  • What support do you need?
  • Are there any trends we should address?

Problems surfaced early. Corrections happened in days, not months. People knew where they stood, always.

The annual review became a summary, not a surprise.

The Command Post Briefing

In combat, every morning started with a briefing. Not a meeting—a briefing. Focused, disciplined, outcomes-oriented.

We walked through:

  • Yesterday's key numbers: What did we process? What came in? What went out?
  • Issues: What broke? What's at risk? What needs attention?
  • Today's priorities: What absolutely must get done?
  • Resource needs: Do we have what we need, or do we need to adjust?

Fifteen minutes. Every single day. No exceptions.

This rhythm created accountability. Everyone knew they'd be asked about their area. Not to embarrass anyone, but to maintain situational awareness.

If you said yesterday that X would be done today, someone's going to ask about X. That expectation—that quiet knowledge that your word matters—creates a culture of follow-through.

When Standards Aren't Met

Here's where most organizations fail: they either ignore underperformance or they overreact to it.

Both are deadly to accountability.

Ignoring underperformance tells everyone that standards are negotiable. That mediocrity is acceptable. That showing up is enough.

Overreacting creates fear. People start hiding problems. They stop taking risks. They spend more energy on CYA than on actually improving.

The military taught me a better approach: the Letter of Expectation.

When someone consistently failed to meet standard, I'd sit down with them and document:

  • The specific standard they weren't meeting (with data)
  • The support we'd provide (training, resources, mentorship)
  • The timeline for improvement (usually 30-60 days)
  • How we'd measure success (clear metrics)
  • Consequences if standards still aren't met (up to and including reassignment)

It wasn't punishment. It was clarity.

And you know what? About 80% of people who received a Letter of Expectation turned it around. Because they finally understood exactly what was expected and had the support to get there.

The other 20%? They either couldn't or wouldn't meet standard. And that's okay—not everyone is suited for every role. The kind thing is to recognize that early and help them find a better fit.

Accountability Flows Up Too

The biggest accountability failure I see in business is leaders who hold their teams accountable but refuse to hold themselves to the same standard.

At Malmstrom, I made a mistake that cost us three days of productivity. We were implementing a new system, and I pushed it live before we'd fully tested the integration. It crashed. Hard.

I could have blamed the vendor. Could have blamed IT. Could have blamed the tight timeline.

Instead, I called an all-hands meeting and said: "This one's on me. I made the call to go live early. It was the wrong call. Here's what we're doing to fix it, and here's what I'm changing in my decision process to prevent it from happening again."

Three things happened:

  1. The team respected that I owned it
  2. They trusted me more, not less
  3. They felt safer admitting their own mistakes

When leaders model accountability, it cascades. When they dodge it, cynicism grows.

Building Accountability in Your Business

Most business owners I work with understand that accountability matters. What they struggle with is implementation.

Here's your starting point:

  1. Pick three metrics that matter. Not thirty. Three. Revenue, customer satisfaction, and cash flow. Or whatever is actually critical to your business. Measure them weekly.
  2. Assign clear ownership. Every metric has a name attached. Not a department—a person. If cash flow is critical, someone owns it and can tell you the number any day of the week.
  3. Create a weekly battle rhythm. Fifteen minutes, same time, same format. What are the numbers? What's working? What isn't? What do we need to address?
  4. Document your standards. Write down what "good" looks like for each key role. Be specific. Use numbers where possible. Make it visible.
  5. Provide feedback fast. When someone exceeds standard, tell them that day. When they fall short, address it that week. Don't wait.
  6. Own your mistakes publicly. When you screw up (and you will), say so. Explain what you learned. Show the team what accountability looks like at the top.

The Accountability Culture

After 20 years in uniform—from a $23K-a-year airman to commanding a squadron managing $125 million—I can tell you this:

Accountability is not a system. It's a culture.

Systems help. Processes matter. Metrics are essential.

But culture is what happens when you're not in the room. It's whether people hold themselves to standard because it's expected, or because someone's watching.

The best organizations I've been part of—military and civilian—had something in common: people cared about doing it right. Not because of rewards or punishment, but because the culture said "we don't accept mediocrity here."

That culture doesn't appear by accident. It's built through:

  • Consistent standards
  • Fair measurement
  • Rapid feedback
  • Leadership example
  • Support for improvement
  • Consequences for chronic underperformance

Build that, and accountability stops being something you enforce. It becomes something your team demands of themselves.

That's when numbers actually matter.

—Gabe

Next in the series: The Finance Team That Runs Without Me - building systems that don't need you.