Notes
Client expects delivery in mid-May 2022
-
Employee responsibility to be safe, but EHS is a collaborative partner in that
- People have viewed them as a group to bring in to “make them safe”
- Emphasize their responsibility, EHS as partner
- They make themselves safe
- Stepping back from heavy-handed compliance
-
“support brand”- changing the perception as described above
-
Part of learning and growth as an employee is your application of the safety guidelines
-
Audience is everyone at Apple
- Assigned to every employee
- Added to employee onboarding
- Over time, only taken by new employees who may not fully understand their jobs
-
Tone: Not pedantic, not the safety police
-
Put learner at the center
- learner’s perspective in the design
- learner sees themself in Apple universe
-
Leave knowing about and how to use
- EHS web site
- training platform
- reporting platform/incidence tool
-
Lean how to
- respond in an emergency
- report an issue
- note: may be able to re-use assets from previous course DM produced on this topic
-
14 job locations- corporate offices, retail, cafe, apple care, manufacturing, etc.
- pick which principles apply to your location
- self-selected, probably will not pull from employee profile
-
Start general, go specific (to location), back to general for wrap-up
-
Pam and TP: Emphasize collective?
- May not align perfectly with their message
-
EHS- Previously “Environment, health, and safety” now “Employee health and safety”
- This may be an assumption based on omission. Need to validate.
-
No assessment but stats are key
- survey results that are tracked (question at the end, in each location)
- How many users went to a given job location, as a percentage of total
- Can SCORM track these? LMS?
Follow-up from Scot Muncaster
For tracking, they are looking to eventually use xAPI which is the successor to SCORM, but will not have a LMS capable of using it initially. xAPI is designed to make it easier to track anything like clicks on specific buttons or links, but it can also be done via SCORM. Ultimately, that all just comes down to us sending tracking information from any of those things we want to track, and then mapping that data into the appropriate storage location within SCORM or xAPI. So, the course-specific part will remain the same, and we would essentially just be swapping the storage adapter. I would love to be able to build a xAPI adapter on this project, but there is not going to be budget for it, so we’ll have to plan on that being some maintenance contract in the future.