How to Run a Successful Tech Meetup — even if you’re forgetful
Tags: software, events, javascript, leicester
Published: 2018-12-28 18:32:27

---
title: How to Run a Successful Tech Meetup — even if you’re forgetful
published: true
tags: software,events,javascript,leicester
canonical_url: https://blog.joshghent.com/how-to-run-a-successful-tech-meetup-even-if-youre-forgetful-aa990227d7dd
---

![](https://cdn-images-1.medium.com/max/1024/0*6VryEVkxZJBRuPta)<figcaption>A picture taken from the November 2018 LeicesterJS meetup</figcaption>

[LeicesterJS](https://www.meetup.com/leicesterjs/) is born out of the rise of Javascript now being the de facto programming language for a majority of developers. Additionally, we aimed to bring together a tech community in Leicester.

I have been running LeicesterJS now for over 4 months and this is just the start. Before the first meetup, I was very nervous about getting everything together and although it went off without any dramatic hitches, I have learned a great deal and continue to do so with each and every event. Here is some of the advice I wish I had before planning my first meetup.

### Start with the essentials

The barebones requirements from a meetup is a venue and catering. For LeicesterJS, I was able to partner with my current workplace to host the event and foot the bill for the food and drinks provided. In exchange, we give them a plug at the start of each event and they receive exposure to potential hires. Often meetups will be arranged in this manner as it makes organizing the event a lot easier, since you, the organizer, are at the venue ready to prepare anything that is required. If you are looking to arrange your own meetup, kill two birds with one stone and look to see if your employer wants to help.

Next up is the speakers, for this, I turned to developers in my team and asked around if anyone wanted to give a talk. You can also reach out on twitter or to other developers you know in the area. Worst comes to the worst, do the talk yourself!

And with that, we had a meetup! Except for one key thing…

### ….People

You want your meetup to be a success and part of that success can be measured by the attendance rate. Here is how I approached building a community of people from the ground up

- **Get support from co-workers**  — since they know you, it will be easier to break the ice that having a room of strangers
- **Link up with other meetups in the area via Twitter**  — I was very fortunate to have the generous support of [PHP East Midlands](https://phpem.uk/) who canceled their own meetup to join in with the first LeicesterJS (thanks again guys!). It was great to have them along and again, a few more familiar faces
- **Connect with a tech Slack group**  — in my case, [TechNottingham](https://www.technottingham.com/) has a thriving Slack community, I advertised the meetup in their #javascript channel
- **Personal social media**  — in addition to using branded [“LeicesterJS” twitter](https://twitter.com/leicesterjs?lang=en) account. I further advertised the meetup with my own personal Twitter and LinkedIn. Additionally, you can encourage your co-workers to put the word out too
- **Word of mouth**  — you’d be surprised how many people just come to events because they saw it on [meetup.com](https://www.meetup.com/). From my purely anecdotal data gathering, it seems that people mostly came because they saw the event on meetup.
- **RSVP’s matter ** — A day before the meetup starts, it is good to encourage people to update their RSVP status if they are no longer planning on attending. Often times, you will only get 60–70% of the RSVP’s you have on meetup. Make sure you keep track of this KPI and encourage the “regulars” to your meetup

![](https://cdn-images-1.medium.com/max/718/0*5t6kUM-EnedEnCmD)<figcaption>Download the full thing here: <a href="https://gist.github.com/joshghent/2bb9c6e2ce616e29aaa3c7a2895cb17d">https://gist.github.com/joshghent/2bb9c6e2ce616e29aaa3c7a2895cb17d</a></figcaption>

### Processes

After the first meetup, I had a number of people come and ask me for the slides to the talks that had been given. I hadn’t even thought about that! There were a number of these sorts of things that I had to get a process nailed down for.

- **Talk slides ** — stealing an idea from NottsJS, I decided to create a Github organization and put the slides in a repo. It was the least frictionless way to distribute them. I considered using Google drive or some other file sharing service but this would give me difficult URLs that audience members may have a hard time finding
- **Talk ideas ** — after having a number of inquirers about giving talks I again turned to GitHub. The process is now to submit a talk idea as a Github issue on a repo. I have a set template for the issue so there is not any information left out that I may need at the last minute
- **Somewhere to talk ** — despite the bounty of slack groups out there, many requested to set up a Slack group to discuss the meetup and the tech community in Leicester at large. This ticks along nicely. I used [Slackin](https://github.com/rauchg/slackin) on a free Heroku box to create a site for people to get instant invites
- **Introductions**  — the first meet had some very basic introduction slides but I’ve gradually fleshed these out to make sure everyone feels at home. Basic things like pointing out the bathrooms and telling people what time the food will be here and the meetup is expected to end can be very useful to people. Another additional tip is I get people to raise their hand if they with me (and therefore, at the office, we were in), I informed other audience members that they can also go to those ones if they need any help

### Other Pointers

After getting through the above, it can seem as if there is nothing more to do — just grow the meetup right? I fell into the same trap too. But a further refinement came first by introducing a [code of conduct](https://www.meetup.com/leicesterjs/pages/27888143/Code_of_Conduct/). In this document, it outlines how not only speakers, but all those in attendance, should behave and having clear processes for people who do not. It’s worth grabbing a document that has already been written because in all likelihood you are not a lawyer (but if you are, fill your boots!). Additionally, it’s good to have a point of contact (an email address and a person named) who should be contacted if someone wants to report something. Although you hope that something like that will never happen, there has been far too many cases in the tech industry alone that have highlighted that problems with intolerance or any sort of bad behavior towards others is unfortunately not uncommon — often it goes unreported, I hope that never happens at LeicesterJS. Nonetheless, it’s essential to have.

Additionally, you can offer yourself as a resource if any potential speakers need help preparing a talk. Since its beginning, I’ve encouraged first-time speakers to give talks. This can be a nerve-racking experience so give generously to offer support with slides, talk topics etc. The [meetup group slack channel](http://slack.leicesterjs.org) can be a great place to do this.

A lesson I learned early on was to encourage audience participation. It makes the meetup more active and motivates people to discuss afterward as well. Perhaps recommend that your speakers open the floor so to speak with a discussion. Asking if anyone uses the technology being discussed, or ask them if they use an alternative.

Starting your own tech meetup is an incredibly rewarding pursuit, but don’t underestimate its work. It’s also worth noting that, if you are in a smaller city as I am, it is better to support any existing meetups than to create your own. Ask the organizers if you can assist in any way, perhaps arranging new speakers or handling promotion of the event, they would welcome anyone to lend a hand.

If you are in the Leicester area, come along to LeicesterJS — the meetup is every 3rd Thursday of the month!

* * *