storyboard

Create your own storyboard pages or template. Do not word-process. Use pencil to make changes easy.

A storyboard is:
•	the description of an event
•	the link between the production flowchart and the product components
•	the last of your design work at the detailed level to be completed
•	a commitment 

Some considerations and guidelines:

•	there is a lot to say about an event and all its parts; include all component labels in the storyboard, and only that information about the components that is not obvious from reading the component descriptions

•	the storyboard is often the first place where some concepts such as art renditions are documented: the storyboard can be used as a design document BUT the other design documents must still be completed in order to ensure that navigation, content, user activity and product goals and treatments are still well handled

•	you know the storyboard is complete when it could be handed over to the production team and they have no questions for you, and the author could assemble it as you requested

Information you will include on each storyboard.

identification	the same unique event identification code as you would find in the "box" for the event on the production flowchart	
description	the purpose of this event, how it works to complete the whole product 	
content	a general description of the content	
components	the labels for each component included in the event	
arrangement	positioning of graphics, video, text, etc  (by sketch and, if necessary by exact screen placement instructions)	
navigation	prior event(s), following event(s)
control buttons…	
overlays	graphics, controls and composite sketches	
timing	total cumulative times for all components	
production instructions	any instructions not obvious from other information given	
authoring instructions	any instructions not obvious from other information given