Writing user stories
Write user stories in the form 'As a ..., I want ..., so that ...' that state who the user is, what they need and why, for one or more users of a digital solution (with a group, with a real user or independently)
Lesson
Set out your lesson
“Writing user stories 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
- Paper for a quick wireframe
- Pencil and eraser
Extra for the adult
Worked example. A big “Save” button helps a young user finish without hunting menus.
Optional challenge. For Writing user stories, add one harder example after success.
What to notice. Keep one parent note: examples tried; results; support used. This session samples Writing user stories, not mastery.
Share and support
Compare teaching approaches
Teaching approaches
Gakuva’s recommended starting approach is selected. You can still compare every option.
1 approach
Writing user stories means practising the idea at the table with a simple screen-free or sandbox check. We will demo once, then your child tries.
Materials: Paper for a quick wireframe; Pencil and eraser. 1. Say the goal of Writing user stories in plain words once. 2. Adult sketches one screen for a user need and names who it helps. 3. Child sketches three tiny screens or flows and states the user need for each. 4. Fresh check: one fresh sketch matched to a user need. Record and stop. Done: three sketches with a user-need sentence each. Proof: parent note of examples and results. Stop: End after the fresh check; keep optional challenge for another day.
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 practiceWriting user stories practice
Practice key ideas from Writing user stories.
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 Fundamentals
Before you open · source notes
Computer Science Fundamentals supports Writing user stories. 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 Fundamentals.” External page; Gakuva does not copy, host, embed, or redistribute materials.
Unknown — link only
Check understanding
- Write at least two user stories for a planned digital solution (e.g. 'As a Year 1 student, I want to hear each word read aloud, so that I can check I said it correctly')
- Check that each user story names the user, what they want and why, and fix any that miss a part
- Write user stories for two different users of the same solution (e.g. after asking or surveying them) and explain how their needs differ
“If your child were designing an app for their little cousin, could they write what the user needs in the form 'As a ..., I want ..., so that ...'?”
Curriculum record
- Type
- Procedural
- Subject
- Computing
- Domain
- Designing Digital Solutions
- Age range
- Ages 8–12
Standards