Making something is a way to ask better questions
A child changes the colour of a poster, gives a character an instruction or explains why a game did not do what they expected. Those small choices can open a conversation about patterns, sequence and communication. The result does not need to look like an adult’s professional project to make the learning visible.
Scratch Foundation describes creative learning through making, experimenting, debugging and reflection. That is educational context, not a claim that one platform suits every child. At TWA, activities are matched to interests, readiness and an agreed learning plan; no fixed age band or guaranteed outcome is invented on this page.
Help your explorer reach the star.
An explorer is at the top-left of a small board. The star is two squares right and one down.
Your role: Add moves, predict where they lead and fix a step that bumps into the edge. A guardian can explore alongside you; no child details are requested.
What you’ll learn: Discover how giving moves in a particular order changes a result.
No account needed. Nothing is sent or saved. You can restart at any point.
Read the full guided story without the interactive controls
You can follow the same lesson here without JavaScript.
Try one move
Move right once. Watch which square the explorer reaches.
What happens and why: One Right move takes the explorer from row 1, column 1 to row 1, column 2. It changes one position, not the whole route.
Build a route to the star
Keep the first Right move. Add another Right and a Down, then run the sequence from the start.
What happens and why: Right, Right, Down reaches row 2, column 3. Instructions run in order. Other valid routes are possible, and a blocked edge move stays in the previous square.
Find the extra instruction
A practice route has Right, Right, Right, Down. Run it, notice the edge bump, then remove the third Right.
What happens and why: The extra Right tries to leave the board. Removing that instruction leaves a route with no blocked move. Debugging means finding and fixing the cause of an unexpected result.
Try a new target
The star moves to the bottom-right. Build and run a fresh route. Say where you expect the explorer to finish before you run it.
What happens and why: Right, Right, Down, Down is one route to row 3, column 3. Compare your prediction with the observed position. No score or age requirement is implied.
Takeaway: Instructions have an order. Predict, run, compare and change one thing when the result surprises you. There can be more than one useful route.
Where this is useful: Useful for puzzles, giving clear directions and early programming exploration.
A fictional educational example, not a confirmed TWA assignment, assessment or learner outcome. Simplified to explore one idea; real situations need context and authorised procedures.
Optional: explore your own route
Want to explore the technical model?
The guided story above introduces the idea. This original workspace lets you try actions in different orders. It has its own reset and does not inherit your story choices.
- Sequence
- Instructions in the order they should happen.
- Run
- Carry out the instructions.
- Debug
- Find and fix the cause of an unexpected result.
- Boundary
- The edge of the board that the explorer cannot cross.
Give your explorer a route.
Learning objective: Predict the result of a sequence and debug one instruction at a time.
Guide a fictional explorer from the top-left corner to the star in the middle-right square. A guardian can explore alongside the child; no details are collected.
Evidence desk
- Start
- Row 1, column 1
- Star
- Row 2, column 3
- Grid
- 3 rows × 3 columns; moves outside are blocked
Your workspace
Worked explanation & takeaway — available without JavaScript
Right, Right, Down reaches the star. Other routes are possible. Run a sequence, compare the destination with your prediction, clear it and try again. A blocked move leaves the explorer in its previous square. This activity does not establish an age requirement or confirmed TWA lesson.
Fictional educational model. No live system, personal assessment or confirmed TWA assignment. All actions run locally in your browser.
Can you reach the star?
Start at row 1, column 1. The star is at row 2, column 3. Discuss the moves before choosing a route.
| Row | Column 1 | Column 2 | Column 3 |
|---|---|---|---|
| 1 | Start | Empty | Empty |
| 2 | Empty | Empty | Star |
| 3 | Empty | Empty | Empty |
You reach row 2, column 3: the star. Explain how the two right moves changed the column and the down move changed the row.
Read both scenarios and explanations
Right, right, down
You reach row 2, column 3: the star. Explain how the two right moves changed the column and the down move changed the row.
Right, down, down
You finish at row 3, column 2. Try changing a direction or the order, then predict the new ending.
An educational illustration using fictional situations. It is not a confirmed TWA assignment, live system, assessment or promise of a particular tool.
From an idea to a sequence someone else can follow
Start with familiar actions: arrange three pictures into a story, describe how to draw a shape or give a toy character a few steps. If the instructions produce an unexpected result, ask which step could change. The challenge can be discussed aloud or on paper before any account or screen is involved.
TWA’s existing children’s direction includes colours/shapes/layouts, posters, Scratch and simple game ideas, first websites, progression towards Python where suitable, storytelling, guided AI exploration and digital safety. These are learning directions, not a promise that every child completes every topic or follows an adult three-level course.
Try a tiny route-finding adventure together
In the fictional three-by-three board below, begin at the top-left square and aim for the middle-right star. Two right moves followed by one down move reach it. One right move followed by two down moves ends somewhere else. Both sequences are short; the difference is their order and direction.
Invite the child to predict the ending, trace the moves and explain what happened. Then change one instruction and try again. This is an illustration of sequencing and checking a result, not an assessment of a child’s ability. A parent can help describe the steps without taking over the explanation.
A story or route the child can explain
Choose a fictional character or the small board example. Make a few instructions, predict the result, try them and explain one revision.
What you could document
- A simple poster, story, game idea or route plan
- A prediction of what the instructions will do
- A revised instruction after a test
- The child’s own explanation, supported appropriately by a guardian
What makes the explanation useful?
Look for curiosity, an explainable choice and a willingness to try another idea. This is not a competition, a diagnostic assessment or a promise of a professional coding outcome.
The learning plan determines actual activities and assessment. These deliverables are examples, not contractual curriculum outcomes.
A learning plan should fit the child and protect their privacy
Discuss interests, current confidence, useful support and how the child responds to a challenge. Ask TWA about supervision, accessibility needs, suitable devices, session arrangements and how work would be shared. Those details need confirmation rather than an assumed group timetable or an active holiday programme.
A project can be a poster, small game, visual story or first webpage, accompanied by the child’s explanation. Share age range and learning needs only where useful; avoid sending a child’s full name, school or sensitive information through an initial enquiry. All enquiries should come from a parent or guardian.