Prioritising needs when capacity is limited
4 min read
Lesson objectives
- Prioritise a bounded L&D backlog with transparent criteria, sensitivity checks and authority for tradeoffs.
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
A capability analysis may produce more needs than the team's time and budget can serve. Ranking requests by the urgency of their sponsors alone will not solve that problem. An L&D specialist prepares a decision list: what gap exists, who is affected, what happens if it remains, and which intervention might address it after ruling out non-learning causes? The specialist proposes criteria and makes uncertainty visible. Ranking is a tradeoff decision, not a scientifically fixed arithmetic result. The sponsor therefore needs to see how the ranking was produced and may adjust weights within stated bounds.
Five locally useful criteria are impact on an organisational task, urgency tied to a real deadline, reach, readiness to implement, and effort. Define each scale before looking at project names; for example, rate impact from one to five by the seriousness of the consequence rather than the seniority of the requester. Do not weight reach so strongly that it hides a rare high-risk task: five people performing a consequential task may need support before a minor improvement affecting a hundred. Nor should low effort alone decide the list, or easy programmes will always win. A documented mandatory requirement from a responsible authority is a separate constraint rather than a score that can be traded away. Its scope and effective date require specialist confirmation.
Give each option a card showing why it was included and what kind of evidence supports it. “Practise classification of new complaints” may be based on a task trial in which a defined sample confused two codes. “Improve the job aid” may be based on agents succeeding when they have a comparison in view. Do not record opinion as observation. Use a cost and time range rather than a falsely precise figure without a vendor quote or design. If a tool repair is the priority, put it in a dependency list; do not imply that L&D owns the repair. A learning option dependent on that repair is conditional on its date.
A weighted sum can support an operational comparison, provided its limits are understood. Suppose impact has weight 40%, urgency 25%, reach 15%, readiness 10%, and inverse effort 10%. Rate each criterion from one to five, multiply by its weight and add the products. “Inverse effort” means five is easiest to implement; state that explicitly so a reviewer cannot reverse the meaning. The total supports discussion; it does not measure economic value. Two options can have almost identical totals but very different evidence quality. Show evidence confidence beside the score rather than burying it in the total.
Test sensitivity. If A leads B only while urgency has a 25% weight, see what happens at 15% or when a project deadline moves. If the order reverses easily, present both options and a choice condition rather than a categorical winner. If one remains ahead through reasonable variations, the recommendation is more stable. Also inspect overlapping audiences and resources: one intervention may serve two tasks, while two activities may both need the same supervisors and cannot run together. Portfolio planning is about dependencies and capacity, not merely sorting spreadsheet rows.
End with an actionable funding and operating decision. For each accepted option name the outcome owner, proposed product, smallest useful trial, initial indicator and review point. For deferred options record why they were postponed, when to reconsider and what could raise them: new evidence, a system change or released delivery capacity. Do not promise a course date that has not been authorised. If a sponsor insists on a priority that differs from the evidence, respectfully show the tradeoff: which work will be delayed, who owns that choice and which assumption would change it if disproved. The specialist makes the choice explicit and implementable; resource approval remains with its authorised owner.
Lesson summary
Prioritise a bounded L&D backlog with transparent criteria, sensitivity checks and authority for tradeoffs.