When we name the steps, we can see what's actually happening when we solve problems. Naming what we're doing turns what feels like intuition into a checklist. And when we know what we need to do, we can get better at it. It's not just a matter of "getting math" or not, it's about building specific skills you can practice.
If we solve a problem by "just figuring it out" and we get it wrong, we don’t know why. But if we get stuck, and use our checklist, we can self-diagnose. For example:
◆ CHOOSE: Did I break the problem down into smaller pieces?
◆ REFLECT: Did I try to represent ithe problem differently (maybe drawing a picture)
◆ DEBUG: Did I check my work another way?
In the RoboTrig Project, we are constantly switching between three major skill sets. If you get stuck, the first step to getting unstuck is identifying which skill you are trying to use.
When you hit a wall, the first thing you can do is try to self-diagnose the problem. Stop and name the skill you’re working on to find ways to improve.
Skill Gap: ○ Mathematical Modeling & ◆ Computational Thinking (○ MODEL + ◆ CHOOSE)
Fix: Look at your diagram. Is it a Right Triangle (SOH CAH TOA) or an Oblique Triangle (Law of Sines/Cosines)? The shape tells you which tool to choose.
Skill Gap: ◆ Computational Thinking (◆ REPRESENT + ◆ PATTERN).
Fix: You are trying to solve too much at once. Break it down. Can you REPRESENT this as two simpler triangles? Look for PATTERNS. Are you repeating the same calculation?.
Skill Gap: ◆ Computational Thinking (◆ DEBUG + ◆ TEST).
Fix: Don't trust the algebra blindly. DEBUG by working backwards. If you plug your answer into the Forward Kinematics formula, does it equal the target (x,y)? TEST your prediction against reality.
Skill Gap: ★ Problem Solving (★ DESIGN + ★ REFRAME).
Fix: Step back. What does the user actually need? REFRAME the problem: Instead of “calculate the angle,” ask “What should the robot do?” Then DESIGN a plan before diving into the math.
Skill Gap: ○ Mathematical Modeling (○ LIMITS + ○ REFINE).
Fix: Your math might be correct, but your model has LIMITS (gravity, friction, mechanical slack, etc.). These create gaps between “perfect math” and reality. REFINE by adding minor corrections.
Every skill has four levels. You're not scored, you're growing.
EMERGING
I see the pieces
DEVELOPING
I see the connections
PROFICIENT
I understand the system
APPLYING
I can optimize the system
Think of it like leveling up. You're not "failing" at a task if you’re Level 2. You're at Level 2, working toward Level 3. The goal isn't to rush to Level 4. It's about understanding what you are currently struggling with so you can figure out how to get better or solve the problem!
Experts don't walk around reciting these lists. They do it automatically. But they didn't start that way. By naming these skills now, we track what we are getting faster at. Eventually, you won't need the names; you will just be a thinker who knows how to apply these skills across disciplines.