Section 1: From Unplugged to Plugged — Why Physical Computing Matters¶

1.1 Introduction: The Next Step in Your CT Journey¶

Welcome to TEM5018. If you're reading this, you've already taken an important step in your professional development by completing TEM5016, where you explored computational thinking as a powerful framework for problem-solving and reasoning. You've learned that CT isn't about computers at all—it's about thinking clearly, breaking down problems, spotting patterns, and designing step-by-step solutions. You've experienced unplugged activities, tackled Bebras challenges, and begun to see how CT weaves naturally into the subjects you teach every day.

Now we take the next step.

This course is about bringing CT to life through physical computing—through robots that move across your classroom floor, programmable toys that respond to children's commands, microcontrollers that sense and react to the world, and even mechanical devices that compute without electricity. Where TEM5016 gave you the conceptual foundations, TEM5018 gives you the tools to make those concepts tangible, visible, and deeply engaging for young learners.

But why "plugged" after "unplugged"? Isn't the point of unplugged activities that they work without technology? Yes—and that remains valuable. Unplugged activities will always have a place in your teaching. But there's something uniquely powerful about seeing an algorithm come to life, about watching a robot execute the exact sequence a child has planned, about debugging not on paper but in the real world where mistakes roll across the floor for everyone to see. Physical computing doesn't replace what you've learned; it extends it.

Throughout this section, we'll explore what physical computing is, why it matters pedagogically, how it connects to the CT concepts you already know, and how it integrates across the primary curriculum. We'll also address the practical realities: managing resources, organising your classroom, and assessing learning that happens through making and doing.

By the end of this section, you'll have a clear understanding of why physical computing deserves a place in your teaching toolkit—and you'll be ready to dive into the specific tools and approaches we'll explore in the sessions that follow.

1.2 What Is Physical Computing?¶

At its simplest, physical computing is computing that interacts with the physical world. While traditional computing happens on screens—clicking, typing, watching—physical computing reaches beyond the screen to sense, move, light up, make sounds, and respond to touch, motion, light, temperature, and more.

The Key Components¶

Every physical computing system has three essential elements:

Input: Sensing the world (buttons, sensors for light, sound, motion, temperature, touch)
Processing: Making decisions based on that input (the "thinking" part—the program)
Output: Acting on the world (LEDs, motors, speakers, displays)

Consider a simple example: a micro:bit programmed as a step counter. The input is the accelerometer detecting motion. The processing is the program that counts each shake and keeps a running total. The output is the number displayed on the LED grid. The child wearing it sees their steps accumulate in real time—abstract counting made physical and personal.

Beyond Screen-Based Coding¶

You may have encountered block-based coding environments like Scratch, where children drag and drop colourful blocks to create animations and games. This is valuable, but it remains on-screen. Physical computing takes those same programming concepts—sequences, loops, conditionals, variables—and connects them to objects that exist in the child's physical space.

When a child programs a Bee-Bot to navigate a maze, the algorithm isn't just an idea; it's a bee-shaped robot trundling across the carpet. When the sequence is wrong, the robot bumps into the wall. There's no "undo" button—just the need to think again, revise, and try once more. The feedback is immediate, concrete, and often delightfully dramatic.

The Spectrum of Approaches¶

It helps to think of a spectrum, from fully unplugged to deeply embedded:

Approach	Examples	Characteristics
Unplugged	Bebras puzzles, human robots, paper algorithms	No technology; focuses on pure CT concepts
Tangible interfaces	Cubetto, Scottie Go!, Osmo	Physical objects control on-screen or robotic actions
Screen-based coding	Scratch, Code.org	Programming on screen; virtual outputs
Physical computing	Bee-Bot, micro:bit, Makey Makey	Programming controls physical devices
Embedded systems	Arduino projects, smart devices	More advanced; real-world applications

This course focuses primarily on tangible interfaces and physical computing—the middle ground where programming meets the physical world in ways accessible to young children.

A Brief History¶

Physical computing isn't new. Industrial robots have existed for decades, and hobbyists have tinkered with electronics since the early days of computing. But what's changed is accessibility. Devices like the BBC micro:bit were designed specifically for education, with friendly programming environments and low costs. Floor robots like Bee-Bot have been classroom staples for over 15 years. The maker movement has brought tools once reserved for engineers into primary classrooms.

