60149558_visual-thinking cover
Psychology

60149558_visual-thinking

by Temple Grandin

13 min read
5 key ideas

The engineers who could prevent bridge collapses and plane crashes are being screened out by a word-first culture that mistakes visual thinking for low…

In Brief

The engineers who could prevent bridge collapses and plane crashes are being screened out by a word-first culture that mistakes visual thinking for low intelligence. Temple Grandin reveals how object and spatial thinkers see physical failures before they happen — and why ignoring them costs lives.

Key Ideas

1.

Match evaluation to thinking mode

When evaluating someone's ability — a student, a job candidate, an employee — ask not 'how smart are they?' but 'which mode do they think in?' Verbal, object-visual, and spatial-visual thinkers each excel at fundamentally different tasks, and mismatching the person to the role wastes talent that looks like failure.

2.

Abstraction barriers mask mathematical talent

If you struggled with algebra but succeeded at geometry, statistics, or anything with a physical correlate, you were probably an object visualizer hitting the wrong kind of math — not someone bad at math. The barrier was the abstraction, not the subject.

3.

Include hands-on evaluation in hiring

When hiring for safety-critical, manufacturing, or design roles, include a hands-on or visual component in your evaluation. The person who can walk through a physical system in their head and spot the fragile single point will not necessarily distinguish themselves on a standardized test.

4.

Cognitive diversity beats pure expertise

Mixed teams of object visualizers (designers, mechanics, craftspeople) and spatial visualizers (mathematicians, coders, physicists) consistently outperform homogeneous expert groups on complex physical problems. Building one without the other produces either a beautiful idea with no path to reality, or a rigorous system no one can actually build.

5.

Object visualizers spot failure points

Single points of failure in engineered systems — one sensor, one generator, one decision-maker with no hands-on experience — are visible to object visualizers before disasters occur. In safety reviews and design audits, explicitly ask: who in this room can picture what happens when this specific component fails?

Who Should Read This

Curious readers interested in Cognitive Psychology and Neuroscience and the science of how the mind actually works.

Visual Thinking

By Temple Grandin

9 min read

Why does it matter? Because the minds being screened out of schools are the same ones keeping physical reality from falling apart.

You've been sorting people wrong your whole life. Two bins: good at school, or not. It feels accurate — it matches what you observe. What it can't explain is why American factories run on Dutch equipment. Why a brand-new Boeing fell from the sky while a room full of engineers reviewed their data. Why the nuclear plant that survived a 50-foot tsunami did so because one superintendent spent 29 years learning every pump and cable by sight.

Temple Grandin thinks in pictures — not metaphorically, but photographically, before language arrives. That's a cognitive mode as distinct as reading music or solving for x. This book replaces your two-bin system with three: verbal, object-visual, spatial-visual. The moment you have that map, the disasters stop looking like bad luck — and America's industrial decline stops looking like a mystery.

The Three-Way Map of Intelligence Schools Don't Teach

A group of middle and high schoolers sits down with a single instruction: draw an unknown planet. No other guidance.

The art students produced planets that had no business being planets. One was square, its surface crowded with pyramids and penguins. Another was crystalline. A third had a massive building jutting from it like an antenna.

The science students drew spheres. Gray, colorless spheres. They cared less about appearance than about what their planet did: its gravity, chemistry, the conditions that might support life.

The humanities students made splotchy abstract paintings. Most had written words on their drawings first, then painted over them. They assumed words were off-limits.

One prompt. Three completely different minds.

Maria Kozhevnikov named what the drawings showed: two types of visual thinker, genuinely distinct. Object visualizers, like the art students, think in photorealistic images. They're the designers, mechanics, architects, and inventors who see a thing whole before they can explain it in parts. Spatial visualizers, like the science students, think in patterns: mathematics, code, physics, the invisible structure underneath. Verbal thinkers, like the humanities students, work primarily through language and sequence.

She tested students across fine arts, engineering, and psychology, and not one excelled at both object and spatial visualization. The two modes are separate instruments. Her conclusion: someone who maxed out both would be a supergenius. A Mozart who also built the rockets.

