1 / 25

Understanding User Behaviour and Designing for Privacy

Understanding User Behaviour and Designing for Privacy. Thomas Hughes-Roberts. Contents. A look at privacy and the related problem A review of experiments conducted to understand the problem Some recommended design considerations based on the results. . The Privacy Problem.

kiley
Download Presentation

Understanding User Behaviour and Designing for Privacy

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Understanding User Behaviour and Designing for Privacy Thomas Hughes-Roberts

  2. Contents • A look at privacy and the related problem • A review of experiments conducted to understand the problem • Some recommended design considerations based on the results.

  3. The Privacy Problem • The concept of Privacy is complex with no formal definition. • Legally – “The right to be left alone”. • How does this work with technology? • Complex social construct – sensitivity of pieces of information variable.

  4. Examples…

  5. Another…

  6. One more…

  7. So what is the problem? • Easy to think that a choice has been made. • Privacy is important – Not just about secrets, but also representation.

  8. The Privacy Paradox • Reported concern – Several pieces of research identify high levels of concern. • People say they behave differently to what we are seeing. • Is something lost in the transition to a technical platform? • If behaviour is a reaction, then what is influencing the disconnect?

  9. Persuasive Technology • Is the system designed to persuade people to disclose more? • Or just to make it easier to do? • Is the User Interface a cause of the disconnect we have observed?

  10. Driving Definition

  11. Social Psychology • The Theory of Planned Behaviour • Developed by IcekAjzen in 1991, it describes the salient information which influences and informs behaviour. • Used as the basis for a series of experiments aimed at examining the influence of the User Interface.

  12. The Model

  13. Experiments • A mock social network, sign-up process. • A range of questions varying in sensitivity. • A control group • Three treatments based on the three influencing factors within the theory of planned behaviour. • How much will people disclose across groups? • How much will subjects protect?

  14. Control Group

  15. Personal Attitude • Our knowledge of behavioural consequences and what we think about them

  16. Subjective Norms • The extent to which the opinions of others influence our behaviour.

  17. Perceived Control • The perception of how easy a behaviour is to perform and how accurate that perception is.

  18. Results • All groups containing a treatment disclosed significantly less information compared to the control • Only perceived control protected significantly more. • Subjective norms actually protected less (although, not significantly).

  19. Why? • There are several theories (or observations) within HCI which apply. • Significant behaviour did not necessarily occur due to the point of the treatments. • E.g. sporadic disclosure

  20. Goal-Driven • HCI suggests that users are incredibly goal driven during technical use. • Happy to complete and pay little mind to sub-tasks of a greater goal. • The ATM problem. • Disclosure would seem to be seen as necessary in order to “Sign-up”.

  21. Clear Options • The salient features made clear that users did not have to fill in all form elements. • Disclosure took place where it was easy to fill in the forms interactions. • E.g. address was long and time consuming – avoided. • Have you lied on a CV was an easy checkbox – disclosed.

  22. Efficacy • A users confidence in their ability to use a system. • SN group potentially reduced self-efficacy. • Complex and confusing pop-ups. • Mistake for error messages?

  23. Persuasive Technology? • A concern that too much has an adverse effect. • E.g. the Perceived control group – goal change? • Detracts from system use?

  24. Design Principles. • Privacy must be made a goal of the interaction without detracting from goal of the system. • UI must facilitate confident behaviour that is reflective of user needs. • Where appropriate optional interactions should be made clear. • Such changes should not increase the complexity of the system.

  25. Thank You Questions?

More Related