Home / Aerospace and defense program execution
When a program's status reports say one thing and your instinct says another, you need an independent read. Set Boundaries assesses program health from the outside, with evidence from the program's own data: schedule, cost, technical maturity, suppliers, risk and people. You get findings ranked by impact and a practical plan, in time to act on them.
Why get an outside assessment at all?
Program teams are close to their work and under pressure to show progress. That combination makes it hard to see, or say, that a plan no longer holds. Status reports drift optimistic, not through dishonesty but because every individual estimate is a little hopeful and nobody adds them up. An independent assessor has no stake in the current plan and no history to defend. That is what makes the assessment worth having: it tells leadership, and often the team, what the data actually says.
What does an assessment cover?
| Area | What we examine | Typical evidence |
|---|---|---|
| Schedule | Structural quality, critical path credibility, execution against the baseline | DCMA 14-point checks, GAO best practices, baseline execution index trend |
| Cost and earned value | Performance to date and realism of the estimate at completion | Cost and schedule performance indices, to-complete performance index, variance analyses |
| Technical | Design maturity, verification progress, open technical issues | Requirements status, test results, review action items |
| Supply chain | Critical supplier performance and readiness | Delivery history, first article status, supplier corrective actions |
| Risk | Whether the register reflects reality and handling plans are working | Register against actual issues, burn-down charts, reserve versus exposure |
| People and organization | Staffing against plan, key person dependencies, decision flow | Staffing curves, interviews, decision and action logs |
| Contract | Deliverables, requirements and obligations | Data deliverable status, open contract actions, customer correspondence |
Which numbers tell you the most about program health?
A few earned value and schedule measures, trended over several months, reveal more than any single report. The standard formulas are below.
| Measure | Formula | What it tells you |
|---|---|---|
| Cost performance index (CPI) | Earned value divided by actual cost | Value delivered for every dollar spent; below 1.0 means over cost |
| Schedule performance index (SPI) | Earned value divided by planned value | Work done against work planned to date; below 1.0 means behind |
| To-complete performance index (TCPI) | Remaining work divided by remaining budget, against the budget or the current estimate | The efficiency the rest of the program must achieve; far above the CPI to date is a warning |
| Independent estimate at completion | Actual cost plus remaining work divided by a performance factor, such as the CPI | A data-driven check on the program's own estimate at completion |
| Baseline execution index | Tasks completed divided by tasks planned complete | How reliably the team finishes what it planned; trend matters most |
| Critical path length index | Critical path length plus float, divided by critical path length | How much schedule margin really remains to the commitment |
One pattern appears often: a cumulative CPI that has settled below 1.0 rarely recovers on its own by the time a program is well into execution, yet the program's estimate at completion still assumes it will. When the to-complete index is far above the performance achieved so far, the estimate deserves a hard look.
How does the assessment run?
- Scope and questions. Agree with leadership what the assessment must answer and by when.
- Data request. Schedule files, earned value reports, risk register, requirements status, supplier data and contract deliverables.
- Analysis. Structural and performance analysis of the data before anyone is interviewed, so interviews test hypotheses rather than collect opinions.
- Interviews. The program manager, control account managers, engineering leads, key suppliers and, where appropriate, the customer.
- Findings. Each finding states the condition, the evidence, the cause and the consequence if nothing changes, ranked by impact.
- Recommendations and plan. Specific actions with owners and dates, starting with the few that change the outcome most.
- Briefing. A short readout to leadership, then to the team, with the full evidence available.
What makes a finding useful?
A useful finding is specific, evidenced and actionable. "Schedule risk is high" is not a finding. "The schedule shows a critical path through final assembly, but 23 percent of incomplete tasks have no successor, so the true driver of the delivery date cannot be identified; until logic is repaired, the forecast delivery date is unsupported" is a finding. It says what is wrong, how we know, why it matters and what to do. Leadership can act on it, and the team can recognize it as fair.
What happens after the assessment?
Three outcomes are common. The program is broadly healthy and the assessment confirms it, with a few targeted improvements; this is valuable in its own right, especially before a major review or when a customer is asking questions. The program has specific, fixable problems, and the team addresses them with a short, focused plan. Or the program needs a full recovery, and the assessment becomes its foundation. In every case, leadership makes the decision with evidence rather than impressions.
What does leadership receive at the end?
- A one-page summary of overall program health, the top findings and the decisions leadership needs to make.
- Ranked findings, each with its evidence, cause and consequence, so they can be checked and acted on.
- An independent estimate at completion and schedule forecast, built from the program's own performance data.
- An action plan with owners and dates, starting with the few actions that change the outcome most.
- The supporting analysis, including schedule health metrics and earned value trends, so the program team can repeat the checks themselves.
How is independence protected?
The assessor reports to whoever commissioned the work, not to the program being assessed. Findings are based on the program's own data and documented evidence, so they can be checked. The assessor does not sell a predetermined answer: an assessment that always concludes more consulting is needed is not independent. If the program is healthy, the report says so.
Holly starts with three questions. First, what are the actual requirements, the contractual ones rather than the accumulated requests? Second, what is the current status of the design and the work against those requirements? Third, what genuinely remains to be completed? The finding that most often surprises a client is how much of the team's effort is going into work the contract does not require, driven by informal requests from the customer's engineers. On one gearbox program that analysis, carried through each hardware iteration, substantiated scope-change claims.
What happens once the three questions are answered?
The answers become a plan and a conversation. Work that is outside the contract or uncontrolled is identified so leadership can stop it, a controlled path is set up for new customer requests, and a detailed plan to completion is built with the people who will do the work. Then Holly meets the customer and explains exactly what was found: where the program really is, what remains, and how it will proceed. The goal is to eliminate ambiguity. A customer that has been hearing optimistic status for months usually responds better to a plain, evidenced account with a plan than to another promise.
That meeting is often the turning point. It resets expectations to something the program can meet, and every commitment kept after it rebuilds confidence.
What does an assessment look like on a large program?
While at Triumph, Holly assessed the state of a wing program for the Bombardier Global 5000 and 6000 business jets, a program, and established an accurate path to First Flight. (Triumph and Bombardier are named to describe her career experience, not to imply a current affiliation with or endorsement of Set Boundaries.) The scale was far larger than a single component program, but the questions were the same: what is actually required, where the work really stands against it, and what genuinely remains before the next major event. An accurate path is more useful to leadership than an optimistic one, because it is the one they can plan the business around.
What does a client get from an assessment by Set Boundaries?
- An engineer's read of the program. Holly can understand the technical issue, challenge assumptions and help develop practical alternatives, then weigh them against schedule, budget, risk and requirements.
- A clear separation between contractual requirements and accumulated requests.
- A realistic path to the next major milestone and payment milestone, built from the team's own input rather than imposed from outside.
- A recommendation you can act on, including when the right answer is a short, focused fix rather than a full recovery.
Who commissions assessments?
Executives who own a portfolio of programs and want an honest view of one of them. Program managers who have inherited a program and want a clean starting point. Business development and capture teams preparing for a follow-on bid who need to know what the current program will say about them. And suppliers whose prime customer has raised concerns and who want to respond with evidence. The schedule and earned value analysis at the heart of the assessment is the same discipline we bring to every engagement.
If you want an honest read on a program before the customer forms one, schedule a call.
References
- US Government Accountability Office, Schedule Assessment Guide, GAO-16-89G.
- US Government Accountability Office, Cost Estimating and Assessment Guide, GAO-20-195G, including earned value analysis.
- SAE International and the Electronic Industries Alliance, EIA-748, Earned Value Management Systems.
- Defense Contract Management Agency, EVMS program analysis guidance and the 14-point schedule assessment.
- US Department of Defense, Risk, Issue, and Opportunity Management Guide for Defense Acquisition Programs.
Questions
Common questions
What is an independent program assessment?
An independent program assessment is an outside, evidence-based review of a program's health: schedule, cost and earned value, technical maturity, supply chain, risk, staffing and contract compliance. It is carried out by people with no stake in the current plan, which is what makes it useful. The output is a ranked set of findings with the evidence behind each one and a practical plan to act on them.
When should a program commission an independent assessment?
Common triggers are repeated slips of the same milestone, earned value indices drifting below plan for several months, a customer raising concerns, a new program manager taking over, a major review approaching, or leadership simply not trusting the status reports. The earlier it happens, the more options remain. An assessment done before a crisis is far cheaper than a recovery done after one.
How long does an independent assessment take?
It depends on the size of the program and how quickly data and people are available. A focused assessment of a single program is typically measured in weeks rather than months: a short data request, interviews with the program manager, control account managers and key suppliers, analysis, and a findings briefing. We agree the scope and timeline at the start so leadership knows when answers will arrive.
Will an assessment disrupt the program team?
Only lightly. Most of the work is analysis of data the program already has: the schedule, earned value reports, risk register, requirements and supplier records. Interviews are short and scheduled around the team. Handled well, an assessment often relieves the team, because it gives them an outside voice for problems they have been raising without being heard.
What is the difference between an assessment and an audit?
An audit checks compliance against a standard and produces a pass or fail. An assessment asks whether the program will deliver what it promised, and why or why not. It uses compliance where relevant, such as schedule structure or earned value practice, but its purpose is a clear picture of risk and a plan to act, not a certificate.
Who sees the findings?
Whoever commissioned the assessment decides. Most clients receive the findings first at leadership level, then share an agreed version with the program team and, where useful, with the customer. Findings are written to be fair to the people involved: they focus on conditions and causes, not blame, which makes it far more likely the team will act on them.
What are program assessments used for?
Program assessments are used to find out whether a program's plan still holds, what is really driving its problems, and what should be done next. Leadership uses them before major decisions, when status reports and instinct disagree, when a customer loses confidence, or before a milestone review. A good assessment covers schedule, cost, technical maturity, suppliers, risk and staffing, and ranks findings by impact. Set Boundaries conducts independent assessments of aerospace and defense programs using the program's own data, and delivers findings with a practical plan to act on them.
What does an independent assessor do?
An independent assessor reviews a program from outside the team, with no stake in the current plan, and reports what the evidence shows. The work usually includes analyzing the schedule and cost data, interviewing leads and suppliers, checking technical maturity and risk handling, and comparing reported status against actual performance. The output is a set of ranked findings and recommendations. Set Boundaries plays this role on aerospace and defense programs, testing schedules against the DCMA 14-point checks and GAO best practices so leadership gets a clear, evidence-based view.
Have a question that is not here? Ask Holly on a short call
