It was 0600 in Iraq, and the command post was already humming.

Not chaotic—humming. Controlled energy. People moving with purpose.

By 0630, every key leader was in their seat. By 0645, we'd briefed the previous 24 hours, identified issues, aligned priorities, and assigned responsibilities. By 0700, everyone was back to work.

Fifteen minutes. Every single day. No exceptions.

That daily sync kept $33 billion in financial operations running across a combat theater. It ensured a coalition of different nations, services, and organizations stayed coordinated despite language barriers, time zones, and cultural differences.

Not through marathon meetings. Through disciplined battle rhythm.

The military term is "battle rhythm"—the predictable cycle of communications that keeps everyone synchronized. In business, most people call it "cadence" or "meeting rhythm."

Whatever you call it, most organizations get it wrong.

The Meeting Disease

Let me guess: your calendar is full of meetings. Some are useful. Most are not.

You've got the Monday morning team meeting that should take 30 minutes but runs an hour. The weekly one-on-ones that feel more like therapy sessions than business discussions. The monthly all-hands that's really just a series of department updates nobody listens to.

And then there are the "quick syncs" that pop up constantly because nobody knows what anyone else is doing.

This is not battle rhythm. This is organizational chaos masked as collaboration.

At Peterson Air Force Base, overseeing $7 billion in space programs, I watched this play out in slow motion. Meetings about meetings. Discussions about what to discuss. Hours of calendar Tetris to find time for "just a quick conversation."

Meanwhile, actual work happened in the margins.

When I took command at Malmstrom, I made a commitment: we would cut meeting time by 50% and double effective communication.

Sounded impossible. We did it in 90 days.

The Five-Layer Communications Stack

Military operations run on a communications stack—layers of briefings and updates, each with a specific purpose, format, and frequency.

No overlap. No redundancy. No wasted time.

We adapted this for business:

Layer 1: The Daily Pulse (15 minutes)

When: 0730, every single day
Who: Finance team leads (3-5 people)
Format: Stand-up, no slides, no laptops

Agenda:

  • Numbers (5 min): What closed yesterday? What's the cash position? Any variances from plan?
  • Issues (5 min): What broke? What's at risk? What needs escalation?
  • Priorities (5 min): What absolutely must get done today? Any resource conflicts?

That's it. Fifteen minutes. Start on time, end on time, no exceptions.

The daily pulse is not for problem-solving. It's for situational awareness. If something needs deep discussion, it goes offline.

This one practice eliminated about 70% of our "quick question" interruptions. People saved issues for the daily pulse instead of breaking your focus six times a day.

Layer 2: The Weekly Deep Dive (60 minutes)

When: Monday 1300 (after people have had time to review weekend numbers)
Who: Full finance team + key stakeholders
Format: Conference room, dashboard on screen

Agenda:

  • Performance review (20 min): Actual vs. budget, trends, variances
  • Issues deep dive (20 min): Pick the top 2-3 issues from the week and actually solve them
  • Forward look (15 min): What's coming in the next two weeks? Any resource needs?
  • Process improvements (5 min): What's not working? What should we change?

The weekly deep dive is where you actually solve problems, not just surface them.

Key rule: every issue that's discussed must have an owner and a deadline before the meeting ends. No "we'll look into that" without a name and date attached.

Layer 3: The Monthly Review (90 minutes)

When: First Friday of the month, 0900-1030
Who: Finance leadership + executive team
Format: Boardroom, formal presentation

Agenda:

  • Financial performance (30 min): Month-end close, full P&L and balance sheet review, KPI dashboard
  • Strategic initiatives (30 min): Status of key projects, investment decisions, resource allocation
  • Risks and opportunities (20 min): What could derail us? What should we double down on?
  • Decisions required (10 min): What needs executive approval to move forward?

The monthly review is where tactics meet strategy. You're zooming out from daily operations to look at the bigger picture.

In Iraq, this was our "commander's brief." It gave senior leadership the context to make informed decisions without being buried in operational details.

Layer 4: The Quarterly Strategic Session (Half day)

When: Last Friday of the quarter, 0800-1300
Who: Leadership team
Format: Offsite if possible, no day-to-day operations allowed

Agenda:

  • Quarter review (60 min): What did we accomplish? What did we miss? Why?
  • Market analysis (45 min): What's changing in our environment? Threats? Opportunities?
  • Strategic adjustments (90 min): Do we need to pivot? Double down? Kill something?
  • Next quarter priorities (60 min): What are the 3-5 things that matter most?

