Translating Military Leadership Into Civilian Program Management
Five operating principles from thirteen years in uniform that transfer directly to running civilian programs and teams.
After thirteen years on active duty — moving from an intelligence analyst leading a 25-person team, to director of strategic communications, to executive assistant coordinating priorities for the commanding general of a 40,000-plus person organization — I've spent most of my career inside environments where the cost of a missed deadline or an unclear plan wasn't a slipped sprint. It was operational.
As I transition to civilian program and project management work, people often ask what actually carries over. Not the jargon, and not the discipline clichés. The real transfer is a small set of operating principles that apply whether you're running a recruiting operation or a product launch.
1. Build the battle rhythm before you need it
In the military, we call the recurring cadence of meetings, reports, and decision points the "battle rhythm." Every organization has an equivalent, whether or not it's named. The mistake I see in both worlds is standing up a cadence reactively, after something has already slipped. A good operating rhythm is designed in advance: what gets reviewed weekly, what gets escalated immediately, and who owns the follow-up. When I managed 30-50 weekly engagements for a commanding general, the rhythm itself — not any single meeting — was what kept dozens of moving initiatives from colliding.
2. Make the plan legible to everyone who has to execute it
A plan that only the person who wrote it can interpret is not a plan — it's a liability. Every standardized tracker, workflow, and reporting template I built in uniform existed to answer one question for anyone on the team: what's the status, and what do I need to do next? The same principle drives good program management: a Gantt chart or a RAID log is only useful if the newest person on the team can read it cold and know what to do.
3. Budgets are trust, not paperwork
Managing operational budgets and resource allocation across recruiting initiatives, training, and events taught me that a budget is really a record of what leadership trusted you to prioritize. Treating budget reporting as a bureaucratic afterthought — rather than as the clearest signal you can give stakeholders about whether you're delivering — is one of the fastest ways to lose the confidence of the people funding your program.
4. Develop the people below you, not just the plan
Leading cross-functional teams of 5 to 25 people across intelligence, communications, and recruiting functions reinforced something that's easy to lose sight of in program management: the plan doesn't execute itself. The people on your team do. Time spent building training programs, clarifying expectations, and developing the next person who can run the workflow without you is never wasted time — it's the actual job.
5. Debrief everything
After every major event, engagement, or project close-out, we debriefed: what worked, what didn't, and what changes we're carrying into the next cycle. It's a simple habit, and it's the single biggest gap I see in civilian project management. Retrospectives get skipped when a team is busy, which is exactly when they matter most. A five-minute debrief compounds into a much stronger process over a year of projects.
None of this is really about the military. It's about the discipline of treating execution as seriously as strategy — building the systems, developing the people, and being honest about what worked.
I'm bringing these principles into program and operations leadership roles now, with a growing focus on using AI-enabled workflows to make the reporting and tracking side of the job faster without losing the rigor. If you're building a program team and want to talk through how a structured operating rhythm could apply to your organization, I'd welcome the conversation.