Plan it like a pro: action map → storyboard → slides
Plan a course before you build it: an action map (business goal, on-the-job actions, practice, minimum information), then a text storyboard with on-screen text, voiceover, image description, programming notes and animation cues. Both turn into Scenes slides, and the storyboard stays in step with them. Paste or import a storyboard you already wrote in Google Docs, Word or Excel.
Last updated 8 min read
I storyboard in Google Docs before I build. Do I have to retype it all into the authoring tool?
Step by step
Start with Plan first
From the dashboard, click New course, pick Plan first (Scenes) and click Create course. It opens on the Plan view. (In any Scenes course, click Plan in the top bar.)
Write the business goal
Type the measurable result the course should change, such as "Cut losses from phishing by half this year".
Add the actions
Click Add an action and write something people do on the job, such as "Report a suspicious email". Under it, add a practice activity (a realistic decision) and the minimum information it needs. Press Enter for the next item.
Turn it into slides
Click Turn into N slides. Each practice activity becomes a slide, with its action's information on a slide before it. The Storyboard view opens.
Write the storyboard
Fill in each row: on-screen text, voiceover, image description, programming notes, animation cues. Leave a cell and its slide follows.
Build and tick off
Click Slides, build each slide, and tick its programming notes off in the storyboard as you go.
Try it
Click Preview, then Share → Get public link and ask two or three people what confused them.
Why plan first
Devlin Peck's checklist says it bluntly: "Do not open your authoring tool until step 6." First you find out what people must do differently (an action map, Cathy Moore's method), then you write the course as a text storyboard and get it reviewed, and only then do you build. Rewriting a storyboard row takes a minute; rebuilding a finished slide takes an hour.
Scenes keeps all three in one place: Plan (the action map), Storyboard (a row per slide) and Slides (the canvas), in the top bar. The storyboard is not a separate document that drifts out of date: it is the slides, seen as text.
1. The action map
Open Plan. It has four parts, top to bottom:
- Business goal. A result the business measures, not a learning objective. "Cut phishing losses by half", not "Understand phishing".
- Actions. What people must do on the job to reach it. Write each so you could watch someone do it: "Report a suspicious email", "Check the sender's address before paying an invoice".
- Practice activities. For each action, a realistic decision the learner makes in the course: "An invoice from a new supplier asks you to pay today. What do you do?"
- Minimum information. Only what the practice needs: "Where the Report button is". Everything else is a job aid, not a slide.
Everything saves as you type. Enter adds the next item; Backspace on an empty item removes it. Removing an action shows Undo.
Tip: If an action has no practice activity, ask whether it needs to be in the course at all.
2. Turn the map into slides
Click Turn into N slides at the bottom of the Plan. For each action you get one slide with its information (as bullets), then one slide per practice activity, with programming notes that remind you what the practice needs (consequences as feedback, a way to try again).
Add more actions or activities later and click it again: only the new ones become slides. One Undo takes a whole batch back.
3. The text storyboard
Click Storyboard. It is a table with Peck's columns and a row per slide:
- Slide title: the slide's name.
- On-screen text: becomes a text box on the slide in a clean layout. Start a line with
-for a bullet. - Voiceover / narration: goes to the slide's notes, which learners can read as a transcript in the player's Notes panel.
- Image description: becomes an image placeholder with that description as its alt text. Pick the picture on the slide later; the storyboard shows Placeholder until you do.
- Programming notes: the triggers in plain words, one per line ("Next goes to slide 4", "Clicking Report shows the Well done layer"). Each line is a checkbox you tick off as you build. Learners never see them.
- Animation cues: for you, too ("Fade in the chart at 2s").
Type in a cell and click away: the slide follows, the edit is saved, and Undo in the top bar takes it back. Add, reorder and delete rows with the buttons beside each number; ↗ opens the slide.
Tip: A slide you built by hand with several text boxes shows its text joined and read-only in the storyboard, so a storyboard edit never flattens your layout. Edit those words on the slide.
Already have a storyboard? Paste it
In Storyboard, click Paste or open a storyboard.
- Google Docs or Word: select the whole table, copy, click in the box and paste.
- Excel or Google Sheets: select the rows including the header row, copy and paste.
- A file: Open .docx or .csv (in Google Docs: File → Download → Microsoft Word).
Columns are matched by their headings, loosely: "VO", "Voice over" and "Audio script" all mean the narration; "OST" is the on-screen text; "Dev notes" and "Interactions" are programming notes. A storyboard with a small table per slide, labels down the left, works too. The preview shows how each column was read; change any with its menu, then click Create N slides.
No storyboard yet? Download the template, Word or CSV: it imports cleanly as it is.
Send it for review before you build
Download .docx gives you the storyboard as a Word table for a reviewer who wants a document; Download .csv opens in a spreadsheet. Both import back as the same slides, so you can take the reviewer's edited copy and paste it in again as new slides.
To have the storyboard written for you, connect your own AI assistant (Settings → AI assistant): it can read the action map and write storyboard rows with the get_storyboard, update_action_map and update_storyboard tools, and you review every row here.
Part of the documentation: Build.
Found something here that does not match what the product does? That is a bug in the guide — see all guides or tell us from the Help Center.