Error Lab Slides Top Secret
Math Detective
Agency
Case File #01: Categorizing the Culprits
The Autocorrect Fail
Message Sent:
"I'll be there in 5 minutes. I'm just putting on my **shoes**."
What Autocorrect Sent:
"I'll be there in 5 minutes. I'm just putting on my **soup**."
Was this a "Typing Slip" or a "Wrong Word Choice"?
The Usual Suspects
Silly Slips
Simple calculation errors. You know how to do it, but your brain moved faster than your pencil!
"2 + 3 = 6"
Process Puzzles
Skipping a step or using the wrong operation. The "How" went wrong.
"Forgot to regroup"
Logic Loops
Not understanding the rule or concept. The "Why" is confusing.
"1/2 + 1/2 = 2/4"
Mission Briefing
We aren't solving the problems yet. We are Profiling the Error . Your job is to label the crime:
Slip, Puzzle, or Loop?
Open Your Evidence Logs
Evidence Category Worksheet Evidence Category Log
Detective Unit: Case File #01 - Error Profiling
Detective Name
Badge Number (Date)
Silly Slip
Calculation error. Brain moved too fast.
Process Puzzle
Skipped a step or used the wrong rule.
Logic Loop
Confused about the concept or idea.
Suspect Files
Exhibit A: Multi-Digit Addition FILE #4492
458
712
Culprit Profile:
Silly Slip (Calculation)
Process Puzzle (Regrouping)
Logic Loop (Concept)
Detective's Reasoning:
Exhibit B: Fraction Comparison FILE #2281
Is \(\frac{1}{2}\) or \(\frac{1}{4}\) bigger?
"\(\frac{1}{4}\) is bigger because 4 is bigger than 2."
Culprit Profile:
Silly Slip (Calculation)
Process Puzzle (Steps)
Logic Loop (Concept)
Detective's Reasoning:
Exhibit C: Long Division FILE #9903
14 4 ) 564
16
0
Culprit Profile:
Silly Slip (Calculation)
Process Puzzle (Dropped Step)
Logic Loop (Concept)
Detective's Reasoning:
Error Lab Teacher Guide Facilitator Field Guide
Lesson 1: Categorizing the Culprits
DEPT: MATH DETECTIVES
Objective
Students will shift their focus from "getting the right answer" to "analyzing the wrong one." By categorizing errors into three distinct profiles, students with learning disabilities gain a concrete vocabulary for self-correction.
Teaching Tips
1
Avoid 'Wrong Answer' Shame
The "Math Detective" persona is vital. We are investigators looking for clues, not judges. Use phrases like "The culprit left a trace here" or "The logic loop is tripping us up."
2
Emphasize 'Silly Slips' are Normal
Normalize slips. Even expert mathematicians make them. The goal is detection, not perfection. This reduces anxiety for students who struggle with working memory.
3
Scaffold Logic Loops
These are often the hardest to spot because the student thinks they are following a rule. Focus on visual representations (like fraction bars) to 'break' the loop.
The Culprit Profiles
Silly Slip
Calculation, copying numbers wrong, basic facts.
Process Puzzle
Steps, algorithm order, regrouping, forgetting a zero.
Logic Loop
Misunderstanding the core concept (e.g., area vs. perimeter).
Case Key
Exhibit A: Process Puzzle (Regrouping). 8+4 is 12, they put the 2 but didn't carry the 10.Exhibit B: Logic Loop (Fractions). Comparing whole numbers instead of the part of a whole.Exhibit C: Process Puzzle (Dropped Step). Forgot to bring down the final 4 and divide it.
Questioning Strategy
To identify the error:
"If you were the student, what part would you feel most confident about?"
"Where did the numbers start to look different than we expected?"
"Is the answer reasonable (estimation check)?"
To categorize the error:
"Did they know the rule but just trip over a number (Slip)?"
"Did they follow the steps in the wrong order (Puzzle)?"
"Did they use a rule that belongs to a different kind of math (Loop)?"
Trace Breakdown Slides Phase 02
Trace the
Breakdown
"To find where the path ends, you must see where the path turned."
The Dead End Challenge
In a maze, we often find a dead end . We don't just give up. We backtrack .
Detective Goal:
Identify the specific "wrong turn" where the math logic left the path.
If you go backwards from the finish line, you'll see the exact point where it all went wrong.
X MARKS THE
The Reverse-Trace Strategy
1
Check the Answer
Is it reasonable? Is it way off?
2
Backtrack One Step
Did the last operation make sense?
3
Spot the Slip
Find the first moment the math changed.
"Math is like a domino chain. If the third domino falls wrong, we check the second one."
Tracing the Path
Today's missions involve multi-step word problems. You will be given a completed but incorrect solution. Your job: Pinpoint the exact line where it all went south.
Reverse Maze Activity Reverse Maze Analysis
Mission Code
BACKTRACK-55
Lead Investigator
Time Log (Date)
Mission: Start at the final answer and work your way up. Find the first line where the math is incorrect. Draw a giant X over the mistake!
Case #1: The Orchard Harvest TYPE: Multi-Step
Problem Statement
"Maya picked 45 apples and 27 pears. She wants to put them into bags of 9. How many bags does she need?"
The Suspect's Solution
Line 1: 45 + 27 = 62
Line 2: 62 ÷ 9 = 6 R 8
Answer: 7 bags
Backtrack Findings
What was the first mistake you found?
The Correction
Fix the mistake and find the real path.
Case #2: Soccer Team Pizza TYPE: Fraction Logic
Problem Statement
"The team ate \(2\frac{1}{2}\) pizzas for lunch and \(1\frac{3}{4}\) pizzas for dinner. How much did they eat in total?"
The Suspect's Solution
Line 1: \(2 + 1 = 3\)
Line 2: \(\frac{1}{2} + \frac{3}{4} = \frac{4}{6}\)
Answer: \(3\frac{4}{6}\) or \(3\frac{2}{3}\)
Backtrack Findings
Where did the logic go off track?
The Correction
Calculate the true total below.
Evidence must be verified by the Lead Detective
Trace Breakdown Teacher Guide Trace Breakdown Guide
Lesson 2: Reverse Engineering Strategy
PHASE: INVESTIGATION
The Logic
Students with executive functioning challenges often look at a whole problem and feel overwhelmed. Working backward (backtracking) creates a manageable "check" on each step. It prevents them from assuming the whole thing is wrong if only one part is flawed.
Facilitation Steps
Visual Scaffolding
Have students physically cover up lines with a piece of paper, revealing them one at a time from bottom to top. This forces the "reverse" perspective.
The "How did they get there?" Question
Ask: "To get to Line 2, what math did they do to Line 1?" If the student can't explain the connection, that's usually where the 'wrong turn' happened.
Mission Key
Case #1
Error: Line 1 (45+27 is 72, not 62).Reasoning: A 'Silly Slip' in basic addition threw off the whole division step.
Case #2
Error: Line 2 (Adding numerators and denominators).Reasoning: A 'Logic Loop'. They treated fractions like whole numbers.
Support Tip
For students who struggle with reading, read the problem aloud but do NOT read the solution steps. Let them "see" the math steps visually to avoid auditory overload.
Common Roadblocks
Student says "It's all wrong."
Encourage them to find one single number that *is* correct. Usually, the first line is right. Build confidence from the start.
Student fixes the math but can't name the error.
Use the categorizing tools from Lesson 1. "Was that wrong turn a Slip or a Loop?"
Favorite No Slides Case #03
My Favorite
"No"
"Every mistake is a beautiful opportunity to see how our brains work."
The "Smart" Part of a Mistake
PROBLEM: 0.5 + 0.08
0.13
Wait! Why is this a "smart" mistake?
They knew 5 + 8 = 13!
They knew decimals go in front!
Mistakes = Proof you are trying!
The Mindset Flip
Fixed View
"I'm bad at math because I got this wrong. I should hide my work."
Detective View
"I almost had it! My brain followed a logical path, but I hit a 'Loop'. Let's find it!"
Workshop Mission
We will look at one common error. First, we will name everything the student did right . Then, we will find the one "No" that makes it incorrect.
Let's Find Your Favorite "No"!
Favorite No Reflection The "Smart Part" Lab
Metacognitive Case File #03
FAVORITE NO
Detective Name
Time Log
MISSION PROTOCOL
Don't look for what is wrong yet! Look for the smart parts . What did this student do that shows they understand math? Then, circle the "No" (the mistake).
EXHIBIT A
The Mistake
12.45
+ 3.2
12.77
THE SMART PARTS
They knew to add the whole numbers together.
They added the columns (5+2=7 and 4+3=7) correctly!
So, where is the "No"?
EXHIBIT B
The Mistake
\(\frac{1}{3} + \frac{1}{3}\)
\(\frac{2}{6}\)
THE SMART PARTS
They knew adding means the numbers should get bigger.
They knew \(1 + 1 = 2\) and \(3 + 3 = 6\).
So, where is the "No"?
Personal Mission Report
"Think about a 'No' you made recently. What was the smart part of your mistake?"
Favorite No Teacher Guide The "No" Strategy Guide
Lesson 3: Growth Mindset & Conceptual Analysis
Status: Empowered
The Metacognitive Goal
The "My Favorite No" strategy is designed to decouple effort from accuracy . By validating the student's logical process before addressing the error, we lower the "affective filter" (stress) and make them more receptive to learning the correct concept.
Workshop Facilitation
Protect the Student
When using actual student work, always copy it onto the board in your own handwriting to maintain anonymity. This prevents the student from feeling singled out.
Wait Time is Crucial
Give students at least 30 seconds to find the 'smart part'. For students with slower processing speeds, this 'positive first' approach builds confidence they often lack.
Common "Smart" Mistakes
Alignment Error
Smart: Knows how to add numbers. No: Doesn't understand place value (decimal alignment).
The 'Whole' Rule
Smart: Knows the rule for whole number addition. No: Generalizes the rule to fractions improperly.
Growth Prompts
"If I was your brain, why would I have thought that was a good idea?"
"What part of this mistake shows that you are getting closer to the answer?"
Case Analysis Key
Exhibit A (Decimal Addition):
The "No" is Place Value Alignment . The student added left-to-right without lining up the decimals. The smart part is the arithmetic (12+3=15 or in this case they added the 3 to the 4).
Exhibit B (Fraction Addition):
The "No" is Denominators . The student added denominators as if they were whole numbers. The smart part is knowing that addition increases the total count.
Algorithm Debuggers Slides System Loading...
Algorithm
Debuggers
ERROR DETECTED // UNIT #04
The "Bug" in the Code
Computers follow algorithms (step-by-step rules). If one line of code is wrong, the whole program crashes.
Math is an Algorithm!
Long division and double-digit multiplication are just "code" for our pencils. Today, you are the Quality Control Inspectors.
IF (step == divide) {
find_multiple();
subtract();
bring_down(apple); // BUG FOUND!
}
// Should have been bring_down(number);
The QC Checklist
Alignment
Are the columns lined up by place value?
The Drop
Did you bring down the next number in division?
Carry/Borrow
Did you regroup and remember the extra digit?
Zero Place
Did you add the 'placeholder zero' in multiplication?
Inspect the Batch
You are now in Quality Control . Put on your badges and use your checklists to find the defective code in these long division and multiplication problems.
$ sudo run debugging_lab.exe
Debugging Lab Worksheet QC Inspection Lab
Algorithm Debugging Unit // System Check: 5.0
Inspector Name
Batch # (Date)
Check 1
ALIGNMENT: Are the columns straight?
Check 2
THE DROP: Did you bring down the next digit?
Check 3
REGROUP: Did you carry/borrow correctly?
Check 4
ZERO: Is the placeholder in Row 2?
SYSTEM ERROR #401
42
126
168
Inspection Report
Bug Found:
Alignment Problem
Missing Placeholder Zero
Calculation Slip (3 × 2)
Debugging Code (Fixed Version):
SYSTEM ERROR #402
24 R 3
23
3
Inspection Report
Bug Found:
Alignment Problem (Quotient)
Missing 'The Drop' Step
Calculation Slip (12 - 10)
Debugging Code (Fixed Version):
[ SYSTEM SCAN COMPLETE // ALL BUGS MUST BE CORRECTED BEFORE FINAL COMPILE ]
Algorithm Debuggers Teacher Guide System Debugging Guide
Lesson 4: Algorithmic Checklists
MODE: QUALITY CONTROL
The Procedural Strategy
Students with learning disabilities often struggle with the sequential steps of long algorithms. By framing these steps as a "Debugging Checklist," we externalize the executive functioning required to hold multiple steps in working memory.
Teaching Tactics
Physical Check-Off
Encourage students to physically check off each item on their list for every single problem. This habit-building reduces "Silly Slips" significantly.
The Programmer Persona
If a student gets frustrated, lean into the persona: "The system has a bug! It's not your fault, we just need to find the line of code that's broken."
The "Bug" Key
Case #401
Bug: Missing Placeholder Zero.
Case #402
Bug: Alignment.
Differentiation
For students with dysgraphia, provide a template with pre-drawn grid lines to ensure alignment before they even start the debugging process.
Debrief Questions
"Which 'bug' was the hardest to find today?"
"Why do you think computer programmers use checklists like this?"
Personal Case Files Slides Final Phase
Personal Case
Files
"Becoming your own best detective."
Reviewing Your Evidence
Over the last 4 missions, you've found mistakes in other people's work. Now, it's time to look in the mirror .
Slips
Do you often rush and miss small facts?
Puzzles
Do you often skip steps in long algorithms?
Loops
Do you often get confused by specific rules?
The "Watch-List"
My Top 3 Culprits:
Forgetting to regroup
Adding decimals wrong
Rushing through addition
A Watch-List is a personal guide. You check it before you say "I'm finished."
"I am not my mistakes. I am a detective who catches them!"
Graduation Day
You are ready to create your Detective's Field Manual . This personal guide will help you solve every math case that comes your way.
Seal Your Personal Case File
Field Manual Project Detective's Field Manual
Metacognitive Self-Correction Guide
MASTER DETECTIVE
Investigator Identity
"I use my metacognitive skills to catch errors before they escape the lab."
My Top 3 Suspects
Which errors do I make most often?
1
Example: "Rushing my basic addition facts"
2
3
MY CATCH-PHRASE
Write a reminder to your future self when you feel stuck.
The "Before I'm Done" Checklist
The Estimation Check
"Does my answer actually make sense?"
The Backtrack
"Can I explain how I got from Step 1 to Step 2?"
The Alignment Inspect
"Are my numbers standing in neat rows?"
Detective's Oath
"I will not be afraid of the red pen. I will use every 'No' to find my way to a 'Yes'."
Signature of Master Detective
Certified Math Detective
Personal Case Files Teacher Guide Personal Case Files Guide
Lesson 5: Self-Regulation & Mastery
PHASE: GRADUATION
The Culmination
The goal of this final lesson is to transition from teacher-led error analysis to student-led self-regulation. By identifying their own "Top 3 Suspects," students internalize the metacognitive prompts they've practiced, reducing the need for external prompts over time.
Coaching the "Watch-List"
Review Past Work
Provide students with a folder of their own corrected work from the past few weeks. Have them look for patterns. "Do you see the same 'bug' appearing in multiple places?"
Drafting the Prompt
Help students write prompts that are actionable. Instead of "Don't be messy," suggest "Check that my 7 doesn't look like a 1."
Teacher Role
In this phase, you are a Coach . Your role is to help students name their patterns without judgment.
"I noticed on your last three quizzes that you knew the math, but the regrouping was a little tricky. Should we add 'Check the Regroup' to your Watch-List?"
Graduation Idea
Print the finished Field Manuals and laminate them. Tape them to the student's desk as a permanent reference for all future math lessons.
Maintenance Phase
Weekly Check-Ins
Once a week, have students look at their Field Manual and ask: "Is Suspect #1 still a problem, or have you 'arrested' that bug?"
Updating the List
As math topics change (e.g., from fractions to geometry), encourage students to update their Field Manual with new suspects.