Today, you don't need an engineering degree to help children build interactive projects. You need curiosity, a willingness to learn alongside your students, and some understanding of why this matters—which is exactly what we'll explore next.

A Physical Computing System in Action

The automatic nightlight: A micro:bit with a light sensor checks the ambient light level. If it's dark, it turns on an LED. If it's bright, the LED stays off.

Input: Light sensor reading
Processing: "If light level < 50, then turn LED on; otherwise, turn LED off"
Output: LED on or off

Even this simple system teaches conditionals, sensors, and the input-process-output model—all visible and tangible.

1.3 The Pedagogical Case for Physical Computing¶

Why should busy primary teachers add robots and microcontrollers to their already full plates? The answer lies in how children learn—and how physical computing aligns with what research tells us about effective education.

Embodied Cognition: Thinking with the Body¶

Cognitive science increasingly recognises that thinking isn't just something that happens in the head. We think with our bodies, through movement and manipulation. When a child physically walks the path a robot will take, or manipulates tangible coding blocks with their hands, they're engaging more of their brain than when they simply watch or listen.

This is particularly important for young children, whose abstract reasoning is still developing. The Swiss psychologist Jean Piaget described children up to about age 11 as being in "concrete operational" stages—they learn best through direct interaction with concrete materials (Piaget & Inhelder, 1969). Physical computing provides exactly this: abstract programming concepts made concrete through objects they can touch, move, and observe.

Bruner's Progression: Enactive, Iconic, Symbolic¶

Jerome Bruner (1966) proposed that learning progresses through three modes of representation:

Enactive: Learning through action and physical manipulation
Iconic: Learning through images and visual representations
Symbolic: Learning through abstract symbols and language

Traditional education often jumps too quickly to the symbolic. We ask children to understand written algorithms before they've had the chance to enact them. Physical computing allows children to begin enactively—physically moving robots, pressing buttons, handling sensors—before progressing to iconic representations (block-based code with visual elements) and eventually symbolic understanding (text-based code, abstract algorithm notation).

A child who has spent time programming floor robots develops an intuitive, bodily sense of what a sequence is, what happens when steps are out of order, and what debugging feels like. This embodied foundation makes later abstract learning more meaningful.

Constructionism: Learning by Making¶

Seymour Papert, a mathematician and educator who worked with Piaget, developed the theory of constructionism. He argued that learning is most effective when learners are actively constructing something meaningful—something they can share, discuss, and reflect upon.

Papert created Logo, an early programming language with a "turtle" that drew shapes on screen, and he pioneered the idea of using technology not to deliver instruction but to empower children as creators. His intellectual descendants include Mitchel Resnick at MIT, whose Scratch programming language and LEGO robotics work have shaped modern educational technology.

From the Research

The role of the teacher is to create the conditions for invention rather than provide ready-made knowledge.

— adapted from Seymour Papert, Mindstorms (1980)

Physical computing is constructionism in action. Children don't passively receive information about algorithms; they build robots that embody their algorithmic thinking. The artefact—the programmed robot, the interactive invention—becomes a vehicle for learning and a source of pride.

Immediate Feedback: The Power of Real Consequences¶

One of the most powerful features of physical computing is the immediacy of feedback. When a child runs a program on screen and it doesn't work, they see an error message or unexpected behaviour. When a child runs a program on a robot and it doesn't work, the robot might crash into a table, spin in circles, or miss its target entirely.

This isn't just more dramatic—it's pedagogically valuable. The feedback is:

Visible: Everyone can see what happened
Unambiguous: The robot either reached the goal or it didn't
Non-judgmental: The robot isn't criticising; it's just following instructions
Immediate: There's no delay between action and consequence

This creates a natural debugging cycle. The robot's behaviour reveals the gap between intention and instruction, and the child is motivated to close that gap—not because the teacher demands it, but because they want their robot to succeed.

Motivation and Engagement¶

Let's be honest: robots are exciting. There's something magical about making a physical object move according to your will. This isn't mere novelty; it's genuine engagement that can be channelled into deep learning.

Research consistently shows that physical computing activities increase student motivation, particularly among learners who might otherwise disengage from abstract or screen-based work. The tactile, kinetic nature of the activities appeals to diverse learners, including those who struggle with traditional approaches.

Harnessing Motivation

The excitement of physical computing is a resource, not a distraction. Channel it by:

