How to run a Hackathon
We’re big fans of the hackathon at Gravitywell and with a few under our belt, it’s time we shared our experiences with others and offer some tips on how to run them.
Table of Contents
Why do it?
There’s usually no money involved so why should you use up valuable studio time on a Hackathon?
Hackathons bring the team together and teaches people to cooperate. But the bonding experience is vastly better than one of those cheesy team-building exercises that nobody really wants to do and probably include awkward interactions involving planks and bits of rope.
Ideally the Hackathon would be a break from the normal routine in many ways. The process should be exciting, refreshing and energising. You’re working on something for yourselves and not the client. It’s an opportunity to try new tools and techniques. Everyone should feel invested in the outcome and enthused by the end of it.
Encourages creativity from all disciplines
Short deadlines will teach you to compromise. Designers will be forced to wrestle with the balance of quality and delivering on time. Everyone will need to make quick, rational decisions. You’ll all be forced to find creative solutions that work for the deadline, rather than a vision of perfection.
R&D tax credit
If you’re a company in the UK, the government will give you a tax rebate for investment in R&D. On its own, it’s not a strong enough reason to plan a Hackathon, but it’s certainly a sweetener!
Of course it’s difficult to measure the Cost vs Benefit of a Hackathon and everyone’s mileage may vary. But from our own experience, it’s brought us closer together as a team, taught us new skills which we’ve applied to client work and given us new internal projects to take forwards in the future.
Reactions from clients
At some point you’ll need to let your clients know about your plan for a Hackthon. Perhaps their work will be put on hold or you’ll need to ask for their patience during the event. Of course you should warn your clients in advance but try to extol the virtues of a revitalised and more committed team.
So how do clients react?
A few have said that it sounds like an excuse for a company holiday. While it’s true that having meals together and the odd evening drinking cocktails by a pool are a lot of fun, we’re usually working longer hours than we do back in the studio.
But mostly clients have been very positive and supportive. They can see the value and are keen to follow the progress. Some have even asked to come along too. You might be surprised by the reactions from your own clients.
How to pick a project
“Tinder for cats” - is the suggestion made at Gravitywell every year, mocking the apparent silliness or arbitrariness of previous projects rather well. But in a sense, the actual project chosen doesn’t matter - it’s the experience of the event and the skills we all learn that are the true value of the Hackathon.
However, you may want to consider the following factors when selecting a project for your event:
Try to make it multi-discipline and as inclusive for the whole team as possible. Something that requires input from everyone and should keep them busy and challenged throughout. Not an easy task!
Can you solve a problem for an existing client or a client you’d like to work with? Having a ‘real’ project to work on will help you identify the requirements and provide you with knowledge about actual users rather than imaginary ones. Plus, it’s likely your client will be very grateful!
Maybe you’d like to help a charity? You’re probably not going to be able to solve world hunger but it might be worth speaking to a local charity to see if you can identify suitable project for your team. Perhaps an app for volunteers or a system that automates processes to save administrators time.
It might be that someone in your team has their eye on a new technology or software library that they’re itching to try out. Discussing its capabilities or future potential might tease out a possibility for the Hackathon.
You could even throw open the topic to your team - why not ask them if they can submit ideas for the event.
Here’s a few topics we’ve covered in the past:
- Mobile app that matches your tastes to tshirt designs from dozens of different designers
- Buy and sell personal items, like ebay, but via a chatbot interface only
- A system for scalable simple multi-player games and interactions, controlled with mobile phones and displayed on giant screens, for use at conferences
Where should we hold the event?
Preferably out of the studio. A different place, somewhere people can’t easily fall into the familiar routines or retreat into isolation.
We’ve taken the route of hiring holiday houses, off season, in Cornwall or Majorca in the past. Yes, it does mean that some of us might be working on a kitchen table or a sofa in the conservatory for a few days but the change of scenery shakes things up in a positive way.
A week away from home may present problems for the staff especially if they’re not used to being separated from family for so long. This is something you’ll have to discuss with your team in advance to see if there is a workaround.
If going away is impossible then try to change the environment in your studio during the event. Can you move the desks around or switch seats to encourage different conversartions and working practices?
What about client work?
What can you do about existing commitments and problems or opportunities that can emerge during the week?
The key is to provide as much notice as possible. Then perhaps the odd reminder, nearer the time.
Be clear. Explain what you’re doing and why. Provide details of the plan with dates and times. Point out that this is important for the team and the benefits will ultimately be felt by all clients.
Be strict. Allow emergency contact only.
You might be able to redirect the studio phone to the mobile of someone on the Hackathon who should then try to deflect calls or arrange callbacks for after the event.
If you have support commitments then perhaps build in specific parts of each day to handle support queries and therefore minimise the impact on the rest of the hackathon time.
Tips and Techniques
Hold Stand-ups. Time is a premium so long meetings are going to eat into what little you have and set a lethargic pace for the week. If you’re not doing stand ups in the studio already then consider starting immediately! On a hack they invaluable for finding out where everyone is without wasting much work time. Is anyone twiddling their thumbs? Is anyone going down a rabbit hole that could be sidestepped easily? You can find out in just 5 minutes every day.
Presentations or demos at the end of every day. This forces people to think about deliverables every day. It means everyone is clear on what is actually working, rather than just hearing what is being worked on. The pressure of having to present means that the team is more likely to test their work before demo time.
Encourage the team to find compromises and solutions between themselves. This seems obvious but if you don’t already have this culture then it may be hard to introduce.
Your team’s dictators and prima-donnas may need to restrain themselves for best results. Egos need to be parked.
Consider how much planning and research you want to do in advance. Although starting the conceptual process during the event can be fun, you might want to arrive with a pre-prepared topic in order to save precious time. It’s easy to lose a day exploring ideas for the event so it’s useful to have some key decisions made already, but at the other end of the scale be careful not to dictate too much otherwise the project will lose the sense of discovery and excitement.
Ask if you can you bringing in external people. Collaborating with an subject matter expert or even a client might give the project some much needed guidance or clarification.
Don’t forget that your team is sacrificing time and energy to be at the event; don’t forget to treat them well and try to make the event memorable for all the right reasons!
Hopefully you’re now confident enough to organise your own Hackathon event.
Let us know on Twitter about your Hackathon. Maybe we can even collaborate on the next one?