Why use design documents and storyboards?  

A design document tells the story behind the project: What is the business problem and why do we need to solve it?  Who needs to learn or grow after the project is implemented and why?  What features are most improtant to us and what are the deadlines for delivery?  How will we measure the learning and growing in short-term progress and long-term structural changes?  A design document allows all stakeholders both present and future to see the goals of a project, what decisions were made during creation and provide clarity and insights for future iterations.

A storyboard is the blueprint for creation of an e-Learning (Storyline) project, designed to document the learners' engagement in the course through layers, triggers, scenarios and visual structure.  A storyboard allows handoff from designer to developer or between team members while preventing the inefficient and question-riddled situation of having each stakeholder interpret the course's creation on their own.  A storyboard is a "single source of truth" for the project, where everyone involved can easily search for information and envision the course before creation is completed.