You've been given one axis — smart or not smart, verbal or visual. The three-way map makes that look flat. The student who fails algebra but can look at a machine and immediately see why it will fail isn't behind. She's built to read a different set of signals. The engineer who writes flawless code but can't explain how a chute works for a nervous animal — same story, other direction. Different modes, different blind spots, different gifts. Once you see the map, you start recognizing people everywhere. Probably including yourself.

Algebra Is Not a Math Requirement — It's a Screening Device

Temple Grandin knew fractions before she knew she was a visual thinker. A pizza cut into eight pieces made sense: she could see the ratio, hold the pieces in her mind, move them around. In fourth grade, she worked with protractors and angles. Concrete, spatial, satisfying. Later, she taught herself trigonometry by picturing the cables on a suspension bridge: the angle of the tension, the geometry made visible in steel. When she needed statistics for her PhD, she invented her own system — each test mapped to a cattle trial she could picture, real animals, real feed, real weight gain.

Then came algebra. Symbols standing for unknowns, operations performed without any image to anchor them. Her teachers tried to drill it in. It didn't work. There was nothing to see. And because algebra blocked the path, it blocked everything behind it. She dropped physics. She dropped biomedical engineering. The hard science and engineering tracks required the math she couldn't access. She wasn't screened out because she couldn't think mathematically. She was screened out because schools had decided that one specific flavor of mathematical thinking was the one that counted.

Andrew Hacker found that algebra is the single most-cited reason students don't finish high school. Nearly 60 percent of community college students land in remedial math, more than twice the rate who need remedial English. Christopher Edley Jr. looked at California's numbers: of 170,000 community college students placed in remedial math, more than 110,000 would never complete their degree. When California State tried replacing the algebra requirement with a statistics track, completion rates went up immediately. The fix was that simple and that obvious.

What algebra selects for isn't mathematical ability. It's a specific cognitive style: the capacity to reason through pure abstraction, untethered from anything physical or visual. Object visualizers, the people who see how machinery fails before it does, who design the infrastructure and build the chutes, hit this wall not because they lack mathematical minds but because their math runs through concrete reality, not symbolic manipulation. The credential disappears. They leave without the degree. The algebra grade sits in the file. Nobody records what they could have built.

We Don't Make It Anymore

Those missing degrees add up to a missing workforce.

She was standing on a catwalk at a pork-processing plant in 2019 — new equipment gleaming below, stainless steel, every moving part tight and precise — when something stopped her. Grandin knew this kind of work. She'd spent decades alongside the people who built equipment like this. Then she found out where it came from: the Netherlands, shipped over in more than a hundred containers.

The thought wouldn't let go: we don't make this anymore.

Months later, researching the Steve Jobs Theater at Apple's Cupertino campus, she found the same story at higher altitude. Walls of glass, twenty-two feet high, the roof floating without a single support column, wiring invisible inside the seams. The glass came from Germany. The carbon-fiber roof from Dubai. The entire installation from an Italian firm. A $3 trillion company's signature building, assembled from parts the United States no longer makes.

These weren't exceptions. They were a pattern with a cause.

Most people trace the decline to boardrooms: labor costs, trade deals, quarterly returns. Grandin sees something upstream. You need a workforce before you can make anything, and the pipeline that built mechanical America was severed a generation ago, quietly, inside schools. Shop class. Welding. Drafting. Auto mechanics. Those courses didn't disappear because students stopped needing them. They were cut because the people running schools had decided what real learning looked like, and it wasn't that.

The kids who would have thrived in those rooms, the ones who understood machines before they could explain them in words, were labeled poor performers and funneled out. Grandin's two eureka moments aren't about globalization. They're about a workforce that never got built. The equipment didn't get made in the Netherlands because Dutch labor is cheaper. It got made there because the Netherlands kept the training pathways that turn visual thinkers into engineers.

The Crash Was Visible Before It Happened

The day after Lion Air Flight 610 killed 189 people off the coast of Indonesia, Temple Grandin stood at a podium at Oakland University and told her audience: "Boeing is going to be in deep poo-poo." No investigation had opened. No cause had been named. She had spent the previous evening on Flightradar24 (a public flight-tracking site), looking at the dead plane's altitude trace. A healthy climb shows a smooth, steady upward line. This one looked like a heart monitor: jagged peaks and valleys as the plane fought something on the way down. No pilot does that voluntarily. Her mind ran through pictures: brand-new aircraft, barely a year and a half in service, altitude swinging wildly after takeoff. She focused on a news photograph of a sensor, a device about the size of a permanent marker, mounted below the cockpit window to measure the angle of flight relative to wind. Her conclusion arrived in pictures, before any official data: the sensor was broken, and the broken sensor was connected to something the pilots hadn't been told about.

