> ## Documentation Index
> Fetch the complete documentation index at: https://www.pickfu.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# PickFu survey best practices and writing tips

> Tips for writing clear PickFu survey questions, choosing sample sizes, targeting the right audience, and getting more actionable consumer feedback.

Follow these guidelines to get the most actionable results from your PickFu surveys.

## Writing good questions

### Be specific

Tell respondents exactly what you want them to evaluate.

<Tabs>
  <Tab title="Good">
    "Which product image would make you more likely to click on an Amazon listing?"
  </Tab>

  <Tab title="Avoid">
    "Which image is better?"
  </Tab>
</Tabs>

### Provide context

Give respondents enough background to make an informed choice.

<Tabs>
  <Tab title="Good">
    "We're designing a logo for a children's educational app. Which logo design feels more trustworthy and fun?"
  </Tab>

  <Tab title="Avoid">
    "Which logo do you prefer?"
  </Tab>
</Tabs>

### Keep it focused

Ask one question at a time. If you need feedback on multiple aspects, use a [multi-question survey](/guides/surveys-overview#multi-question-surveys) (up to 16 questions) so the same respondents answer all of them, or create separate polls.

<Tabs>
  <Tab title="Good">
    "Which headline would make you want to learn more about this product?"
  </Tab>

  <Tab title="Avoid">
    "Which headline is more engaging, and would you click on it, and does it make you trust the brand?"
  </Tab>
</Tabs>

## Choosing the right question type

| Goal                                              | Recommended type |
| ------------------------------------------------- | ---------------- |
| Compare two options directly                      | Head-to-head     |
| Rank multiple options by preference               | Ranked           |
| Get detailed feedback on one concept              | Open-ended       |
| See where people look on an image                 | Click test       |
| Test first impressions                            | Five-second test |
| Measure overall satisfaction                      | Star rating      |
| Pick one winner from several options              | Single select    |
| Find out which features or attributes appeal most | Multi-select     |

## Targeting your audience

### Match your actual customers

Target demographics that reflect your real customer base. If you sell products on Amazon, target Amazon Prime members. If your audience skews younger, set appropriate age ranges.

### Start broad, then narrow

If you're unsure about targeting:

1. Run a first poll with broad targeting to get general feedback
2. Review the demographic breakdowns in your results
3. Run follow-up polls with tighter targeting based on what you learned

### Consider sample size

* **15 respondents** - Good enough for quick directional feedback
* **30 respondents** - Useful for early-stage validation with a bit more signal
* **50 respondents** - Solid for most decisions
* **75 respondents** - Good balance between confidence and speed
* **100+ respondents** - Use when you need demographic breakdowns or high confidence

#### Small samples in an iterative loop

A one-shot survey wants a larger sample, because there's no second poll to correct a noisy result.
An **iterative loop is different** — it triangulates a decision across many small polls (a baseline,
several head-to-head iterations, and a final validation), so no single poll has to carry the whole
conclusion. A 15-respondent iteration that happens to pick a slightly-wrong winner gets caught by the
next iteration or by the larger final validation.

That's why the [playbooks](/playbooks/amazon-main-image) default to cheap polls — **15 for each
iteration, \~50 for the bookend baseline and validation** — and only recommend scaling the final
validation to 100–200 before a costly, hard-to-reverse change. Spend your respondents on the polls
you trust (the bookends), and keep the disposable middle steps fast and cheap. This matters most when
an AI agent runs the loop on your behalf: cheap iterations keep the total cost low while the
loop structure preserves the reliability.

## Preparing your options

### Use consistent formatting

Keep all options at the same quality level and format. If one image is high-resolution and another is a rough sketch, respondents will judge quality rather than the actual concept.

### Test real alternatives

Use options that represent genuine choices you're deciding between, not obviously good vs. obviously bad options.

### Limit the number of options

* **2 options** - Use head-to-head for clear A/B decisions
* **3-5 options** - Best for ranked or single-select polls
* **6-8 options** - Use only when all options are genuinely viable

## Interpreting results

### Look beyond the winner

The written explanations often contain more valuable insight than the vote counts. Read them to understand *why* people chose what they chose.

### Check demographic breakdowns

Different audience segments may have different preferences. A result that's split 50/50 overall might be 80/20 within your target demographic.

### Consider statistical significance

* **Strong signal** - 70%+ of respondents agree
* **Moderate signal** - 55-70% agree, consider [adding more respondents](/guides/survey-lifecycle#adding-more-respondents) to increase confidence
* **Weak signal** - Close to 50/50, the options may be equally viable

### Run iterative tests

Use initial poll results to refine your options, then run another poll. Two rounds of 50-respondent polls often yield better insights than one round of 100.

## Common mistakes to avoid

<Warning>
  These patterns reduce the quality of your results.
</Warning>

* **Leading questions** - "Don't you think Option A looks more professional?" biases respondents
* **Too many variables** - Comparing options that differ in multiple ways makes it hard to know what drove the preference
* **Mismatched formats** - Mixing high-quality images with rough mockups skews results toward production quality rather than concept preference
* **Ignoring written feedback** - Quantitative votes tell you *what* won; written explanations tell you *why*
* **Testing too late** - Run polls early in the design process when changes are still easy to make
* **Duplicating the built-in explanation prompt** - Every PickFu response already includes a required written explanation. Adding a second question like "Explain your reasoning" wastes a question slot (multi-question surveys are priced per question) and produces redundant data. Phrase your real question, and PickFu will collect the *why* automatically.
