Home / Aerospace and defense program execution
Your program is in trouble and you are deciding what kind of help to bring in. A report with recommendations, or people who will do the work with your team until it is fixed? Both are legitimate. They solve different problems, and choosing the wrong one wastes months you probably do not have.
What does each approach actually deliver?
| Advisory consulting | Embedded execution | |
|---|---|---|
| Main output | Findings and recommendations | Work done: schedule rebuilt, suppliers recovered, milestones delivered |
| Who implements | Your team | The embedded team with your team |
| Duration | Usually weeks | Until the agreed outcome is reached |
| Where the team sits | Mostly outside the program | Inside the program, in its daily rhythm |
| Accountability | For the quality of the analysis | For the result |
| Best for | Strategic questions, diagnosis, independent opinions | Recovery, start-up, closeout, capacity gaps |
Why do recommendations so often stall?
Because the people who have to implement them are the same people who were already stretched when the program got into trouble. A good report adds a list of important tasks to a team that has no time for its current list. Unless someone is freed up, or brought in, to carry the changes through, the recommendations compete with daily firefighting and lose. This is not a criticism of advisory work; it is a limit of it. Insight without capacity changes little on a program that is already overloaded.
Why does embedded execution work on programs in trouble?
Because it adds method and capacity together. An embedded team repairs the schedule while the program keeps running, works the supplier constraints directly, runs the weekly rhythm, prepares the customer reviews and closes the technical backlog. The program's own people learn the methods by working alongside it, so the improvements outlast the engagement. And because the embedded team is accountable for the result, it has every reason to focus on the few things that change the outcome.
Which approach fits your situation?
| Your situation | Better fit |
|---|---|
| You need a strategy for a new market or business line | Advisory |
| You need an independent view of a program's health for leadership or a customer | Advisory or independent assessment |
| The program is slipping and the team is already stretched | Embedded execution |
| A new award must be set up properly and quickly | Embedded execution |
| A closeout has stalled with many open threads | Embedded execution |
| You know what is wrong and have capacity to fix it | Advisory input, or none at all |
What does embedded execution look like in practice?
On a typical recovery, an embedded program manager and project engineers join the program's rhythm in the first week. They test and repair the schedule, inventory every open issue, and start working the critical path constraints: supplier deliveries, engineering changes, first articles and decisions waiting on someone. Within weeks the program has a schedule it can trust, a clear list of what drives the finish date and people actively moving it. The customer sees a plan and then sees milestones hit. When the program holds on its own, the embedded team hands over and leaves.
What does advisory consulting do well?
A lot, in the right situation. Strategy firms bring breadth across industries, benchmark data, and the ability to frame a hard question for a board. They are well suited to decisions about markets, portfolios, acquisitions and organizational design, where the output really is a decision rather than a delivered program. An outside diagnosis also carries weight with customers and boards precisely because the firm is not part of the program. The mistake is not using advisors; it is using them to solve an execution problem.
What does an embedded team need from you on day one?
Three things, and an embedded engagement stalls quickly without any one of them. The first is decision authority that matches the job. If the program manager you bring in cannot stop out-of-scope work, set weekly priorities or call a meeting with the customer, they become an expensive status reporter. The second is a real interdisciplinary team: engineering, manufacturing, quality, supply chain and contracts people who are named, available and expected to show up. The third is access to the information and systems the program actually runs on, including the schedule, the contract and its modifications, the cost data and the open action lists.
Set Boundaries prefers to work inside the client's own computer environment for that reason. The plan, the data and the status history stay with your company, and nothing has to be rebuilt when the engagement ends. Advisory firms usually need much less on day one, because they are studying the program rather than running it. That difference is a useful test in itself: if you are not prepared to give an outside team authority, people and access, you are buying advice, whatever the proposal calls it.
What should you see in the first 30 days of an embedded engagement?
- An honest assessment of where the program stands, shared with leadership
- A schedule tested against structural checks, with repair under way
- Every open issue listed with an owner and a date
- The critical path constraints named, with actions already moving on them
- A weekly rhythm running, and the first customer communication prepared
If none of that is visible after a month, the engagement is not working, whatever the reports say.
How do you measure whether the help is working?
Measure the program, not the engagement. Status slides and workshop counts tell you the help is busy; they do not tell you the program is recovering. The measures below are ones a program office, a customer reviewer or a government analyst would recognize, and most can be read straight from the schedule and cost data you already keep.
| Measure | What it tells you | Where it comes from |
|---|---|---|
| Schedule health checks | Whether the schedule is a working model or a drawing: missing logic, hard constraints, high float and invalid dates | The DCMA 14-point schedule assessment and the GAO Schedule Assessment Guide |
| Baseline execution | Whether tasks that were planned to finish by now actually finished | The baseline execution index in the DCMA 14-point assessment |
| Critical path movement | Whether the forecast finish date is holding, slipping or recovering from week to week | The integrated master schedule, statused against a fixed date |
| Cost and schedule performance | Whether the work being done is costing what was planned and keeping pace with the plan | Earned value data, where the program runs an EIA-748 system |
| Milestones and payment milestones | Whether the commitments the customer pays for are being met | The contract and its milestone schedule |
| Open issues with owners and dates | Whether problems are being closed faster than they appear | The program action and risk registers |
An advisory engagement can be judged on the quality and usefulness of its findings. An embedded engagement should be judged on these numbers moving in the right direction, and the firm should expect to be. See Microsoft Project scheduling and EVMS and EIA-748 for how the underlying data is built.
What are the signs you brought in the wrong kind of help?
A thick report that nobody on the program has time to act on. Workshops that produce action lists owned by people already on the critical path. A second assessment commissioned because the first one was never implemented. Or, the other way round, an embedded team doing work your people could do, when all you needed was a clear outside opinion. Matching the help to the problem avoids both.
What should you ask either kind of firm?
- What exactly will we have at the end of the engagement?
- Who will do the work, and will they be the same people we meet in the sales process?
- How will progress be measured, and how often will we see it?
- Who implements the recommendations, and with what time?
- When and how does the engagement end?
- What will our own team be able to do afterwards that it cannot do now?
How should you scope the contract for each kind of help?
Write the contract around what you will have at the end, not around hours. For advisory work that means naming the questions to be answered, the evidence the findings will rest on, and the form and date of the final product. For embedded execution it means naming the program outcome, the authority the team will hold, the cadence of reporting to leadership and the customer, and the conditions under which the engagement ends. Either way, agree in writing how changes in scope are handled before the first one arrives.
If your program is a government contract, two parts of the Federal Acquisition Regulation are worth knowing. FAR Subpart 37.2 defines advisory and assistance services, the category much consulting support falls into when an agency buys it directly. FAR Subpart 9.5 covers organizational conflicts of interest, which can limit what a firm that helped shape a requirement or evaluate a program may later perform on it. Neither stops you hiring help for your own company's program, but both explain why a customer may ask who your outside support is and what role it plays. Your contracts team should confirm how they apply to your specific contract.
How do the costs compare?
Advisory fees are usually concentrated over a short period and can look smaller in total. The implementation cost, and the cost of recommendations that are never implemented, falls on your program. Embedded execution usually carries higher direct fees because people are engaged for longer, but it includes the implementation. On defense programs where a slip to a contract milestone has real financial and relationship consequences, the relevant comparison is the total cost to reach the outcome, including the cost of time.
How does an embedded engagement end well?
With a handover the program barely notices. By the time the embedded team leaves, the schedule should be maintained by your people in your systems, the weekly rhythm should run without outside help, and everyone on the program should be able to answer three questions without looking anything up: where are we, where are we going, and what has to happen next to get there. For a development program in recovery, Set Boundaries treats milestone payments achieved and production deliveries started as the point where recovery is complete. From there the client decides whether continued support, such as help through the transition to production, still adds value.
An advisory engagement ends when the report is delivered. That is cleaner on paper, and it is the right model when the report is the product. When the product is a delivered program, the end of the engagement should be tied to the program's result instead.
Can an embedded team also give independent advice?
Yes, and it often starts that way. An embedded engagement usually begins with an honest assessment of where the program stands, shared with leadership before the recovery plan is set. The difference is what happens next: the same people who found the problems stay to fix them, which keeps the advice practical, because advice that the adviser has to execute tends to be realistic.
A report tells you what is wrong. A program office changes what happens next week. When Set Boundaries works with a client, Holly serves as the program manager and owns time, money, strategy and major stakeholder communication, and our project engineers execute against that plan with the client's team. One client that had previously used another consulting firm ended up with a technical program office capable of helping the team execute rather than simply reporting status. And we work inside the client's own systems, so the plan, the data and the status stay with them.
Where does Set Boundaries fit?
Set Boundaries is built for embedded execution. We assess honestly, then do the work with your team: front-end planning, program recovery and project closeout. When a client needs only an independent view, we provide that too, and we will say so if advisory input alone is enough.
If your program needs people who will stay until it is fixed, schedule a call.
Related guides
- Program management firm or staffing agency?
- Contract program manager or full-time hire?
- Independent program assessment
- Aerospace and defense program execution
References
- US Government Accountability Office, Schedule Assessment Guide: Best Practices for Project Schedules, GAO-16-89G.
- US Government Accountability Office, Cost Estimating and Assessment Guide, GAO-20-195G.
- Defense Contract Management Agency, EVMS program analysis guidance, the source of the 14-point schedule assessment.
- SAE International and the Electronic Industries Alliance, EIA-748, Earned Value Management Systems.
- Federal Acquisition Regulation, Subpart 37.2, Advisory and Assistance Services.
- Federal Acquisition Regulation, Subpart 9.5, Organizational and Consultant Conflicts of Interest.
Questions
Common questions
What is the difference between embedded execution and advisory consulting?
Advisory consulting studies a problem and delivers recommendations; your team then implements them. Embedded execution puts experienced people inside the program to do the work alongside your team, from rebuilding the schedule to running supplier recovery and customer reviews, and they stay until the result is achieved. One transfers insight; the other transfers capacity and accountability for getting it done.
When is advisory consulting the right choice?
When the question is strategic or diagnostic and your team has the capacity to act on the answer: choosing a direction, assessing an acquisition, benchmarking an organization, or designing a new operating model. Advisory work is also valuable when an independent view is needed for a board or customer. It is less effective when the program already knows roughly what is wrong but lacks the people to fix it.
When is embedded execution the right choice?
When the program needs to be delivered, not only diagnosed: a recovery, a new program that must be set up properly under time pressure, or a closeout that has stalled. It also fits when the team is stretched and recommendations would simply add to its workload. Embedded teams bring method and capacity at the same time, which is what programs under pressure usually need.
Is embedded execution more expensive than consulting?
It depends on what is measured. Advisory engagements are often shorter, so their total fee can be lower, but the cost of implementation, and of recommendations that are never implemented, sits with you. Embedded execution usually costs more in direct fees and less in total cost to reach the outcome, especially where schedule slip is expensive. Compare the cost of the result, not the cost of the report.
Can the two approaches be combined?
Yes. A short independent assessment is often the right first step, giving leadership an evidence-based view of the program. If it shows the program needs recovery, the same team or another can then embed to execute. What matters is that the assessment leads to action with named owners, rather than a report that competes with day-to-day pressure for attention.
How do I know if my team can implement recommendations on its own?
Look at capacity and track record. If the people who would implement the changes are already on the critical path, or previous recommendations were accepted but never completed, adding more recommendations will not change the outcome. If the team has time, the authority to change how the program runs and a history of following through, advisory input may be enough.
Have a question that is not here? Ask Holly on a short call
