Skip to content
EventConsultant.com.my

Connecting seminar feedback to the next learning programme

You collect feedback forms after every seminar, and the next programme looks much like the last one.

Ask about an Event BlueprintOpens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.

The short answer

Tie each feedback question to a learning outcome or a decision you may actually change, such as format, level, length or speaker. Then book a short review meeting before the forms are collected, with an owner who records what will change.

Feedback that nobody is scheduled to read becomes an archive, not an input.

What to ask, and what it informs

Question typeExampleInforms which decision
Outcome checkCan you now do X? (yes, partly, no)Whether the programme met its outcomes
LevelWas the pace too fast, about right or too slow?Prerequisites and mixed-level handling
FormatWhich session gave you most to apply?Mix of talks, exercises and discussions
MaterialsWhich take-home item will you use?What goes into the next pack
LogisticsWhat got in the way of learning?Venue, timing, room layout
Next topicsWhat would you like to learn next?Topic list for the next programme

Steps from feedback to action

  1. Write the feedback questions from the outcomes in designing around learning outcomes, keeping to a few focused questions.
  2. Choose when to collect: on the day for response rate, and a short follow-up a few weeks later to see whether participants applied anything.
  3. Name a person responsible for compiling the results, and the date of a review meeting.
  4. At the meeting, sort comments into change, keep, and cannot change, with a reason for each.
  5. Record decisions in a short log, with an owner and a date for each change.
  6. Tell participants what you changed, in the invitation to the next programme.

Failure points

  • Forms with many questions that nobody analyses.
  • Collecting after people have left, so only a few reply.
  • Treating one loud comment as the verdict.
  • Changing the programme without checking whether the outcome check supports it.
  • Not telling participants what changed, which lowers response next time.

Using the next programme's timetable

If feedback points to more practice time, test the revised timetable with the programme duration checker before agreeing the change.

Worked example · Fictional example

A fictional finance-skills series

Fictional organisation and figures, for illustration only.

Persatuan Fiktif Kemahiran Kewangan runs two seminars a year for about 60 participants. Feedback shows many want more practice and that the afternoon felt rushed.

At the review meeting, the education owner decides to cut one talk and extend the exercise block. The change goes in the log with an owner, and the next invitation says: you asked for more practice time, and the afternoon now has a longer exercise session.

Use this yourself

Feedback-to-action table

One row per theme. A theme without a decision is parked, with a review date.

Theme from feedbackEvidenceDecision (change, keep, cannot change)OwnerDateTold to participants?
Example: afternoon felt rushedPace question and commentsChange: cut one talk, extend exercisesEducation ownerBefore next invitationIn the next invitation

Open the tool: Event programme duration checker

Handle it in-house, or bring in help?

Your team can usually handle this when

  • One seminar a year and a committee that meets after the event.
  • A short form and a person who reads it.
  • Changes are easy to make.

Outside planning help earns its fee when

  • A series of programmes across the year with several speakers and venues.
  • Feedback arrives from different forms and systems and needs combining.
  • Decisions need tracking against budget, venue and speaker availability.

Want feedback to reach the next plan?

An Event Blueprint for your next programme can include a feedback design tied to outcomes, a review date, a decision log and the changes carried into the new session plan and timeline. What to change stays with your education owner.

Ask about an Event BlueprintOpens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.Event Blueprint (planning pack)

Questions organisers ask

How long should a feedback form be?

Short enough that most people finish it on the day. Keep the questions to those you can act on.

Should feedback be anonymous?

Often yes for candour, but allow an optional name if you want to follow up.

Do we need a follow-up survey?

A short one a few weeks later shows whether participants applied what they learned, which on-the-day forms cannot show.

What if feedback conflicts?

Return to the outcome check. Change what the evidence shows is blocking an outcome, not what one person prefers.

Related resources

Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.