Activity 01
Pairs: Movement Sequence Challenge
Pairs plan a paper sketch of five block commands to guide a character from start to goal. They build the sequence in ScratchJr, test it, and swap computers to predict and debug each other's code. Record what changed for success.
Compare digital commands to human language in terms of precision.
Facilitation TipDuring the Pairs Movement Sequence Challenge, circulate and ask one partner to explain their block choices while the other runs the code, ensuring both students articulate the logic aloud.
What to look forPresent students with a simple visual code sequence (3-4 blocks) on the board or projector. Ask them to write down what they predict the character will do. Then, have them run the code to check their prediction.
UnderstandApplyCreateSelf-AwarenessSelf-ManagementSocial Awareness
Generate Complete Lesson→· · ·
Activity 02
Small Groups: Predict the Path Maze
Provide a screen maze; groups write predictions for block sequences needed to navigate it. Build and run the code, compare results, then adjust blocks collaboratively. Discuss why predictions matched or failed.
Evaluate the advantages of visual programming over text-based coding for beginners.
Facilitation TipIn the Predict the Path Maze, pause the small groups after their written predictions to have them justify one block choice to the class before testing.
What to look forGive students a slip of paper. Ask them to write one difference between a spoken instruction (e.g., 'Go get a book') and a digital command (e.g., a sequence of move forward, turn, pick up blocks). Collect these as they leave.
UnderstandApplyCreateSelf-AwarenessSelf-ManagementSocial Awareness
Generate Complete Lesson→· · ·
Activity 03
Whole Class: Precision vs Language Demo
Project a simple task; class calls out human directions, then votes on block equivalents. Teacher builds both versions live, runs them, and class notes precision differences. Students suggest improvements.
Predict the outcome of a simple block-based code sequence.
Facilitation TipFor the Whole Class Precision vs Language Demo, use a timer to keep the comparison tight so students notice the difference in clarity between vague directions and exact commands.
What to look forPose the question: 'Imagine you are explaining to a friend how to draw a square. How is telling them the steps different from showing them a sequence of code blocks that draw a square?' Facilitate a brief class discussion.
UnderstandApplyCreateSelf-AwarenessSelf-ManagementSocial Awareness
Generate Complete Lesson→· · ·
Activity 04
Individual: Simple Story Builder
Each student creates a three-step interactive story with character actions and sounds. Test independently, then note one change for better flow. Share one highlight with the class.
Compare digital commands to human language in terms of precision.
What to look forPresent students with a simple visual code sequence (3-4 blocks) on the board or projector. Ask them to write down what they predict the character will do. Then, have them run the code to check their prediction.
UnderstandApplyCreateSelf-AwarenessSelf-ManagementSocial Awareness
Generate Complete Lesson→A few notes on teaching this unit
Teach visual programming by letting students fail forward. Start with playful exploration so they feel safe testing ideas, then guide them to notice why some sequences work and others don’t. Avoid rushing to correct mistakes; instead, ask questions that prompt students to debug their own logic. Research shows this approach builds deeper understanding of sequencing and precision in coding.
Students will demonstrate understanding by translating spoken instructions into precise block sequences, predicting outcomes before running code, and explaining why block order matters. They will also compare the clarity of visual commands with everyday language, showing they grasp both the tool and the concepts behind it.
Watch Out for These Misconceptions
During Pairs: Movement Sequence Challenge, watch for students who treat casual directions like 'go over there' as sufficient instructions. Redirect by asking them to turn their spoken words into exact block commands and test whether the character completes the task.
During Pairs: Movement Sequence Challenge, if students write vague instructions, provide a sentence stem like 'The character must move forward three blocks, turn right, and move forward two blocks.' Have them revise and test the new sequence to see the difference.
During Small Groups: Predict the Path Maze, watch for students who assume block order does not change the result. Redirect by swapping two adjacent blocks in their sequence and asking them to predict the new outcome before running it.
During Small Groups: Predict the Path Maze, give each group two identical block sets. Ask them to swap two blocks, predict the new path, then run the code to confirm. Use the visible difference to discuss step-by-step execution.
During Whole Class: Precision vs Language Demo, watch for students who dismiss visual blocks as 'not real coding.' Redirect by having them compare a spoken recipe to a block sequence that draws a shape, highlighting how both require exact steps.
During Whole Class: Precision vs Language Demo, run a quick live demo where a student gives vague directions to draw a square (e.g., 'make it look like a square') and another student uses blocks to draw one precisely. Discuss which method produced consistent results.
Methods used in this brief