Article reader Listen + reading controls
Article reader
Preparing the reader…
Reading settings
Reorganization will not substitute for an adoption system¶
The Department of Defense's (DoD) August 20 announcement realigns the Chief Digital and Artificial Intelligence Office (CDAO) under the Under Secretary of Defense for Research and Engineering (USD(R&E)). The stated goal is to accelerate artificial intelligence (AI) transformation by placing data, analytics, and AI closer to the department's broader technology enterprise.
Organizational charts matter. They establish authority, access, and incentives. They do not, by themselves, create adoption.
The hard part of defense AI is rarely locating a model. It is moving a validated capability through data access, infrastructure, security, test, acquisition, training, and operational ownership without losing the mission problem along the way.
A realignment can shorten some of those paths. It can also disrupt the relationships and tacit knowledge that make the current paths work.
Structure changes the probability of coordination¶
Bringing CDAO closer to research and engineering could connect AI adoption with technology strategy, experimentation, prototyping, and transition. The arrangement may make it easier to treat AI as a property of systems and portfolios rather than a separate category of software.
But every structural move creates new seams while closing others. Mission owners, cyber professionals, acquisition teams, data stewards, test organizations, and software factories still need predictable ways to work together. When a responsibility moves, the receiving organization needs more than a box on the chart. It needs decision rights, people, funding, repositories, relationships, and access to the history behind open commitments.
Research on coordination in organizations identifies accountability, predictability, and common understanding as outcomes that coordinating mechanisms must produce. Those are good tests for a realignment.
Protect the knowledge in motion¶
During reorganization, tacit knowledge is especially vulnerable. People know which office can resolve a data-access dispute, the rationale for a security exception, which evaluation breaks under realistic load, and which operator requirement remains outside the formal specification.
Leaders should identify active capability threads and preserve four things for each:
- the mission outcome and accountable sponsor;
- pending decisions and their rationale;
- dependencies, commitments, and named counterparts;
- and the artifacts that support technical and governance continuity.
A transition ledger is more useful than a generic handover memo. The people giving and receiving responsibility should review it jointly, with unresolved assumptions visible.
Adoption requires a repeatable path¶
The new structure should earn judgment by whether it improves the time and confidence with which teams move from problem to sustained capability. Useful measures include time to representative testing, time to obtain data and infrastructure, rate of operational use after pilot completion, incident learning, reuse across programs, and user-reported mission value.
Those measures cross organizational boundaries. That is the point.
The strongest outcome from a realignment would not be a more centralized AI brand. It would be a clearer adoption system: mission problems enter through a visible front door; reusable platforms reduce repeated work; assurance evidence follows the capability; operators shape evaluation; and lessons from deployment change the next investment.
Reorganization can create favorable conditions for that system. Durable transformation still comes from the routines, handoffs, and relationships that make the chart real.
Sources and research trail¶
- Chief Digital and Artificial Intelligence Office, “CDAO Re-alignment to USD(R&E) Accelerates AI Transformation at DoD” (August 20, 2025).
- Okhuysen and Bechky, “Coordination in Organizations” (2009).
- Bechky, “Sharing Meaning Across Occupational Communities” (2003).
- Argote and Ingram, “Knowledge Transfer: A Basis for Competitive Advantage in Firms” (2000).