This document summarizes a presentation about achieving flexibility with a learning management system (LMS). It discusses typical LMS functionality, determining needed features through an 80/20 rule prioritization, and a case study of how PADI uses a flexible LMS. Key points covered include asynchronous e-learning courses, assessments, reporting, and supporting standards like SCORM and AICC in LMSs. The presentation also addresses learner and stakeholder requirements through hands-on activities.

1. Session 101
What you Can Achieve with a
Flexible LMS
Jack McGrath
President, Digitec Interactive
Simon Morgan
PADI Worldwide

2. What you can achieve with a Flexible LMS
• LMS “Defined”
• Determining the features you really need
• 80/20 Rule: Achieving Flexibility
• Case Study: PADI

3. LMS “Defined” – typical LMS functionality:
– Asynchronous e-Learning courses
– Assessments, testing, tracking,
reporting, and measurement
– Scheduling/managing
classroom/instructor led training
– Student registration
– Automating reporting and
tracking
– Student history
– Supports industry standards,
such as SCORM and AICC

4. Top reasons
organizations
use an LMS
Source: eLearning Guild 360
Learning Management Systems
Report, 3/07

5. Hands-on Activity:
Step 1. Initial Requirements
TAKE 5 MINUTES
List the functionality you think you’ll need in
your LMS
Survey says…

6. Learner Requirements: How we’re taught
“Throughout the 19th and 20th centuries,
classroom pedagogy was characterized by
one-way, teacher-centered/text-bookcentered delivery of single-media
information to students whose role was
that of passive receptor.”
Source: In Search of the Next
Generation Online Learning
Environment. Becker, Henriksen, 10/06

7. How & where
we really
learn
Source: eLearning Guild 360
Learning Management Systems
Report, 3/07, ‘”What an LMS Can’t
Do”. Mosher

8. Web 2.0 Feature-mania?
–
–
–
–
–
–
–
–
Social networking
Weblogs
Video blogs
Games
Collaboration
Wikis
Twitter
Technology du jour

9. When we need to learn
1. When learning for the first time
2. When wanting to learn more
3. When trying to remember
4. When things change
5. When something goes wrong
Source: eLearning Guild 360
Learning Management Systems
Report, 3/07, ‘”What an LMS Can’t
Do”. Mosher

10. Hands-on Activity:
Step 2. Learner Requirements
TAKE 5 MINUTES
•Who are they? List your learner groups
•How do they currently learn?
•What is the environment and their
constraining factors?

11. Technical
Requirements:
The Use-Case for
your stakeholders
Source: eLearning Guild 360
Learning Management Systems
Report, 3/07

12. Hands-on Activity:
Step 3. Technical Requirements
TAKE 5 MINUTES
•List your Stakeholders
•Outline the use-case for each to identify what
features they need
Survey says…

13. Achieving Flexibility – the 80/20 rule
Prioritize all your requirements,
1. Initial Requirements then choose a system that can
deliver 80%
Source: eLearning Guild 360
2. Learner Requirement
Learning Management Systems
3. Technical Requirements
Report, 3/07

14. Case Study: PADI
• The PADI model
• The PADI learner
– Blended learning
experience
– Learner connectivity
• The Stakeholders
– Localized Dive Shop
administrators and
Instructors
– IT Integration

15. What you Can Achieve with a
Flexible LMS
Thank You!
Jack McGrath
President, Digitec Interactive
jmcgrath@digitecinteractive.com
www.knowledgedirect.com
Simon Morgan
PADI Worldwide
Simon.morgan@padi.com
www.padi.com