Most learning budgets still follow the org chart. Work no longer does.
Value is increasingly created in projects and temporary teams that form, deliver and disband, while development is still designed around permanent roles with stable task lists. The mismatch is quiet but expensive: people are trained for a job description that only partly describes what they actually do, and the skills that made a project succeed are rarely captured when the team disperses.
Why it matters: if work is fluid and learning is fixed, capability lags behind demand, and nobody owns the gap, because no single role does.
Practical implications differ by role. A trainer can anchor sessions in live project problems rather than generic curricula. An instructional designer can design for transfer across contexts rather than one role. An L&D manager needs a process that captures lessons at project close, not only at appraisal time. An HR leader has to decide whether development is attached to grades or to work.
The question worth asking: if your learning architecture had to follow the work rather than the hierarchy, what would you keep?
Comments 0
Sign in to like, save or comment.
No comments yet. Start the discussion.