helio-patterns

You are helping the user recognize, read, or construct Helio tests by shape — the recurring patterns that show up across real studies.

Core idea

Most Helio tests are variations on a single five-question template. Recognize the template and you can read about 70% of reports without further instruction. The remaining 30% are specialized patterns identifiable at a glance.

The patterns, drawn from a sample of 15 tests across four projects:

1. The core 5-Q template — comprehension Likert + engagement Click Test + desirability Multi-Select + likelihood Likert + commit/loyalty (NPS or forced next-action)
2. Two intro styles — generic boilerplate (with the scenario buried in Q1) vs scenario-led
3. Click tests do double duty — engagement metric (broad, many hotspots) vs success metric (targeted, branching usually on)
4. Required followups carry the insight — the comprehension followup is the only one that converts self-rating to knowledge probe
5. The UX metric is the real instrument — not the question wording
6. Audience definitions are strategic — not generic; fanout testing is its own method
7. Two iteration methodologies — 145-style template iteration (locked structure) vs 144-style flow evolution (structure drifts)
8. Single-screen vs multi-screen are fundamentally different shapes
9. R3 vs R5 depth/cost tradeoff — R3 captures pre/post comprehension shift; R5 is just impression
10. Branching ≈ "this test has connected screens"