The Finance Team That Runs Without Me

I was 30 days into my Iraq deployment when I got the email: my most experienced analyst was being reassigned. Immediately.

Not in two weeks. Not after transition. Now.

She was managing a $4.2 billion equipment account—tracking requisitions, monitoring obligations, coordinating with vendors across three countries. She had relationships, institutional knowledge, and a mental map of how everything connected.

And she was leaving in 48 hours.

I had two options: panic, or trust the system we'd built.

I chose the system.

Her replacement—a sharp airman with exactly zero experience in theater acquisitions—stepped into the role. He fumbled for the first three days. Then he found his rhythm. Within two weeks, he was running it better than she had.

Not because he was smarter. Because the system didn't need her. Or me. Or any single person.

That's when I learned the most important lesson in finance leadership: if your operation can't run without you, you haven't built a team—you've built a dependency.

The Hero Problem

Most finance operations have a hero.

You know who I'm talking about. The person who knows where everything is. Who can answer any question. Who works late to fix problems. Who makes it all work through sheer force of will and institutional knowledge.

Lose that person, and the whole operation stumbles.

Early in my career at Peterson Air Force Base, I was that hero. I was the cost analyst who knew the $7 billion space program portfolio inside and out. I took pride in being indispensable.

My Flight Commander saw it differently.

"Denny," he said, "if you got hit by a bus tomorrow, how long would it take us to recover?"

"I don't know, sir. A few weeks?"

"That's a problem. Your job isn't to be irreplaceable. It's to make yourself unnecessary."

It stung. But he was right.

Being the hero feels good. It's validation. It's job security. It's proof you're valuable.

It's also a trap.

Because when you're indispensable, you can't grow. You can't take on bigger challenges. You can't deploy. You can't get promoted. You can't take a vacation without your phone blowing up.

And your organization can't scale.

Systems Over Superstars

At Malmstrom Air Force Base, I commanded 140 people managing a $125 million budget with a $372 million economic impact. I was responsible for everything from payroll to travel to budget execution to financial reporting.

I was also required to be ready to deploy on 72 hours' notice.

That meant one thing: the squadron had to run perfectly without me.

We built it around five principles:

1. Document Everything

Not just procedures—everything.

Standard Operating Procedures: Step-by-step instructions for every routine task
Decision matrices: If X happens, do Y (no need to ask permission)
Contact lists: Who to call for every possible issue
Historical context: Why we do things this way (so people understand the reasoning, not just the steps)
Common problems: Issues we've seen before and how we solved them

Every time someone asked me a question, I'd answer it once verbally and document it once in writing. The next person with the same question got pointed to the documentation.

Over time, we built a knowledge base that made tribal knowledge explicit.

2. Cross-Train Ruthlessly

Every critical function had a primary, a backup, and a shadow.

The primary owned it day-to-day. The backup could step in within 24 hours. The shadow was learning it in case both were gone.

This wasn't optional. It was a commander's requirement.

Once a quarter, we ran exercises: the primary took leave (real or simulated), and the backup ran the operation for a week. Not with help. Fully.

It was uncomfortable. There were mistakes. But that's the point—better to find the gaps during an exercise than during a real crisis.

3. Push Decisions Down

The fastest way to make yourself indispensable is to own every decision.

The fastest way to make yourself unnecessary is to give decisions away.

I started with a simple rule: if a decision was reversible and under $5,000, my team didn't need my approval. They needed to inform me, but the call was theirs.

At first, they hated it. They wanted top cover. They wanted me to own the risk.

I refused.

"If it works, it's your win. If it doesn't, we'll fix it together. But the decision is yours."

Within three months, the quality of their decisions matched or exceeded mine. Because they had skin in the game.

4. Build Battle Rhythm

In combat, battle rhythm is sacred. It's the predictable cycle of briefings, meetings, and updates that keeps everyone synchronized.

We brought that discipline to garrison:

Daily huddle: 0730, 15 minutes, key numbers and issues
Weekly deep dive: Mondays, 60 minutes, review metrics and trends
Monthly review: First Friday, 90 minutes, strategic adjustments
Quarterly planning: Full day offsite, align priorities with command guidance

Battle rhythm creates predictability. People know when they'll have your attention. They know when decisions get made. They stop interrupting you constantly because they know the forum is coming.

More importantly, battle rhythm survives leadership changes. When I went on leave or deployed, the rhythm continued. New leaders just stepped into the existing framework.

5. Measure Independence

You can't improve what you don't measure.

We tracked how often my team came to me with questions versus solutions. Early on, the ratio was about 10:1—ten questions for every proposed solution.

We drove it to 1:3. Three solutions for every question.

How? Every time someone brought me a problem, I asked: "What do you think we should do?"

Most of the time, their answer was solid. I'd approve it and send them on their way.

When it wasn't solid, I'd ask questions until they refined it themselves.

Over time, they stopped bringing me problems. They brought me decisions they'd already made and wanted me aware of.

That's when you know you've built independence.

The Iraq Test

All of this philosophy got stress-tested in Iraq.

I was managing $33 billion in flows, coordinating with Iraqi ministries, supporting coalition partners, and dealing with constantly shifting priorities. I worked 12-hour days minimum, seven days a week.

I couldn't be everywhere. I couldn't make every decision. I couldn't hold everyone's hand.

So I didn't try.

I set clear commander's intent: what success looked like, what our priorities were, and what constraints we operated under.

Then I got out of the way.

My team ran financial operations across theater. They negotiated with foreign governments. They solved problems I never even heard about. They made judgment calls that I would have made the same way—or better.

Not because they were exceptional (though they were). Because the system allowed them to be.

What This Looks Like in Your Business

Here's the practical application for business owners:

This week:

List every financial task you personally handle
For each one, ask: "If I was gone for 30 days, who would do this?"
If the answer is "no one" or "it wouldn't get done," that's your priority list

This month:

Document your top 5 recurring financial processes (step-by-step, with examples)
Identify a backup for each critical financial function
Delegate one decision type you currently own (start small—maybe approval authority under $1,000)

This quarter:

Cross-train someone on your most "irreplaceable" task
Take a full week off and don't check email (seriously—test the system)
Measure how many decisions your team makes without you versus how many they escalate

The Freedom of Being Unnecessary

Here's the paradox: the less your team needs you for daily operations, the more valuable you become to the business.

Because you're freed up to work on the things that actually need your attention:

Strategy: Where should the business go, not just how to keep it running?
Relationships: Building partnerships, landing clients, securing financing
Innovation: What could we do better? What should we stop doing?
Growth: How do we scale this operation to 2x, 5x, 10x?

At IP Consulting Inc., where I serve as Head of Finance & Operations, I spent the first six months building systems. Now I spend most of my time on strategic initiatives because the day-to-day runs itself.

In my fractional CFO practice, I help clients build the same capability. The goal isn't to make them dependent on me. It's to build finance operations that thrive independently—with or without me in the room.

The Ultimate Test

You'll know you've succeeded when you can truthfully say:

"I could leave for 30 days, and my finance operation would run perfectly. Not because I'm unimportant, but because I built something that doesn't need me to micromanage it."

That's not a sign of weakness. It's a sign of leadership.

The military taught me this: your job as a leader isn't to be the hero. It's to build a team that doesn't need one.

—Gabe

Next in the series: Communications Framework - the battle rhythm that keeps everyone aligned.