For event organizers, the day before and the week after
Survey AfterStart from the decision, not a question bank.
List the decisions waiting on feedback and your draft questions. Free in your browser: every question tied to a decision and the person who makes it, wording that asks what people did rather than what they would do, how long the survey should be, when answers must be anonymous, the channel against real response rates, a send within 48 hours, and what you send back. A run writes the design memo, or the survey itself.
1 The event and the draft survey free
2 The survey, checked free
What the page flags
Question by question - which decision it serves
Send plan and response rates
Depth, channel, closing the loop
3 Design memo or the survey metered
Pricing as soon as the session is ready...
Sign inThe reply could not be read. Here it is as it came back:
Depth and channel
Question by question
Anonymity and timing
Back to respondents
Response rates
Record
Caveats
The page's check of this reply
4 Saved designs
How it works
Each question earns its place by changing a decision someone owns; the rest is curiosity, and every extra question costs responses - a two- or three-question survey gets more than twice the median response of a seven-question one. Ask what people did ("which sessions did you attend?"), not what they would do ("would you attend a workshop day?"). Questions about judges, mentors, inclusion or a named person need anonymity, and anonymity rules out a prize draw, which needs a name.
Emailed surveys draw roughly 10-30%; a code shown in the room while the event is still happening draws 40-60%. Send within 24-48 hours, remind at most twice, and give a hackathon a second short survey one to two weeks later. Under about one in ten answering, the collection failed, not the audience. And tell respondents what you changed - people who hear nothing do not answer next year.