Hi everyone!
Wow! These are great. I got lost going through all of them and reading everyone's blog posts. So many creative and practical approaches.
I probably take a more complex approach to storyboarding. Each project dictates on how to approach this process. Larger projects that involve a considerable amount of time in the design process may require a varying storyboards. Smaller projects may only need a single document.
In the end, I see storyboarding as a process and not a single or set of documents. I teach a storyboarding workshop where I cover all angles of the process including different approaches and which templates to use when and how to implement the process into your workflows.
In my work, every project has a minimum of three storyboards - visual storyboard (flowchart) mapping out the contextual structure of the course, the main storyboard itself, and a style guide. Affectionately known as the project's "Storyboard Workbook."
Additionally, one of the storyboard documents I keep separate from the main storyboard is for assessment questions. There's a lot of decisions and moving parts in a single question and keeping it in its own document serves two benefits: 1) collaborating with SMEs, and 2) assign the assessment writing to another designer.
The storyboard documents need to be simple and easy to use for both the designer and SME.
Here's a zip with three templates I use and share in my workshops. Simple storyboard template, an example usage, and the assessment storyboard template. Enjoy!
https://nhs-templates.s3.amazonaws.com/NuggetHead-Studioz_storyboard-templates.zip