Hi, this is Ray.

I want to tell you about a specific moment when I finally understood what math had actually been teaching me. It was in my mid-thirties, and I was trying to figure out why a business project I was running kept underperforming. I'd been going in circles for weeks, trying different things, none of them working. Then I sat down and, almost automatically, started applying an approach that I now realize came directly from years of math work in my youth: I broke the problem into its component parts, identified what I knew and didn't know about each component, isolated the specific variable that was likely responsible, tested that specific variable in isolation, confirmed the hypothesis, and then addressed it directly. The problem resolved within a week.

What struck me afterward wasn't that the problem got solved. It was that I hadn't done any actual math. There were no equations. No numbers to speak of. What I'd done was apply the systematic decomposition and testing approach that math had drilled into me over years… but applied to a business problem that had nothing to do with math. The skill that solved the problem wasn't mathematical knowledge. It was mathematical thinking, transferred to a completely different domain.

This experience made me realize something the research has been trying to articulate for decades. When people ask "what's the point of learning math if I'm not going to use math in my career?" they're asking the wrong question. The value of math training isn't the specific math facts. It's a set of thinking habits that transfer to almost any complex problem you'll encounter for the rest of your life. Most people who did well in math absorbed these habits without realizing they had them. Most people who struggled with math missed these habits, often without realizing what they were missing.

Today's newsletter is about that. Not the abstract claim that math is useful, which I covered in a previous newsletter. The specific problem-solving habits that math training builds, how they transfer to non-math domains when you let them, and how to consciously apply them if you want to think more like a mathematician about problems that have nothing to do with numbers. Let's get into it.

AI is moving fast and most people are falling behind. 

The Rundown AI keeps you ahead of the curve. 

It's a free AI newsletter that keeps you up-to-date on the latest AI news, and teaches you how to apply it in just 5 minutes a day.

Plus, complete the quiz after signing up and they’ll recommend the best AI tools, guides, and courses — tailored to your needs.

Sign up to start learning.

Let me start with what the science has clarified about transfer of learning from math to other domains, because the honest picture is more specific than "math makes you smart."

According to comprehensive research on math transfer, two important aspects of transfer in mathematics learning are the application of mathematical knowledge to problem solving and the acquisition of more advanced concepts, both in mathematics and in other domains. But the research distinguishes between "near transfer" (applying math to closely related problems, like using algebra in physics) and "far transfer" (applying math thinking to unrelated domains, like using systematic decomposition in business problems). Near transfer happens fairly easily. Far transfer is harder… but not because it's impossible, but because it requires deliberate awareness of what you're transferring.

The research on transfer has been clear about this challenge. According to one analysis, far transfer is more difficult because students must deliberately analyze the situation in order to recall the rules or concepts that are needed to apply their knowledge and skill in that particular situation. Good and poor problem solvers differ in their recall of information from previously encountered problems and by extension their ability to transfer concepts to the target problem. Read this carefully. The transfer doesn't happen automatically. It requires deliberate recognition that a mathematical thinking pattern applies to the current problem. This is why some people who are great at math seem to think mathematically about everything, while others who are equally good at math don't. The difference isn't math ability. It's the habit of recognizing when math thinking applies.

A more recent longitudinal study made the mechanism clearer. According to the researchers, recent research on the covariation of mathematical literacy and reading achievement indicated that gains in ML-related skills such as problem-solving and reasoning as well as cognitive abilities in general lead to better achievement in other domains. The specific transferable skills the research identifies aren't math facts. They're problem-solving processes, reasoning patterns, and general cognitive abilities that math trains particularly well. These are the actual gifts math gives you if you can extract them from the specific content.

Let me name the specific problem-solving habits that math training develops. These are the things that transfer to non-math domains when you deliberately let them.

Decomposition into components. Math constantly requires breaking complex problems into simpler pieces you can actually solve. A big equation gets broken into steps. A word problem gets broken into what's known, what's unknown, and what relationships connect them. A proof gets broken into premises, logical steps, and conclusions. Over years of math work, this decomposition habit becomes automatic. And it applies to almost any complex problem… breaking a business challenge into components, breaking a relationship conflict into specific issues, breaking a creative project into manageable pieces. The habit of not staring at the whole overwhelming mess but instead breaking it down is one of math's most valuable exports.

