Subscribe for Insights

Stay connected with our latest Insights

Subscribe for Podcasts
Videos
Venice Goodwine on Workforce, Urgency, and the Human Side of AI

Venice Goodwine on Workforce, Urgency, and the Human Side of AI

Key insights

  • AI adoption in defense starts with psychological safety. When personnel hear AI, they hear job replacement. Goodwine argues that CHCOs and HR leaders, not technology teams, own the responsibility of communicating how AI fits into each role and why the human remains in the loop.
  • AI literacy is a national security issue. Domain expertise is what allows operators to catch hallucinations and drift; without it, the model cannot be trusted, regardless of the underlying architecture or security controls.
  • Agentic AI belongs on the org chart. Goodwine’s argument is that when a non-human entity has a job description, a defined scope, and accountability, the workforce becomes more comfortable with it, and the organization gets a multiplier that does not need a lunch break.

Recorded at the Mission Ready AI event in Melbourne, Florida, this conversation between Jeff Kavanaugh, Head of the Infosys Knowledge Institute, and Venice Goodwine, CIO and AI Product Owner at Arlo Solutions and former CIO of the U.S. Air Force and Space Force, examines what it actually takes to move AI into production in one of the world’s most demanding operating environments.

Goodwine argues that the urgency now visible across the defense industrial base is not rhetorical: the adversary has access to the same technology, the pace-setting projects are public, and the funding is committed. What remains is execution, and the primary barrier to execution is not technical. She explains why workforce psychology and AI literacy have to come before any tool goes live, how cross-functional teams with domain expertise are the real safeguard against model drift and hallucination, and why she now tells organizations to put AI on the org chart with a job description and accountability. She also draws a direct line between the EU AI Act’s risk-tiered framework and what responsible deployment looks like across sovereign boundaries and addresses the next generation directly: the countries treating AI fluency as a mandatory skill are building a structural advantage, and curiosity is the starting point.

Three ideas from this conversation

Psychological safety before deployment
Goodwine’s argument is that workforce anxiety about AI is not irrational. It mirrors what happened during the RPA era. The answer is not reassurance but clarity: explain exactly how AI will operate in each specific role and make the human’s continued responsibility explicit.

Domain expertise as a trust mechanism
A generative model will hallucinate. The check on that is not the model. It is the operator who knows the domain well enough to catch the error. Building cross-functional teams with genuine subject matter expertise is Goodwine’s practical answer to the trust problem.

The NHI on the org chart
Non-human intelligence entities assigned specific roles, held to defined outputs, and subject to replacement when they underperform. Goodwine’s framing gives the human workforce a conceptual model for working alongside AI that does not require pretending the risk is not there.

Q: How is AI investment changing the defense industrial base?
The administration’s AI strategy, the Secretary of War’s pace-setting projects, and the funding behind both have given the defense industrial base a clear signal: deliver AI-enabled capabilities, not tools. Goodwine explains that the requirement is now for capabilities that help warfighters make faster, better decisions, and that industry cannot treat this as separate from the mission.

Q: What does AI urgency actually mean when the adversary has the same technology?
Goodwine is direct: everything built for good can be repurposed by an adversary. The answer is to outmaneuver, outmatch, and outsmart by moving with AI literacy, guardrails, and accountability built in from the start. She also notes that urgency has a different clock speed in the AI era than it did even five years ago.

Q: Why is workforce adoption an HR function, not a technology function?
The technology team can deploy the tool. Only HR can redesign job descriptions, communicate role changes, and build the organizational confidence that makes adoption stick. Goodwine points to SHRM’s growing body of work on AI implementation as evidence that this conversation is already happening outside the technology arena and argues it needs to move faster.

Connect with the Infosys Knowledge Institute

All the fields marked with * are required

Opt in for insights from Infosys Knowledge Institute Privacy Statement

Please fill all required fields