Are you closing the loop?
If your association does a call for presentations for any of your events, do you provide feedback to those submitters whose presentations were not accepted? Or do you simply send a generic "Thanks for applying but your presentation was not accepted" note? If you're not providing feedback on WHY the presentation was rejected, you're missing an opportunity to educate your audience and help them improve their submissions next time.
I recently served in a volunteer capacity evaluating submissions for a technology conference. There were over 200 submissions received, with fewer than 60 sessions being selected. Several times the committee agreed that a particular session would be more appropriate for a different conference hosted by the same association. But when I inquired if this feedback would be shared with the applicants who were being rejected, I was told no.
I understand it takes more time and effort to explain why a session proposal was rejected, as compared to just sending a generic rejection letter. But providing no feedback at all simply frustrates the submitter ("What was wrong with my application?") and your organization is missing a tremendous opportunity to help improve applications over time.
Close the loop! Help educate your submitters!
![]()
Wes's Wednesday Wisdom Archives
A poor launch can set the stage for YEARS
A poor launch can set the stage for YEARS It is not uncommon for me […]
Have the courage of your convictions
Have the courage of your convictions Having the courage of your convictions means you’re willing […]
Even your online directory is out of date!
Even your online directory is out of date! Back in the day of printed directories, […]
Start small
Start small When I work with my clients on projects that involve measuring member engagement, […]
Some context, please
Some context, please A pet peeve of mine: A report about associations (e.g., marketing benchmarks report) where […]
Eventually automated emails get ignored
Eventually automated emails get ignored During the discovery and development phase of implementing a new […]
The challenge the AMS providers see
The challenge the AMS providers see Over the years I’ve asked AMS providers what they […]
Be careful about “solutioning” too quickly
Be careful about “solutioning” too quickly One of the great things about software developers is […]
What’s our next action?
What’s our next action? As you can imagine, I spend a lot of time in […]
Don’t automate for the sake of automation
Don’t automate for the sake of automation I’m the laziest person in the world. I […]
