Industry

# Defense and Research

The prototype works, the program office has no funding line for it, and no operational unit has agreed to own it.

You will recognize this

## You have sat in this meeting.

- A transition review approves the technology for fielding, and the slide naming the operational owner reads 'TBD.'
- The lab ranks its research portfolio by technical merit, the acquisition office ranks by mission priority, and nobody compares the lists.
- Security accreditation work starts after the architecture is frozen, and the authority-to-operate package becomes the schedule.
- A speed initiative removes a milestone review, and later no one can say which decisions that review used to force.

What is changing

## What is changing in Defense and Research.

The White House's 2025 order on modernizing defense acquisitions pushes faster use of Adaptive Acquisition Framework pathways, and GAO is assessing whether reform implementation is designed for speed.

Cascade

### Research to usable capability

Large mission intent must decompose into testable increments and transition decisions.

Rank

### Portfolio choices under uncertainty

Funding, mission value, maturity, risk, and urgency need one visible tradeoff system.

Bridge

### The transition boundary

Researchers, acquisition teams, operators, security, and external partners must coordinate before the handoff becomes a valley of death.

Sources: [White House defense acquisition modernization order](https://www.whitehouse.gov/presidential-actions/2025/04/modernizing-defense-acquisitions-and-spurring-innovation-in-the-defense-industrial-base/), [GAO review of DoD acquisition reform](https://www.gao.gov/products/gao-25-107003)

The system view

## Where the pressure hits the system.

Hover a part of the system to see how this industry strains it. Select it to learn more.

parts of the system

- 1 **Surface***How work enters*
- 2 **Scope***How work is understood*
- 3 **Rank***How priorities are ordered*
- 4 **Cascade***How strategy becomes work*
- 5 **Flow***How work moves*
- 6 **Bridge***How groups connect*
- 7 **Signal***How the system reads itself*

The highlighted parts are where this industry puts the most pressure on how work moves.

What good looks like

## What good looks like when it holds.

What the work looks like once the system holds, and the signal that shows it.

### Transition owner and funding named at program start

Every research effort past early maturity lists an operational sponsor and a target acquisition pathway.

### One ranking across research, acquisition, and mission priorities

Lab and acquisition leaders review a single ranked portfolio against shared mission criteria.

### Speed gains that still show who decided and why

Each removed review has a documented replacement signal and a named decision-maker.

Where to start

## Pick the entry point that matches what you see.

Each starting point names the condition you can see today and the service that addresses it first.

[Portfolio Governance If research and acquisition portfolios are ranked in separate rooms, start with Portfolio Governance.](https://www.agileon.com/professional-services/portfolio-governance)[Operating Model Design If transitions stall because no one owns the handoff from lab to operator, start with Operating Model Design.](https://www.agileon.com/professional-services/operating-model-design)[Embedded Coaching and Facilitation If new acquisition pathways exist on paper but program reviews still run the old gates, start with Embedded Coaching and Facilitation.](https://www.agileon.com/professional-services/embedded-coaching)

From the field

## The same pattern, in other rooms.

Some of these come from other industries. The same component fails the same way here.

[Field story The Quality Problem Began Before Testing At a research and advisory firm, the internal acceptance tester was finding defects faster than she could log them. More testing wasn't the answer. Each team wrote down, and took ownership of, what done had to mean before work left its hands.](https://www.agileon.com/insights/the-quality-problem-began-before-testing)[Field story Portfolio Governance Without Bureaucracy A global IT organization's front-office delivery group was drowning in requests that all arrived marked urgent. The answer was not another approval meeting. It was a set of written prioritization policies that let the team say not yet, with a reason, and sent disagreements to a forum instead of a fight.](https://www.agileon.com/insights/portfolio-governance-without-bureaucracy)[Field story Your Goals Never Reach the Work A CIO demanded a roadmap for every business area within a month, and his business partners blamed their tools. The real gap was that the outcomes leaders agreed on never reached the teams in a form they could build. Once they did, the first forecast showed a commitment that could not be met.](https://www.agileon.com/insights/field-note-044-goals-never-reach-work)
