Showing posts tagged Design Document
Design Document or Storyboard? #19
If you are producing a course end-to-end there is usually no need to produce a detailed storyboard for each screen. Only when working in a larger team is there a need to produce very specific storyboard and asset specifications for a developer. On way of bridging the gap between content and storyboard is to produce a detailed design document. These are essesntial for capturing the text and narration that has been written, agreed and signed-of by subject matter experts. On the Articulate Community forum recently David Anderson published a sample “storyboard template” which proved inspirational for adapting my design documents. I split my usual “content” column into two. One column for on-screen text, one for narration.
This change proved to have some significant benefits when producing a course design. Firstly, it draws attention to the big difference between spoken and written English - they are very different! Secondly, and most importantly, it improves the ability to “visualise” how the content should translate to on-screen graphics and animation.
