Micro:bit First Steps

Overview

Students explore the BBC micro:bit as a programmable digital system and create a simple program that displays an icon and responds to a button press. The lesson introduces safe handling, input, output, algorithms and block-based coding, building foundations for designing and testing digital solutions.

Learning intentions

Students will:

• identify key parts of a BBC micro:bit and explain their purposes
• create and run a simple block-based program
• use an input to control an output
• describe how testing and debugging improve a digital solution

Success criteria

• I can identify the LED display, buttons and connection points.
• I can create a sequence of blocks that runs on a micro:bit simulator or device.
• I can make a button press produce a different output.
• I can test my program, find a problem and make a change.

Curriculum links

• Digital Technologies — investigate how digital systems use input, processing and output.
• Digital Technologies — develop and follow algorithms using visual programming.
• Digital Technologies — design, produce, test and evaluate a digital solution.
• General capabilities — digital literacy, problem-solving, critical and creative thinking.

Lesson structure (50 minutes)

1. 0–5 min · Hook and learning goal. Open with the hook and learning intention slides showing a micro:bit displaying an unexpected message; ask, “How can a tiny computer know that someone has pressed a button?” Students predict possible inputs and outputs, then briefly share ideas with a partner.

2. 5–12 min · Meet the micro:bit. Use the micro:bit parts and safety slides to demonstrate the LED display, buttons, USB connection and battery pack, explaining that a digital system receives input, processes instructions and creates output. Students handle a powered-off micro:bit or inspect the on-screen simulator, then label the parts on the micro:bit labelling and coding worksheet. Remind students to carry devices carefully, keep food and liquids away, and ask before changing cables or batteries.

3. 12–20 min · Teacher modelling. Display the block-coding demonstration slides and model an algorithm: on start, show an icon; on button A pressed, show a different icon; on button B pressed, show a number. Think aloud while dragging blocks and predict what will happen before running the program. Students identify each event, input and output and write the sequence in the worksheet.

4. 20–35 min · Guided build. Students work in pairs, with one driver controlling the computer and one navigator reading the instructions; partners swap after each successful test. Using the simulator or classroom micro:bits, they build the demonstrated program and complete the worksheet prompts: “What is the input?”, “What is the output?” and “What happens when no button is pressed?” Circulate to check that students use the correct event blocks and test after each change.

5. 35–43 min · Design challenge. Show the challenge and testing slides. Pairs modify their program so button A and button B produce two different outputs, then add a short message or animation of their choice. They record one prediction and one test result on the worksheet. Encourage students to change only one part at a time so they can identify the effect of each change.

6. 43–47 min · Share and debug. Invite two or three pairs to demonstrate their programs. Students use the prompts “I noticed…”, “I wonder…” and “We fixed…” to discuss how the program responds to inputs. The teacher highlights debugging as finding and correcting an error, rather than treating an unsuccessful first attempt as failure.

7. 47–50 min · Reflect and exit. Revisit the recap and reflection slides and ask students to explain the input–process–output cycle. Students complete the reflection prompts template by recording what they learned, one success, one challenge and a next step, then hand it in as they leave.

Resources

• BBC micro:bit devices, one per pair where available
• Computers or tablets with an approved micro:bit block-coding environment
• USB leads and battery packs, if required
• the micro:bit introduction, demonstration, challenge and recap slide deck
• the micro:bit labelling and coding worksheet
• the reflection prompts template
• Headphones, if students are using a simulator with sound
• Projector or interactive display
• Device storage tray or labelled workspace

Assessment

• During modelling, question students about the difference between an input, processing instruction and output.
• Observe pairs for safe device handling, correct use of event blocks, collaboration and systematic testing; use the worksheet responses to identify misconceptions.
• Collect the reflection template and check whether students can name a micro:bit input, output and one debugging action.

Differentiation

• Support students with a partially completed block sequence, a visual input–process–output diagram and sentence starters such as “When I press…, the micro:bit…”. Pair students strategically and allow simulator use before handling physical devices.
• Provide step-by-step checkpoints on the worksheet and read instructions aloud for students requiring literacy support. Keep the driver/navigator roles explicit and permit role changes at a planned point.
• EAL/D learners may label diagrams using words, symbols or home-language notes before explaining their thinking in English; explicitly model “button press”, “display”, “event”, “algorithm” and “debug”.
• Extend confident students by adding a shake input, a countdown or a repeated animation, then asking them to explain how their algorithm changed and why the new design is useful.