I Have Some Questions...

196: "Agent Collaboration Should Look Like Co-Working, Not Hand-Offs" ft. Justin Coats

54 min · 14 de jul de 2026
Portada del episodio 196: "Agent Collaboration Should Look Like Co-Working, Not Hand-Offs" ft. Justin Coats

Descripción

Erik and Justin talk through why AI agents get stuck when teams cannot articulate how work is done, and why the answer is iterative agent deployment with guardrails, sandbox testing, and ongoing process refinement. 🧭 Conversation Highlights * Most professionals struggle to explain the steps of their work, which blocks automation and agent adoption. * Agents feel hard to hand off to because people fear losing control, making mistakes, or looking foolish. * A practical path forward is iterative process creation: give an agent the goal, tools, and guardrails, then tighten the workflow based on outcomes. * To make iteration safe, teams need preview or sandbox testing plus limits on real-world actions and token budgets to avoid runaway usage. 💡 Key Takeaways * AI adoption is shifting from “AI literacy” to “how to build and govern agents,” so companies need shared understanding beyond IT. * Iterative deployment works better than trying to hard-code every step upfront, but it requires verification checkpoints and process feedback loops. * Sandbox or preview environments are critical for low-risk learning before enabling agents to take real actions. * Token spend should be treated as governance: set budgets and limits per user/team, and track usage in a way leaders can understand. ❓ Questions That Mattered * How do we automate work we cannot clearly describe step-by-step without stalling adoption? * What guardrails let humans feel safe handing tasks to agents, including security, safeguards, and action approvals? * Is there a practical way to test agent workflows in “failure-free” conditions before going live? * When iteration causes back-and-forth, how should companies think about token efficiency and budget controls? 🗣️ Notable Quotes * “It’s hard to automate what you don’t already know how to do.” * “The majority of people have a really hard time articulating precisely how they perform a task.” * “Understanding the tool and technology, and knowing what it can and cannot do, really creates a safer environment.” * “It’s taking our typical structure. You watch how they work and         adapt to that.” 🔗 Links & Resources * Listen To Other Episodes Co-Hosted With Justin [https://www.google.com/url?q=https://podcast.languageofleadership.io/categories/i-have-some-ai-questions-with-justin-coats/&sa=D&source=editors&ust=1783541882324986&usg=AOvVaw3cPDGHMfUE2VtEJraxNcHR]

Comentarios

0

Sé la primera persona en comentar

¡Regístrate ahora y únete a la comunidad de I Have Some Questions...!

Empezar

2 meses por 1 €

Después 4,99 € / mes · Cancela cuando quieras.

  • Podcasts exclusivos
  • 20 horas de audiolibros / mes
  • Podcast gratuitos

Todos los episodios

194 episodios

Portada del episodio 196: "Agent Collaboration Should Look Like Co-Working, Not Hand-Offs" ft. Justin Coats

196: "Agent Collaboration Should Look Like Co-Working, Not Hand-Offs" ft. Justin Coats

Erik and Justin talk through why AI agents get stuck when teams cannot articulate how work is done, and why the answer is iterative agent deployment with guardrails, sandbox testing, and ongoing process refinement. 🧭 Conversation Highlights * Most professionals struggle to explain the steps of their work, which blocks automation and agent adoption. * Agents feel hard to hand off to because people fear losing control, making mistakes, or looking foolish. * A practical path forward is iterative process creation: give an agent the goal, tools, and guardrails, then tighten the workflow based on outcomes. * To make iteration safe, teams need preview or sandbox testing plus limits on real-world actions and token budgets to avoid runaway usage. 💡 Key Takeaways * AI adoption is shifting from “AI literacy” to “how to build and govern agents,” so companies need shared understanding beyond IT. * Iterative deployment works better than trying to hard-code every step upfront, but it requires verification checkpoints and process feedback loops. * Sandbox or preview environments are critical for low-risk learning before enabling agents to take real actions. * Token spend should be treated as governance: set budgets and limits per user/team, and track usage in a way leaders can understand. ❓ Questions That Mattered * How do we automate work we cannot clearly describe step-by-step without stalling adoption? * What guardrails let humans feel safe handing tasks to agents, including security, safeguards, and action approvals? * Is there a practical way to test agent workflows in “failure-free” conditions before going live? * When iteration causes back-and-forth, how should companies think about token efficiency and budget controls? 🗣️ Notable Quotes * “It’s hard to automate what you don’t already know how to do.” * “The majority of people have a really hard time articulating precisely how they perform a task.” * “Understanding the tool and technology, and knowing what it can and cannot do, really creates a safer environment.” * “It’s taking our typical structure. You watch how they work and         adapt to that.” 🔗 Links & Resources * Listen To Other Episodes Co-Hosted With Justin [https://www.google.com/url?q=https://podcast.languageofleadership.io/categories/i-have-some-ai-questions-with-justin-coats/&sa=D&source=editors&ust=1783541882324986&usg=AOvVaw3cPDGHMfUE2VtEJraxNcHR]

14 de jul de 202654 min
Portada del episodio 195: Rocky Batzel: "What It Means To Be Ready For Manufacturing At One Million Units Per Month"

195: Rocky Batzel: "What It Means To Be Ready For Manufacturing At One Million Units Per Month"

Rocky Batzel, inventor and CEO of Snapslide, shares how a decade of tinkering became a child-resistant pill bottle closure designed for one hand and for people with arthritis or other limitations. From the original “aha” at a liquor store to prototyping, patents, and certification testing, Rocky explains the path to commercial viability and what scaling manufacturing for over a million units per month means next. 👤 About the Guest Rocky Batzel is the inventor and CEO of Snapslide. He left medical school and built a career around product invention, focusing on tangible solutions. Snapslide creates a new approach to child-resistant openings for medication containers, aiming for accessibility without sacrificing safety requirements. 🧭 Conversation Highlights * Snapslide’s core idea: replacing torque-dependent bottle caps with a linear, two-stage opening that can be done with limited dexterity * How Rocky shifted from identifying everyday “pain in the butt” problems to searching for prior art, patents, and manufacturability * The business and regulatory gauntlet: child-resistant testing, USP permeation testing, iterative tooling, and certification timelines * How the team is preparing to scale manufacturing and capacity for large pharmacy distribution while continuing to develop OTC variants 💡 Key Takeaways * Accessibility is not a “nice to have.” It is a design constraint that must be baked into safety products from the start. * Great invention is less about finding a new problem and more about observing a familiar problem from a different angle. * Commercial success requires solving for manufacturability, cost, certification, and distribution incentives, not just the mechanism. * Scaling is a timing problem: tooling lead times, capital planning, and facility growth capacity have to align with demand. ❓ Questions That Mattered * What is Snapslide, and what design change makes it usable for one hand or limited dexterity while staying child-resistant? * How do you validate an idea when it is hard to know if you are truly first, or if prior art exists? * What does the child-resistant certification process actually require, including pass thresholds and sample counts? * What keeps you from taking profitable but misaligned deals, and how do you decide what is “worth it”? 🗣️ Notable Quotes * “Simple, which is one of the big barriers to the market.” * “You know it in your gut.” 🔗 Links & Resources * Follow Rocky Batzel's LinkedIn [https://www.google.com/url?q=https://www.linkedin.com/in/rocky-batzel-780a309a&sa=D&source=editors&ust=1780007408071641&usg=AOvVaw36l6gVoGjlRatUhA8iKUI8] * Check out Rocky Batzel’s Company, SnapSlide: www.snapslide.com [https://www.google.com/url?q=http://www.snapslide.com&sa=D&source=editors&ust=1780007408072118&usg=AOvVaw3_vaWKS4HiXCBneCvgP3-R]

9 de jul de 20261 h 21 min
Portada del episodio 194: Quinn Rose: "What Really Makes Journalism Worth Trusting In The Triple-Check Era?"

194: Quinn Rose: "What Really Makes Journalism Worth Trusting In The Triple-Check Era?"

Quinn Rose challenges the idea of objective journalism and reframes “good writing” as from-the-heart and based in story. She shares how ten years in the news industry destroyed her hope, and how she now uses those storytelling instincts to support brands she believes in. The conversation turns to AI’s flattening effect on voice, whether or not true “facts” exist, and how poker applies to life.  👤 About the Guest Quinn Rose is a journalist-turned-creative strategist and storyteller for mission-driven brands. Her reporting has influenced federal policy, reached over a billion TV viewers, and landed her courtside at the Olympics. Recently, Quinn ghostwrote a 5-star-rated book, traveled with The Discovery Channel, and was the producer for a series of statewide mental health trainings. She works with clients both remotely and in-person, usually in and out of her home state of Oregon and whichever country pulls hardest at her heartstrings (after a decade love affair with Brazil, Italy’s up next).  🧭 Conversation Highlights * The new need to “triple check”  * How funding, clicks, and incentives warped newsrooms, pushing her out * Transferring journalism tools into branding through curiosity and character-based storytelling * AI flattening: when good writing formulas create sameness across everything 💡 Key Takeaways * Truth and trust are built through verification and perspective awareness, not the myth of neutrality * The strongest marketing and journalism start with “why do they care?” since the content is being made FOR that target audience, not you or the company itself  * AI can increase efficiency, but it sands down personality, specificity, and originality * She believes events and person-to-person connection will only become more valuable in this Age of AI  ❓ Questions That Mattered * Do the fundamentals of journalism still matter when the incentives around journalism change? * What can we trust when headlines and conclusions can be made to support opposite sides? * As AI makes language more “perfect,” what happens to voice, personality, and profundity? * Where is the line between influence and manipulation when the goal does not serve the other person? 🗣️ Notable Quotes * On whether or not objectivity exists:  ”If I were writing it, I would choose what we do and what we don't say. We would clip this interview and make it say that.” * On AI’s most overused terms and metaphors: “The DNA woven into the fabric of everything, it’s exhausting” 🔗 Links & Resources * Follow Quinn Rose's LinkedIn [https://www.linkedin.com/in/quinnrose/] * Check out Quinn’s Website: storybasedbrands.com [http://storybasedbrands.com]

8 de jul de 20261 h 15 min
Portada del episodio 193: "How Permission Culture Keeps Us Small Without Us Noticing" ft. Alli Murphy

193: "How Permission Culture Keeps Us Small Without Us Noticing" ft. Alli Murphy

Alli and Erik unpack how so many of us wait for external permission to want things, and how that shows up in both big goals and everyday boundaries. They explore why permission-seeking feels safer, why it can be conditioned into us, and how “permission slips” can be a practical way to reclaim ownership over wants and even needs. 🧭 Conversation Highlights * Erik describes noticing in himself and clients that “external permission” often becomes a gate to pursuing what people actually want. * Alli shares how permission-seeking can be especially reinforced for women, including being taught to not be loud, not be “too much,” or not want visibility and importance. * They discuss how early schooling and structured environments train people to request approval, which then carries into work and personal life. * Alli offers concrete tools: writing literal permission slips, using small systems that create distance from guilt (like off-duty boundaries), and prompting teams to write their own permission slips. 💡 Key Takeaways * Wanting something is not automatically selfish. The challenge is aligning wants with ethics and impact, not suppressing them. * Permission-seeking can feel easier than self-trust, even when it blocks growth and clarity. * You can build internal permission through tangible rituals (writing, visible reminders, and boundary systems) rather than relying on motivation. * Teams can benefit from a shared exercise that makes “what I need or want permission for” explicit and normalized. ❓ Questions That Mattered * Do I actually want something, or am I asking for permission because it feels safer than taking up space? * Where in my life have I confused “need” and “want,” or used guilt as the substitute for clarity? * What boundary or opportunity am I avoiding because I think someone else would not approve? * If I had to write a permission slip right now, what would I grant myself? 🗣️ Notable Quotes * “I want what I want because I want it.” * “We don’t need anybody else’s permission for a lot of this.” * “Literally written myself permission slips before.” * “In your next team meeting  write down one thing they need permission for.” 🔗 Links & Resources * Listen To Other Episodes Co-Hosted With Alli [https://www.google.com/url?q=https://podcast.languageofleadership.io/categories/leadership-talks-with-alli-murphy/&sa=D&source=editors&ust=1781730880009474&usg=AOvVaw2L01Oc_1qAy8lsYlnEObwk]

6 de jul de 20269 min
Portada del episodio 192: "Psychological Safety As The Real Happiness Strategy: Seek, Speak, Listen" (reflections on Scott Crabtree)

192: "Psychological Safety As The Real Happiness Strategy: Seek, Speak, Listen" (reflections on Scott Crabtree)

🧠 Erik’s Take Erik opens with gratitude and a clear reason for doing the review: the Scott Crabtree conversation hit something deeper than the headline topic. He reflects that as a listener he felt the urge to re-extract the core mechanisms, not just the ideas. His throughline is strategic and vulnerable at the same time. He admits he does not want “happiness” to become a performative corporate slogan or a simplistic workplace requirement, and yet he still believes happiness matters. He keeps returning to a balance he thinks leaders often miss: you need the tension between happiness and hard things, and you 🎯 Top Insights from the Interview * Over-focusing on happiness can backfire, turning a worthy aim into an emotional trap and a workplace obsession. * Happiness is not one thing: the difference between hedonic happiness and eudaimonic happiness changes what leaders should try to build. * Psychological safety is a practical lever for creating the right kind of happiness more often, and it is built through a repeatable behavior pattern. 🧩 The Personal Layer Erik contrasts what he has seen in corporate cultures with what Scott’s framing makes possible. He notes how companies leaned hard into hedonic-style “treats” and perks, sometimes drifting into entitlement, then later pulling back. On the personal level, Erik recognizes his own misgivings as a leader about corporate promises. He surfaces the internal question underneath the episode: what is his obligation, and what is not his obligation, if the stated goal is a happier workplace. He also confesses that he learned new conceptual language (hedonic and eudaimonic), and he values that learning not 🧰 From Insight to Action * Reframe happiness as one critical emotion in a larger emotional portfolio, and explicitly hold it in tension with grit, perseverance, and hard outcomes. * Audit workplace “happiness” tactics: keep the treats occasionally, but redesign for more frequent eudaimonic alignment through meaning, growth, values, and contribution. * Practice the psychological safety loop as a leadership routine: seek participation, speak with two seconds of courage, and listen in a way that proves understanding, not agreement. * If you are worried about “corporate responsibility for happiness,” use the episode’s stance as a guardrail: you cannot make people happy, but you can structure conditions that make it more likely. 🗣️ Notable Quotes * “if you over-focus on happiness, it actually is a pretty good recipe to make yourself unhappy.” * “Happiness isn't everything. But it is really important.” * “teams where people feel comfortable contributing even if they disagree, in fact, especially if they disagree, consistently outperform other teams.” * “you're simply listening and demonstrating that you understand and that they feel understood is the goal.” 🔗 Links & Resources * Listen to Scott Crabtree's Episode [https://podcast.languageofleadership.io/202-scott-crabtree-what-google-found-in-project-aristotle-that-changes-how-you-lead-teams]

3 de jul de 202613 min