I’ve been following the passage of GDPR from ideas to law over the last couple of years, and I’m convinced its effects will be far reaching, and extremely disruptive to the industry I work in, but also any industry that collects and processes data around customers.
I started chatting with a friend Maik, and we’re now testing to see if there’s interest in an event around it, that we’re calling OMGDPR.
Okay, what is OMGDPR?
OMGDPR is the working title for an community-run, open space event, in Berlin in late March/early April for practitioners who build digital products or services, to learn from each other about GDPR will affect their organisation, and by extension, how they work.
I’m going to cheat here and use wikipedia’s summary of the changes to the law:
“The proposed new EU data protection regime extends the scope of the EU data protection law to all foreign companies processing data of EU residents. It provides for a harmonisation of the data protection regulations throughout the EU, thereby making it easier for non-European companies to comply with these regulations; however, this comes at the cost of a strict data protection compliance regime with severe penalties of up to 4% of worldwide turnover.”
The GDPR also brings a new set of “digital rights” for EU citizens in an age when the economic value of personal data is increasing in the digital economy.
The changes to the law arrived in late May, and they affect every company in the EU, but loads of companies, particularly smaller ones aren’t really prepared for it yet.
There’s also lots of FUD (Fear, uncertainty and doubt) around, so our intention was to create a space to let people talk about it in a relatively welcoming, safe, informal environment so they can see what they need to do if they haven’t had the time to think through a response to it.
Likewise, we’re hoping there will be a chance to learn from others who have had a chance to look into it, and would like to see more organisations treat personal data with the respect it deserves.
Okay, how do I find out more?
The easiest thing to do is try filling out the form below that we’re using to gauge interest – we’re aiming to run the event along open space principles, where people:
bring the topics they’d like to discuss
autonomously form into groups to discuss the topics that they are interested in
report back what they learn for the rest of the group to reflect on or capture
leave the event, with a clearer idea about what they might do
Earlier in August I wrote a post about the BPB, a German institute focussed on promoting democracy, and WhoTargetsMe, a project to bring more transparency to election campaign advertising on Facebook. After sharing the post online, I had a few people contact me about forming a group to work at an Democracy is Everything, a hackathon at Factory Berlin, in Mitte in Berlin.
Here’s how we got on, and some notes for other people thinking extending a project at a hackday like this in future…
I’ve been going to hackdays and hackathons since 2007, (although to be fair, much less frequently after I entered my thirties, five years ago…), and the format has usually been something along the lines of:
think up a project, usually at the hackday, or maybe a little bit before it starts
meet people, see who you can imagine building something with
work out who is supposed to be doing what
realise how little of what you’ve doing will fit into the time available and update plan
build much less than you thought, and think how to present it
curse self at missing key points in in the minute or two you have to present it
This one was different a in few interesting ways:
Wait, I need to apply?
While I’ve seen a few events where you pay to go to an event like this (which I think is at best pretty cheeky if you have sponsors), this is the first event I’ve been to where you needed to apply to go, and have an idea beforehand.
While this makes an event less approachable for individuals and takes the focus away from meeting new people, it had some interesting effects. It forced me think more about what could be done in the time available, and what the ideal makeup of a team to do this might be, in a way I haven’t had to before.
Extending a existing project
This is also the first time I’ve worked on an extending an existing project, rather than try to come up with a new one, and also one where I hadn’t ever met the most visible project author.
This added another new dynamic: whatever you think you can do in the time available, you need to have some idea of how useful it would be to the maintainers of the project if you want it to last beyond the hackday. I’ll touch on this later.
What we did
If you’re not familiar with whotargets.me, it’s a browser extension that counts the political ads in your Facebook feed, and based on this information, gives you some charts and analysis about how different political parties target you to for your vote during an election. By using it, you help build a dataset of how political parties are using the Facebook platform to advertise voters. This dataset can then be used to help inform public discourse, and eventually policy.
Here’s how the site looked before the hackday:
This wasn’t immediately obvious when you first visited the page though – you were prompted to download a browser extension without understanding what it was really going to do. Germany is known for different attitudes to personal data to the UK, and this seemed a big turn off to a number of Germans we showed it to, so we had a couple of main goals for the hackday:
Make it work in Germany
Make it clearer what it does
I’ll explore these in more detail below:
Making it work in Germany
WhoTargetsMe originally comes from the UK, which has a much more centralised tradition of campaigning than Germany – a nice example of this is the story where a conservative campaigner told me how Tory MPs are essentially barred from even retweeting without central HQ’s permission. I think this is also an artefact of how election financing in the UK places hard limits on online spending in local campaigning, but in in 2016 at least, doesn’t really have limits on national campaigns.
This centralisation is different to Germany, partly because Germany is split into a series of Länder (it’s not totally accurate, but it can help to think of them as states), but also because there are comparatively more parties and decentralised campaigning as a result. Fortunately for us though, in Germany online campaigning with Facebook is less established, so it’s not unreasonable to think that campaigning will start out similarly centralised at first, because that’s where the expertise and budget to run a campaign might be in the main parties.
In the long run through, it’s likely that as campaigning digitally becomes more commonplace, you’d have many, many more advertisers to keep track of – I know in Kreuzberg/Friedrichshain where I live, at least one party in this area is already experimenting with Facebook ads like this. To this end, we did a fair amount of research in the group for this, and found a load of useful datasets to help with matching ads to politicians and parties, but we didn’t pursue this further during the weekend event for time reasons.
I’ll explore this in a future post, which I’ll link to when it’s online, as I think it has an impact on projects like this in the long run.
Making it clearer what it does
If you look at the whotargets.me front page for Germany or for the UK, you’ll see more info on what the whotargets.me browser extension is, and what it does – I’ve taken a screenshot below (the actual wording from the hackday has been tweaked a bit, but the general idea is the same):
Getting a different point of view
The screenshot above is clearly a different style to the previous look for the site with the black and white photo of the Reichstag (the German equivalent to the House of Parliament). In using illustrations like this instead, we were trying to capture some of the mood of democracy being a messy process driven by ultimately by people, rather than faceless institutions, and make the project feel more approachable than before.
These are largely thanks to the illustrator on our team, Judith Carnaby, who was introduced to me by Alice Rose, who helped tidy up the copy and some of the React code in the plugin itself. The two of them being much more comfortable in German than me, and us having a native German speaker in Katarina Rasch really helped here.
Explaining how the data is used
In Germany, people tend to be a bit more wary about how data that might identify them is used than the UK – it’s not clear how it’s used, they often will flat out refuse to use a service. So, we also ended up writing some more about how it works once we had a chance to speak to Louis Knight-Webb (one of the co-founders of the project) over slack at the hackday.
There’s few more details being finalised, but that this info should be available on the main site soon, with some helpful diagrams – in the meantime, this should be visible in tweaks to copy throughout the app that should make it clearer what is happening with adverts, and what data is used in them.
If you want to extend a project at a hackday like this in future
First of all, it is possible, and all in all, I feel it worked out pretty well – I’d totally do this again, rather than try to re-invent the wheel. There’s a few things worth bearing in mind though.
Access to at least one member of the original team is important
I had about 3 hours of skype calls with Louis before starting the hackday to understand the existing project, and we spent quite some time talking about was realistic to attempt in the time we had. We cut back a lot of scope in these calls, and without them I’m pretty sure we’d have wasted a lot of time trying things that we’d realise only later weren’t feasible.
During the hackday itself, we had a slack channel open which Louis was in, which also helped massively – at one point on the Friday night, we realised were going in pretty different directions to the rest of the how the project was communicated, and catching it comparatively early saved some awkward moments the following day.
Louis made himself very available, but if I was doing this again, I’d probably sort out some pre-agreed time slots to answer questions, as being on call over a weekend might not be everyone’s idea of fun…
Typical hackday style rules about pitching change
If you’ve been to any hackday style event, it’s common to see “Pitch-Driven Development”, where you might start with a what you aim to present, then work backwards, only building the bits that will be in a presentation. Doing this in theory saves time spend on login systems, proper backends, and so on, in favour of visible features, that increase the chances of your presentation impressing judges and winning. The implication here is that if you don’t win, your effort was more or less wasted, and it has no life beyond the hackday.
In our case, we had a real working product that we were trying to adapt to a new region, so even if we didn’t catch the eye of the judges, it would still need to be useful, so this didn’t apply in the same way.
At the same time, part of the value of events like this is the coverage for a project if your team DOES win, and the doors it opens to help meet people who can help the project later. So, if you make it all about your contribution to a project than the project itself, you run the risk of everyone you present it to missing the bigger picture.
Finally, there’s the ethical aspect – misrepresenting what you actually achieved during an event when there’s at least some expectation of it being a fair competition isn’t cool, and will almost definitely come back to bite you.
Videos over presentations in future?
Quite late in the day, we realised that the visible changes to the site may not be all that easy to show during the ridiculously short two minute window we had for presenting, so we ended up with some frantic last minute changes to what we showed off.
If we were to do this again, and if we were confident we could show a video, I’d probably rely on putting together a video of what we had made for our two minute slot, rather than put together a short lived presentation for the judges. If we did this, we’d be able to make more use of it after as support material in blogposts too.
Worth a spending a weekend
In the end, I’m pretty happy with what we got together during the Friday and Saturday we had, and it was a lovely surprise to come third place.
Big thanks to Alice, Judith, Kat, Nick, Louis, Brian, and the rest of the whoTargets.me team 👍🏽
How you can find out more about Who Targets Me
If you’re in Germany and you’ve read this, I think you should visit whotargets.me, and try installing it on your browser to help us build a decent dataset to add some transparency to how political ads are used in elections.
If you’re in Berlin and want to chat to one of us, I live in Berlin, but Louis is in town all of this month, and probably the best person to speak to about the project – he’s @LouisKnightWebb on twitter.
I’ve been running events and meetups since around 2010, but I haven’t come across the ‘Pacman rule’ before, as blogged by Eric Holscher.
It’s a simple rule to follow, to make it easier for new people to join groups, and generally help make events feel nicer for first timers:
The rule is quite simply stated:
When standing as a group of people, always leave room for 1 person to join your group.
More memorably, stand like Pac-Man!
The new person, who has been given permission to join your group, will gather up the courage, and join you! Another important point, the group should now readjust to leave another space for a new person.
Leaving room for new people when standing in a group is a physical way to show an inclusive and welcoming environment. It reduces the feeling of there being cliques, and allows people to integrate themselves into the community.
So simple, and easy to try out – I think I’ll give it a go at the next event I’m organising.