Running sprints inside an organization that hasn’t changed anything else is not transformation. It’s double the work.
Healthcare organizations are rolling out Agile methodology in marketing, digital, and operations departments with real intention. Standups. Sprint boards. Retrospectives. The vocabulary is right. The infrastructure around it is not. When one team adopts Agile while every upstream and downstream dependency still runs on annual budgets, committee approvals, and siloed handoffs, the result isn’t velocity. It’s two parallel systems — the sprint and the legacy process that never went away — running simultaneously on the same team’s capacity.
Nobody names this out loud. The department gets credit for adopting modern methodology. Leadership gets to signal organizational transformation. And the people doing the work run both systems and call it progress.
Chris Boyer and Reed Smith examine what actually happens when Agile is adopted in isolation — and what it exposes about the organizational infrastructure that methodology alone can’t fix:
- Why partial Agile adoption creates overhead rather than reducing it, and where that overhead lands
- The three infrastructure prerequisites Agile actually requires — and why most health systems don’t have them
- The difference between doing Agile and being Agile, and why the rituals without the decision rights produce standups, not speed
- How isolated rollouts can function as executive cover for avoiding the harder organizational work
- What closing the gap actually requires: not better training, but changed decision authority, budget flexibility, and compatible cross-functional cycles
The episode ends with a direct challenge. Before a health system assigns another department to adopt Agile methodology, someone should be able to answer one question: what decisions is that team actually allowed to make inside a sprint without asking someone else first? If the answer is “not many,” the methodology is irrelevant.
If the organization hasn’t changed – the sprints are just faster meetings.
Mentions from the Show:
- Only 23% of Agile-experienced executives say their org can shift resources quickly; only 34% say culture naturally enables Agile: Bain & Company, “How Agile Is Powering Healthcare Innovation” — https://www.bain.com/insights/how-agile-is-powering-healthcare-innovation/
- Siloed structures as primary barrier to Agile at scale in large enterprises: Agility at Scale research review, 2025 — https://agility-at-scale.com/implementing/transformation-leadership/
- 55% of organizations cite poor leadership as top barrier to cross-functional OKR alignment (prerequisite for Agile): Hyperdrive Agile OKR research, 2024 — https://hyperdriveagile.com/articles/breaking-silos-how-advanced-okr-cross-functional-performance-drives-unprecedented-growth-83
- CEO “follow me, I’m just behind you” case study — management stuck in old-fashioned way while development teams ran Agile: Bain & Company, “Agile Innovation” — https://www.bain.com/insights/agile-innovation/
- Healthcare structural and cultural barriers to Agile implementation: Rahman et al., SSRN, August 2024 — https://papers.ssrn.com/sol3/papers.cfm?abstract_id=5041524
- Real Agile blockers: decisions, load, trust, habits — finance and HR structural changes required: Bee’z Consulting / Scrum Alliance, 2025 — https://www.beez-consulting.com/blog/adopting-an-agile-culture-and-practices-in-healthcare-challenges-and-solutions
- Agile at scale requires finance, HR, and governance to shift — not just team-level training: Scrum Alliance, Coaching for Transformation microcredential framework — https://www.scrumalliance.org/microcredentials/coaching-for-transformation-sustaining-change
- Reed Smith on LinkedIn: https://www.linkedin.com/in/reedtsmith/
- Chris Boyer on LinkedIn: https://www.linkedin.com/in/chrisboyer/
- Chris Boyer website: http://www.christopherboyer.com/
- Chris Boyer on BlueSky: https://bsky.app/profile/chrisboyer.bsky.social
Reed Smith on BlueSky: https://bsky.app/profile/reedsmith.bsky.social
