The Mental Practice Of Zooming In And Zooming Out

Computer scientists talk about "levels of abstraction" constantly. A program exists simultaneously at the level of machine code, assembly language, high-level language, and application logic. What's true at one level doesn't directly translate to another. You can't understand what a program does by reading its machine code, and you can't fix a memory leak by redesigning the user interface.

This is a precise and useful way of thinking about any complex system — not just software. Every organization, every relationship, every problem has stacked levels of abstraction. And one of the most common analytical errors is working at the wrong level.

When a company's sales numbers are declining, the zoom-in analysis might identify that the sales team isn't following up on leads fast enough. True. Fixable. But the zoom-out analysis might reveal that the product doesn't solve a problem customers actually have anymore. Fixing the follow-up speed at the zoom-in level will produce better-looking activity metrics and no improvement in outcomes. The level of analysis determined the quality of the solution.

Switching between abstraction levels isn't just a conceptual move — it has a real cognitive cost. Detailed analytical thinking and holistic conceptual thinking engage different cognitive modes. Daniel Kahneman's framework of System 1 (fast, associative, pattern-matching) and System 2 (slow, deliberate, analytical) maps roughly onto this: zoom-out thinking leans on System 1's pattern recognition; zoom-in thinking demands System 2's careful attention.

This is part of why people default to one mode. Switching is effortful. Staying at the level you're comfortable with is easier. The expert in detail stays in the detail because that's where their expertise lives and where cognitive effort pays off quickly. The visionary stays in the vision because the detail is uncomfortable and slow.

Deliberately practicing zoom-switching builds the mental habit of asking "what level is this question at, and is that the right level to be working?"

When you're stuck on a problem or a decision, these four questions help you locate what's actually happening and at what altitude:

1. What level am I currently working at? Be explicit. Am I looking at a specific action, a project-level issue, a strategic question, or a worldview-level assumption? Most people don't stop to ask this.

2. What level does the root cause live at? Symptoms often appear at a different level from causes. A team that's constantly behind schedule (zoom-in symptom) might have an under-resourced roadmap (zoom-out cause). You can't fix the schedule if you're only managing at the schedule level.

3. What level does the solution need to be implemented at? Even if you correctly diagnose the root cause at a high level, the fix might need to happen at a very specific level. Knowing both matters.

4. Who has the clearest view of this level? Different people have access to different altitudes. The frontline person has the best zoom-in view. The executive has the best zoom-out view. Getting them in the same conversation — in a way where both perspectives are taken seriously — is how organizations solve hard problems.

There's a strong case that what we call "wisdom" is largely the ability to zoom out while keeping the zoom-in accurate.

Wise people don't lose touch with specifics. They're not floating in abstractions, disconnected from how things actually work. But they're looking at specifics through a lens of long patterns, deep context, and awareness of how things tend to go. They zoom out far enough to see the arc, and zoom in close enough to see the detail that matters.

This is why wisdom tends to come with age — not because people get smarter, but because they've accumulated enough experience to have genuine zoom-out material. They've seen how this kind of situation tends to play out. They have the longitudinal data in their head.

You can accelerate this by deliberately studying patterns at scale — reading history, studying case studies across industries, looking at how similar problems played out in different contexts. This gives you zoom-out material faster than pure personal experience.

Here's a structured version of the practice for any decision or problem:

Altitude 1 — Immediate (0-30 days) What specifically needs to happen? What are the concrete actions, the names, the numbers, the deadlines? What's the most granular version of this problem?

Altitude 2 — Strategic (3-18 months) What is this situation a part of? What system or project or relationship does it sit inside? What does success look like at this level? What are the second-order effects of the zoom-in decisions?

Altitude 3 — Foundational (multi-year) What assumptions underlie this whole domain? What would have to be true for the Altitude 2 strategy to make sense? What does this look like from the perspective of who you're trying to become, or what the organization is trying to be?

Most planning conversations happen entirely at Altitude 1. Good strategic planning adds Altitude 2. Altitude 3 is rare and often transformative — it's where you discover that you've been optimizing for the wrong thing entirely.

There's a specific failure mode worth naming. The charismatic visionary leader who can speak fluently about strategy, culture, and long-term vision — but who has never run an execution-heavy process in their life. They hire "operators" to handle the zoom-in work. This can function. It also means the leader's zoom-out thinking is never corrected by the realities of zoom-in execution.

The best leaders have genuine respect for both levels and have done both. They zoom out because they've felt how quickly good zoom-in execution runs into zoom-out strategic problems. They zoom in because they know what details reveal about the actual health of a system.

The practice is simple enough to start today. Pick any problem you're currently working on and write three descriptions of it — one at each altitude. This forces the zoom. Do it for five minutes. Notice which altitude comes most naturally. Notice which one produces the most unexpected insight. That's the level you're currently underusing.

Make this a regular practice in your planning: before any significant decision, run the three-altitude check. What does this look like close up? What does it look like from the middle distance? What does it look like from far away?

The altitude shift is free and takes about three minutes. The clarity it produces is disproportionate to the effort.