What It Means to Really Look at Design
Bookmarking a hundred sites is useless. Tear them down in order: hierarchy, then spacing, then colors. Use this flow to dissect a good design live
THE QUESTION THIS PAGE ANSWERS
ANSWER FIRSTWhat It Means to Really Look at Design?
Bookmarking a hundred sites is useless. Tear them down in order: hierarchy, then spacing, then colors. Use this flow to dissect a good design live
Turn taste into a behavior the product can repeat. The useful outcome is not a nice opinion. It is a visible rule, a small example, and a way to tell when the experience falls below the bar.
Capture one before-and-after example that shows the quality bar without extra explanation.
Polish that improves the surface while leaving the user's uncertainty untouched.
A hundred "inspiration sites" sit in your bookmarks, and when it's time to work you still have no direction—that kind of collecting equals none. Open a good design, glance and say "nice," screenshot, close. That's tourist behavior: you took a photo, shared it, walked away with nothing.
To really look, tear it down in a fixed order—each layer answers one question: hierarchy first (who's the hero), then spacing (does padding follow a pattern), then count colors (how many, who does what), then pick at details (how many corner radii, shadows, font weights). Big to small: skeleton first, skin later.
Before those four steps comes step 0: squint. Before you stare wide-eyed at details, blur the whole page into blobs once—hierarchy and grouping will float up on their own. This lesson walks all five steps live.
Graphic designers have an old craft called the squint test: close one eye, squint the other at the screen. Once details blur out, what's left is masses, light/dark, and grouping—which elements still pop, which read as a pack, is obvious at a glance. About Face 4, Chapter 17, lists it as the go-to tool for checking hierarchy and relationships, and notes that a different angle often reveals layout issues you'd missed.
What is squinting checking? The same chapter answers: when people see a screen, they instinctively ask two questions—what matters here? how are these things related? Good design answers before you finish asking. Translate those two questions into plain talk and you have this lesson's teardown mantra.
Squint for pass one; open your eyes for pass two. If the answers match, the hierarchy holds. If squinting finds no landing spot and groups blur into mush, polish with open eyes won't save it. The X-ray lens below now has a squint view—switch to that first.
The landing page below was built to this Part's rules: one hero, 8pt spacing, one primary color. Switch views and see how the same page looks in each of the four teardown layers.
Good design doesn't freestyle spacing—it uses a ruler. About Face 4, Chapter 17, calls that ruler the atomic grid unit: pick a minimum spacing, say 8px, and every gap between elements and groups is a multiple of it. The book credits the grid three ways: regular positions help users find things faster (usability); proportions between regions feel right (aesthetics); layout decisions are made early, so redesigns cost less (efficiency).
Flip it and you get a hard test for good design: measure three to five gaps and see if they divide evenly by the same number. If they do, a grid system is running underneath; if not, it was mostly hand-placed. That's what the spacing step is measuring.
The habit-tracker weekly card below was built on an 8pt grid. The X-ray lens showed someone else's teardown—now you do it: squint for hierarchy, light the ruler for spacing, then answer one check question.
Information-design master Edward Tufte defined excellent visual design; About Face 4, Chapter 17, quotes it as-is:
Under that definition, teardown makes sense: the hero you find, the spacing you measure, the colors you count are traces of thinking that landed on the page. Teardown a good design and you're reverse-playing someone else's thought process—that grows your eye faster than ten "color tip" articles. Flip it: a page you can't make sense of tearing down probably wasn't thought through.
Step 0 is on the list now—five steps total. Each answers one question. Tick one, light one; if you can't answer, stay on that step and look harder.
Really looking has a fixed order: Step 0 squint, then hierarchy, spacing, color, details. One question per layer, skeleton to skin.
Squint answers the two mantra questions: What does this UI want me to see first? Which things are grouped as a pack? Squint once, open eyes to verify.
Spacing is judged with a ruler: Measure three to five gaps—if they divide by the same number, an atomic grid is underneath; if not, it was mostly hand-placed.
Before saving a reference, attach one verdict: which variable it's good at. Bookmarks stop being a pile of images and become a case library—next lesson you'll feed that to AI.
Source: Original to Xiaoshan Academy's Taste Engineering series; some design principles adapted from About Face 4, Chapter 17 (Alan Cooper et al.); Tufte's defining line quoted from the same chapter.
Turn the feeling in “Admit it first: a hundred bookmarks equal none” into a judgment
“A hundred "inspiration sites" sit in your bookmarks, and when it's time to work you still have no direction—that kind of collecting equals none.” points out that AI has lowered the bar for making something usable. The skill readers need is noticing what is wrong and turning that feeling into an actionable requirement.
Watch the user's next action, not just the surface
Turn “To really look, tear it down in a fixed order—each layer answers one question: hierarchy first (who's the hero), then spacing (does padding follow a pattern), then count colors (ho…” into observable questions: does the user know what happened, what to do next, and how to recover from an empty or failed state? Does the hierarchy make the important information visible first?
Pretty is not the same as usable
Apply “Before saving a reference, attach one verdict: which variable it's good at.” to a second screen or flow. Record one moment of hesitation and the user action after the change; observable behavior is stronger evidence than polish alone.
From “Admit it first: a hundred bookmarks equal none” to “Step 0: Squint first”
“Admit it first: a hundred bookmarks equal none” grounds the problem in “A hundred "inspiration sites" sit in your bookmarks, and when it's time to work you still have no direction—that kind of collecting equals none. Open a good design, glance and say "nice," screenshot, close. Tha…”. “Step 0: Squint first” then moves it toward “Graphic designers have an old craft called the squint test : close one eye, squint the other at the screen. Once details blur out, what's left is masses, light/dark, and grouping—which elements still pop, which…”. Together, they show that the lesson is not just a conclusion to remember, but a claim with conditions.
Carry the judgment into the next situation
For experience work, turn abstract impressions into user actions: did the person understand the state, find the next step, recover from an error, and want to continue?
- “Admit it first: a hundred bookmarks equal none”: A hundred "inspiration sites" sit in your bookmarks, and when it's time to work you still have no direction—that kind of collecting equals none. Open a good design, glance and say "nice," screenshot, close. Tha…
- “Step 0: Squint first”: Graphic designers have an old craft called the squint test : close one eye, squint the other at the screen. Once details blur out, what's left is masses, light/dark, and grouping—which elements still pop, which…
- “The closing point”: Good design doesn't freestyle spacing—it uses a ruler. About Face 4 , Chapter 17, calls that ruler the atomic grid unit : pick a minimum spacing, say 8px, and every gap between elements and groups is a multiple…
The final “The closing point” brings the discussion to “Good design doesn't freestyle spacing—it uses a ruler. About Face 4 , Chapter 17, calls that ruler the atomic grid unit : pick a minimum spacing, say 8px, and every gap between elements and groups is a multiple…”. The useful thing to carry forward is knowing which judgments must be revisited when input, scale, or risk changes.
I turned one judgment from this article into a small experiment I could run today. Knowing what to observe next is more useful than simply remembering the conclusion.
After reading this, I first looked for the conditions behind the idea instead of copying the method into a project. That order made the later trade-offs much clearer.
When this judgment reaches real work, which constraint should be added first? I am curious which step matters most between reading and the first practical attempt.
No discussion on this article yet.