Why storyboarding still matters
The storyboard is the cheapest place to fix a design mistake. A wrong section in a storyboard costs you a few minutes of editing. A wrong section in a built module costs you a rebuild. AI does not change this arithmetic — if anything, it makes the storyboard more important, because AI can generate large volumes of text that are wrong very quickly.
The storyboard is where your ID judgment is made visible. It is the document that proves the design is right before anyone starts building. Use AI to generate content inside the storyboard — not instead of it.
By the end of this unit- Generate a structured section outline using a five-element Copilot prompt.
- Script individual screens using AI-generated text as a starting point.
- Write an AI-ready asset brief for audio, image, and video assets.
The storyboard in the AI-augmented workflow
In a pre-AI workflow, the storyboard was the document you built painstakingly, section by section. In an AI-augmented workflow, Copilot can generate a first-draft storyboard outline in minutes — but the storyboard's function has not changed. It is still the document that:
- Proves the structure serves the objective
- Specifies every asset (audio, image, video) before the build starts
- Goes to proofread before anything goes into the platform
- Becomes the review document against which the build is checked
AI accelerates the first-draft stage. You still own the quality of the document.
Section outlines with Copilot
The outline prompt is the first AI task in a storyboarding session. Its output is a section-by-section structure — not screen-level content. Keep them separate. Generating screens before you have validated the structure builds in the wrong direction.
Building the outline prompt
An outline prompt for a storyboard should include: the learning objective, the audience, the total time, the number of sections, and a structural constraint (for example, "include a worked example and a short review, exclude general AI background").
Example: outline prompt for a Copilot onboarding module
I am building a 30-minute introductory module on using Copilot in Microsoft Teams for new users in a mid-sized professional services firm. The learners are experienced professionals who are not technical users. The learning objective is: the learner will select the right Copilot meeting feature for three common meeting scenarios.
Generate a four-section outline. Section 1 should establish why meeting preparation matters (not AI background). Section 2 should show what Copilot does in a meeting, using one specific worked example. Section 3 should cover three common scenarios with branching choices. Section 4 should be a short review of four questions. Do not include a general introduction to what AI is. Do not use bullet-heavy format — describe each section as a short paragraph.
What to accept and what to edit in the outline output
Accept: The overall sequence, if it moves from context to concept to practice. Section titles that reflect the learner's task rather than the topic.
Edit: Sections that describe AI features rather than learner tasks. Sections that front-load definitions before context. Generic examples (replace with role-specific ones). Any section that feels like it belongs in a product manual.
Reject and reprompt: If the outline produces a general AI introduction you explicitly excluded, reprompt with the constraint repeated more explicitly. AI does not always follow exclusion constraints on the first pass.
From outline to storyboard table
Take an outline Copilot generates for a module you are designing. How many sections describe the topic rather than the learner's task? What would you need to change to make each section learner-task-led?
Scripting screens with AI
Once the outline is validated, you can use Copilot to script individual screens. The screen script is the content that will appear in the build — text, accordion items, process step descriptions, and so on. This is where AI provides the most direct time saving in the ID workflow.
Screen scripting principles
One screen, one idea
Give each screen script prompt a single content focus. If the section covers three concepts, prompt for each one separately. Combining multiple concepts in one prompt produces either the first one expanded and the rest compressed, or a list-heavy screen that violates the one-idea rule.
Specify the block type
Copilot does not know your authoring platform. Tell it what the text will go into: "This is the text for a Rise 360 text block. Write it as flowing prose, not bullets." Or: "This is an accordion item. Write a 60-word body text for the item titled 'Context constraints'."
Carry forward the audience description
In a long session, restate the audience in each major prompt. Copilot's context window is not infinite, and a generic example may creep back in if the audience description has receded from the active context.
Edit before you paste
Never paste AI output directly into an authoring platform without editing. Run the three-question review (teaches the objective, specific example, real retrieval) on every screen before it moves to the build stage.
The time saving from AI-assisted scripting is real — expect a 40–60% reduction in first-draft writing time. The quality cost from skipping the review step is also real. The net gain comes from using AI for the draft and your time for the review. Reversing that ratio eliminates the benefit.
Asset briefing with Copilot
The storyboard must specify every asset before the build starts. This is non-negotiable — assets coming in late add cost and delay. Copilot can help you write asset briefs faster, but the brief still needs to meet the same standard as a human-written one.
What a good asset brief contains
Required elements for a voiceover brief:
- The verbatim script — word for word, as it will be recorded
- Tone direction: warm and direct, not formal; conversational, not broadcast
- Pacing note: where to pause, where to slow for emphasis
- The screen it accompanies and whether it plays automatically or on demand
Copilot use: "Write a 90-word voiceover script for this section introduction. Tone: warm, direct, second person. Audience: [role]. The script should match this text: [paste screen text]. Do not add new information — this is a read of the screen text with natural spoken language."
Required elements for an image brief:
- What the image shows — descriptively, not interpretively
- What it is for: diagram, screenshot, contextual photograph, or decoration
- What the alt text should say (written in the storyboard before the image is produced)
- Any exclusions: no generic stock photo aesthetics, no text in the image
Copilot use: "Write an image description brief for an illustration showing a project manager reviewing a Copilot-generated meeting summary. The image should show a single person at a desk, reviewing a screen. No phones in frame. Realistic workplace setting. Alt text: 'A project manager reviews a Copilot meeting summary on screen.'"
Required elements for a video brief:
- Use case: demonstration, place, person interview, or interaction
- Maximum length: 2 minutes per clip
- Shot types required: screen capture, wide establishing shot, close-up
- Script (if screen capture with voiceover) or interview questions (if person)
Copilot use: "Write a brief for a 90-second screen capture video showing how to start a Copilot meeting recap in Teams. Script the voiceover as a step-by-step walkthrough: one sentence per step. Do not use click-by-click UI language — describe what each step achieves."
A storyboard contains the note "image of someone using Copilot" as the asset specification. What is missing?
End of Unit 4
You should now be able to:
- Generate a validated section outline using a structured Copilot outline prompt.
- Script individual screens using AI text as a starting point, with editorial review before each one enters the storyboard.
- Write complete asset briefs for audio, image, and video using Copilot assistance.
Unit review
Why is the storyboard more important in an AI-augmented workflow, not less?
What should you do if Copilot includes a general AI introduction you explicitly excluded in the outline prompt?
Which two things must an audio brief always contain?
What is the expected time saving from AI-assisted screen scripting — and what is the condition that makes that saving real?
End of module
You have completed Course 04: Storyboarding with Copilot. Next: Designing Cowork Learning Experiences — how to design learning for people whose working model has shifted to human-AI collaboration.