Home / Aerospace and defense program execution
You have just won one of the largest programs in the company's history. The customer expects a program office, a schedule they can trust, and a program manager who can hold a technical conversation with their engineers. You do not have that yet. The question on the table is whether to build a PMO yourself or bring one in, and the honest answer depends on how much time the program gives you.
The short version
| Build an in-house PMO | Bring in an outside program office | |
|---|---|---|
| Time to a working plan | Months: recruit, onboard, then build | Typically a signed charter and plan within one to two weeks |
| Method | Designed as you go, often on the live program | Arrives already proven on similar programs |
| Cost pattern | Lower hourly cost; salary, benefits and overhead continue indefinitely | Higher hourly cost; scaled to the program and built to end |
| Institutional knowledge | Stays with you from day one | Must be deliberately transferred; stays if the work lives in your systems |
| Independence | Inside the organization's politics | Can say plainly what is and is not in scope |
| Best fit | A steady flow of programs and time to build properly | A major program that has to start or recover now |
What a program office has to do in the first months
Before comparing options, it helps to be clear about the job. A program office on a major aerospace, defense or maritime program has to establish the requirements and what done means, agree scope, schedule, major and payment milestones, budget and roles in a charter, and build an integrated schedule the team actually believes. It has to stand up an interdisciplinary team so engineering, quality, supply chain and manufacturing attack the same problem with the same priorities. It has to run a cadence: frequent coordination, a weekly look-ahead, monthly risk and opportunity reviews. And it has to communicate, with the customer at least weekly and with senior leadership at least monthly.
Above all, it has to control scope. The most common way a newly won program goes wrong is not a technical failure. It is an engineering team responding to every request from the customer's technical organization without asking whether the request is a contractual requirement or what it does to cost and schedule. A program office exists to put a controlled path around that.
What does a program office own, and what stays with the departments?
The program office owns the plan, the boundaries and the communication, and the departments keep ownership of how their work gets done. Getting this split clear early prevents the two most common arguments on a new program: the office that tries to run engineering, and the department that treats the schedule as a suggestion. The split is the same whether the office is built in house or brought in.
| Area | The program office owns | The departments own |
|---|---|---|
| Requirements and scope | What the contract requires, what done means, and the controlled path for new customer requests | Technical judgment on how a requirement is met |
| Schedule | The integrated schedule, the baseline, the critical path and the weekly look-ahead | Realistic durations for their own tasks, and saying early when one will move |
| Budget and cost | Cost visibility at program level and the estimate at completion | Spending within their allocation and flagging overruns as they appear |
| Risk and opportunity | The register, the monthly review and mitigation tasks placed in the schedule | Raising risks in their area and carrying out the mitigation |
| Customer communication | Status, commitments and the record of what was agreed | Technical detail when the conversation needs it |
| Decisions | Bringing tradeoffs to leadership with the cost, schedule and risk of each path | The options and the engineering facts behind them |
| People | Clear priorities and boundaries for the interdisciplinary team | Hiring, assignment and line management of their staff |
Write this split into the Project Charter under roles and responsibilities. When a conflict comes up later, the charter settles it rather than whoever argues hardest.
The case for building your own PMO
There are good reasons to build in house, and for many companies it is the right long-term answer.
- Lower long-run cost per hour. Once staffed, an internal team costs less per hour than outside support, and the gap matters over years of programs.
- Knowledge stays put. Your people learn the customer, the product and the organization, and that knowledge compounds.
- Culture. A program office run by your own leaders reflects how your company wants to work, and it is easier to hold accountable through normal management lines.
- Portfolio view. If you run several programs at once, an internal PMO can standardize methods and share resources across them.
If the company has a steady pipeline of programs, time before the next major award, and leaders who have run program offices before, building your own is sensible. The question is whether this program gives you that time.
What building one really involves
Building a PMO is not the same as hiring a program manager. You need a leader with real aerospace or defense program experience, ideally through qualification and certification. Those people are in demand and can take months to find. Once hired, they need time to learn your product, your customer and your organization. Then someone has to build the method: charter templates, a scheduling standard in Microsoft Project, risk and opportunity management, earned value or cost visibility, reporting formats and an escalation path.
The cost is not only salary. Federal data on employer compensation costs shows benefits alone make up roughly 30 percent of total compensation in private industry, before recruiting, space, equipment and the management time spent onboarding. And the most important cost is hidden: the first program the new PMO runs is also the program it learns on. If that program is the largest win in the company's history, the learning curve sits on the critical path.
What does each option really cost over the life of a program?
More than the hourly rate on either side, so compare whole costs over the same period. An in-house office looks cheaper on a rate card and an outside office looks cheaper on a hiring plan. Neither view is complete. List the costs below against the actual program dates before deciding, including the ones that only appear if the program starts slowly.
| Cost element | In-house PMO | Outside program office |
|---|---|---|
| Finding the leader | Recruiting fees or internal recruiting time, plus the months the role sits open | Selection of a provider, usually measured in weeks |
| Getting to a working plan | Onboarding time, then building the method while the program runs | Charter and plan built early from an existing method |
| Ongoing labor | Salary, benefits and overhead, continuing after the program ends | A higher rate for a defined period, scaled down as the program stabilizes |
| Tools and templates | Scheduling standard, registers and report formats built from scratch | Brought in and set up inside your own systems |
| Learning on the live program | Carried by the program, often on the critical path | Mostly carried before the engagement started |
| Slip exposure | Higher in the first months while the office is forming | Lower at the start, if the provider has real authority and access |
| Ending or handing over | No exit cost, but a weak hire is slow and costly to replace | A planned handover, which needs your time to absorb |
The row that usually decides it is slip exposure. Put a value on a missed payment milestone, a late delivery or a customer penalty, and set it against the difference in labor cost over the same months. On a large first program the comparison is rarely close. On a small program with no hard dates, the rate difference may well win. See how engagements are structured and priced for how outside support is usually scoped.
The case for an outside program office
An outside program office trades a higher hourly cost for speed, method and independence.
- Speed. Set Boundaries typically delivers a signed Project Charter and an executable plan in Microsoft Project within the first one to two weeks, built from conversations with your functional managers and the people doing the work.
- A method that already works. The charter, integrated schedule, interdisciplinary team, critical-path management and communication rhythm have been used on engine controls, gearboxes, fuel pumps, displays and naval programs. None of it has to be invented on your program.
- Engineering depth. Holly is an engineer. She can understand a technical issue, challenge assumptions and weigh alternatives against schedule, budget, risk and requirements, which matters when the customer's engineers are pushing for changes.
- Independence. An outside program manager can tell the customer, and your own leadership, exactly what the contract requires and what a request will cost, without the internal history that makes those conversations harder.
- Scalability. Project Engineers are added where the plan needs them and reduced as the program stabilizes.
How do you evaluate an outside program office before signing?
Ask what the first two weeks will produce and how the engagement ends. Most providers can describe a method. Fewer can say exactly what you will have in hand after the first fortnight, whose systems it lives in, and what has to be true for them to leave. These questions separate a program office from a reporting service.
| Question | What a good answer looks like |
|---|---|
| Who is the program manager, by name? | A named person with experience on comparable programs, not a role to be filled after signing |
| What will exist after two weeks? | A signed charter and an executable integrated schedule, built with your functional managers |
| Where does the work live? | In your systems and files, so status and data stay under your control throughout |
| How are customer requests handled? | A controlled path that checks whether a request is a contractual requirement and what it does to cost and schedule |
| Can they engage technically? | Enough engineering depth to challenge assumptions and weigh alternatives, not only track dates |
| What authority do they need from you? | A clear statement of the decisions, people and access required, and what happens if one is missing |
| How does it end? | Defined exit conditions, such as milestones met and deliveries started, or a working office handed to your team |
Be wary of an answer that measures success in reports produced or hours billed. The purpose is a program that delivers on its commitments. Set Boundaries answers these questions in the first conversation, and the how we work page sets out the phases in order.
The honest drawbacks of bringing one in
Outside support is not free of risk, and it is better to name the tradeoffs than to discover them.
- Higher hourly cost. Per hour, outside program management costs more than an employee. It is justified by speed and outcome, not by rate.
- Dependence. A company can end up relying on outside support it never intended to keep. The engagement has to be designed to end.
- Knowledge leaving. If the schedules, registers and reports live in the consultant's tools, the knowledge walks out at the end. It has to live in yours.
- Authority and access. An outside program manager needs real decision-making autonomy, an interdisciplinary team and access to your systems. Without them, the engagement produces reports rather than results.
- Style. Holly communicates very directly. Organizations used to reading between the lines sometimes need a short adjustment.
The middle path: an outside office that builds your own
The choice is often framed as either one or the other. In practice, the strongest option for a company that has just won a major program is frequently both, in sequence. An outside program office starts the program correctly now, and is designed from the first day to leave behind a program office you own.
That is how Set Boundaries approaches it. The goal is not permanent dependence. When we leave, one of two things should be true: the customer is satisfied, commitments are delivered, milestone payments have been achieved and production deliveries have started; or your organization has a repeatable PMO process and a culture that knows how to execute it. Three practical choices make that work:
- Work inside your systems. The charter, integrated schedule, risk and opportunity register and reports are built in your environment, so they are yours from the start and keep working after we leave.
- Your people are the team. The interdisciplinary team is made of your engineers and functional leads. They learn the cadence by running it, not by reading about it.
- Plan the handover. If you intend to hire an internal program manager, that person can join while the program is stable and inherit a working office rather than a blank page.
This answers the main objection to outside support. You pay the higher rate for a defined period, the program starts on time, and what you are left with is the in-house capability you would have tried to build anyway, already proven on your most important program.
What should a handover to your own program office include?
A working office, not a folder of documents. The test of a handover is whether your program manager can run next week's look-ahead, next month's risk review and the next customer update without help. Plan it as a phase of the program with its own dates, and check each item below before the outside office steps back.
- The charter, current and under change control. Scope, milestones, roles and the escalation path reflect the program as it stands, with every approved change recorded.
- The integrated schedule with its baseline. Logic linked, owners assigned and the critical path visible, in your copy of Microsoft Project, with a record of why the baseline moved when it did.
- The risk and opportunity register. Open items with owners, mitigation tasks already in the schedule, and the date of the next review.
- The decision and action record. What leadership decided and why, and which actions are still open, so nothing has to be agreed twice.
- The customer record. What has been committed, what has been delivered, which requests were accepted as changes and which were declined.
- The cadence, already run by your people. Your program manager has chaired the weekly look-ahead and a monthly review before the handover date, with the outside office present but not leading.
- An introduction to the customer. The customer hears about the change of program manager from the program, in person, before it happens.
When these are in place, the higher rate stops and the program keeps its rhythm. When they are not, the handover date should move, because a program office that leaves early can cost more than one that stays a few extra weeks.
Common mistakes when a company first needs a PMO
- Making the lead engineer the part-time program manager. It seems economical, but the program then loses its best engineer and gains a program manager with no time to do the job.
- Buying software instead of a process. A scheduling tool does not decide scope, run a look-ahead or tell the customer no. The method matters more than the tool.
- Hiring for status reporting. A program office that only reports status tells leadership what went wrong after the fact. At a defense display manufacturer that had previously used another consulting organization for program support, the change came when the office started helping the team execute rather than simply reporting.
- Waiting for the customer to complain. By the time a customer raises penalties, the program needs recovery rather than setup, and recovery is slower and more expensive.
Does the contract or customer expect a particular kind of program office?
Often, yes, and the contract is the first place to check. A customer in aerospace or defense rarely writes "have a PMO" into a contract, but many contracts carry requirements that only a working program office can meet. Read the clauses and data deliverables before choosing, because they set the minimum the office has to produce from the first month.
| Expectation | Where it usually comes from | What it means for the decision |
|---|---|---|
| Earned value management | DFARS 252.234-7002 on larger cost or incentive defense contracts, calling for a system that complies with EIA-748 | Someone must set up and run cost and schedule integration correctly from the start, which is hard to learn on the job |
| Schedule and cost data deliverables | Contract data requirements lists, which may call for integrated program management data and schedule submissions | The schedule has to be built to a standard that will survive customer review |
| Schedule quality | Customer reviews that often draw on the GAO Schedule Assessment Guide (GAO-16-89G) | A schedule with weak logic or missing links will be found quickly |
| Planned and controlled operations | AS9100D, which requires operations to be planned and controlled, including risk and configuration management | Program planning and records have to fit inside the quality system |
| Program reviews | Statement of work requirements for design reviews, program reviews and status reporting | Reviews need a prepared program office behind them, not a slide deck assembled the night before |
| Change and scope control | The changes clause and the contract's definition of deliverables | Every customer request needs a controlled path, or work outside the contract gets absorbed |
If several of these apply and nobody in the company has delivered them before, that weighs toward bringing in experience for the start of the program, at least long enough to set the standard your own office will follow.
How to decide
Four questions usually settle it:
- When is the first major or payment milestone, and could a new hire realistically be recruited, onboarded and effective before it?
- Does anyone in the company today have program office experience through qualification on a program of this size?
- Is this program the start of a steady pipeline, or an unusually large single win?
- If the program slipped six months, what would it cost in payments, penalties and reputation?
If the milestones are close, the experience is thin and the cost of slip is high, start with an outside program office and design it to hand over. If you have time, experience and a pipeline, build your own, and consider outside help only to set up the method.
Just won a program and not sure where to start? A short conversation is usually enough to see whether you need a program office now, a plan to build your own, or both. Schedule a call and we will tell you plainly what we see.
Related guides
- Program management office
- How engagements are structured and priced
- Contract program manager or full-time hire
- A program execution firm or a large consultancy
- How we work
- Questions buyers ask before hiring Set Boundaries
References
- U.S. Bureau of Labor Statistics, Employer Costs for Employee Compensation. bls.gov
- U.S. Government Accountability Office, GAO-16-89G, Schedule Assessment Guide: Best Practices for Project Schedules.
- U.S. Government Accountability Office, GAO-20-195G, Cost Estimating and Assessment Guide.
- SAE International, EIA-748, Earned Value Management Systems.
- DFARS 252.234-7002, Earned Value Management System.
- SAE International, AS9100D, Quality Management Systems: Requirements for Aviation, Space, and Defense Organizations.
- Project Management Institute, The Standard for Program Management.
Questions
Common questions
Should a company that just won its first major program build a PMO or outsource it?
If the first major or payment milestone is close and nobody in the company has run a program office through qualification, starting with an outside program office is usually safer, because recruiting and onboarding an experienced leader can take months. If there is time and a steady pipeline of programs, building in house makes sense. Many companies do both in sequence: an outside office starts the program correctly and hands over a working process.
How long does it take to set up an in-house PMO?
Longer than most leaders expect. Finding a program manager with real aerospace or defense qualification experience can take months, and the new hire then needs time to learn the product, customer and organization. Someone also has to build the method: charters, scheduling standards, risk management, cost visibility and reporting. An outside program office can typically produce a signed charter and executable plan within the first one to two weeks.
Will an outside program office leave us dependent on it?
It should not, and it is worth asking any provider how they prevent it. Set Boundaries works inside your systems, so the charter, schedule, registers and reports are yours from the start. Your own people form the interdisciplinary team and learn the cadence by running it. The engagement ends when the program is delivering or when you have a repeatable PMO process and a team that knows how to execute it.
Can an outside program manager work with our internal hire?
Yes, and it is often the smoothest route. An internal program manager can join while the program is stable, work alongside the outside program office, and inherit a working charter, integrated schedule and communication rhythm rather than a blank page. The handover is planned rather than improvised, which protects the program and gives the new hire a proven structure to run from the first day.
What is the difference between a PMO and a program manager?
A program manager leads a specific program. A program management office is the structure around the work: the charter, integrated schedule, interdisciplinary team, cadence of reviews, risk and opportunity management and reporting. In the Set Boundaries model, Holly serves as the Program Manager and also establishes that structure, supported by Project Engineers where the program's complexity calls for them, so both roles are covered from the start.
Is an in-house PMO always cheaper in the long run?
Per hour, yes, once it is staffed and working. In total, it depends. An internal office carries salary, benefits and overhead indefinitely, and its first program is also the one it learns on. If that program is large and customer-critical, the cost of a slow start can outweigh years of rate savings. For a company with a steady pipeline and time to build, an in-house PMO is usually the right long-term answer.
Have a question that is not here? Ask Holly on a short call
