Make Bad Art
I can waste an impressive amount of time improving work that does not yet exist.
A draft stays open for days. A video idea gets another page of notes. A small feature somehow needs a complete production architecture before anyone has used it.
It feels like high standards. Often it is fear with better branding.
The way out is to make the bad version.
The point of the first attempt
In Art & Fear, David Bayles and Ted Orland tell a story about a ceramics class split into two groups. One group is judged by the quantity of work it produces; the other has to make a single, perfect pot. The best pots come from the quantity group. They spend the term handling clay, making mistakes and adjusting. The quality group spends too much time thinking about quality.
Whether I am writing, coding or making videos, the lesson holds: the first version is not there to prove I am good. It is there to show me what the problem really is.
You cannot learn from an unpublished draft in the same way you learn from a piece that readers ignore. You cannot understand a product from a schema diagram as well as you can from watching one person struggle to use it.
The finished thing talks back.
Planning has a stopping point
Some planning is useful. Security-sensitive software needs more of it than a blog post. A trading system needs tests before it touches capital. “Ship fast” is not permission to be careless with someone else’s money or data.
But there is a point where another hour of planning adds less information than a small, safe release.
I use a simple test: what can reality teach me now that another draft cannot?
If the answer is “whether anyone wants this,” it is time to ship.
Volume with attention
Making bad art does not mean repeatedly making the same mistake.
The useful loop is:
- Finish something small.
- Put it in front of reality.
- Notice where it fails.
- Change one or two things.
- Finish the next version.
Volume works because it gives you more loops, not because volume itself is noble.
This is what I am learning while building a content operation. My early scripts were overwritten. The first editing handoffs were messy. Some videos required far too much rescue. None of that was fixed by waiting for a perfect SOP. It improved because the team shipped, reviewed the failure and changed the process.
Taste is allowed to be ahead
One reason early work feels bad is that your taste is already better than your ability. You can see the gap.
That is not evidence to stop. It is evidence that you know what to work on.
The gap closes through specific repetitions: write a clearer opening, make the handoff less ambiguous, cut the section that is only there to sound clever. After enough attempts, the changes become instinct.
I still care about quality. I have simply stopped treating quality as something that appears before the work.
Make the bad version. Look at it honestly. Then make the next one less bad.