Setting clear learning intentions that go beyond "playing with robots"
Building in reflection time: "What did the robot teach us about sequences?"
Connecting the activity to broader curriculum goals
Celebrating not just success, but thoughtful debugging

What the Research Says¶

Studies on physical computing in primary education consistently report positive outcomes:

Improved CT skills: Children using programmable robots show gains in sequencing, debugging, and algorithmic thinking (Bers, 2018)
Transfer to other domains: CT skills developed through robotics can transfer to mathematical problem-solving (Kazakoff & Bers, 2014)
Increased confidence: Children, particularly girls, show increased confidence in technology after hands-on physical computing experiences (Sullivan & Bers, 2019)
Collaborative learning: Physical computing naturally promotes peer collaboration and discussion (Resnick, 2017)

This isn't about replacing good teaching with gadgets. It's about adding a powerful set of tools to your repertoire—tools that align with how children learn best.

Reflection Prompt

Think of a concept you find challenging to teach—perhaps something abstract in maths or science. How might making it physical (visible, tangible, interactive) help your learners grasp it?

1.4 Physical Computing and the CT Concepts You Already Know¶

You've spent time in TEM5016 developing a strong understanding of the four pillars of computational thinking: decomposition, pattern recognition, abstraction, and algorithmic thinking. You've applied these through unplugged activities and Bebras challenges. Now let's see how physical computing brings these same concepts to life in new ways.

Decomposition: Breaking Down Robot Tasks¶

Decomposition is about breaking a complex problem into smaller, manageable parts. With physical computing, this becomes concrete and visible.

Consider a child tasked with programming a robot to navigate from one corner of a mat to another, picking up an object along the way. They can't simply say "go there"—they must break the journey into discrete steps:

Move forward to the first intersection
Turn right
Move forward to the object
Pick up the object
Turn left
Move forward to the destination

Each step is a small, solvable problem. The physical constraints of the robot—it can only move forward, turn left, turn right, etc.—force this decomposition. There's no way to cheat by giving a vague instruction.

Pattern Recognition: Spotting Repetition in Movement¶

Pattern recognition is about identifying similarities and regularities. In physical computing, patterns often emerge in movement and behaviour.

A child programming a robot to trace a square might initially write:

Forward, Turn Right, Forward, Turn Right, Forward, Turn Right, Forward, Turn Right

With guidance, they recognise the pattern: "Forward, Turn Right" repeats four times. This is the foundation for understanding loops—a fundamental programming concept. The physical activity makes the pattern visible in a way that abstract discussion cannot.

Abstraction: Hiding Complexity¶

Abstraction is about focusing on what's essential while ignoring irrelevant details. In physical computing, this happens at multiple levels:

The robot itself abstracts away the electronics, motors, and engineering that make it move. The child doesn't need to understand circuits; they need to understand commands.
Block-based programming abstracts away the text-based code underneath. A "move forward" block hides lines of code that control motor timing.
Procedures and functions allow children to create their own abstractions: defining a "draw square" routine that can be reused without rebuilding each time.

When a child uses a "forward" block without worrying about how the motor works, they're practising abstraction. When they create a reusable procedure for a complex manoeuvre, they're taking abstraction to a higher level.

Algorithmic Thinking: Sequences That Control Real Objects¶

Algorithmic thinking is about designing precise, step-by-step instructions. With physical computing, algorithms aren't hypothetical—they control real objects with observable consequences.

This makes the requirements of good algorithms crystal clear:

Precision: "Move forward a bit" doesn't work; you need "move forward 3 steps"
Order: Steps must be in the correct sequence, or the robot does the wrong thing
Completeness: Missing a step means the robot won't complete the task
Correctness: Errors in the algorithm produce visible errors in the robot's behaviour

The robot becomes an unforgiving but patient teacher. It does exactly what it's told—no more, no less. This reveals the gaps in children's thinking in a way that's informative rather than punitive.

The Debugging Advantage¶

Perhaps nowhere is the benefit of physical computing clearer than in debugging. When an algorithm on paper has an error, finding it requires careful mental simulation. When a robot's algorithm has an error, you can see it: the robot turns left when it should turn right, overshoots its target, or stops in the wrong place.

This visibility transforms debugging from a frustrating search into an investigative process:

