Go home

Decisions are the work

Most web projects don't stall because of bad design or slow code. They stall because nobody will make a call.

A clean desk with a single notebook, ready for a decision, not a committee.
· 2 min read

I used to think the hard part of building was the building.

Pick the right stack. Design something clean. Ship before the weekend. That felt like the real work. Turns out none of that matters if you cannot make a call.

I once stalled a project for three weeks on things I already knew the answer to. Which headline. Which feature to cut. Which flow made more sense. Every day I told myself I was being careful. I was not being careful. I was stalling.

The site launched late. Not because the code was hard. Because I would not commit.

A decision made now, even an imperfect one, is worth more than the perfect one made two weeks from now. When you decide fast, you find out fast if you were wrong. That is the feedback loop. That is how you improve. When you wait, you lose the thread. The instinct that once pointed somewhere useful fades, and you end up deciding with less confidence than you started with.

I also used to think more options meant better outcomes. It does not work that way. Options without commitment spread the thinking thin. The best work I have shipped came from picking a direction early and going deep, not from keeping everything open.

Now when I feel the urge to think on it a bit more, I ask: what am I actually waiting for? Usually the answer is nothing. I already know enough. I just do not want to be wrong.

Being wrong quickly is the whole game. You fix it and move.

Decisions are not a pause before the real work. They are the work.