What happens when AI helps individual employees work faster, but the whole team still gets stuck?

In this episode, Sandy Kibling talks with Ricardo Arcia, author of The Cognitive Leader, about his organization’s journey to rethink how software gets built. He shares why early experiments produced uneven quality, unexpected bottlenecks, and an important lesson: adding AI to a shaky process can amplify the chaos.

Together, they explore the shift from writing code to guiding and validating AI’s work, why training needs ongoing coaching, and how clear policies support responsible adoption.

Ricardo also explains Team Zero—a dedicated team that tests new approaches and shares what works with the rest of the organization. Whether you lead an engineering team or are navigating AI adoption in your business, this conversation offers practical questions about people, processes, and measuring meaningful progress.

3 Key Takeaways

1. Measure the whole workflow. One person finishing faster does not guarantee faster delivery if the next team cannot use the work.
2. Pair AI tools with training and coaching. People need support to guide AI, validate its output, and build new habits.
3. Give experimentation a clear home. Ricardo’s Team Zero tests approaches, adapts the process, and shares updated guidance with other teams.

Resources:

Teravision

The Cognitive Leader.com

Playbook AI Partners

Join our FB Community: AI Quick Win Club

Join Us In The Huddle - Live training and AI Tools You Can Use

#PodMatch