From PEO to PAE: Org Charts Don’t Deliver Outcomes

When the Department of War (DoW) unveiled its latest acquisition transformation, the headlines focused on speed, fewer layers, consolidated authority, and portfolio leadership. The shift from service Program Executive Officers (PEO) to Portfolio Acquisition Executives (PAE) was framed as a way to deliver capability faster and cut through bureaucracy.

That’s directionally right. The Department has been clear about its intent to empower PAEs with authority and accountability for outcomes.

Where this breaks down is in execution. Without creating the mechanisms to actually move resources, enforce tradeoffs, and realign incentives, this is only aspirational.

What exactly is a portfolio?

There is no single approach to portfolio definition. A portfolio might be constructed around a critical technology (such as robotics and autonomy), a capability (space access), or an operational area (maneuver). Each possible focus implies a different set of tradeoffs, authorities, and measures of success. But one thing that should be common across individual PAE design choices is that a portfolio implies a related, coherent set of investments that collectively produce a warfighting effect within its focus. As with other portfolio applications such as a venture capital fund, corporate strategy, or enterprise manufacturing operations, the common denominator is the ability of the leader to optimize for a desired, overall outcome by dynamically allocating resources and balancing long- and short-term results.

Without clear expectations and authorities that match this fundamental definition, PAEs are left to interpret the role for themselves, yielding predictable confusion. Across the services, many are still unclear on what authority they actually have: Can they consolidate funding across programs? Shift budget between efforts mid-cycle? Override program-level constraints to hit a portfolio outcome? In most cases, the answer is not clearly defined.

Changing the Paradigm

The uncomfortable reality is that being good at running programs is not the same as being good at running portfolios.

Programs are built to optimize within defined boundaries, protecting cost, schedule, and performance inside their lane. Portfolios operate across those lanes, determining how resources, risk, and attention move between programs in pursuit of system-level outcomes.

That shift is not simply a broader span of control. It reflects a different operating philosophy.

A portfolio can underperform even when every program is technically sound. That’s the tension PAEs inherit. A cyber portfolio might fund three pilots across separate programs, each producing promising results. Yet if none are resourced for transition into sustained funding lines, the portfolio has effectively paid for experimentation without changing the operational baseline. On paper, progress. In practice, stasis.

In one recent portfolio review I worked on, leaders discovered that a critical capability needed to close a kill chain was fragmented across several divisions. Each division was funding and delivering a piece of the solution independently. On paper, progress was visible in every lane. What no one was measuring was whether the integrated capability was being delivered in a way that mattered to warfighters.

When the portfolio realigned its metrics around a shared outcome – deploying the integrated capability to theater within twelve months – the implications were immediate. Budgets were pooled to concentrate investment on the components that determined delivery timelines. Governance was streamlined to reduce cross-division handoffs. Decision rights were clarified so tradeoffs could be made at the portfolio level rather than negotiated program by program.

Changing the org chart alone won’t lead to these results. Only an operating model built to fit will.

Portfolio leadership is a design choice

Portfolio leadership is about deliberately shaping how the system behaves.

Every acquisition organization already has budget authority, acquisition pathways, process controls, legal constraints, and workforce incentives. The differentiator is not whether those levers exist. It’s whether portfolio leaders force them to operate as a system instead of as separate silos.

Effective PAEs treat alignment as a design responsibility. They make explicit choices about where authority lives, how resources move across programs, and which outcomes outweigh local optimization. They decide how tradeoffs will be made before pressure forces them. 

Tradeoffs inside defense acquisition aren’t only technical. They’re institutional and reputational. Portfolio leadership requires not only authority, but the willingness to absorb friction when reallocating resources away from entrenched programs. Without that discipline, “portfolio” becomes a reporting construct rather than a decision-making one.

This is why Department guidance increasingly invokes the CEO analogy: not as a statement about stature or control, but about system architecture.

CEOs don’t succeed because they personally make every decision. They succeed because they design organizations where decision rights are clear and placed deliberately, incentives reward the outcomes the enterprise actually values, and tradeoffs are explicit, fast, and repeatable. Just as important, they build enterprises that continue to function when leadership changes, because the operating logic is embedded rather than improvised. This is especially important in the DoW, where leadership rotation is frequent. Operating models ensure a more stable, and enduring, foundation, than personal intervention.

In addition, private-sector CEOs manage market, competitive, and economic risk alongside cost and schedule. Department leaders have historically optimized for cost, schedule, and performance, even when other forms of risk, like operational relevance or industrial base fragility, are more consequential. Portfolio leadership requires expanding that aperture.

It’s time to lock in

A few months into the transition, a pattern is already clear. The PAEs who are making progress are not the ones focused on structure. They’re the ones forcing clarity on decisions, metrics, and incentives in their first 90 to 180 days:

• Locking in clear decision rights throughout the portfolio organization so authority doesn’t drift upward under pressure and bottleneck in two or three people.
• Establishing explicit rules for making and revisiting tradeoffs so resource shifts are deliberate rather than reactive. 
• Aligning incentives to speed, learning, and delivery rather than activity.
• Implementing metrics that track capability outcomes instead of process compliance.
• Ensuring alignment across budget, acquisition, policy, process, and workforce levers so the system reinforces itself rather than working at cross purposes.

Once embedded, these choices compound. Performance accelerates because authority, incentives, and measurement all point in the same direction. 

The transition from PEOs to PAEs is a rare opportunity. Focus on structure and you get reorganization. Take the next step to focus on how decisions, resources, and incentives actually work within that structure, and you get results that endure.

The Department has reorganized before. It has rarely changed how decisions and resources actually interact. This represents one of the few moments where those levers can be intentionally realigned. If that opportunity passes without embedding new operating logic, the system will revert to program protection over portfolio advantage. 

The Department, like many organizations before it, faces the decision of stopping at easy structural change instead of continuing forward into the hard, but necessary, behavioral change that must accompany it. The good news is that the latter – while hard – when done correctly, sets the conditions for a flywheel of future success. PAEs will determine whether this reform cycle becomes another chapter in organizational reshuffling or the moment acquisition finally aligns authority, capital, and accountability around outcomes.

Meagan Metzger is the Founder and CEO of Dcode.