With EIBTM and the UK National Association Congress both taking place in the next week it’s no surprise that I’ve been asked on several occassions to tell people what a “Conference Architect” is and does, and how it’s different from someone who just puts a programme together. Well, if you attend either of the events you will hopefully see the difference but if you don’t I would like to explain what I think a conference architect is and why I use this phrase to describe part of what I do at Gallus Events.
The role of the Conference Architect has evolved from the job of the traditional Conference Programme Developer. Rather than simply fill the slots with speakers willing to speak, a Conference Architect spends more time selecting speakers and ensuring that they deliver the relevant content, which makes an impact on delegates personal or professional life in an engaging way.
A Conference Architect also understand the finer details of meeting design and will take into account the environment and layout of the room as well as timings and the texturising of the learning that takes place.
A Conference Architect is also knowledgeable about event technology and social media and will engage them when appropriate in your event.
Unlike a traditional Programme Developer, where the total focus is on maximum income generation for the organisation, a Conference Architect’s focus is on maximum deliverable benefit to delegates and all others involved in the event process. Where events are run for profit a Conference Architect will ensure the event is designed to ensure a good return for the organisation. Does this sound like a traditional Programme Developer to you?