What Running the Operating Rhythm for a 40,000-Person Organization Taught Me
Lessons on cadence, dependencies, and decision-support from coordinating executive priorities at scale.
When I served as Aide-de-Camp and executive assistant to a Marine Corps commanding general at Marine Corps Installations West, my job wasn't to run any single program. It was to keep the operating rhythm of an entire organization — one supporting more than 40,000 people — moving in a coherent direction. That meant coordinating 30 to 50 weekly engagements, translating strategic priorities into action across departments, and planning more than 100 executive travel and site-visit movements a year, often with last-minute changes. It taught me more about program management at scale than any single project ever could.
Cadence is a design decision, not a byproduct
At that scale, if you don't design the rhythm of reviews, briefings, and decision points deliberately, the organization designs a worse one for you — reactively, out of whatever crisis happened most recently. Part of my job was making sure the recurring cadence of engagements matched the actual tempo of decisions that needed to be made, not just the calendar's default tempo. A weekly sync that exists because it's always existed is worse than no sync at all; it burns time without producing decisions.
Dependencies compound faster than they look
Coordinating executive priorities across departments means most problems aren't really about the task in front of you — they're about what that task depends on somewhere else in the organization. A travel movement that looks simple in isolation might depend on three other departments' schedules, a security review, and a host organization's own constraints. The skill that mattered most wasn't tracking any one of those dependencies; it was building a habit of asking "what does this actually depend on" before committing to a timeline, so surprises showed up in planning instead of in execution.
Decision-support is a craft of its own
A huge part of supporting senior leadership is making sure a decision-maker has exactly what they need to decide, and nothing more. Overloading a leader with detail slows decisions down as much as under-informing them does. I learned to think about every briefing or update as a decision-support product: what does the person receiving this actually need to decide, and what's the shortest path to giving them that with confidence in the underlying information.
Being a liaison means owning the seams
Serving as a central liaison between executive leadership, senior staff, government officials, and outside organizations meant most of my real work happened in the seams between groups — the places where one team's plan met another's constraints. Program managers at any scale live in those seams. The organizations that function well are the ones where someone explicitly owns making sure information and expectations move cleanly across those seams, rather than assuming they'll align on their own.
At scale, program management stops being about any individual initiative and becomes about the system that lets dozens of initiatives move at once without colliding.
That's the lesson I'm carrying into civilian program and operations leadership: build the cadence deliberately, respect how fast dependencies compound, treat every update as a decision-support product, and take ownership of the seams between teams. None of that requires a 40,000-person organization to apply — it requires the discipline to design the system instead of reacting to it.