Anticipating GDPR in Smart Homes Through Fictional Conversational Objects
•Download as PPTX, PDF•
2 likes•961 views
Slide deck used to present a paper at the Mydata 2017 Conference which discusses how Smart Homes are being defined by Voice User Interfaces. Critiquing Human Centered Design in order to advocate for a Constellation-Focussed approach (based in Object Oriented Ontology) the work concludes with a design fiction piece demonstrating how designers may approach creating GDPR compliant Voice User Interfaces.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Anticipating GDPR in Smart Homes Through Fictional Conversational Objects
Similar to Anticipating GDPR in Smart Homes Through Fictional Conversational Objects (20)
Recently uploaded
Recently uploaded (20)
Anticipating GDPR in Smart Homes Through Fictional Conversational Objects
- 1. Anticipating GDPR in Smart Homes Through Fictional Conversational Objects Joseph Lindley Paul Coulton Bran Knowles Haider Ali Akmal
- 2. Aims - Design an interface for adding IoT devices to a home network - The interface should be based around a voice user interface (VUI) - It should be GDPR compliant - It should adhere to the spirit of GDPR and not use technical workarounds
- 6. Good Information (software) Appliances
- 9. Object Oriented Ontology Image credit: Peter Heft, http://www.petersaysstuff.com/2014/11/john-looocke-an-object-oriented-ontological-critique-of-lockean-property-acquisition/
- 10. Metaphorical Constellations “ideas are to objects as constellations are to stars”
- 12. Constellation focused VUI Information Appliances
- 13. Voice can be cumbersome
- 14. Why? Because not all senses are equal
- 15. Scope is wide; consent for what?
- 16. Compromise! Graph of ‘identifiability’
- 17. ’Orbit’ Privacy App Prototypes
- 18. Pros: - Allows atemporal consent - Constellation based design - Avoids simplicity pitfalls - More informed consent - Integration with smart homes, VUIs, and IAs Cons: - To configure app requires large amount of data or manual research - Driving motivation - Challenge including additional dimensions of privacy? Which to use?
Editor's Notes
- LU Imagination – design lab PETRAS – UK-wide Internet of Things Hub, across 9 Unis In the presentation I’m going to try and explain this app and talk through the theory and thinking behind why we made it
- Lots of ideas… these are some of them: Voice user interfaces – things like amazon echo and google home Information appliances, specialised electronic devices (as opposed to general purpose computers) IoT as constellations…. A comparison between the stars in the sky and the internet Object Oriented Ontology…. Part of a contemporary philosophical movement moving away from anthropocentrism Human Centered Design… .. And all of this works towards a design fiction prototype… Feel free to stop me if anything isnt clear as I’m going along. The paper also has several caveats and assumptions, I’ll tell you those as we go along too.
- Caveat 1: we are dealing with technology in homes, personal devices.. Within that context though… Although voice activation has been around for a long time, it is really taking off in a big way Amazon are leading this widespread adoption Google rolling out its assistant software suddenly puts 2bn voice agents in users pockets Nobody can be certain though… futurist Bruce Sterling says “They’re kind of the new smart refrigerator. Where you used to have a webpage unnecessarily attached to everything, you’re gonna have one of these taking donkeys unnecessary attached to everything” Tufty, the road safety squirrel just for fun… but also maybe we will need public service announcement films for voice agents?
- This terminology, originating in the 70s Never really caught on It was meant to describe a move away from general purpose PCs towards Simple, vertasile, pleasurable devices Supposed to be easy to just pick up and use Built around a single application Part of the vision was that platforms, devices, and services would combine…. The newton is, perhaps, an archetypal bad one…. Expensive, unreliable, and not doing much that either a pen and paper or a laptop wouldn’t do better. But today’s IoT is bringing a whole host of awful devices… juicero
- The place they HAVE quietly happened is in smartphone apps Although S/w not hardware They fit the bill Instagram is pleasurable, simple, versatile -The point we are getting at, and where this links in with voice user interfaces is this: Information appliances have never worked, except for now on smartphone apps For that to truly work… they needed a medium, a ‘holding device’ That was the smartphone Our hypothesis is that voice interfaces, things like Amazon Echo, will become that conduit for IoT in the home…. The many disparate devices just don’t make sense unless there is some unified way to access them We’ll return to that, but first, some more theoretic discussion
- HCD… collectinon of techniques And is demonstrably great at getting the interface right Doing what people want, being easy, usable
- sheild
- Metaphysics.. Hard Explain basic idea. For us.. It’s about inspiring the start of a design process Whilst OOO remains the theory that underpins the way we’ve been looking this… we have layered a slightly more accessible idea on top… constellations
- This is a quote from Walter Benjamin… and he seems to playfully use the idea of constellations to explain how simple entities become more complex assemblages Geometric positioning of stars on earth (depending where you stand they appear differently)…. Cultural meanings developing…. Obscurred ones like north star from the south
- With such a flexible metaphor there is not set view on what is or is not a constellation But.. In this example we have….. The circles represent isolated constellations… so, for example… the user, the lights and the fridge may not be exposed to the business models and algorithms of the platforms that run them That is most of the concepts explained… but, crucially, what’s the point? What do we do with all of this?
- Again this backdrop we wanted to design a way of using VUIs to support IoT information appliances We would use the IoT as constellations design metaphor to make sure that the device’s data footprint was not against the ideals of HCD Also the device would need to be GDPR compliant.. Ensuring that users know what it is they’re agreeing to, and to have the various GDPR-protected rights accounted for In order to do this we use a technique called design fiction, which allows us to think through all of the details of how this would work We also ran a series of workshops to help inform the design
- Sadly, the first thing we found out, was that voice was a terrible way to do this! The kettle is another fictional product we designed and the text next to it is the privacy agreement/consent procedure Such a long body of text is too hard to follow.. And what would protect a user from walking off in the middle then coming back and simply saying yes? This needs to be an interaction or conversation, of sorts.
- Visuals have higher bandwidth So.. Even though our design brief was about voice, we in fact returned to visuals.. But made sure that it would fit with the model of voice interfaces enabling Information Appliances
- We also encountered a problem relating to what our bold aims were. Redesigning the consent process includes a vast array of different types of ‘thing’… How do we know what data is collected, where it goes, and what it is for In the workshops we tried to ‘map’ possible flows, but found they always became too complicated too quickly Even with the increased bandwidth of the visual sense, this wasn’t working. (we also found that engineers thought it would be easier to simply redesign the backend systems so that data was encrypted or pseudonymised.. Therefore evading most of the personal protections of GDPR)
- So… we drastically reduced our aims, and elected to focus only on ‘identifiability’ This was somewhat arbitrary, but served as a good starting point Next, through design iteractions around the idea of map, we arrived at these blobs. Explain
- We built them into an app.. Where features associated with this particular application were enabled/disabled depending on what setting the user selected