Turning event feedback into prioritised actions
The feedback is in, the comments are coded, and the committee now asks what you will actually change before the next edition.
The short answer
Rank each finding on three things: how strong the evidence is, how much it matters to your event objectives, and whether someone with authority can act on it. Choose a small number of actions, give each an owner and a date, and record what you are deliberately not acting on.
A finding raised once is a lead to check. A finding that appears in several sources, from different groups, is a stronger basis for change.
Separate the finding from the fix
Delegates tell you what they experienced, not always what to do about it. Write the finding in plain terms first, such as breakouts ran over time, then list possible fixes separately.
This stops the loudest suggestion from becoming the plan before anyone has checked the cause.
Three questions for each finding
| Question | What to ask | Why it matters |
|---|---|---|
| Evidence | How many sources support it, from which groups, and how reliable? Check the respondent bias review. | A single comment is a lead, not a trend. |
| Importance | Does it affect an objective from your feedback objectives, or only comfort? | Protects the event's purpose. |
| Actionability | Who has authority to change it, and is it within the next edition's scope? | Prevents actions with no owner. |
A prioritisation sequence
- List findings from scores, coded comments and your own observations, each as one plain sentence.
- Mark the evidence strength as strong, mixed or thin, and say why.
- Mark importance against your stated objectives.
- For each finding, name who can decide and the earliest date a decision could be made.
- Choose the few actions to take now, the ones to investigate first, and the ones to park, with reasons.
Handling feedback you will not act on
Some feedback is valid but outside your control, such as the venue's air conditioning, or contradicts other feedback. Record it, say who it was passed to, and say why you are not acting.
Telling respondents what changed, and what did not and why, makes future surveys more credible.
Keep the action list small and tracked
- Limit the committed list to what the team can realistically deliver before the next edition.
- Give each action one owner and one date, not a group.
- Add each decision to a decision log so it carries over to next year's team.
- Review progress at a fixed committee meeting.
Worked example · Fictional example
Post-event actions for a members' conference
Fictional organisation and findings, written to show the ranking approach.
Persatuan Fiktif Jurutera Tapak held a one-day conference and coded its comments. Three findings stood out: breakouts over-ran, lunch queues were long, and a few delegates asked for more practical sessions.
The over-run appeared in comments from several groups and in the programme timings, so it was marked strong and tied to the objective of useful learning. The lunch queue came from one table of comments and was marked thin, so the secretariat will ask the venue for its serving arrangements. The request for practical sessions was mixed and goes to the programme committee as a question rather than an action.
| Finding | Evidence | Importance | Who can act | Decision |
|---|---|---|---|---|
| Breakouts over-ran | Strong: several groups plus timing log | High: affects learning objective | Programme chair | Act: set tighter session slots and a chair brief |
| Long lunch queue | Thin: one source | Medium: comfort | Secretariat with venue | Investigate first |
| More practical sessions | Mixed: different views | Unclear | Programme committee | Park: raise as a question |
Use this yourself
Feedback action prioritisation worksheet
Copy into a spreadsheet and fill one row per finding. Keep wording plain so the committee can read it quickly.
- Findings you are deliberately not acting on, with a reason:
- What will be told back to respondents:
- Where the decisions are recorded:
- Date the committee will review progress:
| Finding | Evidence strength and sources | Objective affected | Who can act | Decision: act / investigate / park | Owner and date |
|---|---|---|---|---|---|
Handle it in-house, or bring in help?
Your team can usually handle this when
- You have a small number of clear findings and a committee that meets regularly.
- The programme owner can decide most changes directly.
- The actions only affect your own team's process.
Outside planning help earns its fee when
- Findings cross several committees, suppliers or departments that each hold part of the fix.
- The next edition depends on decisions that keep slipping between meetings.
- Feedback is contradictory and the committee needs a structured way to decide.
Want actions turned into a plan for the next edition?
If your team has the worksheet filled in but nobody owns the follow-through, an Event Blueprint can carry the chosen actions into the next edition's scope, timeline and responsibilities. The ranking stays with your committee; the plan records who does what and by when. Use the feedback questionnaire builder to link next year's questions to these actions.
Questions organisers ask
How many actions should come out of a feedback round?
Fewer than you think. A short list the team can finish is better than a long one nobody owns. Park the rest openly and revisit it at the next review.
Should the loudest comment get priority?
Not by default. Weigh how many sources support it, from which groups, and whether it affects an event objective. A single strong comment can still be investigated.
Do I need a scoring formula?
A simple strong, mixed or thin label with a reason is usually enough. Numerical scores can look more precise than the evidence allows.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.