Pentagon reforms fail to reach brigade combat teams where kill chains remain too slow

A U.S. Army brigade combat team spent roughly 3,500 paratrooper hours attempting to build a digital kill chain before a real-world deployment, yet still ended up with a process too slow for combat. The experience of the 1st Brigade Combat Team, 82nd Airborne Division (1/82) during Operation Epic Fury reveals a gap between Pentagon-level reform promises and the authorities, technical support, and development access available to tactical formations under operational pressure.

Major Lucas Ziller, an infantry officer who served with the unit, detailed the shortfall in an analysis published October 9, 2026. He argued that while the 2025 drone and acquisition reforms and the 2026 Artificial Intelligence Strategy call for faster procurement and fewer integration barriers, "a kill chain measured in seconds cannot depend on processes measured in weeks or months." The brigade found that connecting sensors, targeting software, networks, and fires systems required bespoke configurations, constant troubleshooting, and manual data handoffs that introduced delays lethal targeting operations cannot tolerate.

The analog gaps in a digital process

1/82's legacy kill chain relied on junior paratroopers watching drone video, writing grid coordinates in notebooks, and verbally transmitting fire missions through multiple physical command posts. Quick-fire channels shortened the path by bypassing intermediate headquarters, but the underlying process remained voice-based and manual. "Every manual handoff introduced delays into the process, forcing capable and motivated paratroopers to spend precious time acting as data couriers and analysts," Ziller wrote.

The unit had access to Palantir's Maven platform and successfully integrated some digital systems, but data cleanliness and translation problems persisted even when links were established. Drone video could be routed to an IL5 cloud environment, yet operators still had to check and correct data manually. Targeting packets could not flow reliably to fire direction systems, forcing personnel to transmit them by hand. The lack of direct on-site engineering support made troubleshooting slow and labor-intensive.

Why enterprise reform stalls at the tactical edge

The Army command controlling funds restricted their release for brigade priorities. Integration approvals rested with different authorities depending on which systems were involved. Technical support arrived only intermittently. Ziller noted that formations like the 4th and 25th Infantry Divisions have demonstrated fully digitized fires chains during heavily supported experimentation efforts, but those benefited from purposeful funding and direct developer access that tactical formations do not routinely possess during operations.

Many enterprise controls serve legitimate purposes. Acquisition oversight protects public funds. Cybersecurity approvals protect networks. Targeting safeguards reduce error risk as data moves toward lethal effects. The challenge, Ziller said, is "balancing those assurances against the operational risk created when adaptation and approval timelines lag behind battlefield requirements."

Four changes to close the gap

Ziller proposed four specific delegations of authority and resources to brigade and division commanders.

Financial authority. Brigade commanders need funds made available for their integration priorities and authority to approve purchases of commercial equipment and software up to $50,000, plus technical service contracts up to $100,000. These purchases would remain bound by existing fiscal controls, competition requirements, and cybersecurity standards.

Integration authority. The first division-level commander in the operational chain should receive delegated authority to approve tactical system connections and conditional Authority to Operate modifications. Approvals would be scoped and time-limited, with defined interfaces, monitoring requirements, rollback procedures, and mandatory follow-on review. This moves bounded risk decisions closer to the operational problem rather than leaving them at department-level offices.

Technical expertise at the edge. Dedicated direct-support technical teams should work alongside brigades before and during combat operations. In the near term these would be contracted engineers; over time, the Army should build a military and civilian technical workforce with the system access needed to engineer data links, automate targeting workflows, and troubleshoot integrations continuously.

Direct access to AI development. Tactical formations should serve as continuous development partners with regular access to developers building warfighting AI tools. Brigades can contribute operational data to refine target recognition models and test AI-assisted fire direction workflows, shortening the feedback loop between battlefield experience and capability development.

Why this matters for government and operations professionals

For professionals managing acquisition, legal review, cybersecurity, or operational planning in defense and government contexts, the 1/82 case study surfaces a structural tension that no policy memo has yet resolved. Delegating purchasing and integration authority to tactical echelons creates genuine risks around fiscal controls, network security, and targeting safeguards. But withholding that authority creates a different category of operational risk when formations cannot adapt their kill chains at the pace of combat. The framework Ziller describes-time-limited, scoped authorities with mandatory post-implementation review and rollback procedures-offers one model for balancing those competing demands without abandoning either assurance or adaptability. The metric he proposes is blunt: whether a brigade can adapt its kill chain at the speed of the battlefield.