What the Dog Saw: When the Visible Problem Isn't the Real One

The visible problem is rarely the real one — a thread running under Gladwell's most unrelated stories.

Lately I've been thinking about a strange connection between dog attacks, homelessness, corporate scandals, cybersecurity, and artificial intelligence.

As odd as it sounds, they all lead to the same realization: most organizations spend enormous energy reacting to outcomes, and very little understanding the systems that created them.

That idea kept surfacing while I was reading Malcolm Gladwell's What the Dog Saw — and it has stayed with me for weeks since. Not because every story was memorable, or because I agreed with every conclusion, but because the book quietly changed the way I look at other problems.

At first glance, the essays seem disconnected from one another. Dog attacks. Homelessness. Corporate scandals. Consumer products. Human behavior. Innovation.

Yet the longer I reflected on them, the more I realized they were all circling around the same underlying question:

01The same question under every story

One of the essays discusses dog attacks and society's instinct to focus on specific breeds after a highly publicized incident. But the deeper issue often has more to do with systems: ownership, enforcement, training, early warning signs, and the environments that allow risk to build over time.

Another essay examines homelessness and how communities frequently spend enormous resources reacting to visible symptoms while missing opportunities to intervene earlier and more effectively at critical leverage points.

The Enron story explores how organizations often behave exactly as their systems incentivize them to behave. If short-term performance is rewarded more heavily than long-term stability, people naturally optimize for the rewards that exist. The system itself quietly shapes behavior.

That idea stayed with me.

Organizations, teams, and even technologies often produce outcomes that make perfect sense once we understand the incentives, structures, and assumptions underneath them.

02I've seen this in technology leadership

I've seen versions of this repeatedly in technology leadership.

• A cybersecurity incident is rarely just about security.
• A struggling project is rarely just about project management.
• Low adoption of a new technology is rarely just about the technology itself.

The visible problem is often the final symptom of something deeper that has been developing quietly for a long time.

03Puzzles and mysteries

Another idea from the book that stayed with me was the distinction between problems that are puzzles and problems that are mysteries.

Some problems become clearer as we gather more information. Others remain difficult because what we actually need is a different perspective.

The closer we look, sometimes the less clearly we can see.

04Why this matters now

That observation feels increasingly relevant in a world shaped by artificial intelligence, organizational complexity, and constant streams of data. We often assume better answers come from collecting more information.

Increasingly, I suspect better answers often come from seeing the system differently.

Looking back, I think the title itself contains the central lesson.