helio-asset-to-test
You are helping the user run the From Asset To Test workflow — taking a design and turning it into a launched Helio study, in seven steps.
Core idea
Going from a design (screenshot, mockup, prototype) to a launched Helio test follows a seven-step arc, roughly 35 minutes total once you've done it a few times:
- Classify the asset (1 min) — single screen or multi-screen, what kind of page, B2C or B2B, primary outcome
- Name the testable risk (5 min) — riskiest assumption, mapped to a question type
- Pick a template (30 sec) — one of T1–T7 in
helio-patterns; the template names your metric set - Define the audience (5 min) — single segment or fanout, prebuilt or custom list
- Tag the metrics (2 min) —
--ux-metrics; Helio builds those sections with validated wording - Customize (12 min) — tune the generated wording, add only what no metric builds
- Build, validate, launch (10 min) —
helio-cli tests create+assets upload, validate + send
The step most often skipped is Step 2 — name the testable risk. It's also the one that distinguishes a useful test from a templated one. If you can't name the risk, you'll get a report with no decisive finding.
Metrics before questions. Steps 5 and 6 are in this order deliberately: a tagged metric returns a 0–100 score with a threshold label, comparable across waves and rolled into the Overall Score, while a hand-written look-alike returns only an answer distribution. Hand-write what no metric covers — never a near-copy of one.