You see the same atomic approach in note-taking and self-improvement: break a big goal into small parts, then try to polish each part to perfection. Sometimes that genuinely helps — especially when you lack motivation, or the goal feels so big you don’t even want to start.
Turning a big goal into a stream of small, achievable ones really can get you over that hard first step. And the dopamine hit from clearing each atomic target is a pleasure in itself.
If you atomize your notes, you also break knowledge into units that can be linked and recombined later, sparking new ideas.
But a giant pile of atomic notes doesn’t mean you’ve mastered a subject or built a schema of thinking. The same goes for work: atomizing often lands you in a state that’s satisfying but self-limiting, because bolting together a set of individually perfect car parts doesn’t necessarily give you a perfect car.
If you get too used to solving problems atomically, it’s easy to fall into a trap: you win every small battle and lose the whole war, because you’ve lost sight of the big picture.
And if you happen to be the one leading the team, your most important job at that moment usually isn’t telling people how to crack each small problem and when to have it done — it’s telling them where on the blueprint the problem they’re solving actually sits, and which mountain they’ll have climbed once this leg of the journey is over.
Q: Even when the team is digging deep and solving every small problem beautifully, your gut still says “the direction’s off.” As a leader, how do you tell whether the team has gotten lost in the details and can’t see the whole?
I always put myself back at the start of the whole plan and look down on it again from above — the plan, and where it currently stands.
A leader who stays close to the progress and keeps a grip on the big picture should always know whether the hole the team is currently digging is still on the way to the goal, rather than just cracking the whip and driving everyone to push blindly forward.
As a consultant, when I have to review a past failure, I do the same thing: I sit down with the client and look back over the whole process from above, analyzing where the problem might have come from — not nitpicking the details. At that moment, pointing out “you didn’t try hard enough here” or “if you’d listened to me there you’d have been fine” is meaningless.
I often use an athlete analogy. We’ll review the details of a lost sprinting race — we check whether the athlete is sick or injured, and find a fix. But after all the efforts, we may eventually discover that he’s not cut out for sprinting at all; he’s actually a better long-distance runner.
At that point, the right move is a completely different position and training plan — maybe even a different coach — to make him a world champion in the end. If all you do is stare at “why did he lose another sprint,” you’ll never realize he should be running marathons.
Q: But you can’t ignore the details entirely either. When you “prune the branches” — cutting the people or things that are perfect but contribute nothing to the whole — what do you base that call on?
First you have to separate two things people constantly lump together: judgment quality and decision quality.
Judgment quality and decision quality are not the same thing — in practice they can even work against each other.
Judgment quality is about the sharpness of your observation and analysis. Decision quality can be dragged down by another department’s weakest link, or shifted by changes in the market.
An example: back in the day, Apple’s marketing team was convinced that “the Newton PDA would be the prototype for mobile computing for decades to come.” The iPhone later proved them right. But the decision to “kill this product” overruled that judgment outright, redirecting effort into the first iMac — and that’s what saved Apple.
Note: the Newton MessagePad was Apple’s “personal digital assistant,” launched in 1993; the term “PDA” comes from it. The product was cancelled after Steve Jobs returned to Apple in 1997, and many of its concepts didn’t resurface until the iPhone in 2007 — you could call it the iPhone’s ancestor. After Newton and several other products were cut, Apple put everything into the first iMac, whose sales success built the solid financial base Apple stands on today.
“Newton has real potential” was the judgment of the moment; “kill it” was a decision that sacrificed a single judgment to open up a whole new long-term play — make money with the iMac first, then revive the Newton dream once the market matured and the company had cash.
So a decision is made up of a string of interconnected judgments, but the final decision may sacrifice some of them. All I can say is that the conclusion is “the big picture comes first”: a decision has to weigh every department’s factors, and can’t rest on one isolated gut call, however sharp it is. When you’re facing a “perfect but isolated” detail, the question isn’t “is it perfect enough” — it’s “does it contribute to where the whole team is trying to go.”
Q: This “see the big picture” logic — beyond a leader looking at a product, does it apply to team collaboration, or even to individuals?
Absolutely, and I’d argue that’s exactly where it gets overlooked the most.
The key is this: you have to take in the whole of what’s within your field of view, and think about your own position — and how your output gets used by others on the team.
Some people assume that doing their own piece at 200% is the best contribution. It usually isn’t. One station on an assembly line running twice as fast as the others doesn’t necessarily raise overall efficiency — it can even jam up the flow. A politician’s marketing aide who just keeps his head down cranking out fabulous copy, without thinking through a wave-by-wave campaign strategy, won’t necessarily send the boss into the office either.
In other words, buffing a single part to a shine doesn’t make the car go faster. Seeing the whole picture — knowing whose hands your output lands in and how it gets used, then adjusting your own strategy accordingly — is what actually serves the bigger goal. That’s true for the leader, and it’s true for every single person on the team.
A closing thought
“Tools are accelerators, not steering wheels” — that’s something I say often when I talk about marketing sense. The same goes for “parts”: perfect car parts may guarantee quality and let the car run faster, but they won’t tell you where the car should be headed.
Seeing the big picture isn’t a one-off trick; it’s a habit you have to maintain on purpose. When a team falls into “parts perfectionism,” the most important thing a leader can do is bring everyone out of the cave and re-aim at the real target: where is all of this actually supposed to be going?
Winning every small battle feels great — but don’t forget, the war is decided by the final result.
(Note: this series is written with a book in mind, so some concepts will be developed further in other installments. Expect some jumping around. Stay tuned for what comes next — or wait for the book.)
Hardcore Insights
A set of perfect parts isn’t a perfect car. You can win every small battle and still lose the war; the biggest risk of solving everything atomically is losing the big picture.
A leader’s job is the overhead view. Re-examine the whole plan; in a review, look at direction and positioning, not nitpicked details.
Judgment quality ≠ decision quality. Judgment runs on your eye; decisions put “the big picture first.” A decision is built from a string of judgments, but sometimes it has to sacrifice one of them.
Prune by contribution, not perfection. The test for cutting a branch isn’t “is it perfect” but “does it serve the whole.” A perfect but isolated detail should still go.
It applies to individuals too. Doing your one part at 200% doesn’t make the whole faster; knowing whose hands your output lands in, and how it’s used, is what serves the bigger goal.
