This opinion piece was written by James Reith, formerly a content designer for DWP Digital. It also appears in our digital government newsfeed.
The UK Department for Work and Pensions hub in the city of Sheffield is a young hub. We recently hosted our first hackathon. And with all the unearned confidence of youth, I’m going to tell you how to host your own, based on our limited experience.
At the time of the hackathon, I was working as a content designer for DWP Digital. We tried to solve an issue that emerged from a real project — though one that was outside of our remit at the time. We were trying to help jobseekers identify — by themselves — what could help them find a job.
• If you want to write an opinion piece, take a look at Apolitical’s guide for contributors.
By getting talent together from across the government and digital scenes, we hoped to get a head start on something we’d inevitably be tackling. This is what we learned.
Don’t just invite digital folk
Cross-government means everyone across government. We purposefully invited work coaches, as subject matter experts. But we also invited people from policy, strategy and any other discipline that would listen.
Why? Not only do they get to see what the digital teams do, they get to do it. It makes our work less mysterious and turns them into collaborators. People often complain of the gulf between policy and digital. It was the policy people who, arguably, enjoyed the hackathon most. Events like this help to bridge the gulf between policy and digital.
Set a clear objective, with a bit of scope
What kind of hackathon is it? Are you trying to get a functioning thing or a good idea? Specific problems tend to produce specific prototypes; broader issues produce a broad variety of approaches.
Both are great. But make sure you know what you want. Narrow — but unclear — objectives lead to frustrated teams.
Plan to improvise
Hackathons may seem chaotic, but that chaos is ring-fenced. There are so many issues you won’t consider till the 11th hour. How many power sockets are there? Is this a competition or not? Do we let people choose their own teams, divide them up or assign them by role? There will always be issues you can’t plan for in advance either, so you’ll need to make sure there are some good improvisers on hand at all times.
This subheading is terrible content design (I mean, who uses “obfuscate” in everyday conversation?). But using project specific terms — or the many, department specific acronyms we love to hate so much — isn’t much better.
Your hack’s problem statement should be a sentence or two at most. In plain English. You should also get to the point, rather than forcing attendees to wade through multiple paragraphs.
If you’re going to test, provide research
We’d roped in some people from our building as mock-users, for usability testing. However, we routinely referred to this as “user research”. Some teams ended up trying to work out user needs from people who weren’t actually users, rather than testing if their ideas or prototypes were workable.
This hackathon operated as if the attendees had arrived in the midst of a project. We should have provided some concrete research (users needs, personas etc.) for the teams to build on. If you’re testing a user interface, fake users could work well. But make that clear to the attendees.
Don’t take feedback personally (unless it’s great)
At our hackathon, there were many ways attendees could leave feedback. Almost all of it was positive. Everyone had a good time. But we respected the people who told us about the areas we could improve too.
Despite the few things that went wrong, a lot went right. And in the true spirit of iterative design, the hub will be planning more hackathons and incorporating that feedback. There were even murmurs of other Sheffield departments holding them, too.
Do host your own
Show us how it’s done. But make sure you invite us, too. Hacks are a great way of bringing talent together to solve a problem. And a great excuse for pizza. — James Reith
This was originally posted on the DWP digital blog.
(Picture credit: Flickr/DWP Digital)