Created
August 16, 2019 23:52
-
-
Save mikewilburn/94279ba82a3be015c137fd1e97b6ee5a to your computer and use it in GitHub Desktop.
GeoDev Meetup takeways
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| How do we measure ROI from each GeoDev Meetup? | |
| - # of attendees | |
| - # of redeemed voucher codes | |
| - # | |
| How can we maximize participation? | |
| - decide date sooner | |
| - consider dropping themed approach? | |
| - | |
| - evangelize sooner and via more channels | |
| - Calagator | |
| - Blog about meetup in advance | |
| - Meetup.com | |
| Meetup prep: | |
| - hold pre-brief meeting with Amy | |
| - set up registration tables | |
| - add stickers, pins, pens, & other small swag | |
| - put out name tags | |
| - drink tickets | |
| - get registration app working | |
| - set up Picard conf rm | |
| - confirm projector is working | |
| - remove tables to make room for chairs | |
| - use displays to mirror emcee slidedeck through the night | |
| Other notes: | |
| - charge code is for two individuals only | |
| - if using two registration computers, same login creds should be used on each | |
| - other GeoDev meetups don't go with a theme or keynote; emcee generally prepares 30-45mins of material to update guests, then guests give 3-4 lightning talks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment