Skip to content
Technologies · Year 6

Active learning ideas

Introduction to Conditional Logic

Active learning works for conditional logic because students need to physically move through decision points to experience how ‘if-then-else’ structures branch responses. When learners embody the algorithm themselves, abstract true/false conditions become concrete outcomes they can see and feel, building lasting understanding.

ACARA Content DescriptionsAC9TDI6P02
15–30 minPairs → Whole Class3 activities

Activity 01

Role Play20 min · Whole Class

Role Play: The Human Algorithm

One student acts as the 'Programmer' while others act as 'Data Points' with different attributes like shirt color or height. The Programmer gives branching instructions such as 'If you are wearing blue, step left; else, step right' to sort the group into specific zones.

Explain how a program uses a condition to make a simple decision.

Facilitation TipDuring the Human Algorithm role-play, have students stand in a line and physically move left or right based on the spoken condition so everyone can see the split paths.

What to look forProvide students with a simple scenario, e.g., 'If the temperature is below 10 degrees Celsius, then wear a jacket, else wear a t-shirt.' Ask them to write one sentence explaining what happens if the temperature is 5 degrees and one sentence explaining what happens if the temperature is 20 degrees.

ApplyAnalyzeEvaluateSocial AwarenessSelf-Awareness
Generate Complete Lesson

Activity 02

Inquiry Circle30 min · Small Groups

Inquiry Circle: Logic Flowcharts

Small groups are given a real-world scenario, such as an automated gate at a National Park, and must draw a flowchart showing all possible decisions. They use sticky notes to represent 'if' conditions and 'else' outcomes, allowing them to easily move and refine their logic.

Compare the outcome of a program with and without a conditional statement.

Facilitation TipWhile creating Logic Flowcharts, circulate and ask each group to explain one arrow’s label to ensure the condition and actions are clearly paired.

What to look forPresent students with a short block of pseudocode or visual programming code that includes an 'if-then-else' statement. Ask them to identify the condition, the action if true, and the action if false. For example: 'IF score > 100 THEN display 'You win!' ELSE display 'Try again!'.

AnalyzeEvaluateCreateSelf-ManagementSelf-Awareness
Generate Complete Lesson

Activity 03

Think-Pair-Share15 min · Pairs

Think-Pair-Share: Edge Case Detection

Students look at a simple 'if-then' statement for a school canteen app and brainstorm what happens if a user enters unexpected data. They share their 'logic breaks' with a partner to discuss how an 'else' statement could fix the problem.

Design a simple program that responds differently based on user input.

Facilitation TipFor Think-Pair-Share edge cases, provide two contrasting examples so students must justify why one triggers the ‘if’ path and the other the ‘else’ path.

What to look forAsk students to describe a situation where a program might need to make a decision. Prompt them to explain what the condition would be and what actions the program might take based on that condition. For instance, 'How could a weather app decide whether to show a sun or cloud icon?'

UnderstandApplyAnalyzeSelf-AwarenessRelationship Skills
Generate Complete Lesson

A few notes on teaching this unit

Teachers should start with physical, low-stakes examples so students grasp that conditions are binary gates, not vague suggestions. Avoid rushing to code; instead, use everyday analogies like door policies or traffic lights to build schema. Research shows that students who act out logic before coding write fewer syntax errors and debug faster.

Successful learning looks like students confidently using ‘if-then-else’ to describe branching paths and explaining why the ‘else’ block runs for any unmatched case. They should also point out when separate ‘if’ statements check all conditions versus when an ‘if-else’ chain stops at the first match.


Watch Out for These Misconceptions

  • During Role Play: The Human Algorithm, watch for students who treat the ‘else’ path as an optional side route rather than the default when the ‘if’ is false.

    After the role-play, gather students and ask each pair to count how many classmates followed each path. Point to the larger group and say, ‘See how everyone who didn’t fit the rule went down the else road? That’s always the catch-all.’

  • During Collaborative Investigation: Logic Flowcharts, watch for students who draw separate ‘if’ bubbles instead of a single ‘if-else’ chain when only one condition needs to be checked.

    Hand each group a sticky note with the phrase ‘Stops here once true’ and ask them to place it on the first matching arrow to signal where the chain ends, reinforcing that only one branch runs.


Methods used in this brief