Observe: What did the robot actually do?
Compare: What did I expect it to do?
Locate: At what step did it go wrong?
Hypothesise: Why might that step be incorrect?
Revise: Change the algorithm
Test: Run it again and observe

This cycle—which mirrors scientific method and design thinking—becomes natural when the subject of investigation is a physical robot rather than lines of code on a screen.

CT Concepts in a Bee-Bot Maze Activity

Task: Program a Bee-Bot to navigate from Start to Finish on a grid mat, avoiding obstacles.

Decomposition: The journey is broken into individual steps (forward, forward, turn left, forward...)
Pattern recognition: "I turn left, then go forward twice to get around each obstacle—that's a pattern!"
Abstraction: The child focuses on the path, not on how the Bee-Bot's motors work
Algorithmic thinking: The sequence must be precise, complete, and correctly ordered
Debugging: When the Bee-Bot hits an obstacle, the child identifies which step was wrong and revises

1.5 Beyond CT: What Physical Computing Adds¶

While physical computing is a powerful vehicle for CT, it offers additional benefits that extend beyond the four pillars. These additional dimensions make physical computing valuable not just for computing education, but for broader educational goals.

Design Thinking and Iterative Prototyping¶

Physical computing naturally invites design thinking—a human-centred approach to problem-solving that emphasises empathy, ideation, prototyping, and iteration.

When children create physical computing projects, they often begin with a problem: "How can we make a nightlight that turns on automatically?" They brainstorm solutions, build prototypes, test them, gather feedback, and refine their designs. This cycle—build, test, reflect, improve—mirrors the processes used by engineers, designers, and innovators.

Unlike paper-based planning, physical prototypes provide real feedback. The nightlight works or it doesn't. The robot reaches its goal or it doesn't. This grounds design thinking in concrete reality.

Systems Thinking: Inputs, Processes, Outputs, and Feedback¶

Physical computing introduces children to systems thinking—understanding how components interact within a larger whole.

Every physical computing project is a system:

Inputs: Sensors, buttons, user actions
Processes: The program's logic and decisions
Outputs: Motors, LEDs, sounds, displays
Feedback: Information that loops back (e.g., a sensor reading that affects subsequent behaviour)

Understanding systems is crucial in our interconnected world. From ecosystems to traffic flow to the human body, systems thinking helps children make sense of complexity. Physical computing provides a hands-on entry point.

Systems Thinking with a Traffic Light Project

A simple traffic light project using LEDs and a micro:bit illustrates systems thinking:

Inputs: Timer, or a button press from a "pedestrian"
Process: A sequence that cycles through red, amber, green (and responds to button presses)
Outputs: Red, amber, and green LEDs lighting in sequence
Feedback: The pedestrian button creates a feedback loop that modifies the timing

Children learn that systems have interacting parts, that changing one part affects others, and that feedback loops create dynamic behaviour.

Tinkering and Productive Failure¶

Physical computing invites tinkering—playful, exploratory experimentation without a fixed outcome. This is distinct from following instructions or completing a pre-defined task.

When children tinker, they ask "what if?" questions:

What if I add another sensor?
What if I change the timing?
What if I combine two programs?

Tinkering leads to unexpected discoveries and, inevitably, to failure. But failure in physical computing is productive: the robot that spins wildly reveals something about the code; the sensor that doesn't respond reveals something about connections. These "failures" become learning opportunities.

In a culture that often stigmatises mistakes, physical computing provides a safe space for productive failure. The robot isn't judging; it's just revealing the truth about the algorithm.

Creativity and Self-Expression¶

Physical computing is a creative medium. Children don't just follow instructions; they express their ideas, tell stories, solve problems that matter to them, and make things they're proud of.

A child might program a robot to perform a dance, create a musical instrument from fruit and Makey Makey, or build an automatic watering system for classroom plants. These projects reflect the child's interests and creativity while developing CT skills.

Mitchel Resnick argues that the best learning happens when children work on projects they're passionate about:

From the Research

"When people work on projects they’re passionate about, they’re eager to dive in and immerse themselves. They’re willing to work for hours, or longer, and hardly notice that time is passing. They enter a state that psychologist Mihaly Csikszentmihalyi calls flow—completely absorbed in the activity"

— Mitchel Resnick, Lifelong Kindergarten (2017)

Collaboration: Physical Projects Demand Teamwork¶

