Start Ugly

I have a friend who is a developer. His calendar is a work of art. Color-coded blocks, time estimates down to the quarter hour, notes nested inside notes. Ask him what he's doing at 2pm tomorrow and he'll tell you the task, the context, and which playlist he plans to listen to.

Ask him when the project ships and the answer is always the same. Next week. It's been next week for months.

His todo list is spotless. The codebase isn't. He can describe every feature in detail, but the editor stays closed while the planner stays open. The project doesn't move because the planning feels like moving.

The hard part is rarely the middle. By then you're in the code and momentum does most of the steering. The hard part is the first few minutes, when you're still deciding whether the conditions are right.

Most people lose that window the way my friend does. Organizing instead of starting. It feels responsible, but it's a stall tactic dressed up as preparation.

Start ugly means you open the file and write the bad sentence. You touch the work while it still looks wrong. Readiness doesn't show up before motion. It shows up after you've been moving long enough for your brain to catch up. If you wait for it first, you can wait through whole seasons.

You're not lowering your standards. You're lowering the entry so your standards have something to attach to. A blank page can't carry a standard. A rough paragraph can. Shrink the gate if you have to: two minutes, one line, one checkbox. The size doesn't matter. The start does.

The people who ship aren't the most inspired. They're the ones who began anyway, often badly, often when nobody would have called the conditions ideal. They stopped making a ceremony out of beginning, and that turned into consistency.

The negotiation ends when your hands are busy. Get them busy.