Making implicit assumptions explicit. Math problems require you to identify exactly what you're assuming and check whether the assumptions are valid. In a proof, unstated assumptions produce errors. In word problems, misinterpreting the setup produces wrong answers. Over time, math trains you to notice your assumptions and articulate them. This transfers to almost any domain. The business plan that seems solid usually has hidden assumptions. The interpersonal disagreement usually involves different implicit assumptions on each side. The scientific claim usually rests on assumptions worth questioning. The habit of surfacing the implicit is genuinely valuable and math builds it reliably.

Working with abstract representations. Math constantly requires you to represent situations in abstract form… variables, equations, graphs. You strip away the specific details and work with the underlying structure. This habit of moving between concrete situations and abstract representations transfers powerfully. The business person who can see the abstract structure of a market dynamic beneath the specific competitive situation has an advantage. The scientist who can see the pattern beneath specific observations makes discoveries others miss. The engineer who can see the general problem beneath the specific case builds solutions that generalize. Math trains this movement between concrete and abstract, and once you have it, you use it everywhere.

Systematic verification. In math, you check your work. You verify each step. You plug the answer back into the original equation to confirm it works. Over years, this becomes a habit of not just doing something but checking whether what you did actually accomplished what you thought it did. This transfers to every domain where you can be wrong. The code you wrote might not actually do what you think. The argument you made might not actually support the conclusion. The decision you made might not actually achieve the goal. The habit of systematic verification, developed in math, catches errors in non-math domains that would otherwise go undetected.

Working backward from what you want. Math problems often require working backward from the answer to figure out the steps to get there. Given that you need to end up here, what must the previous step be? What must be true at each stage? This habit of goal-oriented reverse engineering transfers directly to strategic thinking. The person who can start from the desired outcome and work backward to identify the specific actions needed thinks differently from the person who can only work forward from current conditions. In Metroid, you don't just explore forward… you constantly check what upgrades you need to reach specific areas, and you work backward from those needs to plan your route. Math builds this kind of thinking systematically.

Precise definitions. In math, sloppy definitions produce broken proofs and wrong answers. You learn to specify exactly what you mean by a term. This transfers to almost every intellectual endeavor. Most disagreements are actually about definitions rather than substance. Most confused thinking comes from vague terminology. The person who insists on precise definitions before proceeding often solves problems others get stuck on because the others were arguing about words rather than things.

Recognizing pattern types. Math trains you to recognize when a new problem is actually structurally similar to a problem you've solved before. A quadratic equation is a quadratic equation whether it's about rockets or profits or population growth. This pattern recognition transfers to non-math problems too. The learner who has done a lot of math becomes attuned to recognizing that the current business problem is structurally similar to something they've handled before, or that this creative challenge has the same form as one they solved differently. The pattern recognition itself is transferable.

Comfort with not knowing yet. Math problems require you to work under conditions of uncertainty. You know the goal but you don't yet see the path. Over time, math trains you to be comfortable with this uncertainty… not to panic, not to abandon the problem, but to sit with the unknown and work systematically toward resolution. This transfers to every complex problem in life. The person who can hold uncertainty productively while working toward an answer has a genuine advantage over the person who needs immediate resolution.

Here's the question worth asking. If math builds these transferable skills, why do so many people who studied math not seem to have them? The research suggests a specific answer.

According to research on transfer, good and poor problem solvers differ in their recall of information from previously encountered problems and by extension their ability to transfer concepts to the target problem. The difference between people who transfer their math thinking and people who don't isn't mathematical ability. It's whether they've developed the meta-awareness of what they were actually learning when they learned math. The person who did math as a series of specific procedures to memorize doesn't transfer well. The person who did math as an approach to problems that could be applied broadly transfers everything.

This is genuinely good news if you're an adult wondering whether your math background produced these transferable skills. The answer partly depends on how you engaged with math. If you memorized procedures without thinking about the underlying approaches, you might not have absorbed the transferable habits. But you can develop them now, deliberately, as an adult. The habits don't require you to be doing math… they require you to recognize the situations where mathematical thinking applies and deliberately apply it.

Okay, the practical part. If you've realized that math thinking has more to offer than you've been extracting from it, here's how to consciously use it in domains that have nothing to do with numbers.