Physical computing projects often require collaboration. There are physical resources to share, problems that benefit from multiple perspectives, and tasks that are easier with multiple hands.

Unlike individual screen-based work, physical computing naturally promotes:

Division of labour: One child programs while another tests
Peer teaching: Children help each other with tricky concepts
Shared problem-solving: Debugging together, brainstorming solutions
Communication: Explaining ideas, defending decisions, resolving disagreements

These collaborative skills are valuable far beyond computing. They're life skills that physical computing develops organically.

Real-World Relevance¶

Finally, physical computing connects classroom learning to the real world. We're surrounded by physical computing: automatic doors, traffic lights, fitness trackers, smart speakers, robotic vacuum cleaners. When children program a robot or build a sensor project, they're glimpsing the technology that shapes their daily lives.

This relevance has motivational power. It also opens conversations about technology's role in society: Who makes these decisions? How do we want technology to work? What are the ethical implications? These are important discussions for future citizens.

Reflection Prompt

Beyond CT skills, what other educational goals could physical computing support in your classroom? Consider skills like collaboration, resilience, creativity, or communication.

1.6 Integrating Physical Computing Across the Primary Curriculum¶

One of the most important messages of this course is that physical computing shouldn't exist in isolation. It's not a separate "computing" lesson disconnected from the rest of the curriculum—it's a tool that can enrich learning across subjects. This integration is especially important in primary education, where you often teach multiple subjects and can create meaningful connections between them.

Let's explore how physical computing integrates with different curriculum areas, with concrete examples for each.

Mathematics¶

Physical computing is deeply mathematical. The connections include:

Measurement and estimation: How far does the robot need to travel? How many centimetres is one "step"?
Angles and direction: Turning 90 degrees for a right angle; understanding quarter, half, and full turns
Coordinates and position: Grid mats use coordinate systems; robots move through positions
Number and counting: Counting steps, keeping score, calculating distances
Data handling: Collecting sensor data, creating graphs, interpreting readings
Shape and space: Programming robots to draw shapes; exploring properties of shapes

Science¶

Physical computing aligns beautifully with scientific inquiry:

Variables and fair testing: Changing one input while keeping others constant
Observation and recording: Collecting sensor data, documenting robot behaviour
Cause and effect: If I program this, then the robot does that
Prediction and testing: Hypothesising what will happen, then testing
Data collection: Using sensors to measure light, temperature, sound, motion
Forces and motion: How robots move, friction, speed, direction

Literacy¶

Physical computing can enhance reading, writing, speaking, and listening:

Instructional writing: Writing clear, precise instructions (like algorithms)
Sequencing narratives: Programming robots to act out stories in order
Vocabulary development: Technical vocabulary in meaningful contexts
Speaking and listening: Explaining programs, collaborative discussion, presenting projects
Storytelling: Creating interactive stories, robot characters, narrative journeys

Art and Design¶

Physical computing opens creative possibilities:

Interactive art: Installations that respond to viewers
Kinetic sculpture: Art that moves
Sound art: Musical instruments, soundscapes, programmed compositions
Design process: Ideation, prototyping, iteration, refinement
Digital art: LED displays, programmed light patterns

Geography and History¶

Physical computing can bring geography and history to life:

Mapping and navigation: Programming robots to follow routes on maps
Direction and compass points: North, south, east, west through robot movement
Scale and distance: Understanding scale when planning robot journeys
Local geography: Creating mats based on local maps, navigating familiar places

Music¶

Beyond the Makey Makey instruments mentioned above, physical computing connects to music through:

Rhythm and timing: Programming sequences with specific timing
Composition: Creating musical patterns, loops, and variations
Sound and vibration: Exploring how sounds are made with speakers and buzzers
Musical notation: Parallels between musical scores and algorithms (both are sequences of instructions)

Physical Education¶

Even PE can incorporate physical computing:

Movement and timing: Robots that require physical movement to control
Measuring physical activity: Step counters, heart rate monitors
Spatial awareness: Navigating through physical spaces
Reaction games: Physical computing games that require quick responses

Choosing Your Integration Points¶

You don't need to integrate physical computing into every subject, every week. Start with natural connections—subjects involving sequencing, measurement, data, or cause and effect.

