Storyboards for video design and review
Posted by Sarah Maddox
I’ve just created two short instructional videos, introducing specific aspects of our APIs to developers. I used a storyboard as a way of outlining the video content, illustrating my ideas about the flow of the video, and requesting a review from my colleagues.
A colleague, Rachel, introduced me to the idea of storyboarding a while ago. This is the first time I’ve tried it.
What a storyboard looks like
This is what the storyboard looked like when I sent it out for initial review comments:
To get started, I looked at the examples Rachel had given me of her own storyboards, remembering her very useful comments about how she used them. Then I looked online to see what other people are doing. I found two examples that gave me more good ideas on how to represent my video design in a storyboard:
- Storyboards, from the Advanced Computing Center for the Arts and Design. I like the Hunting Sequence from the Jane Animation Project.
- Storyboarding, from the UC Berkeley Graduate School of Journalism. The sketches at the bottom of the page are appealing, and show how different formats of storyboard are useful in different situations.
The design of my storyboard is a conglomeration of ideas generated by my colleagues examples and the two sources above. I shared my storyboard template with members of my team, and suggested they may like to use something similar when designing videos. They like the idea, and each person adapted the template to suit them. This approach works surprisingly well.
What a storyboard is good for
For me, the primary goal of a storyboard is to share an easily-absorbed way of representing the flow of the video.
This is what I wrote at the top of my first storyboard:
This storyboard is a precursor to a script. It’s an illustrative way of outlining the video before we start in-depth development of code and script. Note: All visuals are just mockups to give some idea of what’s happening, and are not intended to be the real thing.
Building out the storyboard
As time passed, I fleshed out the script on the storyboard, replacing the outlined content with the words I was planning to say during the presentation. So the storyboard evolved continually during the scripting of the video, the flow design, and the planning of the visual aspects such as screenshots, demonstrations and annotations.
A number of colleagues responded to my requests for review. After a few revisions, my script was ready to move to a separate document for final tweaking and practice runs. This is what the storyboard looked like at that point:
The resulting video
This is the very first instructional video that I’ve ever presented! (Apart from videos shot during conference presentations.) It’s short by design. The target audience is developers who are using the Google Maps Android API to include maps in their Android apps.
Producing the video
I could write an entire blog post about the process of filming the video. So for now, I’ll just show you a couple of photos of the video production studio.
The first photo shows me sitting in the hot seat, with the green screen behind me. In the foreground are the two video production screens, with ATEM Television Studio (the input stream switcher) on the right and Wirecast (which we used to define the video format and control the flow) on the left.
The second photo is a panoramic view from the hot seat, showing all the lights that glare down at you. The production centre in the middle at the back.
A storyboard is a good tool for solidifying my own ideas about the video, showing them to others, and conducting a collaborative review.
I’d love to hear your ideas about storyboarding, the format of the storyboards you use, and how you find them useful (or not).🙂
About Sarah MaddoxTechnical writer, author and blogger in Sydney
Posted on 18 January 2014, in Android API, Google Maps, technical writing, videos and tagged Google Maps Android API, instructional videos, social media, technical communication, technical writing, videos. Bookmark the permalink. 2 Comments.