A five-dollar computer and the workshops it transformed
The single most effective tool in our professional development toolkit is not software. It is a circuit board the size of a credit card that costs about five dollars.
The BBC micro:bit is a programmable microcontroller with built-in sensors (accelerometer, compass, temperature, light), input buttons, a 5x5 LED display, and Bluetooth connectivity. It can be programmed with block-based code, JavaScript, or Python. It runs on two AAA batteries. And it has fundamentally changed how we introduce computing concepts to teachers who have no prior experience with programming.
Why physical computing changes the conversation
When we run a PD session on computational thinking using only screen-based tools — a simulation, a coding environment, a web application — we lose a meaningful fraction of our audience in the first 30 minutes. The abstraction barrier is real. Teachers who are not comfortable with computers as a medium struggle to engage with computing as a concept when the only feedback loop is text on a screen.
The micro:bit eliminates that barrier. When a teacher writes three blocks of code that cause her micro:bit to display her name, she has physical evidence in her hands that the code worked. When she adds the accelerometer and the display changes when she tilts the board, the connection between input, processing, and output is visceral — not theoretical. That moment of tangible feedback is where engagement starts for teachers who have historically opted out of anything labeled “technology.”
Over 144 of the lesson plans on CxEdHub use the micro:bit as the primary computing platform. That number is not an accident. It reflects the volume of teacher-created content that emerged from workshops where the micro:bit was the entry point.
How we use it in PD
Our micro:bit workshops follow a consistent arc that we have refined across seven years and hundreds of participating teachers.
Day one begins with the micro:bit as a learning tool. Teachers work in groups of three or more to complete a structured sequence: display output, button input, sensor reading, conditional logic, data logging. Each activity builds on the previous one and connects to a computing concept (variables, loops, conditionals, input/output, data collection). By the end of day one, every participant — regardless of prior experience — has a working program that collects real sensor data.
Day two shifts from learning to designing. Teachers identify a topic in their existing curriculum where sensor data or physical computing could add value. A science teacher might build a temperature logger for a weather unit. A math teacher might use the accelerometer to collect motion data for a graphing activity. A social studies teacher might design a “beacon hunt” activity that uses the micro:bit’s radio communication to simulate supply-chain logistics.
The design work happens in collaborative groups. Teachers sketch, prototype, test, and revise — exactly the process we want them to facilitate for their students. The PD models the pedagogy it teaches.
What the data shows
Across our NSF-funded programs — WySLICE (reaching 150+ K-8 teachers) and WySTACK (focused on high school STEM teachers) — the micro:bit sessions consistently produced the highest rates of classroom implementation during the follow-up academic year. Teachers who built a micro:bit lesson during the PD were more likely to teach it, adapt it, and share it with colleagues than teachers who worked with screen-only tools.
The reason, based on our interview data, is straightforward: the micro:bit gives teachers a physical artifact they can hand to students. It transforms computing from a screen activity into a lab activity. And for science and math teachers especially, the lab model is familiar territory. They already know how to run labs. They just did not have a computing lab that fit their subject.
Getting started
If you are considering physical computing for your district’s CS integration strategy, the micro:bit is the lowest-barrier, highest-return entry point we have found. The hardware is inexpensive enough to deploy at scale (classroom sets of 25 cost under $150), the MakeCode programming environment is free and browser-based, and the ecosystem of open resources — including the 144 lessons on CxEdHub — means your teachers will not be starting from scratch.
The hardware is the easy part. The PD design around it is what determines whether the micro:bits end up in student hands or in a closet.