Storyboarding a digital solution
Represent a digital solution's design in a storyboard — each screen, what the user does (inputs), what the system shows or does (outputs) and the resulting behaviour — communicate it, and revise it in response to feedback
Lesson
Set out your lesson
“Storyboarding a digital solution means practising the idea at the table with a simple screen-free or sandbox check. We will demo once, then your child tries.”
Bring to the table
- A shared-doc mock page on paper (or a sandbox doc)
- Two colored pencils for “two editors”
Extra for the adult
Worked example. Add a comment instead of deleting a teammate’s paragraph.
Optional challenge. For Storyboarding a digital solution, add one harder example after success.
What to notice. Keep one parent note: examples tried; results; support used. This session samples Storyboarding a digital solution, not mastery.
Share and support
Family records and proof options
Keep a record of your learning
Save photos, notes, and attendance. Export a proof packet for compliance or portfolio reviews.
Practice this concept
Start practiceStoryboarding a digital solution practice
Practice key ideas from Storyboarding a digital solution.
Free · no login · no ads · Practice answers and completion are not saved. Parent observation remains the lesson record.
Learning resources
Extra practice links — they do not replace Gakuva’s teaching approach.
Code.org · Practice link — not the full lesson
Computer Science for Ages 5 to 11
Before you open · source notes
Computer Science for Ages 5 to 11 supports Storyboarding a digital solution. An adult previews and guides; this is a learning page, not a scored quiz.
Free educational page, no sign-in required for the tested path.
Before you openAsk the learner one fact they learned and one question they still have.
Opening this link does not save learning or assess mastery.
Source, access and review notes
Public Code.org page. An anonymous GET on 2026-11-12 returned HTTP 200 with no login or payment prompt for this URL. Opening the link does not save practice or assess mastery. An adult should preview and guide the learner.
Code.org. “Computer Science for Ages 5 to 11.” External page; Gakuva does not copy, host, embed, or redistribute materials.
Unknown — link only
Check understanding
- Sketch a storyboard for a simple game, app or animation showing each screen, what the user does and what happens
- Present the storyboard to a partner or user, explaining its inputs, outputs and steps, and collect feedback
- Revise the storyboard in response to feedback or testing and explain what changed and why
“If your child planned a simple game, could they draw a storyboard showing each screen, what the player does and what happens — and improve it after someone tries it?”
Curriculum record
- Type
- Procedural
- Subject
- Computing
- Domain
- Designing Digital Solutions
- Age range
- Ages 8–12
Standards