Taste as a Deploy Gate.
A pre-decided, named criterion that decides whether work passes — before feelings get in.
Taste is usually invisible: a feeling about whether the thing is good. That makes it impossible to argue with and impossible to improve. Most teams either over-rotate to the loudest taste in the room, or pretend taste doesn't exist and ship the average.
The fix is to make taste explicit. Name the criteria before you build. Write them down. When the work is finished, run it through the gate as if you weren't the one who made it. The gate either passes or rejects. The rejection isn't an emotion — it's a named diff.
I use this on everything: code, copy, design, this site. The single biggest leverage in a one-person studio is having one set of eyes that knows exactly what they're checking for, every time.