When facing a complex problem, decompose it. Before doing anything else, break the situation into its component parts. What's actually happening here? What are the pieces? Which pieces do I understand? Which pieces are unknown? What relationships connect the pieces? This decomposition alone often reveals what to do next. Sometimes the problem that seemed impossible dissolves into three or four component problems, several of which have obvious solutions.

Articulate your assumptions explicitly. For any problem you're working on, write down what you're assuming. "I'm assuming the market wants X." "I'm assuming she understood what I meant to say." "I'm assuming the current approach will scale." The act of articulating makes hidden assumptions visible, which lets you check them. Most complex problems fail because of a wrong assumption that never got surfaced. Making assumptions explicit prevents this specific failure mode.

Look for the abstract structure. When you're stuck on a specific problem, ask: what's the general form of this? Is this a coordination problem? An information problem? An incentive problem? A capacity problem? Recognizing the abstract structure often points at solutions that others have used for similar problems in different specific contexts. In Fire Emblem, you don't approach every battle map the same way… you identify the abstract structure (defense scenario, escape route, boss fight) and apply strategies suited to that structure. Same for non-math problems.

Verify what you think you've concluded. Whenever you reach a conclusion, check it. Does the evidence actually support what I'm concluding? Would this conclusion still hold under slightly different conditions? What would prove me wrong? This verification habit, borrowed from math, catches errors in thinking that would otherwise go undetected. The check takes a few minutes. The error it prevents can cost weeks or months.

Work backward from your actual goal. When you're planning something, don't just work forward from where you are. Start from where you want to end up and work backward. What must be true at the final step? What must be true at the step before that? Continue until you reach where you currently are. This reverse engineering often reveals steps you'd missed and clarifies the actual sequence of what needs to happen.

Insist on precise definitions. When you're discussing something with someone, or thinking about it yourself, pause to ask: what exactly do we mean by that? What does that word mean specifically in this context? Am I using it the same way you are? Most confused thinking dissolves when the terms get pinned down. Most persistent disagreements turn out to be definitional rather than substantive. The habit of insisting on precision, borrowed from math, cuts through a lot of noise.

Look for structural similarities to problems you've solved. When facing a new problem, ask: what have I solved before that has similar structure? Not the same content… the same abstract form. This transfer question is what turns each individual solved problem into a template for future problem-solving. The learner who does this deliberately gets better at problem-solving over time in a way the learner who treats each problem as new doesn't.

Sit with uncertainty productively. When you don't yet know the answer, don't force premature closure. Sit with the not-knowing while continuing to work systematically. The math habit of tolerating uncertainty while working toward resolution is genuinely valuable in complex real-world problems where premature answers produce worse outcomes than sustained inquiry.

Here's what I want you to take from all this. Math is often defended as useful because it teaches abstract thinking, and that's true, but the framing is often too vague to be actionable. What math actually teaches, when you engage with it deeply, is a specific set of problem-solving habits that transfer to almost any complex challenge. Decomposition. Making assumptions explicit. Abstract representation. Systematic verification. Working backward from goals. Precise definitions. Pattern recognition. Comfort with uncertainty.

These habits aren't automatically transferred by having taken math courses. They're transferred by having engaged with math as an approach to problems, and then by deliberately applying that approach outside of math contexts. The learner who does this becomes measurably better at solving complex problems in domains that have nothing to do with numbers, because the underlying thinking habits are actually general.

If you've absorbed some math training in your life but haven't been consciously applying its methods to non-math problems, please consider that you might have more resources available than you've been using. The next time you face a business problem, a relationship challenge, a strategic decision, a creative block… try consciously applying mathematical thinking. Decompose the problem. Articulate your assumptions. Look for the abstract structure. Work backward from your goal. Verify each step. See what happens.

You don't have to solve equations to think like a mathematician. The equations were just the training. The thinking is the point. And the thinking transfers to everywhere it's needed if you let it.

In Persona 5, Joker doesn't just fight with his personas… he uses their specific abilities in situations that require them, calling up Ann for fire enemies, Ryuji for physical situations, whoever fits the current challenge. Your math training is like a persona. You don't have to use it constantly. But when you face a problem where systematic decomposition, precise definition, or careful verification would help… call it up. Use what you have. The training was for this moment, not just for math class.

Keep learning (and keep applying),

Ray