Home / Aerospace and defense program execution
Most program problems are known to someone long before they reach the people who can fix them. Communication management closes that gap. Set Boundaries designs the reporting, reviews and decision paths that keep your team, your customer and the government working from the same facts, so problems surface early and decisions do not wait for the next meeting.
Why does communication fail on complex programs?
It is rarely a lack of meetings. Most programs have too many. The failures are structural: information travels through too many hands before it reaches a decision maker, different groups report different numbers for the same thing, bad news is softened as it moves up, and decisions are discussed repeatedly without being made. Each of these adds delay. On a program with a tight critical path, a decision that takes three weeks instead of three days can cost more schedule than any technical problem.
What should a program communication plan include?
| Element | What it defines |
|---|---|
| Stakeholder map | Every stakeholder, their interest and influence, and what they need to know |
| Meeting rhythm | Each recurring meeting, its purpose, attendees, inputs and outputs |
| Reports and data deliverables | What is produced, from which source data, by whom and when |
| Decision rights | Who can decide what, and when a decision must escalate |
| Escalation path | How a stuck issue moves up, with time limits at each level |
| Single source of truth | Which system holds the authoritative schedule, cost, risk and action data |
| Customer interface | Who speaks to the customer on which topics, so messages stay consistent |
What does an effective meeting rhythm look like?
Daily or twice-weekly team stand-ups for the people doing the work: what moved, what is blocked, who needs help. Fifteen minutes, no slides.
Weekly program status for the program manager and leads: critical path, top risks, open decisions and actions, supplier status.
Monthly program management review with the customer: performance against the baseline, earned value, technical progress, risks, and the decisions the customer needs to make.
Quarterly leadership review for executives: whether the program is on track to its commitments, what support it needs, and what it means for the business.
Each level uses the same underlying data, summarized differently. When the weekly numbers and the monthly numbers come from different spreadsheets, trust erodes quickly.
How do you communicate bad news to a defense customer?
Early, specifically and with a plan. Customers are rarely surprised that programs have problems. They are frustrated when they learn about them late, or hear a vague version followed by a worse one. The most effective pattern is a clear statement of what happened, its impact on cost, schedule and performance in numbers, the root cause as far as it is known, and the recovery plan with dates the customer can track. Reporting the next milestone honestly and then hitting it rebuilds confidence faster than any presentation. This is central to program recovery.
Which communication metrics are worth tracking?
| Metric | What it reveals |
|---|---|
| Decision latency | Days from a decision being raised to being made |
| Action item closure rate | Whether meetings produce follow-through or just discussion |
| Overdue actions by owner | Where accountability is slipping |
| Data deliverables on time and accepted | Contract compliance and the customer's view of the program's discipline |
| Rework caused by miscommunication | The cost of the problem, often found in engineering change and nonconformance records |
What should a monthly program management review cover?
| Section | What the customer needs from it |
|---|---|
| Summary and decisions needed | The three or four things that matter this month, and what the customer must decide |
| Schedule | Critical path, milestone status against the baseline, and the forecast for the next major event |
| Cost and earned value | Cost and schedule performance indices, variances beyond threshold and their causes, estimate at completion |
| Technical progress | Design, test and verification status against plan, and open technical issues |
| Risks, issues and opportunities | Top risks with handling progress, new issues, and opportunities worth pursuing |
| Supply chain | Critical supplier status, late deliveries and recovery actions |
| Actions | Status of every action from the last review, closed or with a new date |
Leading with the decisions needed keeps the review focused. Customers remember the program that told them clearly what it needed from them.
How should a contractor communicate with the contracting officer?
Through defined channels, consistently and in writing where the contract requires it. The contracting officer is the only person who can change the contract, so scope, price and delivery changes go through them formally, even when the program office agrees informally.
How do contract data deliverables fit in?
Defense contracts specify required reports and data in a contract data requirements list, each with a data item description setting its content and format. Common examples include schedule and earned value data, program management reviews, risk reports and technical documentation. Treating these as a separate reporting burden doubles the work. Building them from the same schedule, cost and risk data the team uses every day makes them cheaper to produce and more credible, because they match what the team is actually managing.
What goes wrong most often?
Several versions of the truth. Engineering, finance and the program office each keep their own numbers. The fix is one authoritative source per data type.
Meetings without outputs. A meeting that ends without recorded decisions and actions has consumed time without moving the program.
Everything through one person. When the program manager is the only channel to the customer and the only route for escalation, communication stops whenever they are busy.
Suppliers left out. Supplier status often arrives by email in fragments. Bringing critical suppliers into a regular, structured review catches slips weeks earlier.
Customers get at least a weekly update from us and senior leadership gets formal status at least monthly, more often when the program is critical. The useful reviews are the ones that answer three questions plainly: where are we, where are we going, and what has to happen next to get there. That means showing the critical path, what changed since last time, what the customer needs to do and which decisions are required, instead of a long narrative of activity. When something has moved, we say so and bring options, not surprises.
Why does Set Boundaries overcommunicate on purpose?
Holly intentionally overcommunicates. On a struggling program, silence gets filled by assumption, and assumptions on the customer side are rarely generous. The weekly customer update and monthly leadership status described above are the floor, not the ceiling. When a program is critical, leadership hears more often. The aim is that the team, the customer and leadership always know where the program stands, what has changed and what needs attention.
Early in a recovery the rhythm is tighter still. When Set Boundaries became the program management partner for a defense display manufacturer whose programs were missing contractual commitments, communication was almost daily at first. Within weeks the customer relationships began to change: commitments became predictable and milestone payments resumed. The defense display recovery case study describes the engagement.
What does the communication style feel like?
Direct. Holly says what she sees plainly, which can take some adjustment in organizations used to reading between the lines. Customers generally find it a relief, because a direct statement of the problem, its impact and the plan is easier to act on than a softened one. The same style applies inside the team.
- Conflict is addressed when it appears. Two people with an issue talk to each other before it is escalated. If Holly has a concern about someone's work, she raises it with that person first, and she expects the same courtesy.
- A problem is a "plot twist," not a panic. When something goes wrong, the message is what changed, what the impact is, what the options are and how the program moves forward.
- Not everything is an emergency. Reserving urgency for the critical path keeps it meaningful, and teams notice the difference.
- Disagreement is welcome; disrespect is not. Professional respect is the one boundary Set Boundaries does not compromise.
Why does one source of truth matter so much here?
The three questions only work if every audience gets the same answers. Because the customer update, the leadership status and the team's weekly look-ahead all come from one integrated schedule, they never tell different stories. A customer who hears the same facts from the program manager, the engineers and the monthly review stops looking for the gap between them, and that is usually when confidence starts to return.
How does Set Boundaries help?
We map the stakeholders, rationalize the meeting and reporting rhythm, set up a decision log and escalation path, align every report to a single source of truth, and build the program management review format with the customer in mind. Where the program is under pressure, we often run the reviews ourselves at first, then hand them to the team once the rhythm holds. The work supports and reinforces risk management and schedule control, because both depend on information reaching the right people in time.
If decisions on your program keep waiting for the next meeting, schedule a call.
References
- Project Management Institute, A Guide to the Project Management Body of Knowledge, stakeholder and communications management.
- US Department of Defense, contract data requirements lists (DD Form 1423) and data item descriptions.
- Defense Acquisition University, guidance on program management reviews and stakeholder engagement.
- National Defense Industrial Association, Integrated Program Management Division guides.
Questions
Common questions
What is program communication management?
It is the deliberate design of how information moves on a program: who needs what, how often, in what form and from whom. On defense programs it covers internal team rhythms, customer program reviews, contract data deliverables, government stakeholders and suppliers. Done well, it means decisions are made on the same facts by everyone involved. Done badly, it produces rework, duplicated effort and decisions that stall.
What is a program management review?
A program management review is a regular, usually monthly, meeting where the contractor presents program status to the customer: schedule, cost and earned value performance, technical progress, risks, issues and actions. The best reviews are short on slides and long on decisions. They present the few things the customer needs to know or decide, backed by data the customer can check.
How do you reduce decision lag on a program?
By making decisions explicit. Every open decision gets an owner, a date it is needed by and the information required to make it, recorded in a decision log. Escalation paths are agreed in advance, so a stuck decision moves up automatically rather than waiting for the next meeting. Measuring the time from question to decision makes the problem visible and usually shortens it quickly.
Who are the stakeholders on a defense program?
Typically the customer program office, the contracting officer, the administrative contracting officer, the end user community, the prime or higher-tier contractor, internal leadership, engineering, manufacturing, quality, finance and suppliers. Each needs different information at a different frequency. A stakeholder map that records their interest, influence and preferred channel is the starting point of a communication plan.
What should a monthly program management review include?
A short summary with the decisions the customer needs to make, then schedule status against the baseline, cost and earned value performance, technical progress, the top risks and issues, critical supplier status and the status of every open action. The same data should come from one single source of truth, so the review matches what the team manages day to day and the customer can check it.
How much reporting is too much?
When the team spends more time reporting than the information is worth to anyone reading it. The test is simple: for every report, name who reads it and what decision it supports. Reports with no reader or no decision can usually be merged or dropped. Contract data deliverables are the exception, since they are required, but they can often be produced from the same data the team already uses.
What is 90% of a project manager's job?
The common saying is that 90 percent of a project manager's job is communication. It is a widely repeated rule of thumb, not a measured standard, though PMI has long emphasized that communication takes up most of a project manager's time. The useful point is that a project manager's value comes from moving the right information to the right decision maker quickly. On defense programs, that means clear reporting, one set of numbers and decision paths that do not wait for the next meeting, which is what Set Boundaries designs.
What are the 5 C's of communication in project management?
The 5 C's of communication are not a formal PMI standard, and lists vary. A common version is clear, concise, correct, complete and courteous; other versions substitute consistent or credible. The shared idea is that a message should be easy to understand, accurate and actionable for the person receiving it. On aerospace and defense programs, consistency matters most: when engineering, finance and the customer see different numbers for the same thing, trust erodes. Set Boundaries builds reporting from a single source so every audience works from the same facts.
What are the 5 stages of project management, or the 5 steps of PMBOK?
The five stages are the PMBOK process groups: initiating, planning, executing, monitoring and controlling, and closing. Initiating authorizes the project, planning defines scope, schedule and cost, executing performs the work, monitoring and controlling tracks performance and manages changes, and closing formally completes the project. PMBOK 7 shifted its emphasis to principles and performance domains, but PMI still publishes the process groups in a companion practice guide. Communication runs through all five, and Set Boundaries designs reporting and review cadences that support each one on complex programs.
Have a question that is not here? Ask Holly on a short call
