
The AI Development Lifecycle: How to Thrive in the SaaS Apocalypse
Code is getting easier to produce, but the cost of building the wrong thing is about to get louder. Jason Rome sits down with Cory Voglesonger, Chief Product and Technology Officer at Aaron's, to unpack what’s actually changing as teams move toward AI-native delivery and an AI development lifecycle filled with coding agents and agentic workflows.We use Cory’s culture framework safety, clarity, urgency as a simple way to diagnose why some teams thrive with AI while others drown in noise. Urgency is not “move fast at all costs.” It is outcome thinking: knowing what business result you’re chasing, measuring it, and avoiding the trap of shipping a mountain of features just because AI makes output cheap. We also dig into why lean thinking, flow, and the basics of continuous delivery still matter, plus how a solid developer experience with a golden path and standard toolchain prevents AI-driven sprawl.Clarity is where AI turns the dial up to 1000. When you’re directing humans and eventually armies of agents, the work lives or dies on context engineering: guardrails, constraints, domain knowledge, and clear intent. We talk about getting closer to users, making knowledge less tribal, and using AI as adviser, assistant, and adversary to challenge bias, stress test ideas, and sharpen decisions before production feedback takes time.Safety closes the loop, from psychological safety around job fears to environmental safety around customer data and blast radius. If you want your team to adopt AI without burnout, this is the leadership work. Subscribe, share this with a teammate, and leave a review with the culture lever you’re focusing on next.Episode Resources:Jason Rome on LinkedIn: /jason-rom-275b2014Cory Voglesonger on LinkedIn: in/cory-voglesonger-81907628Method Website: method.comThe Aaron’s Company Website: aarons.com










