Over the past two weeks, I’ve talked quite a bit about the analysis phase of most Instructional Design models, and now it’s time to talk about the Design phase.
But I’m not a designer!
Oh. But you are! At least if you claim to be an Instructional Designer. Like analysis, many IDs don’t get the opportunity to dip their toes in the design phase, but it’s a very important phase to be a part of.
While it might sound as though we’re talking graphic design and look/feel, we aren’t exactly. Only sort of. The design phase is where you identify how the learning is going to occur. So the look and feel…conceptually. And it may also include elements of visual look and feel.
The output of this phase is typically referred to as ‘design documentation’. This documentation outlines things such as:
- Instructional Strategy
- Learning Objectives
- Assessment Strategies (and sometimes the assessment items)
- Prototype Requirements
- Compliance Specifications (e.g. system requirements for the end user and SCORM requirements)
- Branding Guidelines
- Screenstyles
The design documentation is used to guide the design and allows developers to keep their eyes on the prize (or the project requirements). It also allows multiple developers to ensure a consistent approach across development.
Have I piqued your interest?
Great! Stay tuned for more on the design phase…next!
Leave a Reply