If your L&D team is talented, well-resourced, and still can't move fast enough for the business — the problem isn't your people. It's your process. According to the 2024 ATD State of the Industry Report, 57% of L&D professionals say their design cycles take longer than the business can wait. That number isn't a talent indictment. It's a methodology one.
We've Been Naming the Wrong Constraint
When organizations ask L&D to move faster, the usual responses are: hire more instructional designers, buy better authoring tools, add an AI assistant. All reasonable. None of them solve the underlying problem.
ADDIE — the sequential design model that underlies the vast majority of corporate L&D practice — was built for a world where business priorities were stable enough to survive 6- to 9-month design cycles. That world is gone. Today's organizations are asking L&D to respond in weeks, not quarters. When you pressure a sequential model to move faster, you get rushed ADDIE — not agile design.
The evidence bears this out: fewer than 20% of organizations report having a systematic method for updating learning content when business priorities shift (Josh Bersin Academy Research, 2024). That's not a content problem. That's a process problem.
AI Won't Fix a Broken Process
The natural response to "we need to move faster" has become "let's add AI." And AI is genuinely changing what's possible — McKinsey Global Institute estimates it will automate up to 40% of routine instructional design tasks within three years.
But here's what the data doesn't say: AI fixes your design model. AI-assisted design still runs on sequential, linear logic. If your process requires three rounds of stakeholder review before content can be revised, AI doesn't eliminate that constraint. It just means you're waiting faster. Teams that bolt AI onto ADDIE get faster document generation — not faster, better learning.
The design model has to change before the tools can fully deliver.
What Happens When You Change the Model
Organizations that have moved to iterative, agile design approaches report results that are hard to argue with. Brandon Hall Group's 2024 Learning & Development Benchmarking study found that organizations using iterative design see 40–60% faster time-to-deployment compared to traditional sequential models.
The business impact is just as significant: companies with agile learning design capabilities are 2.4x more likely to be high-performing organizations (Bersin by Deloitte, 2024).
This is what Fluid Design makes possible — not abandoning instructional rigor, but evolving the operating model to match how modern business actually moves. It's iterative, evidence-based, and designed to compress cycle time without sacrificing quality.
Who's Leading This Conversation
Mike Vaughan is the CEO of The Regis Company and the architect of Fluid Design. He has spent two decades helping Fortune 500 organizations build the workforce capabilities their businesses actually need — faster, with better evidence, and without the rework cycles that drain L&D teams. He's not here to tell you ADDIE is wrong. He's here to help you name your constraint and give you a practical first step out.
Karl Kapp is a Full Professor of Instructional Technology at Commonwealth University, a TEDx speaker, 2018 DevLearn Guild Master Award recipient, ATD Distinguished Contribution honoree, LinkedIn Top Voice, and author of multiple books on instructional design, gamification, and learning science. Twenty-seven years at the intersection of learning, technology, and design — and he has strong opinions about what actually makes it work.
What You'll Walk Away With
- The specific ways sequential design methodology creates a speed ceiling — with data you can bring to your next leadership conversation
- Why AI tools haven't fixed the speed problem, and what actually does
- One concrete action you can take this week to begin moving toward a more fluid, responsive design approach
Join Mike Vaughan and Karl Kapp on Wednesday, March 18th, 3–4pm MT for a frank 30-minute conversation about why your design process — not your team, not your budget — is the real constraint on workforce capability development. And what to do about it.