What went well at the 2019 Open edX conference in San Diego? What could have gone better? Add bullet points here, or send an email to oscm@edx.org if you want a more private channel.
Went well:
- Ned caught a behind-the-back throw while juggling on stage
- Nimisha showed off her fresh new juggling skills to a wide audience
- Thanks to the people who went out during the keynotes and stopped the random loud construction noises
- The #openedx-2019-stories Slack channel worked well, lots of great stuff in there
- Is someone tasked with going through #openedx-2019-stories and reporting out to the rest of the company?
- Thank you for including vegetarian options with each meal
- Signage with arrows were surprisingly accurate this time around. (Not sure how much control over architecture we have... but it worked!)
- Separate locations for plenaries and breakouts/talks was great. Outside space was well-utilized!
- ID Summit as an area of focus was well-received.
Could have gone better:
- Why did the laptop fail, forcing Ned to juggle on stage?
- Let's bring a can of WD40 next time; there were some really squeaky conference room doors there
- For lightning talks, it would be helpful if the tech person renamed the files with the speaker's name-- a lot of them turned out to be called openedx2019_presentation or similar
- The pastry breakfasts weren't useful for me; it would be nice if each meal had some sort of protein
- Would be nice to have tea available every time there is coffee
- Dependent on the specific room door setup, but people entering/exiting during the sessions was sometimes very disruptive. Maybe consider limiting entrance after session start for doors that are right by the presenter
- There was (some) confusion around a-la-carte pricing of Tuesday and Friday.
- Would be good to have representatives from UX and Data Science/Eng.
- Reminding folks to provide per-session feedback earlier in the conference.
- We were scrambling for power strips during the tutorial sessions. Especially for ones that last three hours long and involve dev work, we need power.
- Not having an accurate estimate for how many people would attend caused at least one tutorial session to drastically underprovision their cloud environment for the tutorial, causing multiple issues.
Ideas for questions to ask attendees on a survey:
- (ideas here)
- Sched prompts for feedback at the end of each day. Can we leverage that better? Is there more success with that mechanism than a big week-later survey?