Attitude, Aptitude, and Access: The Three A's of AI Adoption
No se pudo agregar al carrito
Add to Cart failed.
Error al Agregar a Lista de Deseos.
Error al eliminar de la lista de deseos.
Error al añadir a tu biblioteca
Error al seguir el podcast
Error al dejar de seguir el podcast
-
Narrado por:
-
De:
Why are corporate knowledge workers structurally prohibited from learning the most important skill of the decade?
In this episode of KP Unpacked, KP Reddy sits down with Nona Black, Head of People, to unpack why hiring 36 people feels harder than running 36 Mac minis with Claude Cowork and why that's both a joke and a serious question. From Delta Airlines innovation leadership to startup chaos, Nona brings the corporate perspective on what happens when IT departments become the biggest barrier to workforce evolution.
The conversation spans the tactical (how Claude holds your ADHD thoughts while you context-switch), the structural (why engineers need to collapse into product roles and talk to customers), and the philosophical (should we expect new hires to show up AI-fluent, or is that unfair?). KP argues that medium-level AI competency means you've automated something frustrating in your workflow not just asked ChatGPT about the weather. Nona counters that most people in corporate America don't have access, incentive, or permission to build that skill, which creates a massive disadvantage for anyone not in a startup environment.
Key topics covered:
- Why managing people is harder than managing AI agents and why that's both true and not the point
- How Claude Cowork helps ADHD superpowers: holding half-finished tasks while you context-switch and come back later
- The expert generalist thesis: AI tools are making everyone capable of cross-functional work without formal training
- Why KP tells architects to keep IT out of the room if they want to make progress on AI adoption
- The three A's of knowledge work: Attitude, Aptitude, and Access and why access is the limiting factor in corporate America
- Why engineers need to collapse into product roles and learn customer empathy, not just coding mechanics
- The middle ground of AI competency: automating frustrating workflows, not just asking questions Google can answer
- Why Claude asked KP if he wanted to pay for data aggregation services or go straight to free public sources
- How to evaluate AI fluency in hiring: have they built an agent, automated a task, or just used ChatGPT for trip planning?
- Why solo entrepreneurship is more appealing now than ever, you don't need 17 people to fill 17 roles anymore
- The sandbox problem: corporate risk tolerance vs. giving employees freedom to tinker and experiment
- Why offshore development teams struggle to build good software, they're not living the customer's life
- How Claude gives real-time feedback on KP's fiction writing: "This chapter doesn't make sense, are you coming back to this?"
If you're a knowledge worker wondering whether to stay in corporate or jump to a startup, a leader trying to figure out how to hire for AI fluency, or an IT department blocking progress in the name of risk management, this episode will challenge how you think about access, aptitude, and the future of work.
Listen now.
BuildingWorks & Brookwood Sponsors