12. Feedback Loops

If you don’t have a loop, you don’t have a system. You have hope.

Long loops create fantasy. Short loops create reality. The longer you go between making something and showing it to someone, the more elaborate the story you tell yourself about how good it’s, and the harder reality hits when it finally arrives. The fix for almost every stuck project is the same: shorten the time between the work and the feedback.

The reason people don’t do this is not laziness. It’s ego, and I know because I spent a design career running on mine. A client would say I don’t love it and I would feel it in my chest for two days. I would pour a week into a logo, they would shrug, and I would go to bed feeling like they had rejected me, not the file. As long as the work and the self are the same object, every piece of feedback is an attack, so you protect yourself the only way that works: you stop showing the work. You build longer and longer in the dark, which feels safe and is actually the most dangerous thing you can do.

Here is the distinction it took me years to feel. Your work is not you. The mockup is not you. The post, the launch, the product, the page. You made it and sent it out, and now it belongs to whoever sees it. Your only job was to ship it.

The Easy Mode move is not to grow thicker skin. Thicker skin is willpower, and willpower runs out exactly when you need it. The move is to ship faster and smaller, so there is less of you embedded in any single thing. You can’t over-identify with a draft you made this morning. Short cycles keep the ego out of the room, which is the only reliable way to keep hearing the truth.

A loop that works for almost anything:

• Ship a version, even a rough one.
• Ask one person one question: what confused you?
• Fix the confusion.
• Repeat.

Notice the question is not do you like it? Praise is pleasant and tells you nothing. Confusion is information. Confusion is the friction between your work and the person using it, and every point of confusion you remove makes the next version better. People are also far more willing to tell you what confused them than to tell you what they disliked, because confusion sounds like their problem and dislike sounds like an attack on you.

This is also why rough drafts get better feedback than polished ones. A polished thing looks finished, so people hunt for small corrections or say “looks great” to be kind. A rough thing looks unfinished, so people feel safe telling you the big thing that’s actually wrong, which is the thing you need.

Move fast. Action produces feedback, and feedback is the only thing that turns a guess into knowledge. The builder who ships ten rough versions and asks what confused people will pass the one who is still perfecting version one in private, every time.

Where are you guessing instead of checking? Replace one guess with one rough version in front of one person this week.