Turning member feedback into conference programme decisions
The survey results are in, and the committee is about to argue over which comments count.
The short answer
Member feedback becomes a programme decision when each comment is sorted by what it says, how many members say it, and whether the committee can act on it before the next edition.
Not every request belongs in the programme. The committee's job is to decide which feedback serves the conference purpose, and to tell members what it chose and why.
Separate four kinds of feedback
| Kind | Example | Who decides |
|---|---|---|
| Programme content | More sessions on practice management, fewer on regulation updates. | Programme committee |
| Format | Shorter talks, more discussion time, a clinic room. | Programme committee, with the secretariat on feasibility |
| Logistics | Registration queue, room temperature, lunch timing. | Secretariat, with the venue and suppliers |
| Member policy | Member rates, access for retired members. | Council or board, not the programme committee |
Decide whose voice counts for what
A conference serves several groups: long-standing members, newer members, non-member delegates, speakers and sponsors. Their feedback often points in different directions.
Agree before reading the results which group the programme is mainly for. Comments from other groups are still recorded, but they inform rather than steer.
A decision sequence for the committee
- Tag every comment with its kind from the table and the respondent group.
- Cluster similar comments and count how many respondents raised each cluster, noting the response base.
- For each cluster, ask three questions: does it serve this year's purpose, can we do it in the time and room we have, and what would we drop to make space.
- Record the decision as adopt, adapt, defer or decline, with an owner and a date.
- Write a short reply to members covering what was adopted and what was declined.
Where feedback misleads
- A loud minority: one detailed email can feel more important than a hundred ticked boxes.
- Survivor bias: only people who stayed to the end answered, and the early leavers said nothing.
- Speaker popularity mistaken for topic demand. A strong speaker can rate well on a topic few members need.
- Conflicting asks, such as more depth and more variety, which cannot both be met in the same hours.
Close the loop in public
Members who gave feedback and heard nothing back answer next year's survey less often. A short note listing what changed and what did not, with one-line reasons, keeps the channel useful.
Use the same note in the opening remarks of the next edition. See feedback action prioritisation for a ranking method and how to evaluate an annual conference beyond attendance for the wider picture.
Worked example · Fictional example
A fictional accountants' association reads its survey
Fictional organisation and figures, for illustration only.
The Persatuan Fiktif Akauntan Amalan received 132 responses from about 600 attendees. Forty-one respondents asked for more small-group sessions, and nine asked for a later start.
The committee adopted small-group sessions by turning one plenary into three clinics, declined the later start because the venue slot did not allow it, and deferred a request for member-rate changes to the council. A one-paragraph reply listed all three outcomes.
Use this yourself
Feedback-to-decision table
Copy one row per cluster of comments. Fill the decision and owner columns at the committee meeting, not before.
| Cluster of comments | Kind | Respondents (of total) | Serves this year's purpose? | Decision (adopt / adapt / defer / decline) | Owner and date |
|---|---|---|---|---|---|
| Example: more small-group sessions | Format | 41 of 132 | Yes | Adapt: three clinics | Programme chair, by next committee meeting |
Handle it in-house, or bring in help?
Your team can usually handle this when
- The committee meets before the programme call opens.
- One person can tag and count the responses.
- Most feedback is about content and format, which the committee owns.
Outside planning help earns its fee when
- Feedback mixes programme, logistics and member policy and nobody owns the sorting.
- The committee is split and decisions are being reopened each meeting.
- The secretariat cannot also brief speakers, update suppliers and write the reply to members.
Want the feedback turned into dated decisions?
If the survey is done but the decisions keep slipping, a conference project lead can sort the responses with your secretariat, bring a decision table to the committee and track each outcome through to the programme and supplier briefs. The committee still decides what the conference becomes.
Questions organisers ask
How many responses do we need before acting?
There is no fixed number. State the response base next to every finding and treat small groups as signals to test, not mandates. A short follow-up question to members can confirm a doubtful point.
Should we publish the results to members?
A short summary of what changed and what did not is usually enough. Check with the committee before sharing raw comments, because they may identify individuals.
What if feedback contradicts our strategic plan?
Record it, explain the strategic reason in the reply, and refer a pattern of disagreement to the council. The programme committee should not quietly change the plan.
Can we collect better feedback next time?
Yes. Use the feedback objectives page to decide what you need to learn before writing questions.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.