Episode 09 · September 26, 2026 · 55 min
The Future of AI: Leadership, Security & Governance
With Steve Earley, Managing Partner at Valenta
Bob Hansen speaks with Valenta Managing Partner Steve Earley about leadership lessons from military and civilian technology roles, mentorship and career growth, AI automation that frees people for higher-impact work, and the need to build data governance and cybersecurity alongside innovation. Shadow AI and post-quantum preparation are also on the table.
What you’ll take away
- Leadership means listening to experts and removing obstacles, not claiming every technical answer.
- Automate repetitive work to create space for higher-impact contributions—and tell people how their roles change.
- Set clear policies around approved AI tools and what customer or personal data may be entered.
- Bring security into projects early so governance enables useful innovation rather than driving Shadow AI.
- Prepare for post-quantum cryptography while using AI to strengthen cyber detection and response.
In this conversation
- Leadership, career development and mentorship
- AI-driven automation and higher-impact work
- Cybersecurity, Shadow AI and data governance
- Post-quantum cryptography
Episode recap
Editorial summary of the conversation, not a verbatim transcript.
Bob Hansen's interview with Steve Earley connects the human work of leadership to decisions about AI, security and governance. Earley describes a route into technology that began with experimenting on a Heathkit computer in high school, continued through a 23-year Navy career, and moved into civilian technology, consulting, audit, security and CISO roles. His work with Valenta draws on both innovation and governance. The conversation treats those fields as parts of the same job, rather than separate conversations held after a product has already launched.
Leadership comes first. Earley recalls that, at 22, he had about 100 people reporting to him on his first ship. Rather than pretending he understood every specialized job, he learned to rely on experienced chiefs and subject-matter experts. A sharp correction from a senior chief stayed with him. The leader's role was to understand their perspective, trust their expertise, give them room to execute and still verify appropriately. He contrasts this with a rigid, top-down style that drives people away. Moving into civilian work also meant adjusting from a clear hierarchy to leading by influence: asking questions, guiding teams and removing obstacles to their growth.
Hansen and Earley discuss a career as a series of opportunities to learn and contribute, not a race for the most impressive title. Earley recalls a reorganization handled so poorly that it eroded his trust in an employer; he stayed longer than he now thinks he should have. He also describes moving from a VP role at a smaller company to a senior-manager role at AWS. The latter brought greater scale, responsibility and opportunity despite the less senior-sounding title. His advice is to assess scope and impact, and to keep learning the business around the technology. Mentorship remains valuable throughout a career, including for a business owner. He recommends deliberately approaching people whose judgment one respects; good mentors listen and ask questions that help the mentee find clarity rather than prescribing their own route.
The AI discussion starts with work, not a tool. Earley argues that repetitive background tasks are candidates for automation when freeing employees lets them spend more time with customers, support growth or tackle higher-value problems. That transition has a people dimension. If employees hear only that a task is disappearing, they may reasonably worry that they are next. Leaders need to say what the change is for, how roles may shift and what support the organization will provide. Experimentation can help teams discover useful applications, but it should happen inside a defined, approved environment.
Data is central to that environment. Earley cautions against placing customer information or personally identifiable data into a model without understanding where it goes or how it may be used. He discusses data-loss-prevention controls, approved-tool policies and clear instructions about what employees may enter into AI systems. When experiments become operational deployments, organizations need governance expertise and an awareness of obligations specific to their industry, including healthcare and payment-card requirements. AI-specific audit and risk work is likely to matter more as deployments expand.
Earley does not frame governance as an excuse to block every proposal. He recalls working with a security organization perceived as a department that only said no. That reputation meant teams left security out of projects, then had to add protections late and at greater cost. A better stance is to engage early, explain the risks and make the initiative secure enough to proceed. Shadow AI illustrates why: if approved paths are absent or impractical, employees may try unapproved tools, potentially with sensitive customer data, without the organization's knowledge. Joining innovation and security at the start is more useful than forcing them into a confrontation later.
The conversation also examines changing cyber threats. Earley says AI can help defenders detect and respond, while making phishing attempts more convincing and lowering barriers for attackers. Resilience involves making intrusion difficult and costly enough to detect or deter. On quantum computing, he raises the prospect that future machines could undermine encryption regarded as strong today, giving leaders a reason to plan for post-quantum cryptography. He closes on a practical leadership note: do the current job well, understand the business model, communicate across technical and executive groups, and choose problems that technology can actually help solve.