Curriculum Area	Physical Computing Tools	Key Connections
Mathematics	Floor robots, micro:bit	Measurement, angles, coordinates, data
Science	Sensors, micro:bit, data logging	Variables, observation, cause/effect
Literacy	Bee-Bot story mats, any tool	Sequencing, instruction writing, narrative
Art & Design	Makey Makey, LEDs, motors	Interactive art, design process
Geography	Floor robots with map mats	Navigation, direction, scale
Music	Makey Makey, micro:bit, speakers	Rhythm, composition, sound

Reflection Prompt

Choose one topic you'll be teaching in the coming weeks. How might physical computing enhance that topic? What tool might you use?

1.7 Choosing the Right Tool for the Right Purpose¶

Throughout this course, you'll encounter a range of physical computing tools. It's tempting to focus on the tools themselves—their features, how they work, what they can do. But effective teaching starts not with tools but with learning outcomes. The question isn't "What can this robot do?" but "What do I want my learners to learn, and which tool best supports that?"

Overview of Tool Categories¶

We'll explore each of these categories in depth in later sections, but here's an overview:

Floor Robots (Section 3)

Examples: Bee-Bot, Blue-Bot, Pro-Bot, Thymio, LEGO SPIKE
Characteristics: Move through physical space; programmed via buttons or screen
Best for: Sequencing, direction, spatial reasoning, early algorithms
Age range: Works well from Early Years through primary

Tangible Programming Interfaces (Section 4)

Examples: Cubetto, TacTile Reader, Osmo Coding, KIBO, Makey Makey
Characteristics: Physical blocks, tiles, or objects control the robot or screen
Best for: Pre-readers, tactile learners, collaborative programming
Age range: Especially strong for Early Years and lower primary

Programmable Microcontrollers (Section 5)

Examples: BBC micro:bit, Crumble
Characteristics: Small computers with sensors, LEDs, and expansion options
Best for: Input-process-output concepts, data, sensors, upper primary
Age range: Most suitable from around Year 3/4 upward

Mechanical Logic Toys (Section 6)

Examples: Turing Tumble, Gravity Maze, GraviTrax
Characteristics: No electricity; logic through mechanical systems
Best for: Pure logical thinking, unplugged-plugged bridge, puzzle-solving
Age range: Varies by complexity; some suitable from Year 1, others from Year 4+

When evaluating tools, consider the "low floor, high ceiling, wide walls" principle—a framework explored in detail in Section 2.2. Briefly: the best tools are easy to start with (low floor), support sophisticated work (high ceiling), and allow diverse projects (wide walls). Bee-Bot has a low floor but limited ceiling; the micro:bit scores well on all three dimensions.

Factors to Consider When Choosing Tools¶

Age and developmental stage

Early Years: Large buttons, tangible input, visual output, immediate feedback
Lower Primary: Simple sequences, floor robots, beginning block-based coding
Upper Primary: More complex algorithms, sensors, data, longer projects

Learning outcomes

Teaching sequencing? Floor robots work beautifully
Exploring data? Microcontrollers with sensors
Developing logical reasoning? Mechanical logic toys
Fostering creativity? Open-ended tools like Makey Makey

Curriculum connections

Match tools to subjects: e.g., floor robots for maths/geography, sensors for science

Resource constraints

Cost: What's your budget?
Quantity: How many devices can you afford? (Affects pedagogy—whole class vs. rotations)
Maintenance: Who manages batteries, repairs, updates?

Technical requirements

Does it need internet? Tablets? Computers?
How much setup time is required?
What happens when things go wrong? (They will!)

Your own confidence

Start with tools you find manageable
Build confidence before adding complexity
It's okay to learn alongside your students

Avoiding Tool-First Thinking¶

Here's a common trap: "I've got a class set of micro:bits—what can I do with them?"

This reverses the proper order. Better: "I want to teach my children about light and shadows in science. Could micro:bits help?" (Yes—the light sensor could measure light levels in different conditions. Or perhaps simple experiments without technology are sufficient.)

Learning-First Planning

Start with your learning intentions: What do you want children to know, understand, or be able to do?
Consider whether physical computing adds value: Will it make the learning more concrete, engaging, or effective?
If yes, choose the simplest tool that supports your intentions
Design the activity around the learning, not the tool
Ensure the tool enhances rather than distracts from the learning

Reflection Prompt

Think about the learning outcomes you most want to achieve with your class. Which physical computing tools might support those outcomes? What factors would influence your choice?

