Why Systems Thinking Matters More Than Perfect Execution
I walked out of an exam recently thinking I'd completely bombed the math section. Three hours of manual calculations, no calculator allowed, working with decimals I hadn't touched in over ten years.
But walking through what actually happened revealed something more interesting than whether I got the answers right: it was about how I approached problems when the standard method wasn't working.
The Setup
Job assessment. Two full pages of manual math—multiplication with decimals, division, percentages, order of operations. No calculator. Just me, a pencil, and arithmetic I hadn't touched since discovering Excel and Python existed. 40+ problems. Results mattered.
The Innovation
15 minutes in, repetition was causing errors. Time to stop grinding and start strategizing.
Strategy 1: The Percentage Table
Instead of multiplying by 0.05 repeatedly, find 10% (move the decimal), then divide by 2. Built a reference table on scratch paper.
| Number (x) | 10% of x | 5% of x |
|---|---|---|
| 0.1 | 0.01 | 0.005 |
| 0.2 | 0.02 | 0.01 |
| ... | +0.01 each step | +0.005 each step |
| 1.0 | 0.1 | 0.05 |
This systematic approach meant I only had to move the decimal once, then halve the result. Way faster than multiplying by 0.05 repeatedly.
Example: Find 5% of 2,850
Step 1: Find 10%
$$2{,}850 \div 10 = 285.0$$Step 2: Divide by 2 to get 5%
$$285.0 \div 2 = 142.5$$Therefore: 5% of 2,850 = 142.5
Strategy 2: Place Value Breakdown
Break large multiplications into place values (thousands, hundreds, tens, ones), multiply separately, sum the results. Standard long multiplication, chosen strategically for control.
Example: 2,356 × 32.50
Break down 32.50 into place values:
$$32.50 = 30 + 2 + 0.50$$Multiply each part separately:
\begin{align} 2{,}356 \times 30 &= 70{,}680\\ 2{,}356 \times 2 &= 4{,}712\\ 2{,}356 \times 0.50 &= 1{,}178 \end{align}Sum all parts:
$$70{,}680 + 4{,}712 + 1{,}178 = 76{,}570$$Therefore: 2,356 × 32.50 = 76,570
These weren't memorized methods—they were solutions that emerged from trying to reduce friction during the exam.
The Teaching Moment
Midway through, I find out that the kid next to me was multiplying everything by 0.5 instead of 0.05 for the percentage problems—getting answers that were 10 times too large. I leaned over and quietly explained: "Hey, it should be 0.05. Here, think of it this way—if you use 100 as your baseline, 0.5 gives you 50, which is 50%, not 5%."
He still looked confused. So I pulled out my phone calculator to show him the comparison between 0.5 and 0.05—not to cheat, just to demonstrate the difference between 50% and 5%.
Demonstrating 0.5 vs 0.05:
$$100 \times 0.5 = 50 \text{ (that's 50%, not 5%)}$$ $$100 \times 0.05 = 5 \text{ (that's 5% ✓)}$$Then I gave him the shortcut: "Divide the whole number by 10 first, then by 2. That's how you get 5%." He asked me to calculate one for him, and I laughed—"Nah man, you gotta do it yourself"—and we both cracked up. But he had the tools now.
Bonus realization: Later I figured out his method could work too! If he multiplied by 0.5 then divided by 10, he'd get the right answer: \(n \times 0.5 \div 10 = n \times 0.05\). Multiple valid paths to the same destination.
What Actually Happened Here
This wasn't about math. It was systems thinking: pause, analyze friction, create frameworks, build shortcuts. Stepping back from grinding work to engineer better methods on the fly.
Teaching someone else confirmed understanding of underlying logic, not just memorized procedures.
The Real Lesson
Systems thinking isn't about perfection—it's about adaptation. Recognizing when to build a better process instead of grinding through a broken one. Understanding relationships well enough to create shortcuts and innovate under pressure.
The value wasn't in perfect arithmetic. It was in the problem-solving approach that applies everywhere: debugging code, optimizing workflows, navigating unexpected challenges.