This is pure strategy time. No operational firefighting allowed.

At Malmstrom, we'd physically leave the building for these sessions. The change of environment signaled: this is different. This is where we think long-term.

Layer 5: The Exception Protocol (As needed)

This is the emergency communication layer—what happens when something breaks outside the normal rhythm.

We had clear criteria for what constitutes an exception:

  • Critical: Operations stopped, legal/compliance issue, major financial loss (>$X)
  • Urgent: Significant customer impact, time-sensitive decision required, resource conflict blocking multiple teams

If it met these criteria, you escalated immediately—call, text, whatever it takes.

If it didn't meet these criteria, it waited for the next scheduled sync.

This distinction is crucial. Without it, everything becomes an emergency and nothing gets the attention it deserves.

The Information Flow Rules

Battle rhythm only works if information flows predictably. We enforced three rules:

Rule 1: No Surprises Up

Your boss should never learn about a problem from someone else.

In Iraq, we had a simple standard: if it's significant enough that the commander might hear about it, brief them first. Even if you don't have the full answer yet.

"Sir, there's a $2M discrepancy in the account. We're investigating. I'll have details by 1400."

That's infinitely better than the commander getting blindsided in a meeting.

Rule 2: Information Pushed, Not Pulled

Leaders shouldn't have to chase information.

We established clear reporting timelines:

  • Daily numbers: by 0700
  • Weekly dashboard: by COB Friday
  • Monthly close: within 5 business days
  • Exception reports: within 4 hours of discovery

If it's late, we want to know why. But the default is information arrives on schedule without being asked for.

Rule 3: Right Level, Right Detail

Junior analysts need transaction-level detail. Executives need trends and decisions.

We built different views for different audiences:

  • Executive summary: One page, key numbers, red/yellow/green status, decisions needed
  • Management dashboard: 3-5 pages, performance metrics, variance analysis, issue summary
  • Operational detail: Full dataset, transaction logs, detailed reconciliations (available on request, not pushed)

The commander got the one-pager. If they wanted more, they'd ask. But we didn't bury them in data they didn't need.

The Ad Hoc Meeting Killer

Here's the magic of battle rhythm: when people know exactly when they'll have your attention, they stop interrupting you constantly.

Before we implemented this at Malmstrom, I was in back-to-back meetings all day. My actual work happened between 0600-0730 and after 1700.

After we implemented battle rhythm, my calendar had white space again. Because people saved non-urgent items for the scheduled syncs.

We tracked this: ad hoc meetings dropped by 60% in the first month.

Not because people had fewer questions. Because they had predictable forums to ask them.

Making It Work in Your Business

You don't need to implement all five layers immediately. Start with two:

Week 1: Implement the Daily Pulse

  1. Pick a time (early morning works best)
  2. Invite 3-5 key people (no more—this is not an all-hands)
  3. Set a 15-minute hard stop (use a timer if needed)
  4. Stick to the format: Numbers, Issues, Priorities
  5. Do it every day for 30 days before deciding if it's working

Week 2: Add the Weekly Deep Dive

  1. Pick a consistent time (same day/time every week)
  2. Create a simple agenda template
  3. Require pre-work (dashboard reviewed before the meeting)
  4. End every issue with an owner and deadline
  5. Track decisions and follow-up items

Month 2: Layer in the Monthly Review

Quarter 2: Add the Quarterly Strategic Session

Build the rhythm gradually. Master each layer before adding the next.

When Battle Rhythm Breaks Down

Even good systems fail. Here's what kills battle rhythm:

Inconsistency: You skip it once, then twice, then it's dead. Protect the rhythm like it's sacred.

Drift: The 15-minute daily somehow becomes 45 minutes. Reset hard. End on time even if you didn't finish—that creates discipline.

No teeth: People show up late or unprepared with no consequences. Battle rhythm requires accountability.

Wrong people: Too many participants and it becomes a report-out. Too few and you miss critical information.

No pre-work: If people are seeing numbers for the first time in the meeting, you're wasting everyone's time.

The Rhythm Creates Space

After 20 years in uniform—from enlisted airman to squadron commander—I can tell you this:

The organizations that move fastest are not the ones in constant meetings. They're the ones with disciplined battle rhythm.

Because rhythm creates predictability. Predictability creates trust. And trust creates speed.

When your team knows exactly when and how information will flow, they stop wasting energy on coordination overhead. They spend it on execution instead.

That's the difference between chaos and control.

—Gabe

Next in the series: Forecasting Under Fire - how to plan when everything's uncertain.