1.8 Practical Considerations for the Primary Classroom¶

Physical computing is exciting, but let's be realistic: it also introduces practical challenges. Devices need charging. Things break. Sessions take longer to set up. Children get distracted by the novelty. Effective physical computing teaching requires attention to classroom management and organisation.

Managing Physical Resources¶

Storage

Dedicate a clear space for physical computing resources
Labelled boxes or trays for each type of device
Visible, accessible storage encourages use
Consider: who is responsible for returns?

Charging

Establish charging routines (overnight? over weekends?)
Visual indicators: charged devices here, charging devices there
Spare batteries for emergencies
Check charge before sessions begin

Maintenance

Regular checks: do all devices work?
Simple repair kits (screwdrivers, spare batteries)
Reporting system: "This Bee-Bot isn't working" notes
Know who to contact for serious repairs

Quantity management

Inventory: know what you have
Booking system if shared across classes
Clear expectations for borrowing and returns

Classroom Organisation¶

Whole-class instruction

Useful for introductions, demonstrations, and shared discussions
Visualiser or document camera to show small devices to the whole class
Limited hands-on time; risk of passive watching

Small-group rotations

Multiple activities running simultaneously; physical computing as one station
Children cycle through; each group gets hands-on time
Requires clear instructions at each station; often needs adult support

Pairs or threes

One device per 2-3 children
Encourages collaboration, discussion, peer teaching
Clear role rotation: programmer, tester, recorder

Individual work

Each child has a device (or each pair)
Maximum hands-on time
Requires sufficient resources; potential for isolation

The Sweet Spot: Pairs

For most primary classrooms, pairs work best:

Collaboration is built in
Resources stretch further
Children learn from each other
One can "drive" while the other "navigates"
Regular role swaps maintain engagement

Time Management¶

Physical computing sessions take longer than you might expect. Build in time for:

Setup: Getting devices out, checking they work, distributing materials (5-10 minutes)
Introduction: Explaining the task, reviewing relevant concepts, demonstrating (5-10 minutes)
Activity: The core hands-on time (20-40 minutes depending on task)
Reflection: Discussing what happened, what was learned, what was challenging (5-10 minutes)
Pack-away: Returning devices, tidying, checking nothing is missing (5-10 minutes)

A "quick 30-minute activity" often needs 45-50 minutes in reality. Plan accordingly.

Health and Safety¶

Physical computing is generally safe, but consider:

Small parts: Some kits have small components (choking hazard for youngest children)
Batteries: Teach safe handling; no licking! Watch for battery compartment access
Cables: Trip hazards; keep organised
Supervision: Floor robots moving around require attention
Hygiene: Devices pass through many hands; cleaning routines
Screen time: Balance physical computing with other activities

Inclusion and Accessibility¶

Physical computing should be accessible to all learners:

Motor difficulties: Consider button size, alternative input methods, partner support
Visual impairment: Sound-based feedback, high-contrast displays, tactile interfaces
Hearing impairment: Visual feedback, text instructions, buddy systems
Cognitive differences: Simpler tasks, step-by-step support, extended time
Diverse learners: Multiple entry points, choice in projects, varied outcomes

Tangible interfaces can be particularly inclusive—they don't require reading and work well for kinesthetic learners. Consider which tools work best for which learners.

Working Within Resource Constraints¶

What if you only have three Bee-Bots for a class of 25?

Rotation stations: Bee-Bot activity is one of five stations
Demonstration with participation: Show the class, invite children up to participate
Unplugged parallels: Paper-based Bee-Bot planning while waiting for the real thing
Loan and share: Negotiate sharing with other classes
Prioritise: Some topics particularly benefit; use devices for those

Limited resources don't mean no resources. Creative organisation extends what you have.

Five Routines That Make Sessions Run Smoothly

"Check and report": At session start, each pair checks their device works and reports any problems
"Freeze and focus": A signal (hand up, chime, phrase) for stopping and listening—essential when children are absorbed
"Park and share": At intervals, pause for pairs to share discoveries or problems
"Clean and count": At session end, clean devices and count to ensure nothing is missing
"What did you learn?": Never end without a brief reflection—even 2 minutes makes a difference

1.9 Assessment in Physical Computing Contexts¶

