Sign up to save your podcasts
Or
Share "How Sean Graham Reduced Deployment Risk with Small Batch Delivery"
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
"How Sean Graham Reduced Deployment Risk with Small Batch Delivery"
Episode Summary:
In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Sean Graham, VP of Engineering at Idelic, to unpack a critical shift in how engineering teams approach delivery in high-stakes environments.
At Idelic, where software directly impacts fleet safety, compliance, and insurance risk, reliability isn’t optional. Sean shares how their team moved away from traditional two-week sprint cycles after realizing that large batch releases were quietly increasing risk. While velocity appeared healthy on the surface, debugging became guesswork, QA was overwhelmed, and every deployment felt like a high-stakes event.
Instead of optimizing Scrum, the team reframed the problem entirely, focusing on reducing batch size and risk. By shifting to a continuous, small-batch delivery model, they dramatically improved traceability, simplified debugging, and restored trust in their system. Lead time dropped from 25 days to just 4, while releases became routine instead of stressful.
The conversation also explores how infrastructure, like per-ticket test environments and fast pipelines, enabled this transformation, and why discipline became the most important skill once sprint boundaries disappeared.
As AI accelerates code generation, Sean emphasizes that structured delivery systems are more critical than ever. Without them, faster output simply compounds risk. Teams that pair AI with disciplined, low-risk delivery models will scale safely, while others risk creating faster chaos.
For engineering leaders, this episode is a powerful reminder: speed isn’t about working harder, it’s about reducing risk and improving feedback loops.
Key Takeaways:
- Large batch releases increase risk and reduce system reliability
- Debugging becomes exponentially harder when too many changes ship together
- Continuous, small-batch delivery improves traceability and confidence
- Lead time can drop significantly with continuous validation (25 → 4 days)
- Psychological safety and trust are critical for high-performing teams
- Strong infrastructure is required to support fast, safe delivery
- AI increases output—but without discipline, it also increases risk
Connect with Sean Graham:
- LinkedIn: https://www.linkedin.com/in/sean-graham-675a054
- Website: https://profed.laroche.edu
Listen Now & Subscribe:
Apple Podcasts, Spotify, Amazon Music, or wherever you get your podcasts.
"Engineering Choices You Have to Defend explores the real technical decisions behind regulated software, compliance, and AI integration, helping leaders build secure, auditable, and user-friendly systems."
View all episodes
By Nicola OnassisEpisode Summary:
In this episode of Engineering Choices You Have to Defend, host Nicola Onassis sits down with Sean Graham, VP of Engineering at Idelic, to unpack a critical shift in how engineering teams approach delivery in high-stakes environments.
At Idelic, where software directly impacts fleet safety, compliance, and insurance risk, reliability isn’t optional. Sean shares how their team moved away from traditional two-week sprint cycles after realizing that large batch releases were quietly increasing risk. While velocity appeared healthy on the surface, debugging became guesswork, QA was overwhelmed, and every deployment felt like a high-stakes event.
Instead of optimizing Scrum, the team reframed the problem entirely, focusing on reducing batch size and risk. By shifting to a continuous, small-batch delivery model, they dramatically improved traceability, simplified debugging, and restored trust in their system. Lead time dropped from 25 days to just 4, while releases became routine instead of stressful.
The conversation also explores how infrastructure, like per-ticket test environments and fast pipelines, enabled this transformation, and why discipline became the most important skill once sprint boundaries disappeared.
As AI accelerates code generation, Sean emphasizes that structured delivery systems are more critical than ever. Without them, faster output simply compounds risk. Teams that pair AI with disciplined, low-risk delivery models will scale safely, while others risk creating faster chaos.
For engineering leaders, this episode is a powerful reminder: speed isn’t about working harder, it’s about reducing risk and improving feedback loops.
Key Takeaways:
- Large batch releases increase risk and reduce system reliability
- Debugging becomes exponentially harder when too many changes ship together
- Continuous, small-batch delivery improves traceability and confidence
- Lead time can drop significantly with continuous validation (25 → 4 days)
- Psychological safety and trust are critical for high-performing teams
- Strong infrastructure is required to support fast, safe delivery
- AI increases output—but without discipline, it also increases risk
Connect with Sean Graham:
- LinkedIn: https://www.linkedin.com/in/sean-graham-675a054
- Website: https://profed.laroche.edu
Listen Now & Subscribe:
Apple Podcasts, Spotify, Amazon Music, or wherever you get your podcasts.
"Engineering Choices You Have to Defend explores the real technical decisions behind regulated software, compliance, and AI integration, helping leaders build secure, auditable, and user-friendly systems."