← All articles

How to move fast toward the right thing

Jonah Abrams · 1 min read

For most of software history, code was the gate to building products, and developers held the keys. That gate is gone. People who have never opened an editor can ship working software. But there is a cost: when you can build anything, building the right thing gets harder.

Speed accelerates execution, not clarity

It's easy to prompt your way to something that looks finished. We've been trained to trust polish, because before, polish reflected hard-won decisions. Today polish is cheap, and the decisions underneath it may never have been made.

Consider it carefully. Build it efficiently. Make it stand out. Skip the first step and the other two only get you lost faster.

Three loops of a considered process
Consider, build, refine: the loop slows down exactly once.

Friction is a feature

There's a name for letting a tool make the call for you: deferred judgment. It feels like speed. It is borrowing against next quarter.

Three habits

  1. Write the problem down before you open the canvas

  2. Prototype two directions, never one

  3. Review behaviour, not screenshots

Make it stand out

When everyone can ship, the difference is taste — and taste is the one thing you can't prompt.

0 comments

  • Be the first to comment.