|
|
|
|
|
|
 |
Storyboarding For Reusable Content
02/07/2005
By: Megan Beyer
Where would a contractor be without a blue print or a conductor without sheet music?
They most likely would be a bit lost, just as an instructional designer (ID) and
developer would be without storyboards. Storyboards are the lifeline between
IDs and developers. Communication is key to creating a quality product and
storyboards help drive that communication.
Storyboards come in a variety of formats and layouts. Every organization has
their own way of storyboarding, the key is to make sure that you include all of
the essential components you will need for the development of your product.
Some items to consider including in your storyboards are:
- A storyboard sheet identifier (similar to a page number)
- Text for the current screen
- Graphics file names
- Audio file names
- Video file names
- A rough graphical layout of the screen
- Programming instructions or notes to the developer.
The format you choose is not important, just as long as you are using a form of
communication that meets the needs of your organization. However, there are
a few things you need to consider when creating storyboards for reusable content.
These considerations will help make your content reusable, searchable and well defined.
They are rather simple to implement too.
Considerations
- Content should not include numbers that reference location:
- Limits reuse: Welcome to Module 01, Overview
- Allows for reuse: Welcome to the Overview
- In On Screen Text, avoid using terms that refer to previous modules, lessons, content
or screens
- Limits reuse: In the previous lesson you learned how to enter your password…
- Allows for reuse: Include contextual information in a stand-alone content
object. This piece of content would not be reusable, but it would enable reuse
for the other content objects. For an example, refer to Other Suggestions
below.
- Avoid using numbers in file naming conventions, use names that are descriptive of
the file so that it would be searchable in a repository
- Limits reuse: 1.2.1.jpg
- Allows for reuse: helpscreen.jpg
- Create non-context-specific content
- Limits reuse: The Quality Assurance Department uses SMART objectives that are specific,
measurable, achievable, relevant and time-based.
- Allows for reuse: Use SMART objectives that are specific, measurable, achievable,
relevant and time-based. (By removing specifics such as the department name, the
content is reusable in other parts of the organizations or other organizations.)
Other Suggestions
- Create a stand-alone introduction that includes context specific details
- Example: In the overview lesson, you learned about the overall process for performing
annual maintenance on the gas chromatograph. Within that process, the safety
procedure is conducted to ensure that the heating and cooling elements are working
properly. The purpose for conducting the safety procedure is to ensure that the
parts within the gas chromatograph are not hot. The consequence of skipping
this procedure is the potential for burning your fingers while you maintenance the
equipment. This lesson demonstrates the safety procedure.
- Design context free media. A way to reach a happy medium between context free
and context specific is by creating a graphic that provides context within the organization
but not so specific that it would only meet the needs for one content object.
- Example: If you were creating content to help a bridal registry department handle
customer objections, you would not show crystal and china in the background of the
visual. Instead, you would just show the employee and the customer so that
that object could be reused for training other departments on how to handle customer
objections.
Many times the question arises about how Sharable Content Objects (SCOs) should
be determined and who should determine them. A suggested practice is that
IDs and developers work together to determine SCOs. Every product and organization
are different, therefore the ID and developer can create a more sound product by
working together to determine SCOs.
If you focus on these areas when creating storyboards and maintain consistent communication,
you will have a solid foundation for creating reusable content as you begin the
development phase.
This article has been provided to ADLNet.gov by an ADL Community member and may
not reflect the views and policies of the U.S Government and the ADL Initiative.
|
|
|
|
|
|