Skip to lesson
Exit
Discovery & Customer Craft1 / 2

1 min lesson

Why days, not weeks

Start at the first move in "Why days, not weeks" and carry it through to the proof.

Step 1 of 2

Why days, not weeks

Speed isn't about looking productive. A thin slice running on the customer's own code does two things a polished v2 can't: it surfaces the wrong assumptions early and it earns the trust that buys you room for the hard parts.

  1. 1Pick one real case. Not a toy - the simplest actual instance from their repo. One file, one PR, one incident.
  2. 2Wire the whole path. Input, the model call, verification, output back where they'd consume it. Stub anything deep.
  3. 3Run it in front of them. Live, on their code, in their editor or CI. Let them see it work and fail.
  4. 4Thicken the riskiest stage next. Use what broke to decide where depth goes first.