Growth engineers write tickets

You lose experiments between the idea and production. Someone presents a slide. Someone else files a backlog item, and you skip writing the sentence that would have made the test runnable. Write that sentence as a ticket.

The ticket

An experiment ticket is the smallest document that lets engineering and data run the same test without a meeting.

Put two things in it:

1. A hypothesis as a bet. If we change X, Y moves, because Z. Fold the CRO reason into that sentence, in language a sceptic can falsify.
2. The UI. The treatment screen itself.

Leave either out and you spend standup debating intent.

Decks skip the constraints

With a deck, the room nods at "simplify checkout." In a ticket you name the optional company field on pay and the checkout completion metric. Sit down and write the ticket before you book the review.

If we remove the optional company field on pay, more carts complete, because each extra input raises cognitive load at the moment of commitment.

Drop that in Linear and attach it to a flag this week. "Let's improve conversion" remains a slide.

MAGE starts from a screenshot

Start from the screen you have. The screenshot shows the density and the button fighting the copy.

Drop the screen into MAGE. You get a spec: the hypothesis (with the CRO reason) and the UI to test. Lite gives you an ASCII treatment and a prompt. Starter and up give you high-fidelity mockups.

Paste the spec into Linear and attach it to an A/B flag.

Write it so you can kill it

If the metric does not move, you spent a generate. A deck costs you a meeting that confirmed the room liked the story.

Kill the ticket if the number stays flat, and write the next one from the same screen.