Several weeks back, I talked a bit about elements featured in the design phase of course development, and now I’ve returned to finish off (the high-level) discussion.
Previously, I talked about design documentation. Now I’m going to focus more on the technology and visual elements.
Within the design phase, this is typically where I would identify an authoring tool or Learning Content Management System (LCMS). Where will the development occur? Will the course be developed in Articulate Storyline? Adobe Captivate? Flash? An internal LCMS? This should be identified before anyone moves further into the development phase. Why? Because the development tool selected may impact some of your specifications in your design documentation. For example, if you specify one authoring tool in your design documentation, but use another, your client might hold you accountable for not doing what you said you were going to do.
Once selected, this authoring tool specification will help you out when coming up with a style guide (e.g. what screen styles you’re planning on using) and will be instrumental in specifying prototype requirements and compliance requirements. If your project requires SCORM compliance, you’ll want to ensure the authoring tool you select has that capability…or redevelopment might be in your future.
Another element you might want to consider during the design phase is to outline your course content. High level is usually best for this.
From a higher education perspective, the design phase is where I would have faculty members begin populating a Course Development Plan document. This document acts as a container for specific high-level course content, and facilitates and easier transition during the development phase. For example, this document (once complete) will have most all of the content housed within the document (and signed off on), and the faculty member can then copy/paste the textual content into the Learning Management System (LMS) instead of having to spend time retyping/researching what content they want to include in which module. It just streamlines the development process.
For design, I think a good rule of thumb would be to outline as much information about the project requirements and high-level course content as you can, because it will make for a smoother development phase!
Leave a Reply