She was right. To match Airbus on fuel efficiency without a new airframe (slow, expensive), Boeing bolted larger engines onto an existing 737 body. The engines were wide enough to generate lift on their own, pushing the nose toward a stall. To compensate, Boeing wrote software called MCAS that pushed the nose back down. The system relied on a single fragile sensor. When that sensor malfunctioned, MCAS concluded the plane was stalling and drove the nose toward the ground. The pilots pulled back. MCAS drove down again. Boeing had never told pilots the system existed or put it in the flight manual — too minor to mention, they decided. On Lion Air 610, the sensor had come from a dealer nicknamed "Cockroach Corner." Both pilots fought the computer to the end. Neither knew what they were fighting.

Five months later, an Ethiopian Airlines 737 MAX dove into a field at nearly 700 miles per hour. Wreckage was buried 30 feet underground. Across both crashes: 346 dead. The inverse had already played out in Japan.

The disaster was visible before it happened, not to the people who built the system or to management racing to match Airbus, but to anyone who could read a jagged altitude trace. The missing piece wasn't data. It was a mind that thinks in pictures of moving things.

Six miles separated two Japanese nuclear plants struck by the same 50-foot tsunami in 2011. One melted down. The other didn't. The difference was a site superintendent named Naohiro Masuda, with 29 years at nuclear plants, who knew every pump and cable by sight, not by manual. When the tsunami knocked out power, Masuda knew immediately what he had to work with. He dispatched his workers to lay miles of heavy electrical cable by hand, connecting the one surviving generator to the cooling pumps. His team called them "giant extension cords." He was on the ground beside them. He shared all damage information as it came in and gave workers one clear goal: cold shutdown. His counterpart at the melting plant six miles away watched the disaster on television from a remote emergency center. The math on both plants was identical. The eyes weren't.

Neither Mind Alone Can Build the Future

In a loft above a trolley car repair shop in Springfield, Massachusetts, four men spent years debugging a device that refused to behave. Some days it worked. Other days it failed for no apparent reason. The device was a magnetic direction finder for airplane autopilots, and cracking why it kept misfiring would take most of the 1930s.

The man who'd conceived it, Haig Antranikian, had been rejected by every airplane instrument manufacturer in the country. He held a 1936 patent and had nowhere to take it. Then he met John C. Purves, Grandin's grandfather, an MIT-trained civil and mechanical engineer. Purves studied the patent and said the thing Antranikian had been waiting to hear: "He had the concept, but he didn't know what to do with it. I saw how to make it work."

Antranikian had designed a device that read the earth's magnetic field from coils in a plane's wing, an approach every manufacturer had dismissed. Purves could engineer it into reality. The failures finally gave up their secret: massive steel trains ran beneath the workbench, disturbing the magnetic field the coils were trying to read. Move the device to an open field and it worked every time. You needed someone who could see the electromagnetic environment around the machine, not just the machine.

The patent came in 1945. The technology flew in WWII fighter planes. It was still being cited sixty years later.

Complementary minds are easy to mistake for interchangeable strengths: put an imaginative person and a methodical engineer on the same team and both contribute. Good hiring. But Springfield shows something harder. Antranikian's concept required Purves because Purves could see the field surrounding the device, including the interference from steel trains two floors down. Purves needed Antranikian because no manufacturer could originate the concept on its own. They weren't swappable. They were each doing something the other literally could not do.

Grandin's argument isn't abstract. The people who can see what's wrong with a machine before it breaks, who hold a half-built design in their minds and walk around it — they're already here. Sitting in remedial tracks or leaving school without degrees. Springfield found its Antranikian. Not every story ends that way.

The Traits Schools Call Problems Are the Ones That Changed History

The traits that get children flagged, medicated, and steered away from demanding subjects are the same traits that built the modern world. What happened to the people who carried them follows a pattern.

