
Recently I “produced” my first Live Event in Teams: a symposium with the project presentations of three of our students.
The organisation expected around 100 attendees, so I tried to push them towards the regular Teams Meeting with some extra control measures (see my earlier post). But they really liked the moderated Q&A, so a Live Event it had to be.
As I need to learn to work with this anyway, I suggested to be the producer, so I could create procedures and scripts so they know how to do this themselves afterwards.
How a Live Event works
Scheduling a Live Event is easy, however I find being a producer quite some work. Tracy’s video makes it all appear fairly simple, but to be honest, I have been struggling a bit with this tool and needed a number of tests to get to grips with it. Perhaps it was our complex setup, perhaps I need more practice.
What have I learned?
1. Give your event a good title
When your audience is entering the event, and the event has not started, all they see is the title of the meeting. Make it a clear one.
2. The producer should just produce
Although you can be producer AND presenter, I would advise against mixing these roles unless you are an experienced one-person-show. If there is a welcome or break slide to be shared, leave it to someone else.
When you (producer) share content or your desktop you do not see your dashboard, which makes it hard to do your work as a producer. And when you go back forgetting to stop sharing you will end up with a very annoying caleidoscope effect. If you do stop sharing there will be an annoying message that the Event will continue soon. You can not win.

3. Keep the # of presenters to a minimum
When I did my first Live Event, a number of people were interested to see how it worked so I added them as a presenter. That provided some challenges as I could not see them all on my 13″ laptop screen, hence I could not select their video to show.
Additionally, during one of the breaks one of the “curious extra’s” decided to move to another room, accidentally sharing her screen. š± She did not have her earbuds in, nor was she looking at the chat, so we could not warn her that her living room was visible for all to see. š

4. Schedule a separate Live Event as a test run
As this was new to everyone we decided to do a test-run a few days before the meeting. You need to create a new Event for that, as you can only “use” a Live Event once.
5. Have as few transitions as possible
Transitions are a bit of a logistical nightmare. I had expected that when the next presenter shares their screen, that would pop up in the Queue, so I could add the speaker’s video and set it all Live at the right moment.
But it does not happen that way – presenters generally override their predecessor’s screen during the event, causing a need for the producer to frantically switch to the correct presenter. Or, they stopped presenting and then their face filled the screen.
So try to limit the number of transitions to keep your producer’s sanity š
6. Test starts, stops and transitions
We really needed this as presenters had no clue as to what to expect. So we went through the programme of welcome talk, first speaker, etc. People could practice how to share their screen, when to stop, how transitions worked, what they had to look out for, what not to do, etc.
7. Invite an attendee to ask questions
It helps to have an attendee in the test run to ask a few questions, so new presenters can learn how to handle the Q&A’s.
8. Use “desktop” rather than “content” for sharing (depending on setup)
We found that the following combination resulted in “flickering tabs” which is a major distraction:
- Using Google Chrome as a browser
- Using PowerPoint Online for your presentation
- Selecting “content” rather than “desktop” for sharing
So: ask people to present with PowerPoint desktop app (if they have that) or ask them to share their desktop.
Or use Microsoft Edge, of course. š
9. Create a script
It may be good to have a timetable with who does what when and the timing of the breaks. It was good for the presenters but also for the producer, as I could then check when I needed focus and when I could relax a bit.
10. The “crew” needs the Teams Desktop App
One of the presenters logged into the test meeting via the web app and she entered the meeting as an attendee. Fortunately all our employees now have the Teams desktop app so all of us can produce or present Live Events (despite the fact that 90% of my colleagues have an F3 license, which is web + mobile apps only).
11. Make sure the producer has a large screen or monitor
As mentioned in item 3, I needed a larger screen to see all presenters, but also to see the Live result better. If your screen is too small, you will get prompts to expand your screen. Fortunately, I have an extra 23″ monitor.

12. Teach presenters how to unmute
EVERY presenter forgot to unmute themselves, so I had to jump in and ask them to unmute. š It was nerves, I get that, but I did not like having to intervene. However, I later heard people actually appreciated me jumping in, as it showed that someone was noticing, saving a lot of questions in the Q&A.
13. Avoid having an audience in the same room as the presenters
Our students really wanted to have some family in the room, so they would not have to talk into a void, but it posed extra issues:
- Due to the delay that a Live Event has (about 1 minute) in image and sounds it was impossible to project the Live Event in the room with the presenters.
- Therefore we needed an extra person to click through the presentations from a separate laptop in the room. We could perhaps have duplicated the laptop screen but it would have to be changed between speakers and I know that some situations/laptops do not support duplication.
- I was producing from home, and I did not exactly know what tech was available in the convention room, which made it difficult to explain to the presenters what to do in the room (which was not my responsibility anyway – that was producing this Live Event)
- Presenters got easily distracted by the audience so the MC’s had to make sure everyone was back at their laptops in time for the next presentation – while this will also happen in a physical-only situation it is less annoying there as everyone can clearly see what is going on. People online do not see that.
- Your laptop’s microphone is not good enough in this situation – it usually sounds rather tinny and will pick up sounds from the surroundings and that can cause an annoying reverb – so your producer must mute you. Presenters, use a headset and keep it plugged into your computer at all times!
- The presenters also had to find a good position in the room with a good background, which needed time during set-up.
- Questions from the room could not be heard and needed repeating by the MC, which they sometimes forgot. Which led to Q&A’s.
14. Learn basic sign language
This may seem silly, but as everything the presenters and producers say when you are Live is audible for everyone online, you can not really talk about things, and not everyone was watching chat all the time. So sometimes I wished I know sign language to tell people “get ready to present the break slide” or “unmute”.
15. Producer, mute yourself when going live
Do not say “Here goes” or something similar when you Go Live, because it will be recorded in the video. Guess how I know this? š
16. Download the attendance report during or immediately after closing the event
When someone from the “crew” enters the Event after it has closed, it will overwrite the attendance report. By the way, the official word is “Attendee engagement report”.
17. The “crew” can only view the recording from the web app, even when they use the Attendee link
If they click the Attendee link and select the desktop app, they go into the “back end” of the meeting, overwriting the attendance report. See item 15.
18. The video lives in Azure, not in Stream
Do not look for the video in Stream – it is not there. You can download it from the meeting information and upload to Stream if you want to make it available for longer term. (It is available on Azure for 180 days)
There’s some good Microsoft info about post-event actions.
And if you know of a way to make transitions smoother, please let me know! If you have any other “gotcha’s” to share, they are welcome too!