Engine
Reach for Engine after launch week, when the question becomes whether any of this runs without the people who ran it.
- Growth is mostly the name of whoever is working hardest this quarter.
- The loudest voice decides which experiment runs next.
- Content goes out on a schedule but doesn't trace back to one story.
- Pipeline would stall if the main operator took two weeks off.
The hardest transition in go-to-market is from heroic effort to a system that runs. Engine makes that transition on purpose instead of by exhaustion.
The Two-Week Vacation Test
Its own grading question, asked of everything it produces: would this survive if the main operator went on vacation for two weeks?
Every output gets one of three answers: PASS, NOT YET or FAIL. An output only passes when every action in it has a named owner and a named backup.
What It Runs
- A retrospective on what the launch actually proved, and the one step that loses the most people
- A backlog where every idea gets one score: impact times unknown, divided by effort
- Two-week sprints, with a kill rule written on every item before it runs
- Growth loop design
- A three-layer strategic narrative
- Four email sequences that carry the narrative on a schedule
Scoring Ends The Popularity Contest
Every idea gets three numbers. Impact is how far it could move the goal. Unknown is how unproven the claim behind it is, read straight off its evidence grade. Effort is what it costs to find out.
The score rewards an idea that could move the goal, rests on something nobody has checked yet, and is cheap to check. The founder's favorite doesn't jump the queue. An idea built on a claim that's already confirmed has little left to teach, so it scores low.
Three Kinds Of Loop
| Loop | How It Compounds |
|---|---|
| Viral | Users bring users |
| Content | Publishing compounds into search |
| Paid | Revenue funds acquisition that funds more revenue |
The Narrative Isn't A Tagline
Three layers: the shift happening in the market, the stakes of that shift right now, and the world the product makes possible. The test is whether a blog post, a case study and a cold email all trace back to the same shift and the same stakes. When they do, content compounds. When they don't, the company is publishing noise on a schedule.
What It Writes
To the knowledge base: the retrospective, the scored backlog, the loop design, the narrative, the sequences and the vacation test results, all on the same foundation the other three wrote to. When a result contradicts a claim upstream, Engine sends it back to Discovery or Positioning to re-grade instead of tuning the numbers.