Around the time I was starting as community manager, we had suggestions to start time-stamping the demos, and I think that has been a helpful exercise for everyone.
At the start of the year, we had suggestions to group the demos into user-focused and dev-focused, as well as to make an effort to group the running order into a logical sequence. I think this is also good practice and where we can, we do.
For a while now, we have added redmine tickets so that anyone who is interested can explore more information about this feature.
Last demo, we started adding the version number of Foreman/Katello where the demoed item can be found (with a caveat that things change).
All of these changes originated from feedback from Foreman demoers and the community around Foreman. I think that all are positive and all are in the spirit of getting as most out of the demoes as possible.
Starting with demo 101 (I’m almost finished ) I will also start writing a summary and include this on the demo topic along with the timestamps. I have heard feedback that some people do not like to watch the demo. While I would love if people watched the demo and also asked questions/ felt comfortable giving feedback and opinions while live, I understand that we all have different styles, and also adding summaries might help a wider group of people access the demo.
Over the last two demos, I have received feedback that viewers would love if the person who is demoing could provide context before they begin the demo themselves. Some people do this naturally, while others launch into the technicalities. Personally, I think that giving some context to your demo, for example, a brief summary of the workflow or the user story that this helps to progress, would be a great benefit.
I want to ask what you think about this and also if you have any other ideas/feedback for improving the demo?