Alan Turing's headmaster wrote that he would "become a big problem in the community." He had illegible handwriting. He neglected his hygiene. He worked out advanced mathematics before he'd formally studied calculus. His school valued classical humanities; administrators concluded that if he intended to be "solely a scientific specialist, he is wasting his time." They were describing a mind they had no use for.

That mind broke the Nazi Enigma code. Turing cracked the cipher system shielding Germany's military communications — a rotor-driven encoding machine that scrambled every order, every troop movement. The British could read the enemy's plans. Historians estimate it shortened the war by years. The government that couldn't see the point of his mind used it entirely, then turned on him.

In 1952, Turing was convicted of homosexuality, a crime under British law. He lost his security clearance and was forced to take estrogen pills. Two years later, he was found dead, an apple laced with cyanide nearby.

The same state that conscripted his pattern-recognition to survive prosecuted him for how he was wired. That is what the state does. The traits that made him a problem to his headmaster never changed. His usefulness did. What schools call disorder and what history calls genius are the same traits — the only question is who names them first, and how early.

The Builders Are Still Out There

The person who could have spotted the fragile sensor before the crash probably failed algebra. The kid who would have machined Mars rover components to 1/64th of an inch is in a special education track somewhere, or dropped out. They did not disappear. They are in your school, your company, your family — still seeing things no one ever thought to ask them about.

That is what makes this an unusual problem. No invention required. The solution is already walking around. It requires a different question in a job interview, a different test in a classroom: not what can you abstract, but what can you actually see? And what would you build if someone finally handed you the tools — the lathe, the circuit board, the drafting table you were told wasn't for you?

Notable Quotes

like me see the world in photorealistic images. We are graphic designers, artists, skilled tradespeople, architects, inventors, mechanical engineers, and designers. Many of us are terrible in areas such as algebra, which rely entirely on abstraction and provide nothing to visualize.

Boeing is going to be in deep poo-poo.

Some at Boeing argued for an aerodynamic fix, but the modifications would have been slow and expensive, and Boeing was in a hurry.

Frequently Asked Questions

What is Visual Thinking about?
Visual Thinking argues that people think in three fundamentally different modes: verbal, object-visual, and spatial-visual. Temple Grandin demonstrates that each cognitive type excels at different tasks, and modern schools and workplaces systematically misidentify visual thinkers as failures. The book shows how matching people to roles by thinking mode—and building mixed teams—produces safer systems and better decisions than traditional verbal-intelligence-only hiring. Understanding these distinctions transforms how we evaluate talent and organize teams.
Why does Visual Thinking say algebra might be the wrong math for you?
Visual Thinking explains that struggling with algebra doesn't mean you're bad at math—it means you think differently. "If you struggled with algebra but succeeded at geometry, statistics, or anything with a physical correlate, you were probably an object visualizer hitting the wrong kind of math." The barrier is abstraction itself, not mathematical ability. Many object visualizers excel at tasks with physical or concrete visual correlates but struggle with symbolic manipulation. Recognizing this distinction prevents mistaken conclusions about aptitude and redirects talent to appropriate domains.
What hiring practices does Visual Thinking recommend for safety-critical roles?
Visual Thinking recommends evaluating candidates through cognitive fit rather than standardized testing alone. For safety-critical, manufacturing, or design roles, include "a hands-on or visual component in your evaluation." The person who can mentally walk through a physical system and spot vulnerabilities won't necessarily excel on standardized tests. Mixed teams of object visualizers (mechanics, designers) and spatial visualizers (mathematicians, physicists) consistently outperform homogeneous expert groups on complex problems. Including both types prevents blind spots and produces more robust solutions.
How do object visualizers help prevent failures in engineered systems?
Object visualizers excel at spotting system vulnerabilities that others miss. Visual Thinking notes that "single points of failure in engineered systems—one sensor, one generator, one decision-maker with no hands-on experience—are visible to object visualizers before disasters occur." They can mentally simulate what happens when specific components fail. During safety reviews and design audits, explicitly including object visualizers and asking who can picture component failure helps prevent catastrophic oversights. This cognitive diversity makes systems more resilient and catches risks earlier in development.

Read the full summary of 60149558_visual-thinking on InShort