My Process
1
Kickoff Meeting
I begin with a kickoff meeting to get the full scope of the course. I like to have the client give me an “elevator pitch” of the project—what it’s about, why they’re seeking e-learning, and what they hope to achieve.
2
Review Materials
I spend time thoroughly reviewing the materials. It's at this point I come up with any questions I might have for the SME, and schedule an additional call with them.
3
Create a High-Level Outline
At the beginning stages of the project, I'll begin aligning whatever materials I have with the goals and learning objectives we have discussed and created together with the SME. After I know what content is important, and what I might be able to cut, I begin with a high-level outline. I like to know the beginning and end of my scripts so I know where the module will ultimately end up, and I can steer the content in the right direction.
4
Expand the Outline
I now build upon the high-level outline with more specifics, such as narration (either full narration or brief notes, depending on my inspiration at the time), and ideas for interactions. This outline allows me to look at the course from a top-down perspective, giving me the opportunity to change or move things without having wasted time.
5
Full Scripting
Satisfied with the outline, I can now begin scripting the module. I use my company's storyboard format, which includes a spot for screen titles, onscreen text, images, narration, interaction details, and a comments section.
I typically start my scripting with the narration. Once that is done, I go back to add images and onscreen text to the storyboard. We source images from Shutterstock, paste the preview in the script, and include the image number for the developer (often myself) to find and download later.
6
Client Reviews
The rest of my process involves working with the client to review and revise my script. They are typically told to make edits directly to the storyboard with Tracked Changes on, or by adding comments in the margin. If multiple people are reviewing, we stress the importance of consolidating the edits in order to avoid conflicting feedback between "multiple cooks."
This typically looks like:
-
Send to client for Alpha Review
-
I make their requested edits
-
Send to client for Beta Review
-
I make their requested edits
-
Send to client for Final Review
At this point, the script should be in shape to begin development.
While this is happening, we also create a design "prototype" for the module, showcasing how it might look in the module. We'll usually offer two versions for them to choose from. The client can make any changes to the look and feel at this point in time.
7
Development
It's time to get out the authoring tool of choice (usually Storyline) and begin development. Development is my bread and butter, and something I enjoy very much.
When finished, we follow the same structure as our scripting - that is, send for alpha review, revise, beta review, revise, and finalize.
8
Publish and Deliver
Once the client has given the go-ahead, we now publish the module to SCORM. After that, it is either uploading the SCORM package to the LMS for them, depending on the situation, or sending the client the package along with all of the source files involved in the project.