Guest Post: FatigueHack - Hackathon done right

This is a guest post from Jayden Castillo, a colleague of mine at Accenture and an active member of Canberra's innovation community. Read the original post at LinkedIn:

I recently attended the Australian Trucking Association (ATA)'s Hackathon aiming to target driver fatigue, aptly named 'FatigueHack'. I'm fairly new to Hackathons, this was my second after the AUSTRAC Codeathon in March (where I was a mentor), and my first experience as a participant along side two of my Accenture team mates.

For those unfamiliar with the concept, a Hackathon is a rapid solution environment where competitors are required to address complex challenges in a short amount of time, and come up with a working prototype to illustrate their concept. In this case, teams had 2 days to develop a viable business model which is capable of addressing fatigue in the trucking industry. Following these two days, each of the 8 participating teams had to pitch their solutions to judges and the top 3 pitched to the entire Australian Trucking Association Annual Conference delegation.

I find hackathons to be a fantastic opportunity to show what's possible, and even more impressive, what's possible in just two days. There were a few aspects of FatigueHack in particular which I believe made it exceptional, and demonstrates not only what is possible, but what innovation and solutioning will be like in The New. The 3 points below are the perfect recipe for innovation, which we must all embrace to stay at the cutting edge.

Short Timelines
We all have a tendency to procrastinate, to plan things excessively, and to over analyse. This is a product of the anti-failure mindset we've been groomed for, we naturally try to think out the whole solution and resolve any issues before we actually start doing. Being under quite a strict time limit means there simply isn't enough time for this. You are forced to make decisions and move things along quickly. This means you might not have all the problems solved straight away, but it also means there's less time between idea and the all important testing of your idea, so you can identify and resolve issues much faster.

Probably the most interesting part here was to demonstrate how unnecessary it is to give long timelines to (particularly innovative) projects. When your timeline is short, you cut out what's not important and make big strides in your solution.

Concentrated ideation
They say that innovation happens when ideas collide, and FatigueHack certainly had a lot of colliding ideas. Think and Grow Rich author Napoleon Hill describes this like brainwaves being radiated out into the ether, and being picked up on by other brains on the same wavelength. While this description might a bit unscientific, I believe there is a lot to be said for the buzz created when a lot of excited people are in close proximity. Your confidence goes up, your creativity goes up, and you are generally more open to thoughts and ideas.

Having run remote meetings and workshop sessions in the past, I can definitely attest to the value of having everyone in the same room, even if they're not all working on the same idea. Body language, excitement, drawing, gestures are all things which (still) don't translate well over digital media.

Easy access to expertise
Innovating or designing in a bubble is a dangerous thing to do. It is basically impossible to know if you're on the right track without some kind of feedback, so it becomes really easy to go down the wrong path and either solve the wrong problem or create a solution which nobody wants. I think FatigueHack managed this really well - they ran the Hackathon in the same venue at the same time as the ATA's annual conference. This was invaluable, because it meant if we had any questions at all, we could find an expert on the area within 5 minutes by simply asking around.

Having such easy access to expertise makes innovating much easier. It allows you to validate ideas very quickly, and when we were listening to the truckers talking about their experience it stimulated new ideas quickly. Our ability to iterate and refine was exponentially higher than in a normal workplace, and ideas were changing and evolving in time frames of minutes. I would love to see this translate to my (and everyone's) daily work, because the potential for generating great solutions is enormous.

Closing thoughts
This Hackathon really demonstrated to me what the future of work looks like. By getting a team together in a highly concentrated, intense environment, and providing more information and experts than we could possibly digest in 2 days, there were some fantastic outcomes (the winning idea is moving forward with creating a business!).

My personal mission is to help businesses and organisations think and act like startups, and FatigueHack is a great example of how to do that.