Deep dive review into lower performing modules

[a-a-ron]

Hey, team! We have some lower performing modules in relation to their overall completion rates. Our goal is to have a completion rate of 60%. Overall, we trend around 61% MoM, but the below modules are pulling our percentages down and have been trending well under that goal.

August Numbers

Module	Completion Rate	# completed / # started
Create and publish custom GitHub Actions	15.25%	12/116
Code scanning with GitHub CodeQL	15.87%	33/208
Configure Dependabot security updates on your GitHub repo	16.57%	28/169
Automate development tasks by using GitHub Actions	28.45%	468/1645
Introduction to GitHub	38.74%	1,177/3,038

For comparison, here is a list of some high performing modules in relation to the module completion rate.

Module	Completion Rate
Search and organize repository history by using GitHub	85.20%
Settle competing commits by using merge conflict resolution on GitHub	84.66%
Manage repository changes by using pull requests on GitHub	83.39%
Maintain a secure repository by using gitHub best practices	72.84%
Communicate effectively on GitHub by using Markdown	71.69%

Plan of Action

We need to conduct a performance review on each of these modules to see how we can increase the completion rates, improve the user experience, and maintain the level of quality that we set for our learners.

Action Items For Each Module

• Thoroughly review the module content for flow, narrative, and length
  • Review use of images, tables, and other visual elements
  • Does the content read like a doc or like a conversation guide?
• Review the introduction unit
  • Does it capture your attention?
  • Do the learning objectives/scope align with the content?
  • Does the target audience match the content?
  • Do we accurately describe the module and learning objectives? (Is it possible that learners start the course thinking it's one thing to find out it's another?)
• Review the module exercise
  • Does it work?
  • Does it enforce a learning objective?
  • How is it placed in the module? Should we move it around?
  • Do we need other exercises?
• Review the questions at the end of the module
  • Do the questions test on content taught in the module?
  • Do the questions follow best practices for item writing?

[rmallorybpc]

Module	Completion Rate	# completed / # started
Configure Dependabot security updates on your GitHub repo	16.57%	28/169

Action Items For Each Module

• Thoroughly review the module content for flow, narrative, and length
  • Review use of images, tables, and other visual elements
  • Does the content read like a doc or like a conversation guide?
• Review the introduction unit
  • Does it capture your attention?
  • Do the learning objectives/scope align with the content?
  • Does the target audience match the content?
  • Do we accurately describe the module and learning objectives? (Is it possible that learners start the course thinking it's one thing to find out it's another?)
• Review the module exercise
  • Does it work?
  • Does it enforce a learning objective?
  • How is it placed in the module? Should we move it around?
  • Do we need other exercises?
• Review the questions at the end of the module
  • Do the questions test on content taught in the module?
  • Do the questions follow best practices for item writing?

[rmallorybpc]

Module	Completion Rate	# completed / # started
Automate development tasks by using GitHub Actions	28.45%	468/1645

Action Items For Each Module

• Thoroughly review the module content for flow, narrative, and length
  • Review use of images, tables, and other visual elements
  • Does the content read like a doc or like a conversation guide?
• Review the introduction unit
  • Does it capture your attention?
  • Do the learning objectives/scope align with the content?
  • Does the target audience match the content?
  • Do we accurately describe the module and learning objectives? (Is it possible that learners start the course thinking it's one thing to find out it's another?)
• Review the module exercise
  • Does it work?
  • Does it enforce a learning objective?
  • How is it placed in the module? Should we move it around?
  • Do we need other exercises?
• Review the questions at the end of the module
  • Do the questions test on content taught in the module?
  • Do the questions follow best practices for item writing?

[rmallorybpc]

Module	Completion Rate	# completed / # started
Introduction to GitHub	38.74%	1,177/3,038

Action Items For Each Module

• Thoroughly review the module content for flow, narrative, and length
  • Review use of images, tables, and other visual elements
  • Does the content read like a doc or like a conversation guide?
• Review the introduction unit
  • Does it capture your attention?
  • Do the learning objectives/scope align with the content?
  • Does the target audience match the content?
  • Do we accurately describe the module and learning objectives? (Is it possible that learners start the course thinking it's one thing to find out it's another?)
• Review the module exercise
  • Does it work?
  • Does it enforce a learning objective?
  • How is it placed in the module? Should we move it around?
  • Do we need other exercises?
• Review the questions at the end of the module
  • Do the questions test on content taught in the module?
  • Do the questions follow best practices for item writing?