The Basics: A hackathon goes by many names – hack day, hackfest or codefest. Essentially, a hackathon is a design, build and demo sprint-like event where you get random people to team up and collaborate intensely, usually for 24 to 72 hours. The skills required are typically in software development, graphics or human centered design; user interface and user experience design, project managers, and domain or subject matter experts.
The organizer will provide some challenges, and the participants will form teams and try to come up with their best ideas/solutions. Eventually, the team(s) who presented the best ideas/solutions will get to win some cool prizes. Prizes can be cash or some gadgets.
Here are some thoughts about how to make the most of your participation in a Hackathon.
Ideate – It’s important! You should be prepared to spend time brainstorming… first defining what you’ll be building. Start with the kind of challenges or problems presented by the organizers. Social or support forums are also a great source of insights into what people are frustrated with, their problems, and what they’re asking for. This way you can be certain that you’ll be developing a solution that provides value and solves a problem.
Do not take on an idea because it sounded the most impressive or tech savvy. Think about the kind of impact your work will have on users. Take time to make sure that your idea is impactful and this should save you time down the line when you need to put all the features together.
Sometimes the idea falls into your lap in a flash, and other times it takes some digging to lock onto a great idea. The hackathon will teach you how to be patient under pressure. Keep in mind that at some point (ideally before the end of the first day), you definitely need to start building.
The All Conquering Team – To win the hackathon, you have to have a dream team. Usually the first thing to do when you get to a hackathon is to scout the registration form to get a sense of who else (and what skill set) is around. Often your team will be random people. Your goal is to locate people for these 3 key roles and ask them to join your team (would be great if you yourself are one of these 3 as well):
- The Dev/Coder — this is someone with front-end development experience. mobile development is even better. If your team doesn’t have a single person who can code, it’s time to find one.
- The Presenter/Pitch maker — this is someone who will sell your idea to the judges. You need a good mix of confidence and empathetic charisma. If your team can’t sell, it won’t matter how great the idea is.
- The Designer — this person understands Human Centered Design – they know how to start with people, and then add technology to the problem. It would be great if they are good with user interface and user experience design. This role is a strong recommendation.
A hackathon is very short. Time flies when you are having fun, 4-5 people are trying to break the ice, pitch ideas, win over team-mates, and still get working. This is the time to communicate openly about what you think (and know) is incredibly helpful. If you have a question, ask for clarification. If you think of a better way to solve a problem, tell your teammates. Don’t hope that someone will see it the way you see it. Make sure that everyone is on the same page – this will save you time down the line.
An important part of finding a good team is determining to be a great team member. Hackathons are high stress, so you want to make sure you can rely on your teammates and they want to feel the same way about you. There is no time to worry about how or whether you will get along with a teammate. Going into a hackathon with people you have worked with before can save you the mental stress and energy of figuring things out during the hackathon, but you won’t always have this opportunity.
Figure The Heart and Soul – Figure out what your hackathon host and sponsor are looking for. Some hackathons will be more impact driven while others may be more technology focused. Knowing the focus of the organizers will help you decide how to narrow down your project idea. If they have organized previous editions of the hackathon, research the winning ideas. See what ideas were accepted to participate. Researching each judge’s background before the pitch can also make a difference on how well you do in the competition. Without a direction, you won’t be able to get to where you want to go.
During the event, make time to talk to the organizers and sponsors – figure out if there are products you will have access to which may help you overcome roadblocks. Talk to them about the idea you are building and the problem it solves, as well as your approach. The advice you will get ranges from which pathways to not tackle, or how you can do it more efficiently, which will save you lots of time.
If you are a developer/coder prepare by reading all about the APIs you are expected to work with and researching libraries you can use. This way, on the actual day you can focus solely on building your prototype and every team member will be on the same page.
Also, leverage the opportunity to network and find out about what other features or even different integrations their customers are asking for. You might just get your next great product idea from them! Don’t be afraid to reach out and ask for advice.
Learn, Unlearn and Re Learn
Get prepared – there’s going to be a lot of learning that happens in such a short time. I have been to a few and it’s clear that even in such a short time you can learn anything if you really want to. You will likely encounter tools you have never used, get insights into domains other than yours. A hackathon is a great place to learn how to learn. Although winning is nice, learning and appreciating the unique experience that a hackathon offers is something I’ve always enjoyed.
Probably the most important life lesson you will get at a hackathon is how to fail fast, and fail often. You will face some uncomfortable moments such as you are not the only expert in the room, but if you learn to deal with simple and small failures, you will muster the power of persistence, endurance and teamwork. Most importantly, that it’s okay to fail. Every failure will lead to a new insight about yourself and the world. Challenge yourself, and apply for hackathons for areas you know nothing about. You will walk away with newfound knowledge.
Coding – How Deep Should You Prototype?
So you have this cool idea – doing many awesome things – the tricky part is stripping it down to its core and focusing on building only what’s essential to deliver it’s value proposition. After all, you have to make it real. It’s time for the coder and designer in your team to start shining – by building a Proof-Of-Concept (POC). We are not looking for a bug-free solution, infact, you can even have zero functionality. Your audience wants to see, so visualize the solution, help them understand how your idea works. Try to make it look really good. Judges can easily be impressed when they see your team coming up with such a beautifully designed product in a short time.
A good technique is mapping the entire user flow you have in mind. This activity is best done along the product, design, and the dev team so everybody brings their perspective to the conversation. Techniques like Story Mapping should get you started.
After mapping, review the flow with the dev team and make them estimate how much it would take to accomplish that. If it requires more time than the hackathon allows, you’ll have to prioritize features and build only those essential to the core value of the product. If you can, work on everything that’s not code beforehand. It is of top priority that you define the specs of what will be built and that the design team gets mocks ready.
The Pitch – Your 3 Minutes Of Fame.
Your presenter needs to prepare for the presentation. Do not wait till the end to put this together, start working on it while the POC is being built. If the presenter is also the coder, prioritize the POC and then get to the presentation. You will need about 2~3 hours preparing for the presentation. 6 slides, 5 bullets on each. The slides are complimenting your own charm and charisma as you interest the audience enough to buy your idea. There’s no hard and fast rule on slide content, but generally make sure you get this across:
- The problem statement — Prepare a few slides telling people about the background of the problem that you are trying to solve. Remember we are trying to solve a problem using technology.
- Demo — People get bored easily. After telling people what the problem is, straight away tell them how you are going to solve it. Quickly show them your demo and WOW them. (Please make sure your demo works!)
- Compare — Do a comparison. Is there already an existing solution to the problem, if there is, how is your idea better?
- Hidden Slides — Always prepare some hidden slides that discuss potential future enhancements of the idea, business model, and what are some difficulties you faced during the hackathon. These can be useful during the Q&A.
The presentation is the only chance where you can sell your idea to the judges, the only time you can tell them: “my(give) idea(me) is(the) brilliant(prize)!”.
The most meaningful hackathons and experiences revolve around the people you meet, and not just what you build together. Your teammates can turn into future coworkers, collaborators, and friends. You get to know someone very quickly when you have to problem solve together in a compressed time and place – think of it as the perfect relationship icebreaker!
Hackathons are not just pizza, soda and free high speed wi-fi all day (and night) long – they are intense! You will not do much good for your team if you are not in a better shape physically and mentally. You’ll have a much happier and more productive experience if you take care of yourself along the way. Drink water. Take care of potential distractions like small errands – get up and walk down a flight of stairs – do whatever you need to make your hackathon a fun and happy experience, whether that means going home to sleep or taking breaks to get some air and some salad.
Prepare for the prize. Of course it’s not guaranteed, but if you work diligently, and follow the guidance above, most likely you will win something. Plan for what to do with tricky prizes like mentorship and incubation – which might require you to set up a business entity. Decide if a cash prize will go to developing the idea further or not.
Not all hackathons are the same, but when it comes to experiences preparation and good team communication will get you through. Many teams think the best outcome of a hackathon is winning the prize, but the better goal is to build the prototype of a product for which there is a proven market need.
Good luck in your next hackathon!
At Outernet256, we believe that free access to information is a human right. The Internet has dramatically enhanced our ability to exercise this right, but unfortunately most humans cannot access the Internet. Today, over 4.3 billion people cannot connect to the Internet at all and another roughly 1 billion people have their Internet connections censored or monitored. A world where only 20% of humans have truly free access to digital information is unacceptable. That is why we support the creation of Humanity’s Public Library, an initiative by Outernet.
Outernet broadcasts a data signal from satellites that is free to receive anywhere on Earth. While this is not an Internet connection, it is a free stream of critical information. What information is considered “critical?” You decide.
Outernet256 and Creative Commons Uganda are co-hosting the first edit-a-thon for Humanity’s Public Library on July 18-19 2015, at Victoria University, alongside #MozFestEA to decide what is included in this library. Anyone on Earth is encouraged to participate – details on how to have your voice heard in this process can be found at http://editathon.outernet.is. We want to encourage our users to submit their own work and to submit content from Outernet256 that is licensed for redistribution. One such work is this very blog post. Copy these words and post them on your own blog and let’s all gather together and build a #LibraryFromSpace.
This blog post is licensed under CC0 and is free to be distributed and edited without restriction.
A while ago, i posted this blog about my experience with an ISP here in Kampala, and rightly so, i was on the receiving end of a phone call from a “boss” who intimated that the persons who had placed their very lives on the line, to help this frustrated customer, had their jobs “threatened”, and the only thing i needed to do was to save their jobs by taking down the article. I agreed to, because a personal friend used his personal relationships to get me to the help i got, and I valued that. But that did not take away my earlier problem, nor my quest for a solution.
The very insinuation that my blog, notwithstanding its colours, is a forum used to attack the ISP, was at the very least ignorant, and the repeated questioning of my “intentions” and whether i had achieved “what you intended to get” is at the very best, an insult.
I’m convinced, i now know how this nicely well oiled machine called Orange works. And if you think its theft, and arm twisting, i beg to differ. Its more like the shrewdness Jesus feared from Matthew the tax collector.
30th Oct, i loaded credit worth 25k, on my data sim, did not activate a bundle, went on line duly and from 3pm, to 9am the following day (not continuous usage), it was all wiped! 2 Weeks of exchanges between me and customer care yield a number of failed explanations and 2 interesting documents. The first, comes in 3 days after my credit disappears – a time stamped record of all urls accessed from 3pm on 30th, to 9am on 31st October. Total amount of data used: 0.0298 MB.
When you do not activate a data bundle, the system defaults to charging you as a mobile data user – See Cost Here – 0.9 UGX per KB. So you can understand why i had a hard time understanding that 0.0298 MB multiplied by 0.9 UGX per KB would result in 25000 UGX.
(Notes from an Open Session, held at IDLELO 5, Abuja Nigeria, 19th March 2012.)
Working with people we do not know, or see, only talk to them virtually. Nnenna, introduces her self and talks about nnenna.org, a privately run consultancy that has no office and yet maintains a full-blown services for its clients. Work happens in the Virtual Realm. Meeting and working virtually has the advantage of running the least administrative costs.
She is not alone, and as the group warms up to the discussion, we learn about a systems administrator, events manager and a systems administrator. Here are some experiences of virtual workers:
Evelyn Namara shares her experience as a virtual systems administrator, who worked on skype, dropbox and docs, while working with Tactical Technology Collectives (TTC) in Kampala, Uganda.
18.5 yrs as a University Librarian from Federal University of Nigeria, another gentleman is intent on merging virtual library with the manual physical library. He is convinced the ICT Sector does have the solution he needs…
UNESCO Abuja’s National Program Officer for Communications and Information – Oluseyi Soremekun is also eager to see if their information needs can be made Virtual. He contends that the power of information and its access to, by Nigerians is a great need and that ‘virtualization’ of work might have to be a solution.