Execution Is Free. Judgment Just Got Expensive
Once anyone can make something usable in ten minutes, "usable" starts to devalue. Vote on three interfaces by gut feel first — come back after this chapter and vote again. See if your eye changed
THE QUESTION THIS PAGE ANSWERS
ANSWER FIRSTWhat is the key idea behind “Execution Is Free. Judgment Just Got Expensive”?
Once anyone can make something usable in ten minutes, "usable" starts to devalue. Vote on three interfaces by gut feel first — come back after this chapter and vote again. See if your eye changed
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.
In the past, "can build" was valuable: knowing code, design tools, video editing—the tool itself was the barrier. AI flattened that barrier. Usable stuff is everywhere. What's scarce now is building it right, with taste: ten options in front of you, pick the right one, say what's off and how to fix it.
| Dimension | Before AI | After AI |
|---|---|---|
| Barrier | Know the tools and stacks; years of learning | Talk like a human and you can start |
| Time | A shippable page took days or weeks | First draft in ten minutes, three versions in an hour |
| What separates you | Execution: who can ship it | Judgment: who can spot which version is right and say what they want |
Same brief—"a booking page for a yoga studio"—AI gave three plans. Skip theory for now; tap the one that feels best. This page doesn't grade you. The vote is saved; after the last lesson in this Part you'll vote again. Side by side, you'll see how your eye changed.
Drag the time to make something usable from 72 hours down to 0.2 hours. Watch two indexes trade places. As time collapses, "usable" devalues; as usable stuff floods in, the premium on picking the right one rises.
By now you always hit the same pushback: taste is talent, beauty is in the eye of the beholder—how do you teach that? Mullet and Sano (Kevin Mullet & Darrell Sano) untangle it in Designing Visual Interfaces. Art is how artists express themselves—fewer constraints the better, uniqueness pays. Design makes something for a specific audience with a specific use; the top job is clear communication.
Mullet and Sano, Designing Visual Interfaces
That sentence is the foundation of this Part. Judging art asks "what does it express?"—no right answer; you can argue till dawn. Judging design asks "did the message reach the target audience?"—that you can verify.
Cooper calls this path goal-oriented in About Face 4, and adds: visual communication always carries some subjective judgment, but once experience and business goals are clear, taste gaps can be narrowed by effort. Aesthetics isn't kicked out—it's framed by goals.
| Dimension | Art | Design |
|---|---|---|
| Question it answers | What do I want to express | Did the message reach the target audience |
| Constraints | Fewer is better; uniqueness is a plus | Users, context, and goals are given |
| How you judge | To each their own—no winner | Check against goals line by line—you can rank them |
| What it means for taste | Close to talent—hard to teach | Judgment has a referee—practice works |
Hang this poster in a gallery and anything goes—it only answers to the maker. Now make it next week's show preview. What's the first question it has to answer?
Theory without feel is hollow—try a live experiment. Three show posters, two reviewers: designer Zhou and organizer Chen. Watch them argue with no goal, then put the goal on the table and see the conclusion surface on its own.
The barrier to shipping collapsed: anyone can make something usable in ten minutes—"usable" is devaluing.
Scarcity moved: from "can build" to "build it right, with taste." Picking the right one from a pile becomes the human's core job.
Aesthetic judgment has a referee: art owns expression, design owns communication (Mullet and Sano). Once goals are clear, taste fights narrow into verifiable questions—the theoretical base for "taste can be trained."
This Part trains two skills: spot what's wrong (lessons 3–6), say clearly what you want (lessons 7–9). Today's vote is saved—come back after the last lesson to compare.
Source: Original to Xiaoshan Academy's Taste Engineering series; some design principles adapted from About Face 4, Chapter 17.
Turn the feeling in “Scarcity moved” into a judgment
“In the past, "can build" was valuable: knowing code, design tools, video editing—the tool itself was the barrier.” 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 “Same brief—"a booking page for a yoga studio"—AI gave three plans.” 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 “This Part trains two skills: spot what's wrong (lessons 3–6), say clearly what you want (lessons 7–9).” 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 “Scarcity moved” to “Try it · Vote by gut first”
“Scarcity moved” grounds the problem in “In the past, "can build" was valuable: knowing code, design tools, video editing—the tool itself was the barrier. AI flattened that barrier. Usable stuff is everywhere. What's scarce now is building it right, w…”. “Try it · Vote by gut first” then moves it toward “Same brief—"a booking page for a yoga studio"—AI gave three plans. Skip theory for now; tap the one that feels best . This page doesn't grade you. The vote is saved; after the last lesson in this Part you'll vo…”. 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?
- “Scarcity moved”: In the past, "can build" was valuable: knowing code, design tools, video editing—the tool itself was the barrier. AI flattened that barrier. Usable stuff is everywhere. What's scarce now is building it right, w…
- “Try it · Vote by gut first”: Same brief—"a booking page for a yoga studio"—AI gave three plans. Skip theory for now; tap the one that feels best . This page doesn't grade you. The vote is saved; after the last lesson in this Part you'll vo…
- “The closing point”: Theory without feel is hollow—try a live experiment. Three show posters, two reviewers: designer Zhou and organizer Chen. Watch them argue with no goal, then put the goal on the table and see the conclusion sur…
The final “The closing point” brings the discussion to “Theory without feel is hollow—try a live experiment. Three show posters, two reviewers: designer Zhou and organizer Chen. Watch them argue with no goal, then put the goal on the table and see the conclusion sur…”. 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.