Traditional tests don't capture the kind of learning that happens when children program robots and build interactive projects. Physical computing develops process skills—how children approach problems, respond to failure, collaborate, and persist—that pencil-and-paper assessments miss entirely.

In physical computing, process often matters more than product. A child whose robot doesn't reach the goal but who shows systematic debugging and clear reasoning may have learned more than one whose robot succeeds by lucky guessing. This requires shifting focus from "Did it work?" to "How did they think?"

Your most powerful assessment tool is observation: watching how children plan, test, debug, and explain. Section 2.4 provides detailed formative assessment strategies, and Section 2.5 offers rubrics specifically designed for physical computing contexts. For now, the key principle is this: assess the thinking, not just the outcome.

Reflection Prompt

How do you currently assess hands-on, practical learning in your classroom? What strategies might transfer to physical computing?

1.10 Looking Ahead: Your Journey Through This Course¶

You've now explored the foundations of physical computing and its place in primary education. You understand what physical computing is, why it matters, how it connects to CT, and how it integrates across the curriculum. You've considered practical issues of classroom management and assessment.

Now it's time to get hands-on.

What's Coming Next¶

Section 2: Designing and Assessing Lessons

We'll establish the pedagogical frameworks you'll use throughout: low floor/high ceiling/wide walls, lesson structures, cross-curricular integration, formative assessment strategies, and planning for your fieldwork.

Section 3: Robots in the Classroom

We'll explore floor robots like Bee-Bot, Blue-Bot, Pro-Bot, and Thymio. You'll learn how these devices teach sequencing, debugging, and spatial reasoning—and how to integrate them into maths, literacy, and geography.

Section 4: Tangible Interfaces

We'll examine tools where programming happens through physical manipulation: Cubetto, TacTile Reader, Makey Makey, Osmo, and KIBO. These are particularly powerful for young children and tactile learners.

Section 5: Programmable Microcontrollers

We'll dive into the BBC micro:bit and Crumble. You'll explore sensors, data, and more complex programming—opening up science, design, and creative projects.

Section 6: Mechanical Logic Toys

We'll investigate tools like Turing Tumble, Gravity Maze, and GraviTrax that teach computational concepts through mechanical systems—no electricity required.

Section 7: Bringing It All Together

We'll step back and consider the bigger picture: building sustainable practice, supporting colleagues, and continuing your development.

Your Fieldwork and Reflective Diary¶

Throughout this course, you'll choose three different tools to try in your classroom, documenting your experiences in a reflective diary. Section 2.7 provides detailed guidance on planning your fieldwork, and Section 2.8 offers frameworks for reflective practice. For now, simply know that your fieldwork will be where theory meets reality—and where much of your professional learning will happen.

Embrace the Experiment¶

Here's a secret: things will go wrong. Devices won't charge. Programs won't work. Children will do unexpected things. This is not failure—it's learning.

The teachers who get the most from physical computing are those who embrace experimentation, model resilience, and learn alongside their students. You don't need to be an expert. You need to be curious, persistent, and willing to say, "I don't know—let's figure it out together."

Final Reflection Prompt

As you complete this first section, consider: What is one thing you're now excited to try? What is one thing you're still unsure about? Make a note of both—the excitement will fuel your learning, and the uncertainty will guide your questions.

Summary: Key Takeaways from Section 1¶

Physical computing brings CT to life by connecting programming to real objects that move, sense, and respond in the physical world.
The pedagogical case is strong: Embodied cognition, constructionism, immediate feedback, and motivation all support learning through physical computing.
CT concepts become concrete: Decomposition, pattern recognition, abstraction, and algorithms are visible and tangible when a robot enacts them.
Physical computing adds more: Design thinking, systems thinking, tinkering, creativity, collaboration, and real-world relevance.
Integration is essential: Physical computing should connect to mathematics, science, literacy, art, and other subjects—not exist in isolation.
Choose tools for learning purposes: Start with outcomes, then select the simplest tool that supports them.
Practical organisation matters: Managing resources, organising classrooms, and planning time are essential for success.
Assessment focuses on process: Observation, documentation, and formative strategies capture learning that tests miss.
Embrace experimentation: Things will go wrong, and that's where much of the learning happens.

Ready to continue? Head to Section 2: Designing and Assessing Lessons to establish the pedagogical frameworks you'll use throughout this course.

Home | References | Section 2 →