Did you know that a beautiful flowchart can still give the wrong instruction? One little word—and instead of or—may send a student down the wrong branch. The problem is not the shape of the diamond. It is the logic hidden inside the question.
AND means every stated condition must be satisfied before a combined decision is true. OR, in ordinary inclusive computing logic, means at least one condition is satisfied; both may also be true. A dependable flowchart makes the conditions explicit, labels the Yes and No arrows, and tests the outcomes rather than trusting the drawing. Here is how to teach that skill.
Begin with the learner’s actual misunderstanding
Suppose a pupil says, ‘If either thing is true, I can follow the Yes arrow’ for every two-part diamond. That is a useful diagnostic. The learner may understand each condition separately but has not distinguished the logical relationship between them. Another pupil may understand AND and OR verbally but reverse the labels of the arrows when sketching.
Before adding computer code, ask four spoken questions: ‘What happens when both conditions are true? When only the first is true? When only the second is true? When neither is true?’ Those four answers reveal much more than asking a student to repeat the definition. Keep the people and data in examples fictional; the point is to practise reasoning, not to process real student permissions.
What the two operators actually do
Imagine a fictional outdoor sketching activity. Condition A: ‘The activity permission has been received.’ Condition B: ‘The pupil has the required sketching materials.’ Both facts are either Yes or No for the purpose of this simplified classroom exercise.
To decide whether the pupil is ready to start, use A AND B. A permission form alone does not supply drawing materials. Materials alone do not satisfy a permission requirement. Readiness means both are present.
To decide whether staff should check for something missing, use ‘permission is missing’ OR ‘materials are missing’. One missing requirement is enough to start a check. This OR is inclusive: if both requirements are missing, the check is still needed. The wording ‘one or the other but not both’ would mean something different, sometimes called exclusive OR.
A hand-checked four-case truth table
- Case 1: A = Yes, B = Yes. A AND B = Yes; A OR B = Yes.
- Case 2: A = Yes, B = No. A AND B = No; A OR B = Yes.
- Case 3: A = No, B = Yes. A AND B = No; A OR B = Yes.
- Case 4: A = No, B = No. A AND B = No; A OR B = No.
That is the whole table. Notice the disagreement in Cases 2 and 3. The quickest diagnostic for an AND-versus-OR confusion is often to test one true and one false. If both conditions are Yes or both are No, the operators produce the same answer and may conceal the misunderstanding.
Worked example: draw a route that students cannot misread
Here is a complete illustrative process, not an actual school’s safety or permissions policy. A student coordinator wants to identify participants who appear ready for a supervised sketching session. The coordinator has authority to check records but not to override permissions.
- Start: Check that you are looking at the correct fictional participant record.
- Diamond 1: ‘Permission recorded AND materials available?’ Label the outgoing arrows Yes and No.
- Yes branch: Mark ‘ready for teacher review’; do not equate a diagram with final adult authorisation.
- No branch: Ask ‘Is permission missing?’ If Yes, route to a permission follow-up. If No, route to a materials follow-up.
- Finish: End each route with a named next action rather than a vague ‘problem’.
Test the diagram with four fictional records: Asha (Yes, Yes), Ben (Yes, No), Cara (No, Yes), and Dev (No, No). Asha goes toward review. Ben goes to the materials follow-up. Cara goes to the permission follow-up. Dev goes to the permission follow-up and must also be flagged for missing materials. If your diagram gives Dev only one notice and loses the second missing condition, the later steps need another check. The initial AND question was correct, but the downstream process was incomplete.
This example exposes a second lesson: logical correctness is not the same as procedural completeness. A diamond can ask the right question while the rest of the flowchart silently drops useful information.
A compact way to draw and check every branch
Write each test as a full Yes-or-No question. Avoid a diamond containing only ‘Permission / materials’, because readers will not know whether the slash means both, either, or a choice between alternatives. Write the operator in ordinary language first; code comes later.
On paper, use one clear start symbol, a decision diamond for each Yes/No test, arrows labelled Yes and No, and action boxes that say what to do. Avoid crossing lines where possible, but never change the logical order merely to make the drawing symmetrical.
Now trace four coloured pencil routes or four separate pencil paths—one for every truth-table case. Read each action aloud. Is any participant incorrectly labelled ready? Does any route end without a next step? Can two people following the same recorded facts arrive at different outcomes? A flowchart that passes those checks is much more useful than one that only looks tidy.
Mistakes worth catching before an assessment or real project
- Using OR when all conditions are compulsory: A single Yes then incorrectly approves a case with one missing condition.
- Using AND when either reason should trigger help: The chart fails to catch a pupil missing only one required item.
- Assuming OR means exactly one: In inclusive logic, both Yes still satisfies A OR B.
- Leaving arrows unlabelled: Readers guess whether the left route means Yes.
- Negating only half a phrase: ‘Not (A AND B)’ means at least one condition is missing; it is not the same as ‘not A AND not B’.
- Testing only the easy case: Two true conditions do not distinguish AND from OR.
- Forgetting real-world authority: An educational diagram is not a substitute for verified supervision or consent requirements.
Practise from guided examples to independent transfer
Guided practice: the library return box
Two fictional conditions are A = ‘The book belongs to this library’ and B = ‘Its identifying label is readable’. Should the automated return scanner record a fully verified return only if both are true, or if either is true? Answer: AND. If only A is true, the item may still need manual verification. Ask the learner to explain why the single true condition is insufficient rather than accepting ‘because AND’ as an explanation.
Paired practice: the classroom help desk
A classroom poster says, ‘Ask for help if the printer does not respond OR the page appears blank.’ Have one pupil play each of the four cases and another trace the flowchart. An unresponsive printer with a visible test page still satisfies the OR condition; the system is reporting a possible problem, not proving the cause.
Independent challenge
Design a flowchart for a fictional project upload: a pupil may submit only when the file opens AND the name is present; if the file fails to open OR the name is absent, it returns a correction prompt. Trace all four combinations. Self-check: exactly one combination qualifies for submission; three require a correction. A complete solution also tells the learner which problem to fix.
Extend the challenge by asking whether a flowchart can identify two failures simultaneously without losing one of them. Students may add a second test or a single action that explicitly lists all missing conditions. There is no need to force every school process into a single diamond.
What learners, parents and teachers can do next
For a learner, the next step is to explain each Yes and No arrow without pointing at the answer key. For a parent, use two everyday checks—’homework complete’ and ‘packed for tomorrow’—but keep the stakes small and the examples kind. For a teacher, diagnose operators separately from drawing skill. A learner who can complete the truth table but cannot draw the route needs diagram practice; the learner who draws neatly but fails the mixed cases needs logical practice.
Progress can be observed in three short attempts: first, choosing AND or OR from a complete sentence; second, predicting the mixed truth-table cases; third, drawing and testing an unfamiliar decision process unaided. Record which stage is secure. A score is not promised, and practice should be adjusted to the learner rather than treating the illustration as an exam prescription.
Useful further reading
For related reasoning, compare testing the converse of an if–then statement with mathematical counterexamples. Follow the larger eduKateSG Education Hub for the learning pathway. The Clementi Secondary 1 Mathematics reference illustrates the diagnosis-first and independently checked practice on which this lesson builds.
Questions pupils often ask
Does OR always mean either but not both?
No. In standard inclusive Boolean logic, A OR B is true when A alone, B alone, or both are true. Natural language sometimes uses ‘or’ to mean an exclusive choice, so a well-written flowchart states the intended rule.
Should every decision be one diamond?
No. If a decision contains many independent conditions, a sequence of smaller diamonds may be easier to test and explain. The priority is a transparent, correct route.
Is a truthful table enough without the drawing?
It proves the operator has been evaluated correctly, not that the diagram’s actions and arrows are correct. You need both.
The learning worth keeping
Every useful decision system is a promise: given these stated facts, this is what we do next. The student who can say what AND and OR mean, test the awkward middle cases and follow every path has learned something more transferable than a drawing convention. They have learned to make a rule understandable enough for another person to check.