Conference Programmer: what’s in a name?
From 1999 until 2010 the majority of my jobs in the world of events included a large chunk of conference producing. Luckily for me it was a part of my job that I loved. To give you some idea of my production credentials, in one role, while doing a score of other things, I put together close to 40 half day or full day conferences a year. I’ve programmed more than 500 conferences. I think I have the badge if not the T-Shirt!
In general as a ‘Conference Producer’ the targets I was set were:
1. To run a set number of conferences a year normally between 20 – 40
2. To achieve a score above 7 out of 10 for content (as judged by delegates)
3. To generate a profit from every conference and a BIG profit overall
4. To generate content that was attractive to sponsors (in order of course to generate revenue)
How to achieve those targets?
In order to hit my goals there was really only one way to approach each conference and that was to treat it very similarly to the previous one, and the next one (see above image!)
Here are a dozen assumptions I made when I organised my conferences. My challenge for those organisations that still employ Conference Producers: have these changed?
1. Hire a good value venue and ensure that it is flexible enough to allow me to change from classroom layout to theatre should my numbers increase.
2. Try to attract the highest level speaker possible.
3. Realise that all speakers will know how to deliver the content and they wiill certainly knew more than about it than me.
4. Speakers are doing us a favour by speaking so don’t be too pushy.
5. The chairman’s role is simply to keep things to time.
6. People rarely have questions after a session and not to worry about it.
7. The more people and companies on the programme the better.
8. The basic format – with four sessions before lunch and four sessions after lunch – was tried and tested.
9. Refreshment breaks and registration was where delegates networked. Assuming they actually wanted to.
10. Sponsors / exhibitors are a necessary evil.
11. Always encourage speakers to use PowerPoint.
12. Encourage them to use / the lectern / the lectern mic (to keep down costs).
What is success?
There is no doubt that the above approach can bring success: if that success is measured against the set criteria that I outlined above. But I wonder how long it is that we can treat our conferences as a product and not a service? I wonder how long before large numbers of delegates join the small numbers already dropping off the scene and stop attending the conferences that are ‘programmed’ on the above criteria.
In my next Blog should this generate some more discussion and comment I will list what assumptions a Conference Architect should take and as importantly what support their organisation should give them.