Kevin Lewis (@_phzn)
Getting the most from running a hackathon
Slide 2
Hi, I’m Kevin (@_phzn) 🎟 👨💻 🎲
Slide 3
Kevin Lewis (@_phzn)
In the next ~20 minutes we will: Understand hackathons as an event format Some common reasons for running hackathons Cover the ‘ingredients’ in running hackathons Talk about how those ingredients should be changed in relation to the goals of the event See some common recipes I’ve found work in the past See some photos of my dog
Slide 4
Slide 5
What are hackathons?
Slide 6
Kevin Lewis (@_phzn)
Slide 7
Kevin Lewis (@_phzn)
Run of Show
Slide 8
Kevin Lewis (@_phzn)
Run of Show
Slide 9
Kevin Lewis (@_phzn)
4 - 36 Hours
Slide 10
Kevin Lewis (@_phzn)
Slide 11
Kevin Lewis (@_phzn)
Slide 12
Slide 13
The art of the challenge
Slide 14
Kevin Lewis (@_phzn)
Slide 15
Kevin Lewis (@_phzn)
Still allow creativity Framing the desired outcome
Slide 16
You need to have a goal
Slide 17
Kevin Lewis (@_phzn)
Research & Development “How can we improve the customer experience for fans coming to Wimbledon - both during and after their visit?”
Slide 18
Kevin Lewis (@_phzn)
Building Communities Communities need a cause or reason to be getting together
Slide 19
Kevin Lewis (@_phzn)
Driving Adoption Make it memorable and easy. It won’t go forgotten.
Slide 20
Kevin Lewis (@_phzn)
Gathering Feedback For pre-release or general release products
Slide 21
Kevin Lewis (@_phzn)
Recruitment Technical | Communication | Teamwork Prioritisation | Problem Solving
Slide 22
Kevin Lewis (@_phzn)
Supporting Sales Use Product Y to provide novel experiences for customers in Avanti train coaches
Slide 23
Kevin Lewis (@_phzn)
Skills Increase “Use today to try out new technologies”
Slide 24
Sometimes hackathons are not the answer
Slide 25
Kevin Lewis (@_phzn)
Have a specific scope? Just hire people for delivery.
Slide 26
Kevin Lewis (@_phzn)
Expecting deploymentready solutions? Hackathon projects are rough around the edges.
Slide 27
Kevin Lewis (@_phzn)
You want to own what is built, without paying people. If you were hoping for some positive community feels, this is not the way to do it.
Slide 28
Kevin Lewis (@_phzn)
Improve Brand Awareness Go support existing established events. Getting attendees requires audience-building.
Slide 29
Slide 30
How to run a hackathon
Slide 31
Kevin Lewis (@_phzn)
Core Ingredients Space
Date
People
Theme & Challenge
Additional Toppings Food
Content
Prizes
Follow-Up Activities
Slide 32
Slide 33
Designing hackathons for our specific goals
Slide 34
Kevin Lewis (@_phzn)
R&D
Community Building
Driving Adoption
Support Sales
Feedback
Recruitment
Skills Increase
Slide 35
Kevin Lewis (@_phzn)
Space
Date
Theme & Challenge Content
Prizes
People Food Follow-Up
Slide 36
Kevin Lewis (@_phzn)
Research & Development Actual solutions to actual business issues
Slide 37
Kevin Lewis (@_phzn)
Research & Development The right makeup of attendees Equip hackers with suitable industry knowledge through content & mentorship Keep stakeholders involved
Slide 38
Kevin Lewis (@_phzn)
Research & Development Best on weekdays Smaller attendance & space Pay people! Food if you can 🤷 Content is 🔑 to ensuring effective hackers Follow-Up Activities: Further development workshops, engaging stakeholders with ‘redux’ events
Slide 39
Kevin Lewis (@_phzn)
Building Communities Around a cause or theme
Slide 40
Kevin Lewis (@_phzn)
Building Communities Focus on the environment - small, thoughtful touches go a long way Encourage people to stay engaged after the event
Slide 41
Kevin Lewis (@_phzn)
Building Communities Weekends are best, when fewer people work The more the merrier 🎅 Food is generally expected, so say if you can’t Content should be helpful for beginners to a topic Follow-Up Activities: Online conversation spaces, more laid-back socials
Slide 42
Kevin Lewis (@_phzn)
Supporting Sales Through contextually-appropriate challenges
Slide 43
Kevin Lewis (@_phzn)
Supporting Sales Make sure hackers know the purpose of the event Make sure stakeholders from all sides are involved Include sales engineers as part of the hacking team Make sure to have a record of projects built Pay people for their time!
Slide 44
Kevin Lewis (@_phzn)
Supporting Sales Weekdays work best (for stakeholders) Try and find a venue on neutral ground Ensure the right makeup of skills, and pay people! Food: Remember this is a professional event Content: Prep hackers before the event if possible
Slide 45
Slide 46
Let’s get in the kitchen and talk recipes 👨🍳
Slide 47
Kevin Lewis (@_phzn)
Community Hackathons Application-Based Hackathons
Internal hackathons
Slide 48
Kevin Lewis (@_phzn)
Community Hackathons
Slide 49
Kevin Lewis (@_phzn)
Pros
Cons
More capacity
Harder to recruit for
Wider range of hackers
Unknown skills
More project ideas
Less complete projects
Cheaper to run
Projects aren’t yours
Can involve more
Need larger spaces
stakeholders Opportunity for great vibe
‘Hacker entitlement’
Slide 50
Kevin Lewis (@_phzn)
Application-Based Hackathons
Slide 51
Kevin Lewis (@_phzn)
Pros Everyone is working to a common goal Correct skills makeup More prepared hackers Project ideas belong to you NDAs, etc
Cons Much smaller (10-20) More expensive Without known outcomes, a harder ‘sell’ internally
Slide 52
Kevin Lewis (@_phzn)
There are so many variations
Slide 53
Kevin Lewis (@_phzn)
How did we do? Understand hackathons as an event format Some common reasons for running hackathons Cover the ‘ingredients’ in running hackathons Talk about how those ingredients should be changed in relation to the goals of the event See some common recipes I’ve found work in the past See some photos of my dog