Skip to main content

Goal:

  • Present tasks that need to be completed during onboarding that allow a person to ‘mark complete’ when they have completed something.
  • Ideally present the tasks in a single place along side other onboarding elearning experiences
  • Allow managers to view and track progress
  • Changes to the task or task list would cascade across the system and not ‘version’, so out of date links don’t simply remain or need to be updated again and again
  • Easy to set up and maintain so that it is not overwhelming for a functional team rep to maintain for their team

Examples:

  • Task 1. Go to this website and set up your email signature based off of the templates
  •  
  • Task 2.  Speak with your onboarding buddy about getting on the appropriate distribution lists for monthly Team calls.
  • Task 3.  Get access to this application and then speak with your manager about how to set up your account.

What I’ve tried:

We previously had Degreed LXP.  In Degreed anyone could write text, let’s say for a single onboarding task and add a link, and that ‘task’ would display in a list with a ‘mark complete’ button. Overall, this was a very easy experience for anyone who needed to create a onboarding task list for their team.  We saw teams own and manage the work, and they were very pleased with the systematic nature of the list as opposed to relying on Excel files.

In Degreed, the learner would click ‘mark complete’ after reading the text and completing the task.  This feels close to a Docebo self-observation checklist, except that the list in Degreed would update across the system, where as a Docebo self-observation checklist appears to version if an update is made.  That means that a person could have an out of date Docebo self observation checklist. Most confusingly, it doesn’t seem like we can tell who has which version of a checklist, so we wouldn’t know across the board who had wrong information if something gets updated.

Right now we are converting some of our Degreed pathway (task lists) into Docebo Courses.  Each ‘task’ is being set up as a HTML training material.  A training material in the Central Repository for a HTML page will update anywhere in the system where it is being used, and if we update a ‘course’ it will update for anyone who views the course.  However, an HTML training material moves to a completed status as soon as the page is viewed.

Managerial visibility to progress in Degreed wasn’t good.  With a Docebo course, there is better visibility to progress.  With a self-observation checklist there is no visibility to progress until the entire checklist is submitted it seems.

It doesn’t seem like anything really fits what we are trying to do, but what we are trying to do feels so basic.

 

Question: How are you sharing ‘task’ based actions with learners that you want them to check off they have done?

 

Thank you!

@Elaine_Barnes Hi, Elaine … Take a look at Checklists; you can find them under the Admin menu. I think that this would fit your requirements.

Be sure to take the DU courses and read the KB on Checklists cause there are some quirks to them. There have been several good threads here in the community around Checklists as well.

 

 

Hi @KMallette  - thanks. As I noted, I’ve tried self observation Checklists.

Are you all using them successfully? How are you working around the quirks?

Hi @KMallette  - thanks. As I noted, I’ve tried self observation Checklists.

Are you all using them successfully? How are you working around the quirks?

So sorry … I missed that!

We have stopped using them; the need expired. The quirk we found had to do with the enrollment into the checklist. We were using a group to enroll, but when the person left the group the enrollment remained. Ugh!

@Elaine_Barnes - I am following your story. I think these types of task lists are valuable, but here are one or two quirks:

  • Observation Checklists do not support html links
  • if the manager kicks off an observation checklist to an employee, they (employees) do not have an ability to retain said tasklist” - like no PDF transcript at the end of the “transaction” between mgr and employee.

Those are a few. There have been some good ideas out there - not slamming OCs, but IMHO - it feels like an 80% bake of a product in the current state. It just misses enough from being much more useful for broader use cases. A proposal as one suggestion as an alternative (which no one wants to hear):

  • Use a web form builder to establish the checklist
    • The web form builder should have two things:
      • being able to deploy a PDF receipt of the checklist (and a “sign off”)
      • being able to send an email to a mgrs email field
  • Deploy it as part of the New Hire experience

The other thing - and it will be more trackable, but also much more to design is to create a SCORM based module to run down said checklist.

Articulate recently deployed a print trigger meaning a clever instructional designer can support generating a form in a course and setting up a receipt as part of the output available from the SCO.

Thanks @dklinger - We have some teams utilizing Sharepoint lists.  They are still freshly released, so I am not sure the exact pros and cons as of yet.  My biggest concern with them is the whole set up seems very dependent on the creator of the Sharepoint experience. If they leave or move roles, I don’t see the complicated set up being sustainable at this time.  

We don’t have the need for a sign off or receipt, per se. We do have the need to have the check and balance that a new hire can ‘help themselves’ and ask their manager or peer about a task on the list, as opposed to having the list completion driven by their manager.  However, the manager needs to be able to see that a person is making progress so they can intervene early.  If there is managerial change - we want them to be able to see what has already been done, or in the case of a new people leader, be able to provide the appropriate onboarding support on the fly.  Dual accountability. There could be opportunities to use Power Automate flows to automatically distribute centralized documents that teams could maintain, but it could get complicated fast too.

I appreciate your candor in talking about OC here in Docebo. 

I’ll look in to the SCORM module solution for my awareness. Thank you for sharing.

I appreciate your time in thinking through the goals I outlined - I was hoping there would be a solution that would work and I was just not aware of or using correctly.  Thanks again!

Reply


Terms & ConditionsCookie settings