Who are your users and how do you know what they need?
|Who are your users and how do you know what they need?|
|Presenter(s)||Bernard Tyers, (maybe Belén Barros Pena)|
|Title(s)||User researchers and interaction designers|
|Social media||@bernardtyers , @belenpena|
|2017 theme||Communication & Design|
The Nielsen Norman Group says UX without user research is not UX. 
However, user research with the Internet Freedom Community can be challenging - privacy concerns, language /cultural barriers, distance between developers and users, budget.
For the past year I have been interviewing a small number developer members of software project used in the Internet Freedom Community, to find out how well they know what their users need from their software, how and why they use it.
My main questions to developers are - Who are your users and how do you know what they need?
The findings so far are interesting - ranging from developers knowing nothing about their users to having regular contact with them, developers making assumptions about what they need to actively seeking feature requests.
OBJECTIVE The objective of this workshop is to gather developers, UX designers and researchers, and users and *together* identify ways projects could learn about their users needs in certain scenarios, all in a privacy maintaining way.
FORMAT The attendees would break up into teams. They would then discuss scenarios relevant to them, or they could work on suggested scenarios.
If developers and users were both present a discussion could be had about what methods of user research they would be comfortable with - for example, filling out a survey, allowing the developer to know what language they used the software in, etc.
If there were more UX people present, the discussion could be about common methods for user research.
Each team would be asked to address a particular scenario and suggest ways to carry out user research.
DELIVERABLE The outcome would be various privacy maintaining ways in which the project could learn about user needs. A blogpost or some written output would then be published.
|Target Groups||Journalists, Software Developers, Security Trainers, Designers, Usability, Communications Professionals, Front Line Activists|
|Language||English (and maybe Spanish)|
The outcome would be various privacy maintaining ways in which the project could learn about user needs. A blogpost or some written output would then be published.
Possibly a blogpost, and other shareables.
If you're interested in taking part, let me know - get in touch via www.ei8fdb.org/thoughts/contact or twitter
If you have particular things you'd like to cover, let me know.