How to build a useful magazine reader survey

What to take away

A reader survey can test needs, habits, satisfaction, format preferences, topic demand, and service experience. It cannot reliably answer every question about behavior or prove that the loudest respondents represent the whole audience. This method keeps the project tied to a real editorial or product decision.

Photo and credit

The image shows a retail setting from 2008. It does not describe current sales conditions or this publication's distribution.

1. Write the decision brief

Complete this sentence: "When the results arrive, we will decide whether to..." Examples include changing issue frequency, adding an audio edition, revising a department, testing a student plan, or redesigning renewal messages.

2. Define the population and sample

Name the group the conclusions are intended to describe: all active print subscribers, recent digital purchasers, lapsed annual subscribers, newsstand buyers, newsletter readers, or another defined population. Then define how people can enter the sample.

An open link on social media describes volunteers who saw and chose that link. It does not automatically represent subscribers or the public. A survey sent to all active subscribers can still overrepresent people who open email, feel strongly, have time, and can use the survey format.

The Journalist's Resource's explanation of a nationally representative sample describes the order of operations. Researchers define the target population first, then build a sample meant to resemble it on characteristics that matter: age, income, or affiliation.

Its counter-example is blunt: interviewing thousands of people at shopping malls in one region does not describe a country, however large the count grows.

A reader survey works the same way. Its population is a magazine's own defined audience rather than a nation. Keep invitation, response, eligibility, completion, and analysis counts. Plan accessible recruitment and survey operation. Avoid collecting identity or sensitive data that the decision does not require.

3. Build the questionnaire

Use a short route from recent, concrete behavior to evaluations and then optional background items. The Pew Research Center's guide to writing survey questions explains how wording, answer format, question order, mode, and pretesting affect responses. It also recommends keeping wording and context stable when measuring change over time.

Apply these rules:

Instead of "How useful and well designed was the new app?" ask usefulness and ease of use separately. Someone may value the content and struggle with the interface.

4. Test the instrument

Ask several people from the intended population to think aloud while answering. Check what they believe each question means, how they recall an answer, whether any choice is missing, and whether the route fits their situation.

Run a small pilot. Inspect completion time, device use, skipped items, breakoff points, repeated patterns, open-text quality, and technical errors. Test keyboard use, labels, focus, zoom, errors, and screen-reader output. Revise before broad fieldwork, then freeze the final wording.

5. Recruit without pressure

State who is conducting the study, why the person was invited, approximate time, how responses will be used, whether answers are confidential or anonymous, any incentive, and a contact. Do not make access to paid content depend on answering optional research.

Send reminders only within the disclosed plan. Prevent duplicate completion where the design requires it without collecting more personal data than necessary. Keep incentives proportionate and report them.

6. Analyze against the sample

Clean impossible combinations, duplicates under the stated rule, and test entries without hiding unfavorable responses. Use the right base for each percentage and display the base size. Separate "not applicable" from missing answers. Compare groups only when sample sizes and recruitment support the comparison.

Do not turn a difference into a trend from two mismatched questions or field methods. Treat open comments as examples of experience, not a vote count, unless they were coded through a documented process.

7. Report and act

Publish or archive the population, sample source, invitation method, field dates, incentive, exact wording, question order, response and completion counts, weighting if any, analysis rules, small-base cautions, and known limits.

Turn results into a decision table:

Common questions

How long should a reader survey be?

Only as long as needed for the decisions. Test actual completion time on phones and with assistive technology.

Is a large response count representative?

Not necessarily. Recruitment and nonresponse determine who is represented more than raw size alone.

Can survey answers replace behavioral data?

No. Reported preference, memory, and observed use answer different questions. Compare them without forcing agreement.

Should every respondent receive the same questions?

Not when routing can remove irrelevant items. Keep trend questions and experimental forms controlled and documented.