Skip to lesson
Exit
Positioning & Messaging for a Developer ICP1 / 2

1 min lesson

The narrative order that works for engineers

Start at the first move in "The narrative order that works for engineers" and carry it through to the proof.

Step 1 of 2

The narrative order that works for engineersproblem → aha → mechanism → proof

  1. 1Lead with the problem. Open on the developer's actual pain - re-explaining the repo, stitching multi-file changes by hand. They have to recognize themselves in the first line.
  2. 2Land the aha. Show the moment it gets better: the diff appears across the files, already wired up. One vivid before/after beats a capability list.
  3. 3Then the mechanism. Now explain how it works - context from the codebase, a concrete plan, a reviewable change. By now they want the detail.
  4. 4Close with proof. A real metric, a recognizable workflow, a named customer. Specifics are the credibility, not the superlatives.

Notice the order. Most marketing leads with the mechanism or the brag; this leads with the reader's problem and earns the mechanism by the time it arrives.