Core Design
At a large e-commerce and technology company, we’d been working on creating new training programs for 11 different business units for 5 years. But, no one stepped back to look at the big picture. When I did, I saw an opportunity to solve gaps, streamline, and set us up for a better training future.
What’s the problem?
The Gaps
The tools got simpler. The training didn't. New Hires used to need long, detailed training. They had to memorize processes and juggle several complex systems just to handle a basic customer contact. Then the technology changed. New guided workflows made the system intuitive enough that people needed far less instruction to use it. But the training was still built for the old, complex system.
Training took too long for what learners actually needed. New Hires spent days in a blended classroom-style training before taking their first real contact. Much of that time covered navigating tools and memorizing steps the new system now handled for them. The longer training ran, the longer it took people to become productive. It also made it harder for the business to move people where they were needed most.
Learners didn't feel ready. A steady share of learners said the same thing in course feedback: "I need more practice to feel confident." That lack of confidence showed up in their first week on the job. Learners were getting plenty of information but not enough realistic, hands-on practice or personal feedback before facing real customers.
Learners were trained on the same skills more than once. Each business unit had its own learning path. Many of those paths taught the same skills. When an experienced associate cross-trained into a new program, they had to repeat training on skills they had already mastered. That wasted time, frustrated learners and slowed down cross-training.
The Solution
We had a unique opportunity to streamline the training to match the simpler technology across all business units. We’d build one shared foundation of common skills. We’d move away from "tell" and toward "practice" so learners could get hands-on experience from the start. It would get them ready for their first customer contact faster and with more confidence. We called this approach Core.
When you have an idea, you don’t start with a meeting or a PowerPoint. You write. It’s part of the process that helps you refine your idea and think about it in a different way. When it’s in good shape, you present that doc to leaders and stakeholders and continue to iterate until you have something real that can move forward.
This is a highly redacted sample of the strategy doc that I wrote for Core. Confidential information, data, metrics, and examples have been edited or removed.
What’s the plan?
Once we had the idea of Core fleshed out, it was time to make the plan. I used AI to analyze learner anecdotes, met with stakeholders and Subject Matter Experts (SMEs), and listened to real learners who had completed our previous learning paths.
Using that information, I created a map of the Core learning path. The easiest and fastest way to get everyone aligned is to get everyone at the table (metaphorically) in a synchronous virtual meeting. I call this a Design Jam. It’s not just about efficiency (although it does prevent email ping pong), but it also helps bring all the creative juices together in one room.
We go line by line through the map, tweak things, riff off each others’ ideas, and all leave with a plan we’re excited to implement together.
This is an edited version of the map of the Core learning path. The Core learning experience is shared between all business units.
Proprietary use cases, examples, and terminology have been removed.
Get Started
With the plan locked in, it was full speed ahead.
I created a workback schedule in Asana using our available designer headcount and business flow dates to determine the best launch windows. This schedule included task by task dates and instructions for all of the IDs, SMEs, and Approvers working on the project.
I designed templates for Storyline, Rise, PowerPoint, and Word so all of the assets would have the same voice regardless of the designer working on them.
At the project start, we hosted a kickoff meeting with everyone involved (Localization, Operations and Program SMEs and Approvers, Training Delivery, and Instructional Designers). I outlined the strategy, the roles, the responsibilities and shared key dates so there’d be no surprises.
This video was shared with IDs to introduce them to the new templates.
Design and Development
Every training module starts with a storyboard. This storyboard includes the on-screen text, narration, and visual notes and sketches. This storyboard is what is reviewed by the project leads (me and one of my fellow Sr. IDs), SMEs, and approvers.
Project leads review for design thinking, accessibility, the ability to be localized, and overall learning quality.
SMEs and approvers review for content accuracy.
Before we ever touch any of our development tools, we have a fully approved vision for the training. Then, it’s onto development. For the trainings I personally created as an ID for this program, I used Vyond, Storyline, PowerPoint, and Adobe Photoshop. You can preview two of the finished products below.
Each of these previews were heavily edited to remove any proprietary or confidential information.