Skip to main content
Sticky

👀 Before we share the findings: where does your skills strategy stall?

  • October 8, 2026
  • 1 reply
  • 9 views
Docebian

Something big is coming on October 14, and before we share what the research found, we want to hear from this community.

Most organizations can name the skills they need next. The harder part is turning that insight into action.
 

If you had to move one skills initiative forward this quarter, where would it hit friction first?

  • Getting priorities aligned
  • Turning skills data into decisions
  • Funding the work
  • Keeping the data current
  • Getting buy-in from managers and business leaders

Think about the last time your team tried to identify a gap, fund a program, support internal mobility, or prepare people for changing roles. What slowed things down? What hurdles are you often trying to overcome?


Let us know in the comments below. No perfect answers needed. We’re curious to see how your experiences line up with the data we’ll be sharing out next week. 

👇👇 Tell us a barrier, an example, and/or a question you hope the report answers. 

1 reply

lrnlab
Hero III
Forum|alt.badge.img+10
  • lrnlab
  • Hero III
  • October 8, 2026

I’d say it depends on what’s coming next...The Skills app is pretty basic and one of the biggest hurdles is finding skills (from the defined list) and creating new ones. The prep work to launch skills is quite heavy regardless of the tool you use. Another big gap we have is that we cannot create jobs or manage/change/update any jobs that are input by users. Lastly, there is no notion of skill levels. While a user can self-assess their perception of their own skill level, there is no way (in the LMS) to show the user what represents what level of expertise; all this needs to be done outside the LMS which is not great. same applies to when your tagging courses with skills. A course cannot necessarily address all skill gaps so we have to use the course description to layout what skills and what skill levels the content addresses. Improvement here would be very welcome indeed.

Terms & ConditionsAccessibility statement