Julien stares at the acquisition strategy document at 6:47 AM. Coffee's cold. Because of that, the milestone decision review is in three weeks. The contractor's behind schedule, the test data's incomplete, and the program executive officer wants options — not excuses — by Friday.
This is the job. Day to day, not the PowerPoint version. The real one.
What Is a DoD Program Manager
A Program Manager in the Department of Defense isn't a project manager with a fancier title. That's why it's a statutory role. Think about it: congress created it. Which means title 10, U. S. Think about it: code, Chapter 87 spells it out: one person, accountable for cost, schedule, and performance of a major defense acquisition program. One throat to choke, as the saying goes.
Julien holds a DAWIA Level III certification in Program Management. That's why he's got twenty-two years in — eight as an engineer, six as a deputy, the last eight running programs. His current portfolio: a mid-tier ACAT II communications satellite modernization effort. On the flip side, budget: $1. 4 billion over seven years. Team: 140 government civilians, 300+ contractor personnel across three prime contractors and a dozen subs.
He doesn't build satellites. He builds the conditions where satellites get built.
The Authority — And The Limits
Here's what most people miss: a PM has enormous authority on paper. Milestone decisions. Worth adding: contract modifications. Also, requirements trades. Source selection. But in practice? Julien can't order a single contractor employee to do anything. So he influences. Practically speaking, he negotiates. He escalates. He builds coalitions across PEOs, service chiefs, OSD staff, Capitol Hill staffers, and industry executives — all of whom have different incentives.
The job is political in the best and worst senses And that's really what it comes down to..
Why This Role Exists — And Why It's Different
Before the Packard Commission in 1986, defense acquisition was a mess. In practice, requirements creep. Cost overruns. No single point of accountability. The Goldwater-Nichols Act and the Defense Acquisition Workforce Improvement Act (DAWIA) created the modern PM role to fix that That's the part that actually makes a difference..
Julien's position exists because someone has to own the whole problem. Day to day, not the technical piece. Not the contracting piece. But not the budget piece. All of it.
The Three-Legged Stool
Every PM lives or dies by three metrics:
Cost — Measured against the APB (Acquisition Program Baseline). Breach the threshold? Nunn-McCurdy review. Congress gets notified. Careers end Simple, but easy to overlook..
Schedule — Key milestones: MS-A, MS-B, MS-C, FRP decision. Slip one, and the ripple hits force structure plans, training pipelines, depot stand-up.
Performance — KPPs (Key Performance Parameters). Threshold vs. objective values. If the satellite doesn't meet the threshold KPP for anti-jam capability, it doesn't matter if it's on budget and on time. It's useless Simple as that..
Julien's current nightmare: KPP #3 — protected tactical waveform throughput. Also, that's money. That's schedule. On the flip side, contractor's testing shows 85% of threshold. The fix requires a hardware redesign. That's a conversation with the PEO he's not looking forward to That's the part that actually makes a difference..
How It Actually Works — The Daily Reality
No two days look the same. But the rhythm is recognizable.
Monday: The Battle Rhythm
0600 — Email triage. Day to day, 95. Think about it: contractor CPR (Cost Performance Report) shows SPI 0. 92. Congressional inquiry response due. Not catastrophic. In real terms, cPI 0. Not good.
0730 — Staff meeting. Deputy PM briefs risk register. Top three: 1) Waveform ASIC yield rates. On top of that, 2) Ground segment cybersecurity ATO delay. 3) Spectrum licensing for new frequency band Less friction, more output..
0900 — IPT (Integrated Product Team) lead sync. Accept the schedule hit. Test & evaluation pushes back — "If we relax it now, we'll never get it back." Julien makes the call: keep the requirement. Systems engineering wants to relax a requirement to save schedule. Document the rationale for the MS-C brief.
1100 — Contractor PMR (Program Management Review). And prime contractor's program manager — let's call her Sarah — presents a recovery plan for the ASIC yield issue. In practice, it's aggressive. Julien pushes on assumptions. "You're assuming 95% first-pass yield on the respin. Last time you got 67%. And what's different? " Sarah's team scrambles. The conversation gets uncomfortable. Good.
1400 — PEO sync. One-on-one with the Program Executive Officer. Because of that, thirty minutes. Julien brings three decisions, not problems. PEO approves two, kicks the third to the service acquisition executive.
1600 — Requirements owner call. Because of that, "Just a software change. Julien explains the impact: six-month slip, $40M, rebaseline the APB. On the flip side, the operational user wants a new capability inserted. " Julien's systems engineer shakes his head visibly on the video call. User says "never mind.
1800 — Walk the floor. Talk to the junior engineers. Consider this: ask what's blocking them. Hear things the deputies filter out.
The Art of the Trade Study
Every major decision comes down to a trade study. Consider this: cost vs. Here's the thing — schedule vs. performance vs. So risk. Julien doesn't do the analysis — his team does. But he frames the question, challenges the assumptions, and owns the outcome.
Example: The ground segment cybersecurity ATO (Authority to Operate). So current path: RMF (Risk Management Framework) assessment, six months, $12M. Because of that, alternative: make use of existing ATO from a similar system, tailor controls, three months, $4M. Risk: the authorizing official might reject the tailoring.
Julien's call: pursue the tailored path in parallel with the full assessment. On the flip side, it's not in the textbook. Practically speaking, spend the $4M. If it fails, the full path is already underway. If it works, save three months. It's how programs actually succeed.
Managing the Contractor — Without Managing Them
This is the central paradox. Day to day, julien has contractual authority through the KO (Contracting Officer). But the KO works for the contracting command, not Julien. The contractor's employees work for the contractor.
So Julien builds relationships. Even so, he knows Sarah's kids' names. He knows which technical lead on the prime's team is sharp and which one pads estimates. He knows the subcontractor's financial health better than their own CFO — because he reads their 10-Ks and earnings calls Less friction, more output..
When the ASIC yield problem hit, Julien didn't issue a cure notice. He called Sarah. "Help me help you. What do you need from me to fix this?" She asked for a government-furnished test asset to accelerate qualification. That said, julien got it in two weeks — normally a six-week process. He burned a favor with the test range commander. Sarah's team caught the root cause three weeks earlier That's the part that actually makes a difference..
Not the most exciting part, but easily the most useful.
That's the job. Not the contract. The relationship.
What Most People Get Wrong
"The PM Controls the Budget"
Julien controls his budget — the program's RDT&E and procurement funding. But he doesn't control the service's top-line. Consider this: when the budget drill hits and the service marks down his program by 15% to fund a higher priority, Julien executes the cut. He doesn't complain to Congress. He doesn't leak to the press Turns out it matters..
and explains to his team why the scope had to shrink without sacrificing the minimum viable capability.
The illusion of control is the trap. On the flip side, seasoned PMs learn the difference between what they own and what they influence. In real terms, julien influences the POM (Program Objective Memorandum) cycle two years out by writing compelling justifications and showing up to the right reviews — but he owns only the dollars already appropriated to his line. When the mark comes down, he treats it as a constraint to design around, not a grievance to nurse Small thing, real impact..
"The Schedule Is the Schedule"
New PMs worship the Integrated Master Schedule (IMS). He pulled the harness rework forward, told the deputies to stop reporting green, and took the hit on the monthly status. Julien believed the engineer. The junior engineer told him in March it would slip to July because the harness drawings were wrong and nobody had flagged it. The IMS said the payload integration would finish in May. Julien reads it, but he trusts the floor more than the Gantt. The program slipped two weeks instead of two months.
Not the most exciting part, but easily the most useful.
A schedule is a hypothesis. The floor is the data That alone is useful..
"You Rise by Avoiding Risk"
The opposite is true. Julien's reputation was built on the program he saved after it went Nunn-McCurdy breach — cost growth over 25%. He didn't hide it. He briefed it straight, proposed the restructuring, and took the scrutiny. The general who led the review later said, "He didn't flinch." That's why he got the next program, bigger and harder.
And yeah — that's actually more nuanced than it sounds It's one of those things that adds up..
Risk avoided is risk deferred. Risk owned is trust earned.
The Quiet Compounding of the Job
None of this shows up in the award citation. Because of that, there's no ribbon for reading a contractor's 10-K. No medal for the 1800 walk. The work compounds quietly: a test asset pulled early, a trade study framed right, a junior engineer heard before the slip became a crisis Most people skip this — try not to. And it works..
Julien will retire in three years. The program will deliver a year late and 8% over the original baseline — but with the cybersecurity ATO in hand, the ASIC qualified, and the ground segment fielded. His successor will inherit a stable line, a known risk register, and a contractor team that answers the phone.
That is the whole art of program management in one sentence: you do not command the storm, you learn to sail it — and you leave the next captain a better chart than the one you were handed.
