Most L&D intake processes were never designed. They just accumulated.
A request comes in over Slack, another lands in someone's inbox, and a VP corners an instructional designer in the hallway asking for “something quick” before Friday — none of it goes through a system, because there is no system, just a patchwork of side doors that stakeholders have learned to use because it's faster than waiting for an answer.
This is how most L&D teams end up drowning without anyone quite deciding to let it happen.
The team isn't the problem
When a training team is missing deadlines, the instinct is usually to look at headcount, as if the fix were another instructional designer or a project manager to keep things organized.
But in my experience leading an agile transformation at Optum, adding people rarely fixes a broken intake process — it just gives the chaos more surface area to spread across. I worked with a team supporting 13 different lines of business, where projects routinely ran over budget, designers were burning out, and stakeholders were frustrated by slow, inconsistent delivery, even though the team itself was neither understaffed nor underskilled. What it lacked was a consistent way for work to enter the system, get sized, and get prioritized.
Without that, every request looks urgent, every stakeholder assumes theirs is next, and the team spends more energy managing perception than actually building anything.
What "no intake process" actually costs you
A missing intake process doesn't show up as one big failure, but as a hundred small ones:
- Scope changes mid-project because requirements were never nailed down up front
- Designers context-switching between five “urgent” priorities in a single day
- Leadership with no real visibility into what the team is working on or why
- No clean way to say no, or even to say “not yet”
Individually, each of these looks like a minor annoyance, but together, they're the reason a team can work harder every quarter and still fall further behind.
What actually fixed it
The turnaround at Optum didn't come from a new tool or a bigger team — it came from applying Scrum, real ceremonies rather than just the vocabulary, to how training requests moved through the organization:
A structured intake system. Every request went through the same front door, with the same basic questions answered before it entered the queue: What behavior needs to change? What's the deadline, and why? Who's the audience? This alone eliminated most of the guesswork that used to happen mid-project.
Sprint planning with stakeholders in the room. Instead of requests landing and instantly becoming “urgent,” work was sized and slotted into sprints stakeholders could see. Everyone knew what was in progress, what was next, and what wasn't happening yet — and why.
Transparent capacity tracking. Leadership could finally see the team's actual bandwidth, which made it possible to have honest conversations about priorities instead of just absorbing every new ask.
Retrospectives that actually changed things. Regular reflection meant the process kept improving instead of calcifying into a new version of the same chaos.
None of this required exotic tools or a big budget. It required treating L&D operations as something that could be designed, not just endured.
The results
Within months, the shift was measurable: out-of-scope work dropped 86%, and the team hit a 99% response rate on daily standups, a real signal that people trusted the process enough to actually use it, while stakeholders got clearer timelines and designers finally got some breathing room.
None of that came from working harder. It came from giving work a front door.
The question worth asking
If your L&D team is constantly firefighting, it's worth stepping back before reaching for more headcount or another tool, and asking instead: does work have one clear way to enter our system? Can we see what's in progress and what's blocked? Do stakeholders know how to ask for something, and what happens after they do?
If the honest answer is no, that's not a people problem — it's a process that was never designed, and one that can be.
If this sounds familiar and you'd like to talk through what it might look like for your team, reach out below.