Design Tool - Storyboards

Name:

Date:

Class:

Quick Questions

Shade in the A or B circle for each question.

1. Does a storyboard show a sequence of steps or screens?

A True

B False

2. Are storyboards usually created before or after a solution is built?

A After

B Before

3. Can storyboard panels include written notes?

A Yes

B No

4. Do storyboards typically use rough sketches or polished final graphics?

A Rough sketches

B Polished final graphics

5. Can a storyboard have multiple panels?

A No

B Yes

Match the Pairs

Draw a line connecting each item on the left to its match on the right.

Left column		Right column
1A sequence of panels showing screens and user actions		AStoryboard
2A rough sketch showing what happens when a button is tapped		BStoryboard note
3A tool used to visualise the user journey before development		CStoryboard
4Written text added alongside a panel to explain the step		DStoryboards should be created before development, to guide the design
5The team wrote full source code instead of sketching the user journey		EStoryboards should use sketches to plan the journey, not final code
6A storyboard was created only after the app was fully coded		FStoryboard panel

Definitions

Storyboard

Fill in the Blanks

Complete each line of code by filling in the missing parts.

1. _______ 2. Actions 3. Notes

1. Screens 2. _______ 3. Notes

1. Screens 2. Actions 3. _____

A storyboard shows a ________ of steps

Storyboards help visualise the user _______

Spot the Error

Shade in the letter of the line that contains an error.

Question 1

A A storyboard shows a sequence of steps or screens.

B It helps visualise how a user moves through a solution.

C A storyboard must always be written in full code.

D Each panel can represent a different stage of use.

Question 2

A Storyboards can include notes describing each step.

B These notes explain what is happening in each panel.

C Storyboards are created after the solution is fully built.

D They are useful for planning the user journey.

Question 3

A Storyboard panels can never include written descriptions.

B Each panel in a storyboard represents one step or screen.

C Panels are usually arranged in a specific order.

D This order shows the flow of user interaction.

Question 4

A Storyboards are useful early in the design process.

B Storyboards focus mainly on writing final source code.

C They help teams agree on the user journey before building.

D This reduces the risk of confusion later in development.

Question 5

A Storyboards require polished, final-quality graphics only.

B A storyboard can show what happens when a user taps a button.

C It can also show what screen appears next.

D Storyboards typically use rough sketches or simple images.

Answer Key

Design Tool - Storyboards

Section A: Quick Questions

A — True

B — Before

A — Yes

A — Rough sketches

B — Yes

Section B: Match the Pairs

A sequence of panels showing screens and user actions → Storyboard

A rough sketch showing what happens when a button is tapped → Storyboard panel

A tool used to visualise the user journey before development → Storyboard

Written text added alongside a panel to explain the step → Storyboard note

The team wrote full source code instead of sketching the user journey → Storyboards should use sketches to plan the journey, not final code

A storyboard was created only after the app was fully coded → Storyboards should be created before development, to guide the design

Section C: Definitions

Storyboard — A sequence of visual panels showing how a user moves through and interacts with a solution, step by step

Section D: Fill in the Blanks

1. Screens
2. Actions
3. Notes

1. Screens
2. Actions
3. Notes

1. Screens
2. Actions
3. Notes

A storyboard shows a sequence of steps

Storyboards help visualise the user journey

Section E: Spot the Error

C — A storyboard is a visual planning tool, not written code — it doesn't need to be coded.

C — Storyboards are created before a solution is built, to plan the user journey in advance.

A — Storyboard panels often include written notes or descriptions alongside the visuals.

B — Storyboards focus on visualising the user journey, not on writing final source code.

A — Storyboards typically use rough sketches, not polished final-quality graphics.