Hackathons: Don't try them if you don't like risks

Rules and tools to get the most out of your pizza-replete staff

When organisations grind to a halt, weighed down by their own bureaucracy, inertia and politics, they flail about for something to give a short, sharp shock to their vitals. Something to get them moving again.

The techniques used to get things humming along again have varied over the years – a rogue’s gallery of specious business trends and fads. Twenty years ago, it might have been role playing. Ten years ago, an offsite with those cringeworthy trust-building games.

Today, we turn to hackathons.

Until quite recently, hackathons were the exclusive preserve of the tech startup community, thriving on the 48-hours-locked-in-a-room-together intensity followed by the near-orgasmic release of a great pitch. Suddenly, both big business and big government, in a collective penny-drop moment, have adopted the hackathon methodology to inspire employees and capture innovative ideas.

That should be making us suspicious. The purpose of a hackathon is to create a space so unconstrained by conventional wisdom as to be truly disruptive. Owing nothing to anyone, participants can be free to ‘think different’.

That’s the theory, anyway – but I doubt anything would be more terrifying to a big organisation. As much as we might hate bureaucracy, it’s a great way to herd cats, and bureaucracies rein in the natural tendency of any group of humans to go feral. Throw that away, and the organisation risks disintegration.

Big bureaucracies – whether corporate or government – are at odds with hackathons, so they try to have it both ways: they stack the deck of the hackathon, then complain if they don't get the promised results.

It might be helpful to highlight some of things that should be kept in mind to make a hackathon successful.

One: You can establish the questions – but not the answers

The most common defensive strategy in any hackathon is an attempt to control outcomes. That’s often done by framing the questions so narrowly only one answer is possible, or by limiting the terms of discussion, or limiting the range of proposed solutions.

These constraints may be real, and may be presented in good conscience – to ‘help’ hackathoners to a solution – but they hamstring participants’ capacities to develop unexpected solutions to the usual problems.

Two: Conflict resolution skills are key

One recent hackathon saw one team split by an irreconcilable impasse. Half the group wanted to go in one direction, half in another – but they were only given one pitch. Their solution? Clumsily glue the two pitches together, doing a disservice to both.

While conflict is an important part of creativity – and hackathons – participants have to understand that the ability to resolve those conflicts is at the heart of the hackathon. When squaring the circle, out-of-the-box insights are most likely to happen.

Taking your toys and going home just won’t cut it.

Three: Meta-moderation

Every hackathon needs a meta-moderator whose sole purpose is to keep each team of hackathoners moving smoothly toward their goal. Meta-moderators check in regularly with each team, observing group dynamics, and stepping in with tweaks as needed, using their own conflict resolution skills to keep the teams coherent, focused, and productive – while passing those skills along to the team.

If needed, meta-moderators identify intransigent team members – who won’t play fair or won’t play at all – and blast them out of the way. They’re the ultimate arbiters, and use their powers to help each team achieve the best possible outcome.

Four: Expect mixed results

Hackathons will never produce uniformly excellent results. The mixture of personalities and ideas and organisation is too variable to provide any guarantee of success. Instead, every hackathon will likely produce a few standouts, a few good efforts, and a few disappointments. That’s as it should be: even the most disappointing pitches will teach you something you didn’t know before.

Five: Don’t expect anything to stick

Throwing a group of individuals into a crucible may produce an excellent pitch, but everything after that is left to the organisation supporting those individuals.

The team may be energised and ready to implement their pitch, but if the organisation isn’t ready – because the pitch is too weird, dangerous, or disruptive – it will be ignored and eventually forgotten. And if the winning pitch doesn’t see the light of day, why even bother with a hackathon?

Finally, if you find yourself at a hackathon – and you probably will, before long – remember that it’s not a contest, even though they may crown a ‘winner’. A hackathon is about finding the right mix of creativity and teamwork. Neither is easy. Together, they can generate a spark that will wake the dead. ®

Other stories you might like

  • These Rapoo webcams won't blow your mind, but they also won't break the bank

    And they're almost certainly better than a laptop jowel-cam

    Review It has been a long 20 months since Lockdown 1.0, and despite the best efforts of Google and Zoom et al to filter out the worst effects of built-in laptop webcams, a replacement might be in order for the long haul ahead.

    With this in mind, El Reg's intrepid reviews desk looked at a pair of inexpensive Rapoo webcams in search for an alternative to the horror of our Dell XPS nose-cam.

    Rapoo sent us its higher-end XW2K, a 2K 30fps device and, at the other end of the scale, the 720p XW170. Neither will break the bank, coming in at around £40 and £25 respectively from online retailers, but do include some handy features, such as autofocus and a noise cancelling microphone.

    Continue reading
  • It's one thing to have the world in your hands – what are you going to do with it?

    Google won the patent battle against ART+COM, but we were left with little more than a toy

    Column I used to think technology could change the world. Google's vision is different: it just wants you to sort of play with the world. That's fun, but it's not as powerful as it could be.

    Despite the fact that it often gives me a stomach-churning sense of motion sickness, I've been spending quite a bit of time lately fully immersed in Google Earth VR. Pop down inside a major city centre – Sydney, San Francisco or London – and the intense data-gathering work performed by Google's global fleet of scanning vehicles shows up in eye-popping detail.

    Buildings are rendered photorealistically, using the mathematics of photogrammetry to extrude three-dimensional solids from multiple two-dimensional images. Trees resolve across successive passes from childlike lollipops into complex textured forms. Yet what should feel absolutely real seems exactly the opposite – leaving me cold, as though I've stumbled onto a global-scale miniature train set, built by someone with too much time on their hands. What good is it, really?

    Continue reading
  • Why Cloud First should not have to mean Cloud Everywhere

    HPE urges 'consciously hybrid' strategy for UK public sector

    Sponsored In 2013, the UK government heralded Cloud First, a ground-breaking strategy to drive cloud adoption across the public sector. Eight years on, and much of UK public sector IT still runs on-premises - and all too often - on obsolete technologies.

    Today the government‘s message boils down to “cloud first, if you can” - perhaps in recognition that modernising complex legacy systems is hard. But in the private sector today, enterprises are typically mixing and matching cloud and on-premises infrastructure, according to the best business fit for their needs.

    The UK government should also adopt a “consciously hybrid” approach, according to HPE, The global technology company is calling for the entire IT industry to step up so that the public sector can modernise where needed and keep up with innovation: “We’re calling for a collective IT industry response to the problem,” says Russell MacDonald, HPE strategic advisor to the public sector.

    Continue reading

Biting the hand that feeds IT © 1998–2021