The challenge
When an organization grows quickly, training requests multiply. Some are valid. Some are symptoms of unclear process, weak tools, missing manager reinforcement, or a business rule no one has explained well.
If L&D says yes to every request, the portfolio fills with content that misses the real issue.
The challenge was to protect capacity while still helping stakeholders solve the problem.
The approach
I used needs assessment as governance. The intake process asked what behavior needed to change, what evidence showed the gap, what cause was most likely, and what intervention was smallest enough to work.
The taxonomy mattered because it gave the team language beyond "needs training." Knowledge, skill, clarity, process, tool, incentive, confidence, manager support, access, and measurement gaps lead to different solutions.
The goal was to route work to the right fix and reserve build capacity for learning problems where learning could change performance.
Downloadable takeaway
A one-page version of the model with the decision questions, sequence, metrics, and red flags someone can use after reading the case.
What I built
Diagnostic intake for new requests
Requests had to name the audience, task, current behavior, desired behavior, source material, business owner, and success evidence.
That made vague requests easier to clarify before they entered production.
Portfolio governance
The same logic helped review existing modules. Some content needed updates. Some needed consolidation. Some needed retirement.
A growing library needs a way to decide what deserves maintenance and what deserves creation.
Routing beyond courses
Some issues moved to job aids, manager tools, process clarification, or workflow support.
That protected the team from building courses for problems outside training's reach.
Operating artifacts
These are sanitized work-product examples. They show the kind of artifact I would expect the team to use. They are sanitized and exclude confidential company material.
Diagnostic Intake Fields
Diagnostic Intake Fields
The questions a request had to answer before it became a project.
Cause Taxonomy
Cause Taxonomy
A shared language for sorting the problem before building the answer.
Course Request to Job Aid
Course Request to Job Aid
A sample of how a request can move out of the course queue.
The results
The operating insight
Performance consulting gets overclaimed in L&D. The practical test is whether the process changes what gets built.
The out-of-the-box move was treating needs assessment as portfolio governance and a front-end conversation.
What this proves
- I can protect learning capacity through diagnosis.
- I know how to route requests to the smallest useful intervention.
- I can make portfolio decisions based on performance value and stakeholder pressure.