The Hackathon: An MIT Tradition

It’s 3AM at the MIT Media Lab and my team and I begin to show signs of mental and physical fatigue. We are in the middle of a 24-hour hackathon, developing an idea in response to a prompt from high-fidelity speaker company, SONOS, concerning the ultimate in-home audio experience. In 13 hours we will present a 3-minute pitch to a panel of judges.

Prior to today’s event, I had a rather elusive understanding of what a hackathon entailed. As I walked from the comfort of my apartment to the Media Lab earlier in the day, I began to second-guess my decision. I had this deep-rooted feeling that I had made a terrible mistake. Had I missed a set of qualifications on the application and unknowingly misrepresented my skills? I sat down on a bench and weighed the possibility of embarrassment, resolving to continue on.

After a short hiatus to sleep, the team regroups at 8AM. Caffeine slowly aligns our creative differences into productive activity and we fall into an audible rhythm. We’re a diverse team of seven, heralding from MIT, Berkeley and Emerson, with a range of unique backgrounds.

As we turn to the development of our presentation, we build our pitch deck prior to our pitch, which turns out to be a great lesson in how not to build a pitch deck. The discontinuity puts stress on both deliverables and the friction begins to surface.

“Please don’t touch my screen!” I snap in momentary frustration.

We practice our pitch with a handful of event mentors, to a mixed response. One mentor is visibly confused by our value proposition. After a lengthy clarifying discussion, he remarks while departing, “Sorry if that wasn’t at all helpful and you guys are more lost than when I came over here.” The teammate tasked with delivering the pitch on stage shows signs of mental duress and tells me he’s changed his mind. Our team begins to unravel in the final hour.

Unraveling turns out to be a great opportunity for renewed perspective. After concluding that the